Chapter 7: Anti-Patterns

The common standup behaviours that look reasonable but quietly destroy value, and how to fix each one.

What Are Anti-Patterns?

Anti-patterns are common behaviours that seem reasonable but actively harm standup effectiveness.

They are insidious because they feel productive while destroying value.

This chapter catalogues the most common standup anti-patterns and how to fix them.

Status Report Theatre

The Anti-Pattern

What it looks like:

Manager: "John, what did you do yesterday?"
John:    "I worked on tickets, had some meetings, reviewed PRs."
Manager: "Okay. Sarah?"
Sarah:   "I worked on the dashboard feature."
Manager: "Good. Next."

Why it is bad:

• Information only flows to manager
• No team interaction or collaboration
• Feels like surveillance
• Zero value to teammates
• People perform rather than collaborate

Why It Happens

• Manager thinks standup is for status tracking
• Team does not understand standup purpose
• Low psychological safety
• Hierarchical culture
• Manager is control-oriented

The Fix

Manager: stop asking for status. Instead ask:

• "Any blockers?"
• "Who needs help?"
• "What does the team need to know?"

Or better: let the team run the standup. Manager just listens.

Team: talk to each other, not to the manager.

The Rambler

The Anti-Pattern

What it looks like:

John: "Yesterday I started working on the feature and I had to set
       up the environment which took a while because there were
       some issues with the dependencies and I had to debug that
       and then I looked at the code and tried to understand how
       it works and then I started implementing but I got stuck on
       this one part where..."

[5 minutes later, John is still talking]

Why it is bad:

• Wastes everyone's time
• People tune out
• Pushes standup over the time limit
• Details are not relevant to the team
• Others do not get time to speak

Why It Happens

• Person thinks out loud
• Lacks preparation
• Does not understand what is relevant
• Wants to appear busy or productive
• No facilitation or time enforcement

The Fix

As facilitator:

"John, I am going to pause you. Sounds like there is a lot going
on. Can you give us the bottom line in 30 seconds? We can dig
into details after standup if needed."

As the rambler (self-awareness):

• Prepare your update before standup
• Write it down, practise saying it
• Lead with the conclusion
• Keep it under 2 minutes
• Filter for what is relevant to the team

Team norm: 2-minute timer per person.

The Silent Treatment

The Anti-Pattern

What it looks like:

Alice: "I finished the API. Sarah, you can start frontend work now."
[Silence]
Bob:   "I am blocked on the database schema."
[Silence]
[Standup ends with no interaction, questions, or offers to help]

Why it is bad:

• Missed collaboration opportunities
• Blockers do not get resolved
• No team building
• Feels transactional and cold

Why It Happens

• Low psychological safety
• Team does not feel ownership
• Just going through the motions
• No facilitation
• Async mindset in a sync meeting

The Fix

Model active engagement:

Alice:  "API is done. Sarah, you are unblocked."
You:    "Sarah, when will you start on that?"
Sarah:  "I can start today."
You:    "Alice, can you be available for questions?"
Alice:  "Yes, ping me anytime."

Ask questions:

• "Who can help Bob with the database schema?"
• "Sarah, do you need anything from Alice to get started?"
• "Anyone else blocked on similar things?"

Create the expectation that standup is a conversation, not a report.

Death by Detail

The Anti-Pattern

What it looks like:

"I am working on the authentication system. Let me show you the
code. So here in line 47, I have implemented the JWT validation
logic. The issue is that the token refresh mechanism needs to
handle edge cases where..."

[10 minutes of technical deep-dive during standup]

Why it is bad:

• Standup becomes a technical review
• Goes way over time
• Only 2 people care, others are bored
• Not the right forum for this discussion

Why It Happens

• Person is stuck and thinking out loud
• Wants to show expertise
• Does not know how to ask for help briefly
• No facilitation

The Fix

Interrupt politely:

"This is good detail but too much for standup. Park it. Who needs
to be in this conversation?"

