CX Methods
The six behavioral lenses of task observation
The steps are not the insight. The tools, knowledge, workarounds, issues, concerns, and obstacles around the steps are.
Most task observation fails by documenting only the happy path: the steps a customer takes when everything works. The real signal sits around the steps, in six behavioral categories that reveal unmet needs, automation openings, and the friction customers never report.
Watch a customer complete a task and you will see two stories. The first is the sequence of steps, and it is usually unremarkable. The second is everything happening around those steps: the customer opens a calculator, checks a note on their phone, googles a term your product assumed they knew, invents a workaround, hesitates before clicking, or stalls entirely. Six behavioral lenses capture that second story: the tools people reach for, the knowledge they must already possess, the workarounds they invent, the issues that create friction, the concerns and doubts they voice, and the obstacles that halt progress. Documenting all six every time turns a session recording into a map of unmet needs.
Why it matters to the business
Customers rarely tell you about any of this. ThinkJar research by Esteban Kolsky found only 1 in 26 unhappy customers complains; the rest leave silently. A workaround is a complaint the customer filed with themselves, and it never reaches your dashboard. The lenses also flag effort, and effort is expensive: CEB research reported in The Effortless Experience found 96% of customers become more disloyal after high-effort interactions, versus 9% after low-effort ones. Every spreadsheet a customer builds to use your product is effort you will eventually pay for in churn or support volume.
How to use it
- Add the six lenses as columns in your observation notes: tools, knowledge, workarounds, issues, concerns, obstacles.
- In every session, log each time the customer leaves your product for another tab, a calculator, or a phone note.
- Interrogate every workaround: what should the system have done so it was never needed?
- Have customers think aloud; voiced doubts predict abandonment even when the task technically succeeds.
- Convert each finding into a backlog item: absorb the tool, encode the knowledge, remove the obstacle.
Where teams get it wrong
Teams record clicks and completion, declare the flow passed, and file the study. But a customer who completed the task using two browser tabs, a calculator, and a phone call to a friend did not have a good experience. They rescued your product from failure, and success-rate metrics alone hide the rescue.
Ask your team
- What tools do customers reach for while using our product, and why haven't we absorbed them?
- What is the most common workaround our customers have invented, and who owns removing the need for it?
- In our last research readout, which findings were about the steps, and which were about what happened around them?
A workaround is a complaint the customer filed with themselves.
Apply this
Reading about the six behavioral lenses of task observation is one thing. Seeing where it applies in your journey is the useful part.