Team Operations is the primary framework. We score your team across 27 dimensions in 6 functions, each 1-5, for a composite of 27-135. The composite places you on the 5-stage Team Operations ladder: Foundation, Building, Scaling, Leading, Compounding.
Team Operations framework
Team Operations is the primary scoring framework. It reads a team’s operational capability across 27 dimensions in 6 functions, each scored 1-5, for a composite of 27-135. It answers the question: how capable is your team at building and shipping?Five maturity stages
1
Foundation (27-48)
Basics missing across most dimensions. Team hasn’t yet established consistent practice. Most work is manual, ad hoc, or driven by individual contributors rather than shared systems.
2
Building (49-70)
Practice exists but lands unevenly. Some functions are stronger than others. Team is experimenting with new workflows but lacks repeatability and measurement.
3
Scaling (71-91)
Systematic process with measurable outcomes. Team ships features repeatedly and reliably. Data loops are starting to compound.
4
Leading (92-113)
Deeply integrated practice across all functions. Capability is embedded in the team’s ways of working, not just the product. Distance from Building-stage peers is meaningful and widening.
5
Compounding (114-135)
Self-improving systems. Every function reinforces every other. Team gets better with every cycle, creating advantage that’s hard to copy.
Six functions, 27 dimensions
Strategy
How well the team reads its market and makes evidence-based calls.Design
How effectively the team turns user insight into shipped experience.Development
How efficiently and consistently the team builds and ships.Intelligence
How well the team captures, organizes, and uses customer and product signal.GTM
How effectively the team takes products to market and drives adoption.Operations
How well the team learns, adapts, and optimizes its own ways of working.How dimensions interact
Dimensions compound within and across functions.- Data flywheel + feedback loop quality = the compounding engine. Strong data feeds strong models, which generate more useful data.
- Architecture and systems + delivery velocity = the delivery engine. Deep integration enables fast iteration.
- Market intelligence + competitive positioning = the positioning engine. Clear market read produces defensible differentiation.
- Customer signal synthesis + product analytics = the intelligence layer. Strong collection plus strong analysis produces actionable read.
Scoring criteria
We score each dimension 1-5 based on observable signal:- Public evidence - what the product shows, says, and does externally
- Technical signals - architecture patterns, API design, infrastructure choices
- Business model signals - pricing structure, packaging, monetization
- Team signals - job postings, engineering blog, conference talks
- Adapter signals - operational ground truth from connected tools (GitHub, Linear, PostHog)
Using your scores
For individual contributors
For individual contributors
Pick the function most relevant to your role and focus on its 4 dimensions. A PM leans on Strategy and Operations. An engineer leans on Development and Intelligence. Your function score is your primary growth lever.
For product leaders
For product leaders
Use the dimension heatmap across your portfolio to surface systemic weakness. A dimension that scores low across multiple products is an org-level capability gap, not a team problem. Invest in org-wide training and tooling, not individual coaching.
For founders and executives
For founders and executives
Compare your Team Operations score against your Lifecycle and Product Assessment scores to surface the biggest tension. A high product score with a low team score means your product has more capability than your team can sustain. That’s a scaling risk, not a strength.
Related
Three frameworks
How the three frameworks fit together.
Score your product
Run an assessment and read your 27-dimension breakdown.
Read your report
Walk through the maturity report.