gtmjosh
Define the Decision
Chapters · 1 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 1 of 80 complete

Turn a Vague Request Into a Decision

State one decision, its trigger, and the moment it must return, then split out the decisions hiding inside it.

2a · vague request to decision

Unbundle the request

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

Meet Maya.

Maya helps turn an unclear request into a decision: what needs answering, which evidence matters, and who can act on the result.

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

The case

The request as it arrived

A request names a topic. A decision states the trigger, record, question, and moment an answer is needed.

Message
"Can we use AI to qualify our inbound?"
From
VP of Marketing, in the team channel
Marketing ops heard
A spam filter
Sales heard
A routing rule
The builder heard
A scoring model

Your place saves as you go.

Chapter 1 of 80 complete