
Sometimes you're simply too close to a problem.
The change isn't landing. The backlog isn't improving. People have created workarounds. You've tried the obvious solution and nothing much has changed.
Perhaps it's worth taking another look.

There's no particular type of problem you need to bring. I'm interested in the ones where the obvious explanation doesn't quite fit what's happening.
The backlog
You've added resources. It's still there.
The change
You've communicated, trained and supported. It's still not landing.
The workaround
People aren't following the official process. Why?
The restructure
The boxes moved. The problems didn't.
The capability problem
You've provided training. Nothing much has changed.
The conflicting stories
Two parts of the organisation describe the same process completely differently.
Or perhaps you can't quite articulate the problem yet. You just know something doesn't make sense.
Tell me briefly what's happening and I'll let you know whether it sounds like a good fit for a Second Look.

Tell me what's happening. Send me up to five existing things that might help me understand it.
Please don't create anything especially for me. What already exists is usually more interesting.

We explore the problem together, usually with one or two people.
I'll ask questions, test assumptions, look for patterns and pay attention to what doesn't quite fit.

I'll send you a concise Second Look Summary capturing what emerged, what I'd be cautious about concluding, and what deserves attention next.
90-minute session · pre-reading of up to five existing items · written Second Look Summary within 48 hours.
No obligation for further work. Sometimes a second look is all you need.
Before deciding what the problem means, I want to separate what we're observing from how we've interpreted it.
A backlog becomes a resourcing problem. A behaviour becomes resistance. A mistake becomes a capability problem. But that's already an interpretation.
What evidence supports that explanation and what might challenge it?
Different experiences of the same problem aren't necessarily contradictions to resolve. The differences themselves can tell us something.
I'm interested in the exceptions, workarounds and inconvenient bits of information that don't fit neatly with our explanation.
If we're not seeing it, that's worth another look. 🔎
How the problem currently appears, including the different perspectives you've shared.
Patterns, contradictions, exceptions and things that deserve more attention.
Where the evidence doesn't yet support the explanation, or where we may be making assumptions.
Alternative explanations or hypotheses worth considering, not claims dressed up as certainty.
Questions, evidence, conversations or observations that could help make things clearer.
Three practical next moves: what deserves attention now, what could be tested and what you need to understand better.