Handbook
Wizard 201 — Start from idea
Mission mode: early discovery; value and constraints are still open.
What it is
Mission mode: early discovery; value and constraints are still open.
Parent: Wizard 201 — Mission modes.
When to use it
When Mission should emphasize a new initiative and the team has not locked problem scope yet.
Outcome
A crisp brief, explicit assumptions, artifacts for a spike or RFC.
When not to use it
Skip this mode when the problem is already scoped and funded and you only need execution planning — use a posture that emphasizes Scope and Run plan without re-litigating discovery. If the team mainly needs process repair (same gap every review), consider Repair stage instead.
Inputs you need before the session
| Input | Why |
|---|---|
| Sponsor or customer voice (even informal) | Avoid a brief that only reflects engineering convenience |
| Known constraints (time, compliance, platforms) | Keeps the spike or RFC honest |
| Where notes live today | Reduces thrash when you consolidate into the session |
Map to Wizard 101
The twelve steps in Wizard 101 are the same stepper order you see in the UI. In Start from idea, expect heavier Mission, Context intake, and Understanding before you lock Scope and Run plan.
Common mistakes
| Mistake | What to do |
|---|---|
| Treating the session as a status meeting | Capture one problem statement and explicit assumptions |
| Skipping Contribution setup | Name who speaks for product vs engineering |
| Jumping to execution without a spike or RFC-sized next step | End with one owned next step |
Example scenario (mission mode)
| Starting situation | Notes in three tools; no shared brief; sponsor asks for alignment before funding. |
| Action taken | Run a Wizard session in this mode; emphasize Mission and Context intake; end with a spike or RFC-sized next step. |
| Expected result | One agreed problem statement, explicit assumptions, and a single next owner. |
| What to check | Stakeholders can repeat the problem sentence without referring to private chat only. |