The Team Problem: Why Teams Don't Scale
You have great engineers individually. But as a team:
- Meetings drag on without decisions
- Ideas are shot down without explanation
- Junior engineers are afraid to speak up
- People work in silos, duplicate effort
- Turnover is high; people leave for "better opportunities"
- Politics create inefficiency
You're not scaling the team. You're scaling the dysfunction.
High-performing teams are intentional. They have patterns, norms, and practices that enable fast decision-making, collaboration, and growth.
Why Team Performance Is Hard
Challenge 1: Implicit Expectations
Team leaders assume: "Everyone knows how we make decisions." But they don't. Different people expect different things.
Challenge 2: Avoiding Conflict
People avoid conflict. Instead of debating ideas, they nod and go do their own thing. No alignment, duplicate work.
Challenge 3: Fear of Speaking Up
Junior engineers see their ideas dismissed harshly. They learn to be quiet. Diverse ideas stop flowing.
Pattern 1: Psychological Safety
The foundation of high-performing teams. People feel safe to speak up, admit mistakes, ask for help.
How to build it:
1. Leader Goes First with Vulnerability
As a leader, admit when you don't know something. Share mistakes you've made and what you learned.
Good (creates safety): "I made a mistake on this design. Here's what I learned. What do you think?"
2. Respond Constructively to Bad News
When someone brings a problem: Thank them. Investigate. Fix the system, not blame the person.
3. Solicit Criticism of Leaders/Ideas
Explicitly ask: "What could I do better?" "What's wrong with this plan?"
Without explicit invitation, people assume criticism isn't welcome.
Pattern 2: Communication Patterns
High-performing teams have explicit communication norms.
| Norm | What It Means | Benefit |
|---|---|---|
| Default to Async | Write decisions in documents, discuss async first | Timezone-friendly, documented, time for thought |
| Explicit Decisions | Every decision has a doc: what, why, alternatives considered | Clear, no second-guessing, onboarding easier |
| Blameless Postmortems | After incidents, investigate system not blame | People report problems early, learning culture |
| Unblock Principle | Don't wait for perfect info, move forward, adjust | Fast velocity, learning by doing |
What are we deciding?
Why does it matter?
What are the options?
What are the tradeoffs?
What's the decision?
What's the rollout plan?
Pattern 3: Decision-Making Frameworks
Make decisions faster by being explicit about who decides and how.
| Decision Type | Who Decides | Input Process | Timeline |
|---|---|---|---|
| Reversible | Individual/small team | Async discussion optional | 1 day |
| Semi-reversible | Team lead + team | Async feedback required | 3-5 days |
| Hard to reverse | Director + leads + affected teams | Sync discussion + doc | 1-2 weeks |
This prevents:
- Death by committee (reversible decisions taking weeks)
- Unilateral decisions affecting many teams
- Lack of input and buy-in
Pattern 4: Ownership and Accountability
High-performing teams have clear ownership. Everyone knows who's responsible for what.
R - Responsible: Who does the work?
A - Accountable: Who owns the outcome? (Must be one person)
C - Consulted: Who provides input?
I - Informed: Who needs to know the outcome?
Example: Project X
R: 5 engineers
A: Tech Lead (single point of accountability)
C: Product Manager, QA Lead
I: Other teams, leadership
Benefits:
- Clear who to ask questions
- One person drives to completion
- Easy to identify blockers
- Less diffusion of responsibility
Building the Culture: Practical Steps
- Document team principles
- Set up decision framework
- Hold retro to identify blockers
Month 2-3: Practice Patterns
- Use decision docs for 5+ decisions
- Run blameless postmortem after incident
- Get feedback on how it's working
Month 4+: Reinforce and Evolve
- New people learn patterns from day 1
- Retros focus on improving patterns
- Leadership models the culture
Key Takeaways
✓ Build psychological safety through vulnerability
✓ Make communication patterns explicit
✓ Use frameworks for faster decisions
✓ Assign clear ownership
✓ Practice blameless postmortems
✓ Reinforce culture through hiring and onboarding