Going in dumb

That’s the strategy.


My daughter's been playing tennis for a while and we've been working on improving her forehand. It's genuinely really good. But there was a kink, a quirk, something preventing her from taking it to the next level. I asked her to walk me through it, to teach me, which grew suspicion seeing I'd been playing for much longer than she's been alive.

Somewhere in the middle of her teaching me, she stopped. "Wait," she said. "Why am I doing that?" She'd built a compensation into her swing somewhere along the way, a small adjustment that made the stroke work well enough that she'd never had reason to examine it.

She didn't find the problem by practicing harder. She found it by having to explain what she was doing to someone who was going to take her at her word.

I use a version of this everywhere.

When I walk into a room to understand how something actually works, I set the frame before the first question. Not the version that made it into the brief, the brand standards manual, or the official process doc. The real version. Treat me like the dumbest person here. Imagine you're onboarding a new employee who knows nothing about how this actually runs. Explain everything. Assume nothing.

What happens next is the point. Not because I get better answers, though I do. Because the person explaining starts working through something they've been doing on autopilot for so long they've stopped seeing it. And when you make the automatic conscious, things surface.

The frame you set before the conversation determines what the conversation actually produces.

The tell is a specific moment. It usually sounds like: "Yeah, I'm actually not sure why we do it that way." Press on that, gently and genuinely, and what you find underneath is almost never negligence. It's a workaround someone built years ago for a problem that may not even exist anymore, baked so thoroughly into the process that it stopped being a choice and started being just how it's done. Nobody challenged it. Nobody thought to. The person who knew why is probably long gone.

I warn people upfront that I'm going to be that kid. The one who keeps asking why, not about the steps, but about what the steps were built on top of. Why does this space work this way? Why is this how the guest moves through it? Why is this what we're measuring, or building, or asking people to walk through? Operational questions get asked constantly. The foundational ones almost never do. And the foundational ones are almost always where the actual problem has been living, quietly, for longer than anyone wants to admit.

What looks like a process problem is usually an assumption that never got questioned.

I used a version of this on job sites years ago. Someone would come to me stuck, looking for the answer. Instead of giving it, I'd say: imagine I'm unavailable for a week and this has to get done. Walk me through how you'd actually solve it. Almost every time, they'd talk their way to the answer before they finished the sentence. It was already there. The only thing keeping them from it was the assumption that someone else was supposed to provide it.

The same principle operates when a room hits a wall and every reasonable idea has been exhausted. The move that works more than it should is asking for the outlandish one, the idea nobody expects to survive contact with reality. Somewhere in the ridiculous version is usually a grain of something true. The bad idea points at the right constraints. The dumb frame does the same thing.


The goal isn't to perform not-knowing. It's to create the conditions where the person across from you has to work through the thing instead of handing you their conclusion about it.


And in the working through, things come out. The gaps, the workarounds, the assumptions baked so deep into how the problem's been framed that nobody thought to question them. Most of the time the people in the room already know what's true. They just haven't had a reason to say it in a way that made the pieces connect.

Giving them that reason is the whole job.

It doesn't require expertise or authority or a particular title. It requires walking in willing to say you don't know, and asking the question as if you mean it. Set the frame before the conversation starts. Tell people how to talk to you. Make it safe to start from the beginning.

The room will do the rest. Somewhere in the explaining and the teaching and the walking-it-back-to-the-start, the actual problem tends to introduce itself.

Usually it's not the one anyone came in to solve.

Previous
Previous

No mountaineering background. Just the decision to go.

Next
Next

Everyone nodded. Nobody actually understood.