DEV Community

CBT Tools
CBT Tools

Posted on

Standup Anxiety Follow-up: The Pre-Standup Grounding Protocol

Standup Anxiety Follow-up: The Pre-Standup Grounding Protocol

The 5-Minute Pre-Standup Grounding Protocol

You've felt it. That 9:58 AM Slack notification: "Standup in 2 minutes." Your stomach drops. Your mind races through everything you haven't done yet. You scramble to find the right words to sound productive without overpromising.

This is standup anxiety — and it's not about the meeting itself. It's about the cognitive distortions that hit in the 5 minutes before standup.

5 Cognitive Distortions That Hit Before Standup

1. Mind Reading ("They'll think I'm lazy")

You assume your teammates are judging your progress. In reality, they're thinking about their own updates.

Reframe: "My teammates are focused on their own updates, not mine. My update is just data."

2. Catastrophizing ("If I say I'm stuck, they'll think I'm incompetent")

You fear admitting blockers will label you as incapable. In reality, blockers are normal.

Reframe: "Blockers are data, not weakness. Sharing them helps the team unblock me."

3. Labeling ("I'm a slow developer")

You generalize one slow day into a global self-label. In reality, velocity varies.

Reframe: "One slow day doesn't define me. My track record speaks for itself."

4. All-or-Nothing ("If I don't finish this today, I failed")

You see your day as binary success/failure. In reality, progress is incremental.

Reframe: "Progress is incremental. Moving the needle is success, not just completion."

5. Should Statements ("I should have finished this by now")

You impose unrealistic expectations on yourself. In reality, estimates are guesses.

Reframe: "Estimates are guesses. I'm doing my best with the information I have."

The 5-Minute Pre-Standup Grounding Protocol

Minute 1: Write down what you actually did (not what you planned to do)
Minute 2: Identify one blocker (if any) — and write it as data, not weakness
Minute 3: Write your update in 3 sentences (Yesterday, Today, Blockers)
Minute 4: Read your update aloud once — notice if any distortions slipped in
Minute 5: Take 3 deep breaths, then join the call

The Pre-Standup Thought Record

Distortion What I'm thinking Evidence for Evidence against Reframe
Mind Reading "They'll think I'm lazy" No evidence They have their own updates "They're focused on themselves"
Catastrophizing "I'll look incompetent" No evidence Blockers are normal "Blockers help the team"
Labeling "I'm slow" One day Track record shows consistency "Velocity varies"
All-or-Nothing "I failed" No completion Progress made "Progress is incremental"
Should "I should finish" Estimate Estimates are guesses "Doing my best with info"

Why This Works

The pre-standup grounding protocol works because it externalizes the distortions before they hijack your update. By writing them down, you see them as data — not as truth.

You're not "anxious about standup." You're experiencing 5 predictable cognitive distortions that hit before every standup. And you have a 5-minute protocol to break them.

Next Steps

  1. Try the protocol before your next standup — 5 minutes, no tools needed
  2. Track your anxiety — rate it 1-10 before and after the protocol
  3. Notice the pattern — the distortions are predictable, so the reframes become automatic

Resources


This article is part of the CBT×dev series — cognitive behavioral therapy for developers who think too much. Because your mind is your most important tool — and it deserves maintenance too.

Top comments (0)