[Identify 2 to 3 people]

"You three chat after standup. For now, John, can you give us the
one-sentence summary?"

Teach the team: "Save the how for after standup, share the what during."

The Ghost

The Anti-Pattern

What it looks like:

Monday      Sarah is absent
Tuesday     Sarah is absent
Wednesday   Sarah shows up: "Yeah, working on the thing. All good."
Thursday    Sarah is absent
Friday      Sarah is absent

Why it is bad:

• Team cannot collaborate with a ghost
• Blockers are not surfaced
• Others cannot help
• Feels disrespectful
• Team does not trust them

Why It Happens

• Finds standup useless
• Has conflicting meetings
• Different timezone
• Checked out from team
• No accountability

The Fix

As manager (1-on-1):

"I noticed you missed 4 of 5 standups this week. What is going on?"

[Listen]

"Standup is important for the team. If the timing does not work,
we can find a better time. But showing up is non-negotiable."

For timezone issues: async updates plus attendance at key standups.

If behaviour continues: performance management.

The Everything's-Fine Liar

The Anti-Pattern

What it looks like:

Monday      "Everything's fine. On track."
Tuesday     "Yep, all good. No blockers."
Wednesday   "Making progress. Should finish soon."
Thursday    "Almost there. No issues."
Friday      "I am not going to finish this sprint. It is more
             complicated than I thought."

Why it is bad:

• Team cannot help if they do not know there is a problem
• Surprises at the end
• Erodes trust
• Prevents early intervention

Why It Happens

• Low psychological safety
• Fear of looking incompetent
• Optimism bias
• Does not want to admit struggle
• Punished for honesty in the past

The Fix

Build psychological safety:

• Model vulnerability yourself
• Thank people when they surface problems
• Never punish honesty
• Celebrate asking for help

Ask probing questions:

"You are saying everything is fine, but that task was estimated
at 3 days and it is now day 4. What is the confidence level you
will finish today?"

"Scale of 1 to 10, how stuck are you?"

"What is the biggest risk to finishing on time?"

Break work into smaller pieces so problems surface earlier.

The Meeting About Meetings

The Anti-Pattern

What it looks like:

"Good standup everyone. Now we should discuss the architecture
for the new feature. So I was thinking we could use
microservices..."

[30 minutes later, standup has become a planning meeting]

Why it is bad:

• Standup goes way over time
• People have other meetings
• Not everyone needs to be there for this discussion
• Standup loses its purpose

Why It Happens

• No other regular meeting to discuss things
• Eager to solve problems immediately
• Poor facilitation
• Blurred boundaries between meeting types

The Fix

Interrupt and park:

"Good discussion, but this is not a standup topic. Who needs to be
in this conversation?"

[Identify people]

"Can you three meet at 2pm today? Continuing standup for now."

Have the discussions you need, just not during standup.

The Micromanager's Dream

The Anti-Pattern

What it looks like:

Manager: "John, you said yesterday you would finish today. Why is
          it not done?"
John:    "I ran into issues with the API."
Manager: "You should have flagged that earlier. How long will it
          take now?"
John:    "Maybe tomorrow."
Manager: "That is not acceptable. I need it today. Work late if
          you have to."

[Every standup feels like an interrogation]

Why it is bad:

• Creates fear and anxiety
• People hide problems to avoid heat
• Destroys psychological safety
• Focuses on blame, not problem-solving
• Team hates standup

Why It Happens

• Manager is insecure
• Lack of trust in team
• High pressure from above
• Command-and-control culture
• Manager thinks this is leadership

The Fix

Manager needs to change approach:

John:    "I did not finish. Ran into technical issues."
Manager: "Okay, thanks for being honest. What is the blocker?"
John:    "The API integration is trickier than expected."
Manager: "Who can help John figure this out today?"
Sarah:   "I can pair with him this afternoon."
Manager: "Great. Thanks Sarah. John, you two sync up after this?"

Focus on:

