Add Unknown and Review Outcomes

Make "we do not know" a real answer, and stop a record being stranded when the decision never returns.

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

Unidentifiable submission

Unknown means evidence is insufficient. Error means the decision process failed. A timeout needs an owner and a visible review state.

Email: Free email address
Company name: "n/a"
Message: Two words
Matched account: None
Honest estimate possible: No

Your task

Choose a state for each unresolved case. Check the feedback before moving to the next case.

Need a little guidance?

You’re done when: No unresolved case is silently treated as a negative answer or successful decision.

Uncertainty is operational only when somebody knows what happens next.

Need a reminder? Reopen the worked example

Watch one example first

No company source produces unknown eligibility. A crashed parser produces an execution error. An unresolved case after the promised decision time produces a timeout. Each needs a different repair.

Why this follows from the evidence

These states describe evidence, execution, and timing respectively; none means “not qualified.” A test boundary is separate again: it allows local evaluation without authorizing production actions.

GTM Lab

Saved locally

Decision Card · 0 of 8 sections started

Saved locally to your browser.

Decision Card workshop

Make "we do not know" a real answer

Your job: Nothing required is present and nothing can be honestly estimated. The first version returned the safest-sounding answer available, and a month later a share of disqualifications carried no evidence at all.

Case evidence

Unidentifiable submission

Email: Free email address
Company name: "n/a"
Message: Two words
Matched account: None
Honest estimate possible: No

Review inbox · 1 of 4

Give each case the state its evidence supports

Inspect the current evidence, then assign unknown, error, a supported business outcome, or the test boundary. A correct review or hold is a successful disposition.

No checkable company

The message asks about buying. No company name or matched account is available.

Which state belongs on the record?

Current review dispositionCompare the original state with the proposed change. This preview does not change live records.

Current review disposition
Item	Before	Proposed state	Why
No checkable company	No business or execution state recorded	Choose a state	The proposed state remains open until you check it.

No checkable company: BeforeNo business or execution state recorded; Proposed stateChoose a state; WhyThe proposed state remains open until you check it.

Queue progress 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 3

Add this section to the card

Three situations get collapsed into one bucket. Which pair most needs telling apart in reporting?

Unknown and errorReview and not a prospectRoute to a seller and keep and nurture

Inspect the full card preview

Three situations get collapsed into one bucket. Which pair most needs telling apart in reporting?Not written yet
The decision never returns. The record sits undecided, nothing fails, nothing alerts. What should the card say?Not written yet
An internal test submission arrives, tagged as a test. What should the card have already decided?Not written yet

Your place saves as you go.

Chapter 6 of 80 complete