Trust Framing: How to Help a Client Be Smarter

The skill clients remember you for. Also the one that scares me most.

Trust framing is the third of the four trust skills. The move is simple to describe and hard to do: say your draft of the client's problem out loud, in their language, before you're sure of it, and let them fix it until it's theirs.

The payoff is the reason clients keep you around. They leave the meeting feeling smarter about their own problem. And a frame the client helped build gets carried into rooms you will never be in: their leadership meeting, their board, their budget conversation. That's how one good frame turns into a relationship.

Many professionals avoid the vulnerability of out-loud framing with their clients. They take notes, nod, say "great, we'll get back to you," and go build a solution to what they think the problem is. Then they spend all their energy selling that solution. That's where the trust leaks out.

Reporting is not framing

When I was a junior ad guy, the call report was drilled into me. Within an hour of any client meeting you sent your notes: what was discussed, what happens next. Proof I attended the meeting. And almost completely useless. Especially today in the age of AI notetaking.

Reporting sounds like this: "You need the agreement drafted by Friday. Your board wants options before the quarter closes. Your CFO wants the numbers restated."

Every word true. Nothing in it the client didn't already know when they walked in.

Trust framing does a different job. It organizes the reality underneath the request and reflects it back in language the client recognizes as true. It simplifies the mess without pretending it isn't messy. It names the trade-offs. It points forward.

Why it's the hardest of the four

As I said above, this is the skill I find hardest. Not because the concept is complicated. Because it requires me to say my understanding out loud before I'm sure of it. In front of the client. And then let them correct me.

Old me avoided that risk by going straight to reporting and recommendations. It felt safer. It felt smarter. It actually sucks. A lot. This is where my self-orientation loves to cheat: skip the draft, jump to the answer, keep the conversation about what I know.

First-draft frames are often wrong or at least not quite right. I've learned that isn't the failure. It's the success of this approach. When the client corrects my frame, they're taking ownership of it. They are opening up. They are collaborating with me. Clients never remember my first attempt. They remember where we ended up. Together.

So the frame is never a verdict. It's a working hypothesis, offered out loud. Here is an example:

"Let me test a frame with you. I might be off, but this is what I think I'm hearing. The core issue isn't just that the brief is late. It's that the scope changed, the budget owner is on leave, and the team doesn't have what it needs to approve anything. Does that match what you see? What am I missing?"

The four-line frame

The version I teach my team runs four lines. You can use them in almost any room.

1. I heard you say the problem is ___. (their words)

2. It feels like ___ might matter here. (the thing they didn't say)

3. Which means a key challenge is ___. (what that forces them to deal with)

4. What am I missing?

Line one proves I listened. Lines two and three prove I understood. Line four hands them the pen. Most of the time they pick it up, fix one of my blanks, and the frame becomes theirs. That is the win.

What it looks like when someone is good at it

My business partner Nolin is the best framer I've ever watched. Where I used to fill silences with recommendations, he fills them with questions. Open ones. Patient ones. Then a draft frame. Then more questions. Until the client grabs the language and runs with it.

I watched him on a call with the leader of an in-house agency. She came in frustrated and defensive: heat from her stakeholders, complaints about process, responsiveness, delivery quality. Most of us would have jumped to fixes. New process. Better project management tools. A stakeholder communication plan.

Nolin asked where the heat was coming from. What people said when the boss wasn't in the room. What the process looked like on a good day. Then, after a few minutes:

"What I'm hearing might not be a process problem. It could be a prioritization problem. Your team is doing strong work, I heard that clearly. But the way the work is sequenced doesn't seem to reflect your organization's current priorities. My hunch is your critics aren't frustrated with the output. They're frustrated their priorities aren't at the top of the list. Does that make sense?"

She went quiet. Then: "That's exactly it. And those priorities don't even match the budgets we put in place. This isn't a process issue at all. I think I know what we need to do."

Nolin didn't invent the answer. It was already there in everything she'd told him. He listened carefully enough to find the frame that made it visible. She went back to her team, realigned the work against the priorities that mattered, and the heat went away.

You are the outsider. That's the point.

Notice what Nolin brought to that call. Not expertise in her process. Distance from it. She couldn't see her problem clearly because she was standing inside it. He could, because he wasn't.

That is the part of trust framing most professionals undervalue. We think our job is to know more than the client. Our advantage is that we know less, and we're outside the building.

There's a well-worn illustration of this. A building owner gets complaints that the elevator is too slow. The engineers propose a faster motor, a new elevator, smarter software.

Someone from outside the engineering conversation asks a different question: what if the problem isn't the speed, it's that the wait feels long?

So the owner installed mirrors by the doors (yup, that's why they are there; we are all so self-oriented by nature that looking at our reflection helps time speed up). Complaints dropped after an outsider proposed an alternative framing of the "slow elevator" problem.

Organizations are bad at diagnosing problems

A survey of 106 senior executives across 17 countries found 85 percent said their organizations were bad at diagnosing problems, and 87 percent said that failure carried real costs. The pattern the author found was consistent: smart people rush into solution mode before they've checked whether they've got the problem right. And two of his recommended fixes are the skill in this post. Bring in outsiders who understand the situation but don't live inside it. Then ask what's missing.

Your client's team has already tried to solve their problem with the frame they've got. If that frame worked, they wouldn't need you. So the draft you offer isn't a guess at the one true problem. It's an alternative frame, from outside, that might be a better problem to solve. Sometimes it's wrong and they fix it. Sometimes it's the mirrors.

Either way, you don't get there by taking notes.

The proof

The proof of a good frame isn't a polite nod. It's when the client starts using the language themselves. When they take the frame you built together into their own internal meeting and present it as their thinking. Every time it happens, it feels great for everyone in the room.

That's the moment I know I've crossed from asshole to ally. Not because I was clever. Because I helped my client feel smarter.

Try it once this week. Say, "Let me test a frame with you. I might be off." Then notice how differently the meeting feels.