The Visibility Paradox
What about it?
This is something the people in tech are really aware of, yet would not acknowledge unless one learns it the hard way. I had read and ignored a lot about this on the internet, until one day it arrived as an uninvited guest on a random Wednesday afternoon, opened my inner eye and rewired my work approach.
You may think this is the vanilla version of placing a loudspeaker in front of you and subtly announcing (praising, to be precise) the work you have done to the Maha-manager-rajas in daily sprint-rajasabhas. But No, it’s more subtle and complicated than that. The paradox is: the cleaner and quieter you finish a piece of work, the less of it anyone sees.
I used to be the person who, when assigned work, would sit down and go through the entire analyse-finalise-approach-implement cycle (even faster with the AI agents now, Long live Claude!), then finish the work quietly and move on. While this seems like the normal approach, it’s not how it should be done.
Corporate Loves Chaos!
The leadership is always busy in corporate. They are jumping from meeting to meeting, convincing management on tech decisions, budget allocations. It’s a whole other world. With their own issues to tackle, they are mostly unaware or oblivious to the efficiency of a team member unless Chaos comes into the picture.
Cooking the Chaos Recipe
To be the superstar team member, once you receive a task / ticket, analyse if it is Chaos-worthy or routine work. This is very important, else you will be labelled slow / difficult to work with.
Once the task is identified to be complicated, the next step is CALLS!
Not simple CALLS! CALLS with maximum participation. Rope in the person who raised the ticket, the person who added a semicolon to the code which has a dependency on this issue, that senior engineer whose time is invaluable (at least tag him in the Teams chat on a non-obvious doubt, e.g. “@raghavendra why is DNS not DNSing. Could we connect to discuss?”).
The task which could’ve been silently completed in 30 mins should be explained in the first 30 mins in a screenshare to you by the person who raised the ticket, then take a 30-min break to “analyse” the issue yourself, then after lunch and a ping-pong game, set up a call with a team member who has just touched this code 4 quarters back. Then, wait, you shouldn’t just fix it yet. Wait for tomorrow’s sprint call, then announce to the manager, even if he is ignoring you, call him by his name, establish eye contact, then elaborate the ticket issue as if it is the next big thing, make the entire team listen and register that you are working on something big, throw in some technical jargon on it, then proceed to tell the manager that you are planning to implement the solution, i.e. the obvious one. Do keep in mind to only do it occasionally and for tickets related to the primary goals the company is focused on.
Follow the above approach and you are guaranteed to get best employee of the month, praise in group chats, promotion and increments in the next cycle and all the goodies related to it.
The Practical Approach (at least the one I follow)
If you are wary of this whole drama trope, the balanced approach would be to do the work and actively rope in other developers occasionally, rather than taking extra effort trying to find all the items yourself. Be confident in saying that you don’t know something and need the help of the person who previously worked on it. Announce in the sprint call that you are indeed actively working on this prominent ticket, rather than dismissing the sprint call as unimportant and using that time too to work on the issue.
At least in IT, the work does not speak for itself; it’s a silent old man. You need to hand-hold the silent old man down the road of fame to the other side, so he can give you his fortune (career coins).