It seems like you are using an ad blocker. To enhance your experience and support our website, please consider:

  1. Signing in to disable ads on our site.
  2. Sign up if you don't have an account yet.
  3. Or, disable your ad blocker by doing this:
    • Click on the ad blocker icon in your browser's toolbar.
    • Select "Pause on this site" or a similar option for lancecourse.com.

How our behavior impacts projects

zooboole

Published By zooboole

How many times you've said to yourself "we cannot implement this or that feature"?. Or "there is no need to use this or that" or asked yourself if it was possible to achieve a project or part of it?

At a given point our limitations or/and our skills influence how we handle projects. It's always a present phenomenon that is, in most cases, neglected and mistaken.

Developers and designers will tend to only approve or support ideas that they know they can handle. The project manager will push the team to their nightmare zones. Then the project owner might go further or fold to a little possibility because he/she has no idea that those things can be achieved or even exist.

Knowing a technology means also knowing its limitations, you will tend to instinctively avoid or reject to implement certain ideas or solutions. It happens naturally. Sometimes it interprets as a self-satisfactory stage. You just feel it as in I think it's OK. Yes, I know we should avoid falling into the loop of perfection. But it's crucial for advancement. from time to time we must ask ourselves if that's the only limit.

So, someone with fewer skills in tech would be pushed to think of only expected results without thinking of the pain poured on the technicians. They would see it as I just want it like this and that. Not knowing how things are done gives them the courage and peace of mind to express themselves to the extreme. Hence, they will usually have that feeling of dissatisfaction. Or, the fact that they have less knowledge about it will turn them speechless. That leaves room for the technicians to suggest to them what can be done or not. And that could have an opposite impact which is to do what the technicians see and not what the project owner sees.

In all cases, these behaviors affect how we undertake projects. My goal in this post is to call your attention to such psycho-antagonism in teams. Get the habit to check where you and others stand. Then throw the pride and shame away to admit to what is necessary and viable for the project's success.