# Write the need before naming the implementation

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

---

## Write the need before naming the implementation

ID: MHC-D-RESEARCH-0780 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/write-the-need-before-naming-the-implementation

A solution written too early can hide the requirement it was supposed to satisfy.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A requirement arrives already phrased as a feature, field, button, tool or technical solution and the underlying job is unclear.

### Avoid when

- Some implementation choices are genuine constraints because of standards, contracts, architecture or interoperability; label the source of that constraint.

### Explanation

Ask why the requested implementation is needed and write the desired capability or outcome separately. Keep hard constraints, but distinguish them from a proposed way to meet the need. Only then compare solution options.

### Steps

1. The requirement still makes sense if the first proposed implementation is replaced by another feasible approach.

### Example

'Add an Excel export button' becomes 'Users need to reconcile selected records outside the system without manual re-entry'; export is then one candidate solution.

### Check

The requirement still makes sense if the first proposed implementation is replaced by another feasible approach.

### Limits

- Some implementation choices are genuine constraints because of standards, contracts, architecture or interoperability; label the source of that constraint.

### Evidence and sources

- supports: NASA guidance recommends requirements that identify the responsible product or party and needed behavior, use consistent terminology, state what is needed rather than prescribing implementation, and include rationale and assumptions. — RS-A059268EF3F10749. Some constraints legitimately specify implementation when mandated by architecture, regulation or compatibility. (Editorial checklist; general goodness checklist)
- supports: GOV.UK user-story guidance recommends recording the actor, needed action and goal, focusing on why the need exists, and using acceptance criteria to state observable outcomes that show the job is done. — RS-AA4CF71A3FB24D22. User-story syntax is one framing method and is not appropriate for every technical, regulatory or infrastructure requirement. (What to include; Focus on the goal; Acceptance criteria)
- RS-A059268EF3F10749: Appendix C: How to Write a Good Requirement — https://www.nasa.gov/reference/appendix-c-how-to-write-a-good-requirement/
- RS-AA4CF71A3FB24D22: Writing user stories — https://www.gov.uk/service-manual/agile-delivery/writing-user-stories

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/give-each-requirement-one-behavior-to-prove
