# Separate what happened, what it meant and what should change

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Separate what happened, what it meant and what should change

ID: MHC-D-RESEARCH-0757 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/separate-what-happened-what-it-meant-and-what-should-change

Evidence, meaning and action are different layers.

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

### Use when

- Notes mix observations, interpretation and recommendations so later readers cannot tell which part came from the source.

### Avoid when

- Direct quotations can still be misunderstood; context and consent rules remain important.

### Explanation

Capture three fields separately. Observation: what was said, done or recorded. Interpretation: your current explanation. Implication: what you might test or change. This preserves traceability and makes later disagreement productive.

### Template

Observed: [trace/behavior/statement]. Interpreted as: [current explanation]. Next test/action: [what would reduce uncertainty].

### Example

Observed: user reopened the export twice. Interpretation: they may not trust completion. Next: ask what signal they expected and test status visibility.

### Check

Another reviewer can accept the observation while rejecting your interpretation without rewriting the record.

### Limits

- Direct quotations can still be misunderstood; context and consent rules remain important.

### Evidence and sources

- supports: GOV.UK interview guidance recommends starting from research questions, organising topics, and preparing starter plus follow-up questions rather than improvising the whole session. — RS-8C87115E8FFA48A7. A discussion guide should support rather than rigidly control the conversation. (Design the interview)
- supports: GOV.UK planning guidance recommends clear, actionable research objectives linked to assumptions and information needed for upcoming decisions. — RS-49C81944D7E6105A. Some exploratory work legitimately starts without a single immediate decision. (Research objectives and assumptions)
- RS-8C87115E8FFA48A7: Using in-depth interviews — https://www.gov.uk/service-manual/user-research/using-in-depth-interviews
- RS-49C81944D7E6105A: Plan a round of user research — https://www.gov.uk/service-manual/user-research/plan-round-of-user-research

### Vedokrok editorial review

Keep the observation separate from the explanation

A note should let another reader accept what was observed while questioning what you think it means. Keep the proposed change separate too.

#### Preserve the evidence’s status

Record what you directly saw, what a participant reported, or what a named artifact shows. Then write the interpretation as a separate, revisable explanation and the implication as a possible next test or change. Hearing someone describe a failure establishes that they reported it; it does not by itself establish the failure’s cause.

#### Let a different explanation survive

Suppose someone says an export disappeared. Record that report without silently turning it into an observed deletion. Possible explanations include an expired download or a different destination folder. The next step is to inspect an authorized event record or reproduce the sequence, not immediately redesign deletion behavior. Keep the source and any uncertainty with the note.

**Editorial takeaway:** Check whether a reviewer can replace the interpretation or proposed action without rewriting the underlying observation. Follow consent and privacy rules for notes and recordings; a quotation is evidence of a statement, not automatic proof of its contents.

#### Editorial evidence

- supports: GDS separates extracting observed or heard details from determining findings and deciding what to change or research next. — gds-analyse-research-session. Selected official passages inspected on 2026-10-04. This is a more direct basis for the three-way distinction than the original interview-planning references. The disappeared-export example is independently authored. (Extract observations; Determine findings; Decide actions)
- limits: The guidance organizes observations, interpretations and possible actions; it is a method of research analysis rather than independent verification of a participant’s account. — gds-analyse-research-session. The reported-versus-observed warning is an explicit editorial inference from these categories, not an experimentally measured effect or a quotation. (Extract observations steps2–4; Determine findings; Decide actions)
- limits: Research notes and recordings must be handled within consent and privacy arrangements. — gds-research-notes-recording. Useful traceability does not authorize broader collection or sharing. No participant data were collected in preparing this card. (Privacy and consent; Taking notes, What to record)
- gds-analyse-research-session: Analyse a research session — https://www.gov.uk/service-manual/user-research/analyse-a-research-session
- gds-research-notes-recording: Taking notes and recording user research sessions — https://www.gov.uk/service-manual/user-research/taking-notes-and-recording-user-research-sessions

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
