I learnt the following from one of my former managers whose style I didn't agree with, which reminds me of something that my father used to always tell me: "You can learn from anyone. Learn to avoid the incorrect from those who fail, and learn to do the correct from those who succeed."
My manager used to avoid looking into details, despite having the opportunity to optimize there. The assurance that things are working correctly and efficiently is in the details. To do the job right, and to be able to make correct decisions, one must be informed about the details of how the things they want to make right works. The more detailed relevant information one has, the better the decisions they are able to make, and the more opportunity they have to enhance things.
Avoiding communicating details hindered the team's progress because of arbitrary decisions that are not technically optimal and at times just incorrect. If one doesn't want to look into the details, then they should not make decisions. Not only should they consult those who are familiar with the execution details when they want to make decisions, but they should also delegate the whole decision making process to them at times since they are the best suited for this.
Having said that, this means that decision makers should also know in details the capabilities of their team and know how they work and how their decisions affect their efficiency. And keep a healthy communication channel to facilitate the exchange of information and use that channel eagerly to ensure that relevant information is communicated and done so early on.
How can you make technical decisions if you don't know what an API looks like and how it is used?
How can you fix something if you don't know how it works and be familiar with its components and their interactions?
But details are not a burden that gives someone a headache. Details are beautiful because without them the things you are dealing with would not exist. Details make the things that we see and interact with every day. There are details in everything, and if you have the curiosity and learning about things stimulates you, then details will not be a burden but an interesting, enjoyable, and beautiful thing to deal with.
Of course details must be relevant and not overwhelming, otherwise they might distract you from your primary goals. This is where delegation comes in handy. But delegation does not mean to throw work at your subordinates and go sleep. Managers have to closely follow up with the purpose to assist and not just blame and hold accountable their employees. Anything motivated by laziness or lack of concern backfires.
My manager used to avoid looking into details, despite having the opportunity to optimize there. The assurance that things are working correctly and efficiently is in the details. To do the job right, and to be able to make correct decisions, one must be informed about the details of how the things they want to make right works. The more detailed relevant information one has, the better the decisions they are able to make, and the more opportunity they have to enhance things.
Avoiding communicating details hindered the team's progress because of arbitrary decisions that are not technically optimal and at times just incorrect. If one doesn't want to look into the details, then they should not make decisions. Not only should they consult those who are familiar with the execution details when they want to make decisions, but they should also delegate the whole decision making process to them at times since they are the best suited for this.
Having said that, this means that decision makers should also know in details the capabilities of their team and know how they work and how their decisions affect their efficiency. And keep a healthy communication channel to facilitate the exchange of information and use that channel eagerly to ensure that relevant information is communicated and done so early on.
How can you make technical decisions if you don't know what an API looks like and how it is used?
How can you fix something if you don't know how it works and be familiar with its components and their interactions?
But details are not a burden that gives someone a headache. Details are beautiful because without them the things you are dealing with would not exist. Details make the things that we see and interact with every day. There are details in everything, and if you have the curiosity and learning about things stimulates you, then details will not be a burden but an interesting, enjoyable, and beautiful thing to deal with.
Of course details must be relevant and not overwhelming, otherwise they might distract you from your primary goals. This is where delegation comes in handy. But delegation does not mean to throw work at your subordinates and go sleep. Managers have to closely follow up with the purpose to assist and not just blame and hold accountable their employees. Anything motivated by laziness or lack of concern backfires.
