Most feedback you receive comes from above you or beside you. Your manager, your reviewers, your peers.
That is useful, and it is also a narrow slice.
The people who see your work most honestly are usually downstream of it. The support engineer answering tickets caused by the thing you shipped. The QA person who reads your test coverage as a promise and finds out what it left out. The junior who inherits your service and has to make sense of it at midnight without you.
They know things about your work that no code review will ever surface.
Your manager sees whether you delivered. They see whether it was any good to live with.
So go and ask them, deliberately, and make it easy.
Ask support what your feature generates the most tickets about. Ask the person who took over your old project what confused them in the first week. Ask the designer whether the thing you built matched what they had in mind, and whether you asked them enough questions along the way.
Ask the data person whether the events you emitted were actually usable, or whether they spent a week cleaning them up.
You will hear things that sting a little, because this is the feedback nobody bothers to give upward. They assume you are not interested. They assume it is not their place. They fix your gaps quietly and never mention it.
That silent fixing is the exact thing you want to hear about.
Two rules make this work.
Ask about specifics, not about you. What was hard about the handover beats how am I doing.
And do not defend. The moment you explain why it had to be that way, you have taught them not to answer honestly next time, and you will not get a second chance for a while.
Then close the loop. Tell them what you changed. That is what turns a one time favour into a standing relationship.
The view from behind you is the one you never get to see.
Ask for it.
– Asael Shinder
Top comments (0)