Why can I build what's designed but not decide the design itself?
You know how to build the thing once someone else has decided what the thing is. Give you a design and you will execute it well. Ask you to be the one who decides the shape, and something in you locks up. Notice what you are actually afraid of. Not the work — you already do harder work than this daily. You are afraid of being seen choosing wrong, with no design document to hide behind. That is not a skill gap. That is exposure, and you are avoiding it. Your team feels this too, even if they don't say it. Someone still has to decide. If it is never you, you have not avoided the decision — you have handed it to whoever is least afraid, or to no one, which is worse.
You fear the call because you cannot blame the blueprint afterward. That is the whole terror, and it is not evidence you lack the ability. Choose one structural decision this week, state your reasoning to your team in writing, and let the outcome teach you. Judgment is built the same way skill was: by doing it while afraid.
What changes unlock by starting
- You state a structural opinion out loud before checking whether others agree with it first.
- Your team sees you propose, not just implement, at least once this month.
- You can name your own reasoning for a decision without hedging it into someone else's idea.
- The fear stays present but stops being the thing that decides for you.