# Name both sides of the trade-off

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

---

## Name both sides of the trade-off

ID: MHC-D-BRALI-0051 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/name-both-sides-of-the-trade-off

'Make it faster' sounds clear until speed damages the accuracy you also need. Write both requirements. That turns a vague demand for improvement into a design problem: where can the requirements be separated, supported differently or tested together?

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

### Use when

- An improvement appears to make another important requirement worse.

### Avoid when

- A clever redesign may not remove the trade-off. Keep failure cases and non-negotiable constraints visible.

### Explanation

'Make it faster' sounds clear until speed damages the accuracy you also need. Write both requirements. That turns a vague demand for improvement into a design problem: where can the requirements be separated, supported differently or tested together?

### Template

We need more of ___ because ___.
But that can worsen ___ under these conditions: ___.
Could we separate the requirements by time, place, case or system part?
Small reversible test: ___.

### Example

A form needs fewer steps but must still collect rare-case details. One candidate is a short common path with an explicit additional branch, not silently removing the required information.

### Check

Both requirements and one testable design option are explicit.

### Limits

- A clever redesign may not remove the trade-off. Keep failure cases and non-negotiable constraints visible.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-21b82e8b7398a1c821d8. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/break-down-big-problems-triz.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-82d862e69ecc276c69d2. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/triz-contradiction-coach.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-d11d3976a6b8e45039dd. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/triz-if-then-contradictions.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-862d4918789bb2a5afae. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/triz-trade-off-identification.json)
- FP-BRALI-SRC-21b82e8b7398a1c821d8: Decompose a Hard Problem with TRIZ-Inspired Contradictions — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/break-down-big-problems-triz.json
- FP-BRALI-SRC-82d862e69ecc276c69d2: Use Standard Triz Contradiction Templates Like 'technical Contradiction' and 'physical Contradiction — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/triz-contradiction-coach.json
- FP-BRALI-SRC-d11d3976a6b8e45039dd: Frame Contradictions Using 'if — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/triz-if-then-contradictions.json
- FP-BRALI-SRC-862d4918789bb2a5afae: Identify Trade-Offs That Might Indicate a Contradiction — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/triz-trade-off-identification.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (useful_with): https://vedokrok.com/knowledge/do-not-turn-a-game-model-into-a-social-rule
