# Ask for the last real example before asking for the usual process

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

---

## Ask for the last real example before asking for the usual process

ID: MHC-D-RESEARCH-0751 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/ask-for-the-last-real-example-before-asking-for-the-usual-process

A recent episode has edges that a generic process description can hide.

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

### Use when

- Someone describes what normally, usually or ideally happens and the answer sounds clean but unauditable.

### Avoid when

- One episode is not a frequency estimate. Use more cases or other data before generalising.

### Explanation

Ask for the most recent concrete instance: when it happened, what triggered it, what the person did, what happened next and what artifact remains. Compare that episode with their general description only after the sequence is clear.

### Example

A user says approvals are 'normally quick'; the last approval took two days because the owner was unclear.

### Check

The answer contains a specific episode with sequence and observable details, not only a policy or preference.

### Limits

- One episode is not a frequency estimate. Use more cases or other data before generalising.

### 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.
Related (useful_with): https://vedokrok.com/knowledge/build-the-sequence-before-asking-for-the-cause
