Asking and receiving feedback

"Any feedback for me?" produces "you're doing great." Specific prompts produce usable signal. Ask soon after the work, while memory is fresh. Ask more than one person — manager, PM, a peer who reviews your code, someone you disagreed with. Patterns across sources matter more than one opinion.

After a rocky incident, ask the primary on-call: "During the sev, was my communication clear on impact and next steps? What should I copy from how you ran updates?" You will get operational coaching no review form will capture.

Walking through a hard conversation

Try prompts like:

• "What's one thing I could have done differently on the payments launch?"
• "Where do I create extra work for partners?"
• "If you were me aiming at SDE2, what would you stop / start / continue?"
• After a meeting: "How did that design review land? Anything I should change next time?"

Your nervous system will want to explain. Pause anyway.

1. Listen to the end. Do not interrupt with context.
2. Summarize. "I'm hearing that my PR descriptions lack test plans and reviewers waste time asking — is that right?"
3. Thank them. Even if the delivery was clumsy. Thanking buys you goodwill and time to think.
4. Ask one clarifying question. Prefer future-oriented: "What would good look like on the next PR?"
5. Decide later what is true. You can reject feedback that is wrong. You cannot evaluate it fairly while defending.
6. Act visibly. In a week, show the change ("I've been using a PR template — has review gotten easier?"). Feedback ignored once teaches people to stop giving it.

Separate intent from impact. You meant to be efficient; they experienced you as dismissive. Impact is what you manage. Intent can be shared as context after you have owned the impact — not as a shield.

Common mistakes

• Vague asks. "Any feedback?" invites empty praise.
• Defending in the moment. You cannot evaluate truth while explaining.
• No visible change. People stop investing.

Check yourself

Someone says your design review ran over people. You have context. First move?

Summarize what you heard and check it. Decide what is true later.

You asked "any feedback?" and heard "you're doing great." Next ask?

A specific prompt tied to recent work: one thing to change on the last launch.

Key takeaways

• Ask with concrete prompts soon after the work, from more than one person.
• Listen, summarize, thank, clarify, evaluate later, act visibly.
• Manage impact first. Intent is not a shield.
• Ignored feedback trains people to stop giving it.

Further learning

Next: giving feedback.