• Problem-solving, not blame
• How to help, not why you failed
• Moving forward, not rehashing the past

If the manager will not change: team needs to escalate or work elsewhere.

The Social Hour

The Anti-Pattern

What it looks like:

9:30am    Standup scheduled
9:35am    Still chatting about the game last night
9:40am    Finally starting standup
9:45am    Someone tells a funny story, everyone laughs
9:50am    Back to talking about weekend plans
10:05am   Standup finally ends

[Actual work updates: 5 minutes. Socialising: 30 minutes.]

Why it is bad:

• Wastes everyone's time
• Actual blockers get buried
• Standup becomes useless
• People stop attending
• Goes way over time

Why It Happens

• Team likes each other (good)
• No facilitation or time boundaries
• Remote team starved for connection
• No other social time

The Fix

Separate social time from standup:

9:25am to 9:30am    Optional early join for socialising
9:30am to 9:40am    Standup (strictly facilitated)
9:40am onwards      People who want to hang out can stay

Start exactly on time:

"Alright team, standup time. We can keep chatting after. Quick
updates, 10 minutes max."

Have dedicated social time so people do not cram it into standup.

The Update to No One

The Anti-Pattern

What it looks like:

John gives update.
No one reacts or responds.
Sarah gives update.
No one reacts or responds.
Everyone gives updates into a void.
Standup ends.
No collaboration happens.

Why it is bad:

• Information is not being processed
• No one is listening
• No collaboration or handoffs
• Standup is pure theatre

Why It Happens

• People multitasking
• Low engagement
• Do not see value in listening
• No expectation of interaction

The Fix

Model active listening:

• Look at the person speaking (camera if remote)
• Nod and react
• Ask questions
• Offer help

Facilitate interaction:

John:  "I finished the API."
You:   "Nice. Who needs to know about this? Sarah, does this not
        unblock you?"
Sarah: "Yes, I can start the frontend now."
You:   "You two sync after standup?"

Create the expectation: standup is a conversation, not a series of monologues.

The Sacred Cow

The Anti-Pattern

What it looks like:

Team:    "Standup is not working. It is a waste of time."
Manager: "But we have to do standup. It is agile."
Team:    "Can we try a different format?"
Manager: "No, standup must be every day at 9am with three
          questions. That is the rule."

Why it is bad:

• Process over outcomes
• Team has no ownership
• Ignores actual problems
• Creates resentment
• "Because agile says so" is not a reason

Why It Happens

• Cargo-cult agile
• Manager read a book and follows it religiously
• Fear of change
• Does not understand the principles, just the practices

The Fix

The goal is collaboration and alignment, not following a format.

Experiment:

• Try different formats
• Adjust timing or frequency
• Let the team decide what works
• Measure value, not adherence to format

If standup is not working, change it or stop doing it.

The All-Hands Standup

The Anti-Pattern

What it looks like:

30 people on a call.
Each person gives a 1-minute update.
30 minutes of updates.
90% irrelevant to any given person.
No one is listening.
Everyone is multitasking.

Why it is bad:

• Does not scale
• Information overload
• No one retains anything
• Massive time waste
• No real coordination

Why It Happens

• Org conflates alignment with attending meetings
• Manager wants visibility into everything
• No trust in team autonomy
• "This is how we have always done it"

The Fix

Split into smaller standups:

• Team-level standups (5 to 8 people)
• Tech leads sync separately
• Weekly all-hands for broader alignment

Use written updates for large groups:

• Daily Slack post in #general
• Weekly newsletter
• Dashboard with status

Standup does not scale past about 12 people. Do not try to force it.

The Blocker Collector

The Anti-Pattern

What it looks like:

John:    "Blocked on database access."
Manager: "Okay, noted."
Sarah:   "Blocked on design approval."
Manager: "Got it."
Bob:     "Blocked on code review."
Manager: "Thanks."

[Standup ends. No one is assigned to unblock. Nothing happens.]

Why it is bad:

