Terrain Scan

Open with a question and take whatever comes back raw. Interpretation happens two steps from here, and asking for it now gets you conclusions instead of observations.

Three questions that open it: → What's changing outside our organization that could affect us? → What are we seeing in customers, competitors, or adjacent industries? → What feels different, even if we can't explain it yet?

Observations come from anywhere: an article, a shift in how a customer buys, a competitor's hiring, a technology development, a regulatory conversation, or something internal that doesn't fit the pattern.

The rule that makes this work: nothing here has to be proven. It only has to be noticed. The moment people feel they have to defend an observation, they stop offering them, and you're left with whatever was safe enough to say out loud.

No slides, no pre-work. Preparing for this turns it into a report-out.

A single signal is easy to dismiss, and usually should be. Patterns are what earn attention.

Put this session's observations next to the ones from previous sessions. Something that appeared once in March and three times in May has started to say something, and the frequency is the information.

This requires a running list. Without one you'll re-notice the same thing every month and never watch it accumulate.

Ask: → Are we seeing this in more than one place? → Is it increasing in frequency or intensity? → Are different signals pointing at the same underlying shift?

Watch for: clusters arriving from unrelated sources. When a customer comment, a competitor's job posting, and a regulatory conversation all point the same direction, that's the strongest indicator available that something real is moving.

Interpretation is the easiest step to skip and the one that produces the advantage. A signal without it is noise with a timestamp.

You're building a working point of view. It should be specific enough to be wrong.

Ask: → If this continues, what could it mean for us? → Where would it touch our strategy, our operations, or our talent? → What assumption of ours does it challenge?

That third question is the one that gets skipped, and it's the only one capable of producing an answer you didn't already hold. Interpretation run inside your existing assumptions will return your existing assumptions.

When something looks consequential, take it through three futures before deciding anything: what if it creates an opportunity, what's most likely, and what if it disrupts us. Holding all three keeps the team out of arguing over whether it will happen at all, which is the argument that eats the meeting.

Match the response to what you actually know, which at this point is not much. Keep the move small.

Small moves are the point. They're cheap, they generate information you can't get by thinking harder, and they put you in motion while competitors are still waiting to be certain.

What a small move looks like: → Run a contained experiment → Shift a priority for the next 30 days → Assign one person to track the signal and report back → Start a conversation with a customer or partner you weren't having before

Early and small beats late and large. Then close the loop. Bring the signal back to the next scan and say what the move produced, because a scan that never revisits its own calls never gets better at making them.