# Map opportunities to solutions and tests

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Map opportunities to solutions and tests

ID: MHC-D-BRALI-0133 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/map-opportunities-to-solutions-and-tests

Jumping from a broad problem to a favourite feature hides the choices in between. Separate desired outcome, observed opportunities, candidate solutions and tests so the team can change one layer without pretending the whole tree is proven.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A product or project has a desired outcome but several possible problems and solutions.

### Avoid when

- A tree organizes hypotheses; it does not prove user need, causality or solution quality.

### Explanation

Jumping from a broad problem to a favourite feature hides the choices in between. Separate desired outcome, observed opportunities, candidate solutions and tests so the team can change one layer without pretending the whole tree is proven.

### Steps

1. State the outcome in observable terms.
2. List user or system opportunities supported by evidence.
3. Generate more than one solution for important opportunities.
4. Attach a small test to the riskiest assumption in each promising solution.
5. Prune branches when evidence changes rather than defending the diagram.

### Check

At least one solution is linked to an evidenced opportunity and a test of its risky assumption.

### Limits

- A tree organizes hypotheses; it does not prove user need, causality or solution quality.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-71558ba45cb3e8c2e545. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/opportunity-solution-tree-planner.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-3c46142ff55fd24e64ba. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/opportunity-solution-tree-tracker.json)
- FP-BRALI-SRC-71558ba45cb3e8c2e545: Tackle Any Challenge or Goal with the Opportunity Solution Tree (ost) — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/opportunity-solution-tree-planner.json
- FP-BRALI-SRC-3c46142ff55fd24e64ba: Use the Opportunity Solution Tree (ost) to Structure Your Path to Growth or Problem-Solving — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/opportunity-solution-tree-tracker.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
