Scorecard
Close the loop. Score what matters. Kill what doesn't compound.
Per-Venture Form
This blueprint is the format spec — the canonical shape every scorecard must take. The rendered instance lives at /ventures/{slug}/scorecard/, powered by the VentureOperatingKit React component which reads the per-venture coverage map at src/data/venture-blueprints.json.
The lit exemplar is Better Practice — Scorecard. Three canonical sections render in the order Navigation declares (Value first, then Belief, then Control):
- Navigation Strip — direction of intent: Value anchor · Belief pull · Control lever
- Blueprint Coverage Matrix — state of progress: essential blueprints first, then venture-specific picks, each scored 0–4 with named evidence
- Fires Next — derived from the
next_instrumentsactivation graph: which artifact to author or upgrade in the next cycle
Below the canonical scorecard, a venture may add a venture-specific layer that answers questions the canon cannot — Better Practice adds Pictures × Pages × Crew × Ecosystem because the third-place practice protocol demands them. Canon plus extension; never canon alone or extension without canon.
The format below remains the spec for what the scorecard must contain. The React component is one way to render the spec; the markdown template below is another. Both must satisfy the quality_criteria in the frontmatter above.
Business Alignment
| Question | Answer |
|---|---|
| Venture name | [name] |
| All phases complete? | YES / NO — which is missing? |
| Date of first score | [YYYY-MM-DD] |
| Review cadence | Weekly / Monthly / Quarterly |
| Who reviews? | [name or role] |
Tight Five Scorecard
Priority (is this worth doing?)
| Dimension | Score (1-5) | Evidence | Improvement Path |
|---|---|---|---|
| Pain | [what makes you say this?] | [what would move it +1] | |
| Demand | [conversations, signups, revenue] | ||
| Edge | [what you do that others can't easily copy] | ||
| Trend | [what changed that makes this work now] | ||
| Conversion | [proof people pay, not just praise] | ||
| Priority Composite | [product of 5] |
Preparedness (can you deliver?)
| Dimension | Score (1-5) | Evidence | Improvement Path |
|---|---|---|---|
| Principles | [values alignment, founder fit] | ||
| Performance | [metrics, dashboards, feedback loops] | ||
| Platform | [tools, infrastructure, capabilities] | ||
| Protocols | [processes, standards, automation] | ||
| Players | [team, advisors, network, channel partners] | ||
| Preparedness Composite | [product of 5] |
Quadrant
Plot Priority (x) vs Preparedness (y). Determine quadrant.
| Quadrant | Priority | Preparedness | Action |
|---|---|---|---|
| Ship Now | HIGH (>100) | HIGH (>100) | Execute. This is ready. |
| Invest | HIGH (>100) | LOW (<100) | Build capability. The demand is real but you're not ready. |
| Harvest | LOW (<100) | HIGH (>100) | Extract value. Maintain, don't grow. |
| Cut | LOW (<100) | LOW (<100) | Kill or pause. Neither demand nor readiness justifies resources. |
This venture is in: [quadrant]
Rationale: [why this quadrant, citing specific scores]
Kill Criteria
Minimum 3. Each must be observable, measurable, and have a deadline.
| # | Signal | Measurement | Deadline | Status |
|---|---|---|---|---|
| 1 | [specific threshold] | [date] | Active / Triggered / Cleared | |
| 2 | ||||
| 3 | ||||
| 4 |
Five KPIs
The five numbers that tell the truth.
| # | Metric | Current | Target | Gap | Conviction |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 |
Course Correction
Off-Course (what to do when signals go red)
| Condition | Action | Owner | Deadline |
|---|---|---|---|
| [KPI below threshold] | [specific intervention] | [who] | [when] |
On-Course (what to amplify when signals go green)
| Signal | Amplification | Expected Effect |
|---|---|---|
| [KPI above target] | [double down on what caused it] | [projected impact] |
Measurement Log
Record scores at each review cadence. Track trajectory, not snapshots.
| Date | Priority Composite | Preparedness Composite | Quadrant | Key Change | Action Taken |
|---|---|---|---|---|---|
| [YYYY-MM-DD] | |||||
Loop Back
What would trigger a restart from SCAN?
| Trigger | What It Means |
|---|---|
| Kill criterion triggered | Idea failed. New opportunity needed. |
| Quadrant = Cut for 2 reviews | Persistent low scores. Reallocate. |
| Market shifted | Original SCAN gap closed or moved. Rescan. |
| New force emerged | Matrix has new columns. Rescan. |
Legacy Rule
What did this venture teach that the template didn't anticipate?
| Lesson | Where It Applies | Change to Make |
|---|---|---|
| [specific insight] | [which template or phase] | [concrete edit] |
Questions
If the scorecard says "Cut" but your gut says "Keep going," which one is lying — and how would you tell?
- Which KPI are you most tempted to game — and what does that reveal about your real priorities?
- If you removed the lowest-scoring dimension, would the venture still make sense?
- What would a first-time reader of this scorecard conclude about whether to invest?