OLD SCRIPT DETECTED
Try this response:
“I don't know yet, and I can check the part that matters.”SEE THE PRACTICE
THE THOUGHT
“If I say “I don't know” in design review, I'm done”
YOUR RECORDED RESPONSE
“I don't know yet, and I can check the part that matters.”
ONE PRIVATE MOVE
Open the review notes you already have, find one place where you felt the urge to bluff, and add two private labels: “known” and “still unclear.” Do not send anything.
SCENE_01
You’re in design review, looking at a diagram that makes sense in pieces but not as a whole. Someone asks about a tradeoff, and the thought lands fast: If I say “I don't know” in design review, I'm done. Your face stays still, but your attention leaves the room and starts scanning for a safer answer than the honest one.
SCENE_02
Inside, the moment isn’t just about not knowing. It feels like proof that you were supposed to have stitched every branch together before anyone saw the deck. So you nod, hedge, or talk around the missing part, then spend the rest of the meeting protecting that gap instead of naming it. Afterward, you carry the unanswered question alone and make it heavier than it was.
SCENE_03
The more accurate read is simpler: design review is where unclear edges get found, not where only finished certainty is allowed. You do not need a grand explanation to be honest. You need a small, usable sentence that keeps the work moving. Put the missing point on paper privately, label what you actually know, and mark what still needs checking.
TRACE · 01/04
SOURCE_LOCATED · 02/04
The Solo Compile
The private rule is: if a review reveals a gap in your understanding, that gap must mean you were unprepared, and being unprepared means your standing drops. So you try to hide uncertainty, answer indirectly, or keep the unknown to yourself until it feels “safe,” which usually means alone and late.
FORGING_REPLACEMENT · 03/04
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
When I think
“If I say “I don't know” in design review, I'm done”
I say
“I don't know yet, and I can check the part that matters.”
Then I do one thing
Open the review notes you already have, find one place where you felt the urge to bluff, and add two private labels: “known” and “still unclear.” Do not send anything.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
Not always. Design review often exposes partial understanding in real time. The thought turns one gap into a character judgment, but the gap itself may just mean the question landed before the answer was fully checked.
It can feel risky, especially in technical rooms that reward quick responses. But a clean acknowledgment can be more credible than a confident detour. The cost usually comes more from hiding the uncertainty than from naming it plainly.
Because the thought treats the missed answer like a public failure, even when nobody else seems to be keeping score. Replay is often your mind trying to recover status by perfecting the scene afterward, instead of just sorting the missing piece.