The person who defines the problem controls the room. Not because they’re the loudest or the most senior, but because everyone else is responding to their version of reality.
What Setting the Frame Looks Like
“Every project needs one owner from start to finish. Right now nobody owns the work end to end. Tasks get handed to teams, not people. Handoffs get messy. By the end, no one is on the hook. That’s why we’re missing deadlines.”
If the room accepts that definition, everything that follows stays inside it. The conversation becomes about who owns what, where ownership breaks down, and how to assign it. The direction is set before the debate begins.
Barbara Minto called this the Pyramid Principle. State your conclusion first, then support it. I have used it and it works, but when I dug deeper I realized that what this does is control the frame that is used to evaluate what is being discussed. Control the frame, and you control the argument. Control the argument, and you control the room.
The Counter-Move
Here’s what most people miss. A tight argument doesn’t make the problem definition right. It makes it persuasive. Those are different things.
If you’re on the receiving end of someone else’s frame, you owe it to the room to test the definition. A well-packaged argument isn’t the same as a correct one.
The way to do that is to step outside the frame and question the definition itself.
“What does own the work end to end actually mean here?”
“Does this only work if one person owns everything, or are there other ways to create accountability?”
“If ownership is the issue, how have we hit deadlines before?”
How you ask these questions depends on where you sit in the room. The questions are the same whether you’re a peer or a level above. If you’re a level below, the approach needs to read the room. The intent is the same. The delivery has to be calibrated. This often means you need to hedge a little like this: “Just so I am clear on this, if ownership is the issue, how have we hit deadlines before?”
Now you’re not debating the solution. You’re testing whether the problem was defined correctly. That’s a different conversation and a more useful one.
What You’re Also Testing
When you push on someone’s frame, you’re doing two things at once.
You’re testing the logic.
Does the definition hold up when you pull on it?
Are the constraints real or assumed?
Is the conclusion actually supported by what’s underneath it?
You’re also testing the person.
Can they define the problem clearly when asked?
Can they adjust when pushed, or do they just repeat the same line louder?
Do they have answers to the obvious objections, or does the frame collapse the moment someone questions it?
That’s the difference between someone who has worked the problem and someone who is presenting an answer they arrived at before they walked in the room. In modern times this is the “Did AI do this for you” test.
We were having a new piece of equipment installed in the factory to automate part of the process. Engineering came in, detailed the timeline, and finished with: everything has to be bolted to the floor and running by end of Q4 this year.
I asked what happens if it isn’t installed by then. They said it will be.
So I pushed on the frame. “Of the last three projects you’ve done, how many were delivered on the timeline provided at this point in the process?”
They tried to explain why there had been issues on those projects. I asked the question again. Their answer was zero.
I said that since we hadn’t been able to hit the timeline on the last three projects, we needed to add to the plan what happens if this lands in Q1 or Q2 of next year. There was some squawking and upset faces in the room.
Then the room agreed it was needed before anyone signed off.
When the frame doesn’t hold, the work goes back. The meeting isn’t the place to rebuild the problem definition on the fly. Most organizations already have a process for this. Use it.
This is not about challenging the person. It’s due diligence. You’re working the problem they presented from outside their frame to see if it holds up. The best questions come from genuine curiosity about whether the definition is solid, not from a desire to win the room.
Separate the person from the data. You’re not trying to prove them wrong. You’re trying to find the best solution, not your solution or theirs. The goal is that the person presenting walks away believing the exchange was tough but fair.
Both Sides of the Table
Whether you’re the one setting the frame or the one receiving it, the same principle applies. The quality of the conversation depends on the quality of the problem definition.
If you’re presenting, do the work before you walk in. Define the problem specifically. Know what you’re willing to defend and where you have gaps. Get comfortable asking yourself before you get in the room: “What breaks my argument?”
If you’re evaluating, don’t accept the frame just because it’s well packaged. A confident delivery and a clean structure are not evidence that the problem is right. Ask the questions. See what holds. Push on the frame and make sure the data still works. Remember you are pushing the frame not the person here.
The room will move fast once a frame is accepted. It’s much harder to redefine the problem after the conversation has been running for twenty minutes than it is to slow down at the start and make sure you’re solving the right thing.
Often managers are on both sides of this in the same week. Monday you’re presenting your analysis. Wednesday you’re sitting across from someone else’s. The move is the same either way. Know which seat you’re in before the meeting starts, and do the work that seat requires.
If you’re setting the frame, ask yourself what breaks your argument before someone else does.
If you’re testing someone else’s, separate the person from the data and push on the frame until you know whether the definition holds.
The frame gets set in the first few minutes. After that the conversation is downstream of it.
The frame controls the conversation. Know which side of it you’re on, and what that side requires of you.

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.