gtmjosh
Define the Decision
Chapters · 3 of 8
  1. 01 · Turn a Vague Request Into a Decision
  2. 02 · Name the Owner and Business Purpose
  3. 03 · Define the Allowed Outcomes
  4. 04 · Choose the Required Evidence
  5. 05 · Separate Hard Rules From Interpretation
  6. 06 · Add Unknown and Review Outcomes
  7. 07 · Decide What May Happen Next
  8. 08 · Capstone: Complete the Decision Card
Guide overview →

About 16 min · Lesson and activity

Chapter 3 of 80 complete

Define the Allowed Outcomes

Build a closed, mutually exclusive outcome set where every outcome earns a different consequence.

2a · allowed outcomes

Match each outcome to its next step

Start with the example, then try it yourself. The last case is optional practice.

See the situation

Start with the situation below. Next, we will work through an example together before you try the activity.

Maya’s decision workshop. A planning wall, pinned request cards, an open notebook, and a warm wooden worktable.
Maya, decision designer, explain pose
Maya · Decision designer

The case

Regional non-profit · demo request

Define outcomes that are understandable at the point of action. Preserve interested people who do not fit, and route ambiguity for review.

Company
Regional non-profit
Annual budget
Far below the scale GTM Lab sells to
Message
A specific, well-informed question about a real problem
Direction of intent
Wants to buy from GTM Lab
Under a two-outcome set
Handled identically to junk mail

Your place saves as you go.

Chapter 3 of 80 complete