Pre-Frame Architecture: Why the Invisible Move Wins the Room

His own team thought the results were luck. Nobody saw the actual move. That invisibility bothered me more than it should have, because the move was the whole thing.

That’s not preparation. That’s combat staging. And most CEOs walk into hard conversations doing exactly that: rehearsing three key points, sequencing arguments, loading evidence. None of it matters if the other person’s frame is already set against you.

The Pattern This Week

Let’s call him Marcus. He had a referral partner who thought the markup was unfair. Marcus never argued the point. He surfaced every reason the overall approach saves the partner’s clients money, slowly, as context, until that frame was the room they were both standing inside. The partner concluded the markup was fair on his own.

Marcus did that twice in one week, with two different people. Same invisible architecture both times.

The question he asked before each conversation wasn’t “What do I need to say?” It was “What does this person need to walk away believing?”

That shift is the difference between a conversation that lands and one where the other person digs in, the deal dies, or the partnership slowly frays. The failure mode isn’t conflict. It’s the other person walking away more entrenched than when they arrived.

The skill has a name: Pre-Frame Architecture. You decide the destination before the conversation departs. Three components, in order:

1. The Target Belief: what you want them to conclude, in their own words, as their own thought.
2. The Entry Point: never the contested ground.
3. The Oblique Path: evidence surfaced as context, not argument, so it gets absorbed instead of resisted.

Facts without a frame get interpreted inside whatever frame the other person already holds. That’s rarely the one you want.

Read the full piece: “Stop Preparing What to Say. Start Deciding What They Should Believe.” [LINK]

Pre-Frame Architecture is about external conversations. The next two patterns are what happens when a CEO hasn’t built the same architecture internally, for themselves.

Two Sharp Edges

Being indispensable to your company isn’t a strength. It’s a ceiling you built yourself.

A founder I coach runs several businesses with no dashboards, no standing reviews, no shared performance data. When I asked about one of them, the leader of that business was mentioned almost as an afterthought. The tell was one phrase: “I just haven’t activated people yet.” As if his team exists in standby mode until he flips a switch.

Every decision flows through one node. Remove him and the whole thing stalls. Your leaders should be giving you updates you didn’t ask for. Decisions should be getting made while you’re not in the room. If that sounds foreign, you’re still the relay.

The Sliding Permission Line: an operating tax with no end date.

A CEO I coach hit the cash milestone he’d been chasing for eighteen months. Late in our session he said: “It’ll probably be another year, another number, before I actually let myself enjoy it.” The milestone had already moved. Same anxiety, new address. No frame for what “enough” meant, so every result got interpreted inside a fear frame.

The company starts to mirror this. You delay the hire because it doesn’t feel safe yet. You hold the bonus because “let’s see one more quarter.” You build an org chart shaped by unresolved fear, not by what the business actually needs.

The fix is simple: write down what “enough” means in actual numbers, reviewed quarterly, revised only by intention, never by fear.

A Question Worth Sitting With

Marcus’s team thought the results were luck because they never saw the architecture. The move only works when you can name it yourself. If you can’t name it, it stays luck, and luck doesn’t scale.

Name one decision you’ve been calling “strategy” that is actually just delay. Hit reply and tell me what it is.

Jerry

---