Finding direction
How can I generate more than the obvious two options before deciding?
Generate options before comparing them. Write the outcome first, add the current-course baseline, then list the parts that could vary—scope, method, timing, support, and commitment. Swap or recombine those parts to create a minimum, middle, ambitious, and genuinely different route. Remove only options that fail a true requirement; do not use preferences as early vetoes. Keep a short record of why each option stayed or left. The BROAD builder—Baseline, Requirements, Option components, Assemble variants, Document and filter—makes the option set visible before ranking begins.
Define the outcome before naming more solutions
Start with one sentence: “I want an option that helps me achieve ___ by ___ while preserving ___.” Keep your two obvious candidates off the page for a moment. If you define the goal as an activity—“take the course” or “accept the job”—you have already hidden alternatives inside the wording.
The 2026 Green Book says outcome-based objectives can encourage consideration of different outputs that could achieve the same goal. Its setting is government appraisal, not personal choice. The modest transfer is to name the change you want before treating one familiar action as the only route to it.
Use the BROAD option builder
BROAD is a Forever Free Compass framework, not an external research finding. Use it to create a small longlist before you compare or score anything.
- Baseline: describe what is likely if the current course continues and no new option is chosen.
- Requirements: list the few conditions every viable option must meet; move desirable features into a separate preferences list.
- Option components: identify parts that could vary, such as scope, method, timing, support, location, sequence, or commitment level.
- Assemble variants: recombine viable component choices into a minimum route, a middle route, a more ambitious route, and at least one route that works differently.
- Document and filter: keep options that could meet the outcome and requirements, and write one sentence explaining every removal.
Generate components instead of waiting for whole ideas
A blank page asks your mind to invent a complete third answer at once. A component table asks smaller questions. Could the same outcome be pursued with less scope, a different method, another sequence, shared support, a trial period, or a different timing boundary? Combine only pieces that can work together.
The Green Book and HM Treasury's 2026 business-case guidance describe an options framework filter that breaks viable options into components and recombines them into alternatives. The formal process includes structured workshops and public-value appraisal. BROAD borrows only the generative pattern; it does not turn a personal worksheet into that formal method.
| BROAD field | Prompt | Illustrative entry |
|---|---|---|
| Baseline | What happens if I continue as I am? | Keep the current schedule for one month |
| Requirements | What must any option preserve? | Stay within the agreed budget and permission boundary |
| Option components | Which parts could vary? | Scope, timing, delivery method, support |
| Assemble variants | What viable combinations differ meaningfully? | Pilot one part, phase two parts, or use a different method |
| Document and filter | Why did each route stay or leave? | Kept: meets both requirements; removed: needs unavailable access |
Expand first, then filter against true requirements
Do not rank the first three ideas while you are still generating them. First collect plausible routes. Then remove a route only when it cannot achieve the stated outcome or crosses a real requirement. A preference such as familiarity, elegance, speed, or approval may matter later, but using it as a hidden must-have can recreate the original either-or choice.
HM Treasury guidance distinguishes critical success factors from merely desirable features and warns against setting them so narrowly that options are excluded too early. It also requires the evidence, assumptions, and reasons behind option ratings to be recorded. For a low-stakes choice, one line per option is enough: what it changes, which requirement it meets or misses, and what is still assumed.
Keep alternatives meaningfully different
A longer list is not automatically a better list. Five cosmetic versions of the same route still leave you with one underlying approach. Ask whether at least one candidate changes the method, sequence, scope, or commitment—not just the label. Include the baseline so the cost and consequence of staying on the current course are visible rather than treated as neutral.
The government MCDA note says formal option work can construct alternatives from component choices and keep a transparent record of evidence and assumptions, while also warning that the full method is resource-intensive and requires appropriate expertise. For ordinary reflection, stop when you have several viable and meaningfully different routes; do not perform formal analysis merely to make the list look rigorous.
Know when option generation is enough
Stop broadening when new combinations repeat an existing route, fail a real requirement, or would not change what you compare next. Move to criteria only after the list contains the baseline, a smaller route, a middle route, a more ambitious route, and one genuinely different approach—or after you have documented why one of those forms is not viable.
BROAD is for low-stakes reflection and reversible planning. It cannot determine whether an option is safe, lawful, affordable, ethical, or acceptable to another person. Preserve consent and required processes, and seek qualified guidance when the decision carries material legal, medical, financial, employment, safety, or duty-based consequences.
Original contribution
The Forever Free Compass take
Forever Free Compass uses BROAD as an original option-building sequence: Baseline makes the current course a visible alternative; Requirements separates true must-haves from preferences; Option components lists the parts that could vary; Assemble variants recombines viable parts into minimum, middle, ambitious, and different routes; Document and filter records why each route stays or leaves. BROAD adapts public-sector option-generation principles for low-stakes personal reflection. It is not the Green Book options framework filter, a validated decision method, formal appraisal, or a substitute for consent, required processes, safety controls, or qualified guidance.
Sources
- The Green Book (2026) — HM Treasury. Outcome-first framing; broad option generation; documented longlisting; critical success factors; component recombination; proportionality; and a visible baseline.
- Guidance on developing business cases for projects and programmes — HM Treasury. Broad longlist generation; true requirements versus desirable features; component recombination; varied shortlist forms; explicit deliberation; and records of evidence and assumptions.
- Use of Multi-Criteria Decision Analysis in options appraisal of economic cases — Department for Energy Security and Net Zero and HM Treasury. Component choices as building blocks; transparent option records; proportionality; and the limits and expertise requirements of formal MCDA.
This is educational reflection, not medical or mental-health care. If distress is persistent, severe, or involves immediate safety, contact a qualified professional or local emergency service.