Communications and efficiency are the 2 root causes, as identified by my senior manager.
For the initial 2 months i operated as a senior developer, in a self-directed mode. For example, i gave only high level updates to managers, on a weekly basis. I made decisions on implementation or how to communicate with users or external teams. However, As managers inquire about details, they see many things not done “right”. My supervisor explained a few times “we will give you more freedom and leeway once we have confidence in you”.
For a long time i felt extremely micro-managed. My supervisor was so busy (almost a bottleneck) i didn’t want to ask him at every right turn and left turn. But feedback was i should communicate more with managers. I shifted gear to operate as a junior developer, requiring lots of hand-holding — “high-maintenance”, my senior manager said. For example, i decided to give daily updates and discuss many implementation details with managers.
My communications with users was more problematic than my technical, so i needed even more hand-holding. In my 2nd year’s review this improved so much that i received top rating on client service, but still some users commented on my communications.
Hand-holding slowed me down. Productivity requires a certain level of autonomy. I didn’t know or attempt to acquire such autonomy. In fact, I avoided increasing responsibility or additional work, driven by the fear of overwhelming workload. It’s a negative feedback cycle — overwhelmed by workload so (subconsciously) i fell into avoidance mode.
Avoiding unfamiliar components of our system, i remained unfamilar with most of our system for a year (until I changed my mind to take up those components.) I also filtered out most email threads, due to information overload and other reasons. Consequently, it was impossible to gain confidence, efficiency or autonomy. So far in 3 sub systems i show confidence, efficiency and autonomy, all because of one reason — system knowledge (implementation, requirement, limitations…) I feel the pattern is the same for all the colleagues too.
Avoidance mode was my choice, a practical, healthy, self-preservation decision. I didn’t feel confident I could handle the increased responsibility, not at that time.
At end of 2008, another career advice was project management — what i call “autonomy”. However, when I tried to operate more independently, i hit resistance. 3 steps up, 2 steps down. I don’t feel managers have confidence in my judgement. Also I wanted protection and proper approval from a control perspective. So i continue to function as a junior developer — high maintenance.