Decide What May Happen Next

Map each outcome to what the system may do about it, gated on risk rather than confidence.

See the situation

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

Maya · Decision designer

The case

Submission whose decision never returned

A decision outcome says what the evidence supports. A separate execution gate decides whether a downstream action may occur.

Decision status: Triggered, never returned
Time waiting: Past the stated interval
Record state: Held by the execution gate
Anything failing: No, which is why nothing alerted

Your task

Choose whether to allow, block, or review the proposed action. Check the write preview.

Need a little guidance?

You’re done when: The action gate reflects the decision plus its separate permission and ownership rules.

A supported answer is not the same thing as permission to act.

Need a reminder? Reopen the worked example

Watch one example first

A request qualifies for sales review, but the proposed email fails its contact-permission gate. Keep the supported qualification result and hold only the email.

Why this follows from the evidence

A business answer and authorization are separate decisions. This makes it possible to repair permission or choose an allowed next step without falsifying the evidence.

GTM Lab

Saved locally

Decision Card · 0 of 8 sections started

Saved locally to your browser.

Decision Card workshop

Decide what the system may do

Your job: The conversion automation picked up Priya four seconds after submission, while the decision was still running. The answer arrived correct and completely irrelevant.

Case evidence

Submission whose decision never returned

Decision status: Triggered, never returned
Time waiting: Past the stated interval
Record state: Held by the execution gate
Anything failing: No, which is why nothing alerted

Finite workflow replay

Place the gate before the irreversible work

The decision returns after four seconds. Choose a gate and action policy, check each choice, then inspect the replay. Wrong choices can be changed and checked again.

Step 1: Where should the conversion gate sit?

Step 2: What happens while the result is unknown or under review?

Step 3: What should guide which action may run automatically?

Step 4: For this seller team, which outcome interrupts a rep?

Finite example replay · the timeline follows your gate placementFollow the example events in time order. No live integration runs here.

09:14:00
Demo request submitted
The person record exists; no seller action has been authorized yet.
Supported
09:14:01
No gate is active yet
The record can proceed while the decision is still pending.
Not checked
09:14:02
Conversion runs before the decision returns
A later result cannot roll back every downstream side effect.
Needs review
09:14:04
Decision result returns
Only now can the outcome-specific, authorized action proceed.
Supported

Gate practice will save as you work.

Optional: inspect or edit the card sections directly

The case tool above is the main activity. These alternatives let you inspect each rule and its consequences without starting another required quiz.

Section 1 of 4

Add this section to the card

Unknown and review are not answers about the record. What may the system do automatically for them?

Hold or queue the record, alert the decision owner, and take no outcome-shaped actionApply the handling of the nearest normal outcomeTake no action and raise no alert until a person opens the record

Inspect the full card preview

Unknown and review are not answers about the record. What may the system do automatically for them?Not written yet
What should decide whether an action is allowed to run automatically?Not written yet
How do you stop the conversion automation acting before the decision returns?Not written yet
Which outcomes should interrupt a human?Not written yet

Your place saves as you go.

Chapter 7 of 80 complete