Illustrative internal decision: choose a customer-feedback tool for a 20-person product team.
Why it works: The decision uses the same criteria across options and states a condition that would change the recommendation.
Start with the worked examples to see complete reasoning, then use the shorter pattern library for variation. Level guidance and frameworks show how the same task changes as the evidence, audience, or assignment becomes more demanding.
A strong recommendation report makes the choice defensible: the reader can see the decision criteria, evidence for each option, tradeoffs, assumptions, risks, implementation implications, and why the recommended option fits better than the alternatives—including no action when that is a realistic choice.
Use these fuller examples to see what changes between a recognizable pattern and a finished piece of writing. The examples are original or explicitly illustrative, so they demonstrate structure without inventing real-world evidence.
Illustrative internal decision: choose a customer-feedback tool for a 20-person product team.
Why it works: The decision uses the same criteria across options and states a condition that would change the recommendation.
Illustrative decision: how to reduce approval delays.
Why it works: The recommendation follows the observed constraint and preserves a test for the competing capacity explanation.
These transformations make the hidden planning step visible so the template does not become a fill-in-the-blanks substitute for judgment.
Starting material: Source describes Vendor A in detail and lists only price for Vendors B and C.
Result: Finished structure: decision → criteria → comparable options → tradeoffs/sensitivity → recommendation → implementation condition.
Starting material: Source spreadsheet has 40 features with checkmarks but no distinction between required and optional capability.
Result: Finished structure: requirements + evidence + weighted/qualitative tradeoff + conditional recommendation.
| Level | What changes | Quality test |
|---|---|---|
| Short recommendation | State the decision, compare a small number of options against explicit criteria, and recommend one with a material tradeoff. | The recommendation should remain understandable even without a scoring model. |
| Formal recommendation report | Use comparable evidence, assumptions, costs, risks, implementation implications, and sensitivity to explain why one option ranks higher. | The reader should be able to challenge the criteria or assumption without losing the evidence trail. |
| High-stakes decision | Add independent evidence, scenario/sensitivity analysis, governance constraints, expert input where needed, and conditions that would reverse the recommendation. | The strength of the recommendation must match the quality and reversibility of the evidence. |
Observation → function 1. What can the viewpoint actually perceive? 2. Which 1–2 details matter now? 3. What do those details change in image, pace, relationship, or action? 4. What interpretation remains uncertain?
Generic → specific revision Generic line: [x] Observable evidence: [x] Context/constraint: [x] Unnecessary inference removed: [x] Revised line: [x]
Software selection report: compare three tools on required capability, integration effort, recurring cost, support, and migration risk, then recommend the best fit for the defined use case rather than the tool with the longest feature list.
Workspace recommendation: compare renewing the current lease, moving, and hybrid downsizing against cost, capacity, commute, flexibility, and operational disruption.
Vendor recommendation: use the same delivery, quality, security-review, service, and total-cost criteria for every vendor and disclose when evidence is incomplete.
Policy recommendation: compare maintain, revise, and replace options against the policy objective, implementation burden, stakeholder effect, and enforceability.
Equipment recommendation: separate purchase price from lifecycle cost, maintenance, training, downtime, and compatibility before selecting an option.
Hiring-process recommendation: compare process changes against time-to-decision, candidate burden, interview signal, consistency, and staffing capacity.
No-change recommendation: explain why the current process remains preferable under present evidence and identify the trigger that would justify reopening the decision.
Conditional recommendation: recommend Option B only if the pilot meets an agreed reliability threshold; otherwise retain Option A until the dependency is resolved.
Keep the underlying decision or pattern, then replace the subject, evidence, relationship, constraints, and tone with details that belong to your situation. If your final line still works after swapping only one noun, it may be too close to the example.