I keep noticing that when the clock is running, I skip stating a hypothesis and forget basic data sanity checks. After a few veteran-led debriefs here, I built a simple debrief template with time stamps: open with the goal, state a one-sentence hypothesis with key drivers, outline the plan, call a data checkpoint before any math, then synthesize and defend. It helps, but when nerves spike, I still blow past the hypothesis or fail to sanity-check units and order-of-magnitude. For those who’ve fixed this, how do you hardwire these into your process? What exact phrases, visual cues, or timing prompts force you to hit them every time? If you’ve got a debrief template or time-stamped notes that make it stick, mind sharing a redacted example?
you’re skipping the hypothesis because you never commit it on paper. before you talk, write “H:” and a one‑liner. if they cut you off, you can still point to it. for sanity, literally say “units times price equals revenue” like grade‑school maths, then compare your final number to a known range. if you don’t know a range, say so and park it. make it a ritual: pen taps H, mouth says gate check, eyes scan units. stop hoping discipline shows up; force it.
i stuck a tiny sticky note on my notebook: “H first. sanity check.” i touch it before speaking. feels dumb, works tho. i also say “assumption check” out loud before math so i don’t sprint past it.
Two mechanisms work reliably under pressure: pre-commitment and external cues. Before you start, pre-commit to a single sentence you can deliver under stress: “My hypothesis is X; the key drivers are Y and Z.” Then insert a verbal “gate” you must clear before any math: “Quick sanity check on units and magnitude.” Ask your mock partner to interrupt immediately if either gate is skipped. Track misses in a simple log with time stamps and reason for the miss. After each session, rewrite your opening line and sanity-check script until they are verbatim and automatic. Within a week of consistent reps, you’ll notice you reach synthesis with fewer walk-backs and tighter defenses.
You’re so close! Lock in a tiny script: hypothesis first, sanity check second. Say it out loud every time. After a few reps, it becomes muscle memory. Keep going—you’ve got this!
First few IB mocks, I dove straight into math, no hypothesis, and got dinged for “aimless analysis.” A VP told me to start with, “My bet is X because Y and Z,” then pause and sanity-check units before touching numbers. I recorded two sessions and literally counted how often I said “hypothesis” and “check.” Embarrassing, but it worked. By week two, the opening line came out on autopilot and I stopped backtracking on bad units. Small script, big difference.
Design two explicit gates and timebox them. At T+0:20, deliver a one-sentence hypothesis with two drivers. At the start of any computation, run a 10-second units and order-of-magnitude check and verbalize it. Use an “if-then” cue: if I start a case, then I state H; if I begin math, then I sanity-check. Implementation intention cues are well-supported in behavioral research and translate cleanly to mocks. Log every skip by type and trigger. After 5–7 reps, aim to reduce skipped gates to under 10% and review your log weekly to isolate patterns.