Three frameworks, three reads. Team Operations measures team capability. Development Lifecycle measures how you ship. Product Assessment measures the product itself. The composite across all three lands you on the maturity ladder.
Three frameworks
We score every product through three frameworks that each answer a different question. Together they give you a defensible read on where you operate today and where the next move sits.
Team Operations
Question: How capable is your team at building and shipping? This is the primary scoring framework. It reads 27 dimensions organized into 6 functions, scoring your team’s operational maturity across the full product lifecycle.The 6 functions
Scoring
Each dimension lands 1-5:- 1 (Foundation): Basic or absent capability
- 2 (Building): Emerging practice, applied unevenly
- 3 (Scaling): Systematic, measured, repeatable
- 4 (Leading): Deeply integrated practice, hard to copy
- 5 (Compounding): Self-improving systems that compound
Development Lifecycle
Question: Where are you in the build process? Development Lifecycle tracks your product through 6 sequential stages. Where Team Operations measures capability, Lifecycle measures how you ship.The 6 stages
1
Specify
Problem definition, user research, competitive read, opportunity sizing. The foundation of product-market understanding.
2
Context
Solution architecture, feasibility, model selection, success metrics. Translating insight into a buildable plan.
3
Orchestrate
UX design, prompt engineering, interaction patterns, prototype validation. Making the experience tangible and testable.
4
Validate
Implementation, integration, testing, infrastructure. Building with the right architecture for the workload.
5
Ship
Launch execution, monitoring, rollout, incident readiness. Getting the product safely into production.
6
Compound
Performance tuning, cost optimization, model improvement, feedback loops. Making the product compound over time.
How it works
Lifecycle uses a self-assessment model. For each stage, you report status on specific tasks (not started, in progress, done). We compute completion per stage and surface where you sit on the ladder.Product Assessment
Question: How capable is your product itself? Product Assessment reads the product (not the team) across 27 dimensions measuring how deeply capability is integrated into the experience, architecture, and business model.Key areas
- Integration depth: How central capability is to core functionality
- Personalization: Adaptive experiences that learn from behavior
- Automation: Intelligent workflows that cut manual effort
- Data flywheel: Whether usage data improves the product over time
- Native UX: Interaction patterns designed for the workload (prompts, suggestions, explanations)
- Cost architecture: Inference economics and infrastructure cost discipline
Scoring
Product Assessment uses the same 1-5 scale as Team Operations. It runs as a separate assessment via the Product Assessment API or through the platform UI.How they relate
The three frameworks form a tension map. High team capability without process maturity means you ship inconsistently. Strong product capability without operational maturity creates a fragile product.The composite read
When all three frameworks land high, you sit at the top of the composite ladder. The composite collapses all three into a single verb-form stage: React, Augment, Orchestrate, Lead, or Compound. That’s the read you’d put in a board summary or a dashboard header.Score your product
Run a Team Operations score and see your 27-dimension breakdown.
Start the lifecycle assessment
Complete your Lifecycle self-assessment to track build progress.
API reference
Score programmatically via the API.
When do I look at which framework?
When do I look at which framework?
Use Team Operations when the conversation is about team capability or hiring. Use Development Lifecycle when the conversation is about a specific build (planning, post-mortem, scope review). Use Product Assessment when the conversation is about the product roadmap or competitive position. Use the composite when the conversation is at the board level, where one read across all three is what’s wanted.
Why three frameworks instead of one?
Why three frameworks instead of one?
A single number is easy to game and easy to misread. Three frameworks force you to look at capability, process, and product separately, then fuse them. The fused read survives a stress test: if your team is strong but your product is weak, the composite tells you, and the next move is product investment, not training.
Per-framework stage names vs. composite verb forms
Per-framework stage names vs. composite verb forms
Per-framework stages have their own canonical names (Team Operations: Foundation/Building/Scaling/Leading/Compounding; Lifecycle: Specify/Context/Orchestrate/Validate/Ship/Compound; Product Assessment: Wrapper/Augmented/Integrated/Native/Compounding). The composite ladder uses verb forms (React/Augment/Orchestrate/Lead/Compound). Context decides which set you’ll see in any given view.