Chapter 7: Anti-Patterns

What Are Anti-Patterns?

Anti-patterns = Common behaviors that seem reasonable but actively harm standup effectiveness.

They're insidious because they feel productive while destroying value.

This chapter catalogs 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's 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 doesn't 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's the team need to know?"

Or better yet: Let 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's bad:

• Wastes everyone's time
• People tune out
• Pushes standup over time limit
• Details aren't relevant to team
• Others don't get time to speak

Why It Happens

• Person thinks out loud
• Lacks preparation
• Doesn't understand what's relevant
• Wants to appear busy/productive
• No facilitation or time enforcement

The Fix

As facilitator:

"John, I'm going to pause you there. Sounds like there's 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, practice saying it
• Lead with the conclusion
• Keep it under 2 minutes
• Filter for what's 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'm blocked on the database schema."
[Silence]  
[Standup ends with no interaction, questions, or offers to help]

Why it's bad:

• Missed collaboration opportunities
• Blockers don't get resolved
• No team building
• Feels transactional and cold

Why It Happens

• Low psychological safety
• Team doesn't feel ownership
• Just going through the motions
• No facilitation
• Async mindset in sync meeting

The Fix

Model active engagement:

Alice:      "API is done. Sarah, you're unblocked."
You:        "Great! Sarah, when will you start on that?"
Sarah:      "I can start today."
You:        "Perfect. 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 expectation that standup is a conversation, not a report.

Death by Detail

The Anti-Pattern

What it looks like:

"I'm working on the authentication system. Let me show you the code.
So here in line 47, I've 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's 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
• Doesn't know how to ask for help briefly
• No facilitation

The Fix

Interrupt politely:

"This is great detail but too much for standup. Can we park this?
Who needs to be in this conversation?"

[Identify 2-3 people]

"Great. 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's bad:

• Team can't collaborate with a ghost
• Blockers aren't surfaced
• Others can't help
• Feels disrespectful
• Team doesn't 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've noticed you've missed 4 of 5 standups this week. What's going on?"

[Listen]

"Standup is important for the team. If the timing doesn't work, let's
find a better time. But showing up is non-negotiable."

For timezone issues: Async updates + attendance at key standups

If behavior 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:    "Uh, so I'm not going to finish this sprint. It's more
            complicated than I thought."

Why it's bad:

• Team can't help if they don't know there's a problem
• Surprises at the end
• Erodes trust
• Prevents early intervention

Why It Happens

• Low psychological safety
• Fear of looking incompetent
• Optimism bias
• Doesn't 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're saying everything's fine, but that task was estimated at 3 days
and it's now day 4. What's the confidence level you'll finish today?"

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

"What's 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:

"Okay great standup everyone. Now let's 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's 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:

"This is a great discussion, but it's not a standup topic. Who needs
to be in this conversation?"

[Identify people]

"Can you three meet at 2pm today? Let's continue standup for now."

Have the discussions that are needed, just not during standup.

The Micromanager's Dream

The Anti-Pattern

What it looks like:

Manager: "John, you said yesterday you'd finish by today. Why isn't it done?"
John:    "I ran into issues with—"
Manager: "You should have flagged that earlier. How long will it take now?"
John:    "Maybe tomorrow—"
Manager: "That's not acceptable. I need it today. Work late if you have to."

[Every standup feels like an interrogation]

Why it's 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 didn't finish. Ran into technical issues."
Manager: "Okay, thanks for being honest. What's 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: "Perfect. 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 manager won't 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. Socializing: 30 minutes.]

Why it's 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 - 9:30am: Optional early join for socializing
9:30am - 9:40am: Standup (strictly facilitated)
9:40am onwards: People who want to hang out can stay

Start exactly on time:

"Alright team, let's start standup. We can keep chatting after.
Quick updates, 10 minutes max."

Have dedicated social time so people don't 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's bad:

• Information isn't being processed
• No one's listening
• No collaboration or handoffs
• Standup is pure theatre

Why It Happens

• People multitasking
• Low engagement
• Don't see value in listening
• No expectation of interaction

The Fix

Model active listening:

• Look at 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, doesn't this unblock you?"
Sarah: "Oh yes! I can start the frontend now."
You:  "Perfect. You two sync after standup?"

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

The Sacred Cow

The Anti-Pattern

What it looks like:

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

Why it's bad:

• Process over outcomes
• Team has no ownership
• Ignores actual problems
• Creates resentment
• "Because Agile says so" isn't a reason

Why It Happens

• Cargo cult Agile
• Manager read a book and follows it religiously
• Fear of change
• Don't understand the principles, just the practices

The Fix

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

Experiment:

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

If standup isn't 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 1-minute update.
30 minutes of updates.
90% irrelevant to any given person.
No one is listening.
Everyone is multitasking.

Why it's bad:

• Doesn't 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've always done it"

The Fix

Split into smaller standups:

• Team-level standups (5-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 doesn't scale past ~12 people. Don't 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's bad:

• Blockers are surfaced but not resolved
• Team feels like complaining into 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'll 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's preventing that? How can I help?"

Blockers without owners don't get resolved.

The Sprint Planning Standup

The Anti-Pattern

What it looks like:

"Okay, so today let's discuss what we're building this sprint. I'm
thinking we should tackle the user dashboard, the API improvements,
and maybe the reporting feature..."

[Standup becomes 45-minute sprint planning session]

Why it's 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 aren't working. I hear the frustration. Let's fix this."

Step 2: Identify Specific Issues

"What specifically isn't working?
- Too long?
- Not valuable?
- Wrong people?
- Wrong format?"

Step 3: Experiment

"Let's try [specific change] for 2 weeks and see if it's 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 doesn't. 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: don't worship process
7. Split large teams: standups don't 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's not working, change it or stop doing it: don't 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's 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 | Can't hear over background noise | Goes off on tangent |

What's Next

You now know what not to do. Let's end with advanced techniques to make you a standup rockstar:

→ Chapter 8: Advanced Techniques: Level up your standup game