Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why do I freeze when a PM or engineer pushes back on my work?

You built something in the quiet. It made sense there. Then you brought it into a room with a PM who has a deadline and an engineer who has limits you did not see, and the ground moved. Your chest tightened. You went silent, or you got defensive. Neither helped. Here is the truth you keep avoiding: their pushback is not proof you failed. It is proof the work now touches other people's real limits — time, code, risk. That collision was always coming. You cannot design alone in a room forever and call it finished. What is within your power is not their tone or their timing. It is how you receive the objection. Choose to ask one more question before you defend. If this overwhelm follows you home, or sits heavy for days after, talk it through with someone you trust. That is not weakness. That is sense.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
This problem is less about new theory and more about rehearsing a different response the moment pushback actually lands, so it leans heavily toward practice.
How the two dials adapt to you →
What’s really going on

You do not freeze from lack of skill. You freeze because you confuse your design with your worth. Separate the two now. Their pushback is information about the work, not a verdict on you. Choose to hear it as raw material, not as an attack. This lies within your power today.

🔒 What you’ll build togetherUnlock by starting
A moveBefore your next design review, write down one question you will ask instead of one defense you would normally give.
A moveWhen pushback comes, count three breaths before you speak.
A moveAfter the meeting, sort the notes into two piles: what touches the work, what touches your pride. Discard the second pile.
A moveAsk the PM or engineer directly, first: 'What constraint am I not seeing?' Make it your opening line, not your last resort.
A moveKeep a short log of pushback moments — what you felt, what you did. Review it once a week.

What changes unlock by starting

  • You stop treating disagreement as danger.
  • You ask sharper questions in the room instead of defending on instinct.
  • Meetings with PMs and engineers get shorter and more useful.
  • Your designs get stronger because they meet real constraints earlier, not later.

Related problems

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.