# Follow labels with observable detail

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

---

## Follow labels with observable detail

ID: MHC-D-RESEARCH-0753 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/follow-labels-with-observable-detail

A label is the start of a question, not the end of one.

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

### Use when

- An answer depends on words such as slow, confusing, risky, difficult, unreliable or often.

### Avoid when

- Not every experience needs a metric. Feelings and perceptions can themselves be relevant data; label them as such.

### Explanation

Treat evaluative words as pointers. Ask what the person observed, how long or how many when measurable, what action became difficult, and what comparison makes the label meaningful. Preserve their wording in notes but add the evidence behind it.

### Steps

1. What did you observe that made it feel [label]?
2. What happened next?
3. Compared with what?
4. Is there a time, count, artifact or example that shows it?

### Example

'The interface is slow' becomes 'Saving took about 18 seconds in yesterday's batch, versus 3–4 seconds last week.'

### Check

The note can be challenged or verified without debating the meaning of the adjective alone.

### Limits

- Not every experience needs a metric. Feelings and perceptions can themselves be relevant data; label them as such.

### Evidence and sources

- supports: GOV.UK interview guidance recommends open, neutral questions, asking for real stories and examples, listening carefully, and using follow-ups when meaning is unclear. — RS-8C87115E8FFA48A7. Neutral wording reduces one source of bias but does not make interview evidence objective or representative by itself. (Do the interview)
- RS-8C87115E8FFA48A7: Using in-depth interviews — https://www.gov.uk/service-manual/user-research/using-in-depth-interviews

No review details supplied.