• Blockers are surfaced but not resolved
• Team feels like they are complaining into a void
• Nothing changes
• Morale drops

Why It Happens

• No ownership culture
• Manager just collecting information
• No follow-through process
• No accountability

The Fix

Assign an owner to every blocker:

John:    "Blocked on database access."
Manager: "Who can get John database access? Alice?"
Alice:   "I will reach out to ops team this morning."
Manager: "Great. Alice, can you update John by noon?"
Alice:   "Yes."

Track and follow up:

• Next standup: "Alice, did you unblock John?"
• If not: "What is preventing that? How can I help?"

Blockers without owners do not get resolved.

The Sprint Planning Standup

The Anti-Pattern

What it looks like:

"Today we should discuss what we are building this sprint. I am
thinking we should tackle the user dashboard, the API improvements,
and maybe the reporting feature..."

[Standup becomes 45-minute sprint planning session]

Why it is bad:

• Wrong meeting for this
• Goes way over time
• Different purpose than standup
• Not everyone needs to be there for all decisions

Why It Happens

• No dedicated planning time
• Manager improvises
• Blurred meeting boundaries

The Fix

Have separate meetings for different purposes:

• Standup. Sync on today, surface blockers
• Sprint planning. Plan the sprint
• Refinement. Break down stories
• Retro. Reflect and improve

Keep standup focused on the short-term: today and tomorrow, not the whole sprint.

Key Anti-Patterns Summary

Diagnosing Your Standup

Warning Signs Exercise

Check all that apply to your standup:

• [ ] Regularly goes over 15 minutes
• [ ] People arrive late frequently
• [ ] Team members multitask during standup
• [ ] No one asks questions or offers help
• [ ] Blockers are mentioned but not resolved
• [ ] Same person dominates every standup
• [ ] Updates are vague ("working on stuff")
• [ ] No interaction between team members
• [ ] Team openly resents the standup
• [ ] Nothing actionable comes from it

0-2 checked   Your standup is probably fine
3-5 checked   Significant room for improvement
6+ checked    Your standup is broken, needs serious changes

The Fix-It Framework

Step 1: Acknowledge the Problem

"Team, our standups are not working. I hear the frustration. We
should fix this."

Step 2: Identify Specific Issues

"What specifically is not working?

- Too long?
- Not valuable?
- Wrong people?
- Wrong format?"

Step 3: Experiment

"Try [specific change] for 2 weeks and see if it is better."

Step 4: Measure and Adjust

"After 2 weeks: is this better? What should we keep? What should
we change?"

Step 5: Iterate

Keep what works. Drop what does not. Try something new.

Key Takeaways

1. Anti-patterns are common. Most teams fall into some of these traps
2. Status reporting is not a standup. Focus on collaboration, not reporting
3. Time limits are non-negotiable. Enforce 2 minutes per person
4. Psychological safety is essential. People must feel safe surfacing problems
5. Blockers need owners. Collecting blockers without resolving them is useless
6. Format should serve the team. Do not worship process
7. Split large teams. Standups do not scale past 12 people
8. Separate meetings by purpose. Standup is not planning, retro, or technical review
9. Listen actively. Standup is a conversation, not a series of monologues
10. If it is not working, change it or stop doing it. Do not waste everyone's time

Anti-Pattern Bingo

Play this during your standups (internally, not out loud). If you get 5 in a row, your standup needs serious help.

| Someone rambles 5+ min | No one listening | Manager interrogates | Same blocker for 3rd day | Standup goes 20+ min | | Tech deep-dive starts | "Everything's fine" (but it is not) | Social chat dominates | Someone absent again | Planning happening | | No interaction | Vague update ("working on stuff") | Manager solves problems in standup | Side conversations | Someone multitasking | | Updates to manager only | Blocker mentioned, no one assigned | Team resents being there | Cannot hear over background noise | Goes off on a tangent |

Next Steps

Continue to 08-advanced-techniques.md for advanced techniques used by high-performing teams.