Capstone: Complete the Decision Card

Validate the whole card against a set of records and approve version 1.0.

See the situation

Bring together the decisions you have saved. Prepared examples and current-plan approval are separate checks.

Maya · Decision designer

The case

Capstone: inspect a usable decision card

Inspect what the examples can show, validate the current saved plan, and approve only that version.

Validate the whole card against a set of records and approve version 1.0.

Your task

Check your saved Decision Card against the final case. Follow any repair links, then validate the card.

Need a little guidance?

You’re done when: The validated card matches the current saved version and every required boundary can be traced to evidence.

The final check catches gaps before another team relies on your decision card.

Need a reminder? Reopen the worked example

Watch one example first

Card version 1 passed validation and was approved. A later edit changes required evidence. The old approval remains historical; version 2 needs validation and approval of its own.

Why this follows from the evidence

Completion records that someone finished the lesson. Current approval says a particular saved plan was checked. Those facts must not be conflated.

GTM Lab

Saved locally

Decision Card

sample-decision-card · v1 · draft

Review the prepared record set

Six prepared examples illustrate different parts of the card. Review their stated outcomes here; the guide does not compute them from your saved rules. Validate the authored card separately below.

Priya Shah, matched account, complete evidenceRoute to a seller
The clean path. Every required input observed, nothing estimated.
Regional non-profit, genuine question, far below scaleKeep and nurture
The outcome set’s whole reason for existing.
Staffing agency above the revenue threshold, selling to usNot a prospect
Stops at the direction rule, which no threshold could have caught.
Global manufacturer, clears every threshold, message reads "test test"Not a prospect
Vetoed by an interpretive rule before any threshold is evaluated.
Free email, company name "n/a", two-word messageNot enough information to decide
Unknown rather than a pessimistic answer nobody judged.
Decision triggered and never returnedRoute for review, marked defaulted
Hits the timeout, takes the defined default, and is not recorded as decided.

Repair the saved card · prepared example boundary

Let the test tag control execution, not the business answer

One prepared record is a plausible internal test. Repair the saved policy so its business evidence can still be evaluated, while this team's execution and reporting gates keep test traffic out of external work and production measures.

Set the boundary, then check itBusiness evaluation: use the stated evidence; the test tag does not decide prospect status.Execution gate: block outreach while this record is in the test boundary.Execution gate: block seller assignment while this record is in the test boundary.Measurement policy: exclude tagged fixtures from this production population.

Run all 10 validation checks

The checks test the seams between sections, since every section was written while looking at that section. Each runs by its stable ID and reports pass or fail with a reason.

Approve the current version

If the current checks pass, what does approving this saved version commit you to?

Approve with one check failing, and note it as a known gap to fix laterApprove once every check passes, since the checks are the definition of doneEvery check passes, and somebody who was not in the room could implement this from the card alone

Your place saves as you go.

Chapter 8 of 80 complete