From Insight to Behaviour
The ladder between knowing and doing.
Research teams know this particular grief. The study was solid. The finding was true. The presentation landed well, people leaned in, someone said this is really useful. Then everyone walked back to their desks and built the thing they were always going to build. The insight was admired and abandoned in the same afternoon.
It happens for a reason that has nothing to do with the quality of the thinking. Insight arrives as a description of the world. A team has to act in the world, and action needs an instruction. Between the description and the instruction sits a conversion step, and most presentations never attempt it. They deliver the forecast and leave before anyone is told to take an umbrella.
Why insight dies in slides
Consider two sentences about the same problem. The first: users find the process confusing. True, tidy, and completely inert. Nobody in the room now knows what to do differently tomorrow, so tomorrow looks exactly like yesterday. The second: the design must let people save and return without penalty, because people abandon at the moment they are asked for documents they do not have to hand. Now a designer can act. They can build something, and be wrong in a useful, correctable way.
Insight describes the world. Behaviour needs an instruction. Insight needs a verb.
The ladder
The distance from a true finding to a changed behaviour is not one leap. It is seven rungs, and each one converts the thing below it into something more usable. Miss a rung and the work falls through the gap.
- Insight
- What you learned, in one honest sentence, with the evidence behind it.
- Interpretation
- What the behaviour is doing for people. The job it holds, the payment it makes. This is the most-skipped rung, and skipping it is why so many interventions fight the wrong thing.
- Design principle
- What any solution must make easier, safer, clearer or more rewarding. Deliberately solution-agnostic, so it can outlive the first idea.
- Intervention idea
- A concrete change to conditions. Something you could point at in a room.
- Prototype
- The smallest version that stages a real action. One screen, one script, one changed moment.
- Test
- Where reality disagrees, found cheaply. Action watched, not opinion collected.
- Rollout
- Trying made safe, repeating made likely, recovery made ordinary.
Watch a single idea climb. Insight: users quit at the evidence step. Interpretation: gathering documents mid-flow feels risky and effortful, so people leave to protect themselves. Principle: make providing evidence staged and safe. Idea: accept a photo now and the formal document later. Prototype: one mocked-up screen. Test: do more people finish? Rollout: staged, with a gentle prompt for anyone who drops. Same idea throughout, just made progressively more real.
What a good recommendation looks like
Weak recommendations share a tell, and once you can hear it you cannot unhear it. They could be posted to any organisation on earth, unchanged, and still sound wise. Improve communication. Foster a culture of trust. Increase engagement. These are not recommendations. They are the sounds a recommendation makes on its way to being written.
The move nobody proposes
There are four things you can recommend: build something, change something, remove something, or test something. Teams reach for the first two almost every time, because additions are visible and someone gets to own them. Removal is the neglected move, and it is often the most powerful and the cheapest.
Get the full guide
The complete guide, with worked examples, the running order for a team session, and all the detail the excerpt leaves out, is available as a free PDF.
Free. No spam. One email with your download link.