Why do I freeze when asked how it all fits together?
You can take a ticket and build exactly what it describes. Hand you a whole system — a dozen services, no clear edges, three teams with opinions — and something in you locks shut. You wait for someone else to speak first. That freeze is not proof you're missing the gift for this work. It's proof you're skipping a step. You try to produce the final answer before you've cut the mess into pieces you can actually hold. No one holds a whole system in their head at once. Not you, not the senior engineer you compare yourself to in that meeting. Your team feels this too — even the ones who talk first. Often they are guessing out loud, not seeing clearly, and the room mistakes their speed for sight. The fix is not more confidence. It is a method, practiced together, out loud, one piece at a time.
You don't freeze because you lack the skill. You freeze because you reach for the finished design before you've broken the problem into pieces small enough to hold. Stop reaching for the whole shape. Choose the one piece you can name right now, say it out loud, and build from there.
What changes unlock by starting
- You speak early in design discussions instead of waiting to be asked twice.
- You and your team break big problems into pieces each person can own.
- The freeze still shows up sometimes, but now you know the next move.
- You stop mistaking other people's confidence for clarity they don't actually have.