Coaching practices for Small Team Advantages
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Small Team Advantages, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- I keep assuming the fix for being stretched is to hire more people, but every time we grow we somehow move slower and spend the day just keeping each other in the loop
- Everyone on my team is quietly playing for their own scoreboard
- My team only ever gets the leftover scraps from me, and it shows
- My departments are each winning their own little battles while the whole thing loses
- One-on-one keeps falling apart the second the other person gets busy
Practices that may help
- Protect the advantages of small — resist headcount as a measure of success
Adding people to a team adds communication overhead faster than it adds output — protect the productivity of small.
Designing a Calm Company (Fried & Hansson) - Align around collective results, not individual status
Teams fail when members prioritize their own visibility or department’s success over the shared goal.
The Five Dysfunctions of a Team, Made Practical - Use delegation as a development tool
Assign Q3 tasks to team members who are ready to stretch — and treat the learning curve as the point.
The Eisenhower Matrix and Delegation - Cover and move (teamwork over silos)
Every team and department exists to support the others toward the same mission, not to win locally.
Extreme Ownership, Made Practical - Join a small accountability group
Report to a small group rather than one person to add redundancy and social proof.
Accountability Partners - Run a daily team huddle
Hold a brief daily standup to sync on what’s happening and surface stuck points before they become crises.
The Rockefeller Habits: Scaling Up with Rhythm and Focus - Protect important-not-urgent work as a team commitment
Schedule Q2 work on a shared calendar so urgent tasks can’t claim it by default.
The Eisenhower Matrix for Teams - Use structured team forecasting to aggregate diverse views
Combine independent estimates from multiple people before the group talks — aggregation beats any single expert.
Superforecasting - Run a single weekly priority-setting meeting
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
The Eisenhower Matrix for Teams - Build vulnerability-based trust
Teams that can’t admit weakness, mistakes, or ignorance to each other cannot genuinely collaborate.
The Five Dysfunctions of a Team, Made Practical
Related concerns
- Cross Team Collaboration
Every team and department exists to support the others toward the same mission, not to win locally.
Cover and move (teamwork over silos)
- Teamwork At Work
Teams fail when members prioritize their own visibility or department’s success over the shared goal.
Align around collective results, not individual status
- Team Decision Quality
Teams fail when members prioritize their own visibility or department’s success over the shared goal.
- Building Team Capability
Hire and assemble deliberately for domain coverage, not for people who think like you.
Build a team whose combined strengths cover all four domains
- Dunbars Number With My Team
Robin Dunbar's research proposes that the human neocortex supports a stable social group of roughly 150 people, with nested layers of closer relationships (5, 15, 50) requiring progressively more time investment to maintain. The 150-person figure has observational support across hunter-gatherer societies, historical military units, and company sizes; the nested-layer model is more contested. The practical implication is that meaningful relationships are a limited resource that require deliberate allocation.
- How To Scale A Company
Verne Harnish’s Rockefeller Habits (updated in Scaling Up) distill John D. Rockefeller’s management practices into a system of priorities, data, and meeting rhythms that keep growing companies focused and coordinated. The framework is practitioner-developed and widely used in scale-up companies; the evidence base is primarily case-study and clinical rather than controlled trial.
Describe your situation in your own words to search the complete practice library.