Team Stability Meter
Score your team across 6 dimensions and find the single highest-leverage fix
How it works: Rate your team on 6 dimensions using the scales below. The tool calculates a weighted stability score and identifies the single highest-leverage area to fix first.
Unplanned Work
Incidents, fires, and unplanned interruptions per week
Priority Churn
How often do your top 3 priorities change?
Rework Rate
Percentage of work that gets redone, reversed, or thrown out
Context Switching
Concurrent projects per person on the team
Meeting Load
Hours per week each person spends in meetings
Escalations
"This is on fire" escalations per week
Get 364 Daily Leadership Lessons
A structured 52-week leadership course covering team stability, communication, delegation, and decision-making. One lesson per day, free to start.
Start the CourseFrequently Asked Questions
How do I know if my team is unstable?
The clearest signs of an unstable team are: more than 3-4 unplanned work interruptions per week, top priorities shifting more than once per month, a high rework rate (work that gets thrown out or redone), and frequent escalations. Teams with more than 3 concurrent projects per person are also typically operating in a chronically destabilized state.
What is the most common cause of team instability?
Unplanned work — incidents, fires, and ad hoc requests — is the single highest-weight driver of team instability because it is both disruptive and unpredictable. Priority churn (leadership changing direction frequently) is the second most common root cause. Most teams struggle with both simultaneously, which is why addressing unplanned work first usually has the highest leverage.
What is a good team stability score?
A score of 70 or above generally indicates a stable, productive team environment. Scores in the 50-70 range indicate moderate instability with one or two fixable root causes. Below 50 usually means the team is in a reactive, firefighting mode and incremental improvements will have limited impact without addressing the structural root cause.
How do I reduce context switching on my team?
The most effective approach is to limit work-in-progress (WIP) — explicitly cap the number of concurrent projects per person at 2. Research consistently shows that productivity drops by 20-40% when people work on more than 2 projects simultaneously. The second lever is protecting blocks of uninterrupted work time, typically by designating two or three 'no-meeting' days or mornings per week.