The Deer in Headlights

Stare at the whiteboard. Wait for someone else to go first. Keep waiting.

Commonly affects: Juniors, people who usually work in isolation, first-timers, teams that have never worked together.

The Anti-Pattern

The team reads the brief, looks at each other, and… nothing happens. Someone asks “so, how should we start?” Silence. Another person tries: “what do you think about this requirement?” More silence. Everyone is waiting for someone else to take the first step, but nobody does. Minutes tick by. The whiteboard stays empty.

When someone finally does propose something, the response is a hesitant shrug rather than engagement. The team isn’t disagreeing; they simply don’t know what to say or do next.

Why It Feels Right

Architecture katas can be intimidating, especially for people who haven’t done one before or who feel less experienced than their teammates. Speaking up first means risking being wrong in front of the group. Staying quiet feels safer. And if the team has never worked together, there’s no established trust to fall back on.

There’s also a genuine skill gap at play: if you’ve never broken down a problem into architectural decisions, you might truly not know where to begin. The freeze isn’t laziness; it’s uncertainty.

The Catastrophe

The clock runs while the team stands still. By the time someone finally breaks the ice, half the available time is gone. The eventual design is rushed and shallow because the team spent most of the kata paralyzed. The one person who did speak up ends up carrying the entire exercise, which collapses into a variant of The Loudest Voice by default.

During the presentation, the team has very little to show. The experience confirms everyone’s fear that they “aren’t ready” for architecture work, when in reality they just lacked a way to get started.

The Rescue

Getting unstuck is a skill that can be practiced:

• Start with what you know. You don’t need a brilliant opening move. “Let’s read the brief out loud together” is a perfectly good first step.
• Use structured prompts. If the team is frozen, pick a concrete question to answer: “Who are the users?” “What’s the most important quality attribute?” “What does the happy path look like?” Small questions break big paralysis.
• Make it safe to be wrong. Explicitly say “this might be completely off, but what if we…” The first idea doesn’t need to be good; it just needs to exist so the team has something to react to.
• Assign a starting activity. Have each person spend 3 minutes writing down their initial thoughts independently, then share. This removes the pressure of speaking into silence.
• Ask the facilitator. If the team genuinely doesn’t know where to begin, asking the facilitator for a nudge is not a failure. It’s exactly what they’re there for.