Curiosity Walk Exercise

A director of data strategy has built her professional reputation on pattern recognition. She is sharp, fast, and often right. Over two years in her current role, her team has noticed — and her manager has named in feedback — that she has become less curious and more conclusory: she brings analysis, not questions, and she has stopped being surprised by things. She dismisses this characterization as efficiency. Her coach suspects her analytical strength has calcified into a closed system.

Frame this as a capability maintenance exercise, not a remediation. 'You've built strong analytical capacity by finding patterns. The risk with pattern recognition as a dominant mode is that you stop seeing what doesn't fit the patterns — which is usually where the most important information lives. This is a structured way to practice the anterior step: observation before analysis.' Framing it as skill maintenance rather than behavior correction reduces the defensive response from clients who experience their analytical style as an asset.

The observation walk has two distinct steps: a timed observation session and What-If question generation. Watch whether the client completes the observation step with sensory specificity — 'a cluster of three people standing at the far corner of the floor, not talking' — or with analytical labels — 'two employees who looked disengaged.' Labels indicate that analysis is happening simultaneously with observation, which collapses the two-step structure. The goal is raw observation first. Also watch the What-If questions: thin or generic questions ('What if people were more engaged?') indicate the observation step didn't generate specific-enough data.

Start with the observations, not the What-If questions. 'Read me two or three things you noticed that surprised you or that you hadn't seen before.' Surprise is the signal that the observation was genuinely new — not confirmation of a pattern she already held. Then move to the What-If questions: 'Which one of these would be worth actually investigating? What would you learn if you asked it directly?'

A VP of Operations is taking on strategic oversight of a business unit in a sector she doesn't know. She is preparing through research — reading industry reports, studying competitors, talking to analysts. She has not yet spent time in the spaces where the business actually operates: the factory floor, the retail locations, the customer service center. Her preparation is comprehensive but secondhand. Her coach wants to shift the ratio.

Position the observation walk as a preparation method rather than an alternative to her current approach. 'The research you've done gives you the vocabulary. This exercise gives you the actual material. Before your first cross-functional review, spend 90 minutes in one of the locations and document what you observe — not what you expect to see or what you know about the industry, what is actually in front of you. Then bring what surprised you.' The specific instruction to document 'what surprised you' frames the exercise as information-gathering rather than validation.

The quality of the observation entries tells you whether the client is genuinely encountering the environment or confirming what she already learned in her research. Entries that match her pre-existing knowledge — 'the assembly line follows the standard process' — suggest she is looking for confirmation. Entries that describe specifics she didn't expect — 'the team lead was translating between English and Spanish on the floor, which isn't mentioned in any of the process documentation' — suggest genuine encounter. Push for the unexpected.

After she completes the walk, start with: 'What did you see that you couldn't have gotten from the reports?' That question draws out the unique value of direct observation. Then connect to the What-If questions: 'Which of these questions are you most curious to answer before your first review with this team?' This moves the observation toward preparation, which is where the payoff is for this client.

A senior manager on a product innovation team describes a six-month creative block. He used to generate ideas consistently; now he edits existing ideas and responds to others' proposals rather than initiating. He attributes this to being 'too close to the work' and 'too tired' but hasn't changed his approach to information input — he reads the same sources, attends the same meetings, and moves between the same environments every day.

Frame this as a cognitive environment change rather than a creativity exercise. 'Creative blocks are often environmental — the same inputs produce the same outputs. This exercise is about changing your inputs for 60 minutes in a deliberate way: going somewhere you don't normally go, observing without an analytical objective, and generating What-If questions from what you see. The mechanism isn't inspiration; it's cross-contamination of domains.' The word 'mechanism' matters for analytically oriented clients — it makes the exercise feel rigorous rather than wishful.

The location choice is diagnostic. Clients who choose environments adjacent to their current domain — a similar office building, a competitor's retail location — are seeking confirmation rather than genuine novelty. The observation walk works best when the environment has no obvious relationship to the client's work: a farmers market, a construction site, a hospital waiting area. If he chooses an adjacent environment, note it and ask what would feel genuinely unfamiliar.

Start with the What-If questions. 'Read me the one that surprised you — the one you didn't expect to think of.' Then ask: 'Which of these could be translated into a question about your current product context?' The translation step is where the creative value lives — it requires the client to hold two domains simultaneously, which is what creative insight typically involves. Don't skip this step; many clients stop at the observation and miss the transfer.