The first decision gate: is this worth doing? Capture the idea, its value, rough effort and options before any design effort is spent.
Mirrors the canonical FSD-FRM-01 — FitSD v0.2.0; the canonical form is the authority, so review before use. Nothing is sent to any server — this runs entirely in your browser; download a Markdown record to save your progress.
Resuming a saved form? Load a .md you (or a teammate) downloaded earlier to pick up where it left off — read in your browser only, nothing is uploaded.
.md
Accountable for this solution.
What is the idea, in a sentence or two?
Internal team or named customer(s).
The gap we are plugging and the outcome sought. High-level scope. State whether this is a one-off requirement or the start of a service that must scale.
Internal and/or external.
Primary driver: Value / Compliance / Risk reduction. For compliance- or risk-driven work the case rests on §4 (impact of doing nothing) and the cited obligation or risk record, not the value total. Score each lens 1–3 (1 = low, 3 = high) — a priority signal, not a pass/fail.
New revenue, users or capability.
Keeps current users, or protects a service they rely on.
Saves time, cost or toil.
Reduces a risk or meets an obligation — e.g. closes an exception, meets a regulatory measure.
Summary only — a priority signal, not a pass/fail.
Size each as S / M / L with a short note. Consider all aspects — monitoring, security, billing, support and documentation — not just the build.
Purchase / one-off costs.
Ongoing run / licensing / support costs.
The compelling event — a customer opportunity, a technology change, something on the critical path.
A date or trigger to revisit the case. No clear date? Set a reminder for a quarter or two out.
Complete if this brings in a new technology, tool, product or third-party dependency — regardless of cost or effort.
Due diligence so a new dependency comes in through the front door, not the back.
What is being adopted?
Licence model and cost; the supplier, and how they've been to deal with so far.
How and how often it's updated; its support / end-of-life horizon.
Who owns and supports it once live.
How we'd get off it if needed; alternatives considered.
Optional — only if feasibility is still in doubt.
What question does the PoC answer?
How we judge it proved.
Where you'll run it, and what it costs.
Completed after the PoC, before Gate 2.
Sign-off authorises progression to Gate 2 (or to a PoC first). Note any conditions.