Protocol

Follow labels with observable detail

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

About 1 min read

Before you use it

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

Keep this limit in mind

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

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

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?

An example

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

Check your result

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

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingFollow labels with observable detail

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.

Neutral wording reduces one source of bias but does not make interview evidence objective or representative by itself.

Using in-depth interviews · Do the interview

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details