Chapter 4 · Part Two: The Comfort Check
I don’t like frameworks.
I’ve sat through the four-quadrant matrix, the five forces, the pyramid with the triangle inside it, the wheel with eight spokes and a verb on each one. I have also built a few, which is how I know what they’re usually for. Most marketing frameworks aren’t instruments for thinking. They’re instruments for presenting, and the giveaway is that they’re almost always beautiful. You can tell a framework was designed to be projected because somebody spent time on the icons.
A framework you present is a framework that requires an audience, a meeting, and a slot on somebody’s calendar. Which means it gets used roughly four times a year, at planning, by the people who already had the authority to change things.
So what follows isn’t a framework. It’s a check, in the sense that a pilot runs a check: fast, unglamorous, the same every time, and run before the thing rather than about the thing.
You met it in the front matter. Here it’s again, because it’s the spine of the rest of this book and you should be sick of it by the end.
The Comfort Check
1. What’s the comfortable assumption?
2. What’s the true objective?
3. What’s the redesigned approach?
Three questions. It fits on an index card. It takes four minutes. You can run it silently, in a meeting, without telling anybody you’re running it.
Why three
Because four is where a tool stops getting used.
I’m not being cute about that. Anything you can hold in your head while somebody else is talking gets used constantly, and anything that requires you to open a document gets used at planning offsites. The entire value of this thing is that it’s available at the moment the comfortable choice is being made, which is usually a Tuesday, in a conversation nobody scheduled, when somebody says “we’ll just do what we did last year” and everybody moves on to the next agenda item.
There’s a longer version of this method. I use it myself and I’ll give it to you: observe, interpret, simplify, amplify, measure. Five steps, genuinely useful, and it describes what actually happened across most of the campaigns in Part Three.
I keep it off the index card on purpose. Five steps is a process, and a process needs a project, and a project needs a budget. The three questions need a pen.
Why it’s a check and not a review
The distinction that matters most: run it before, not after.
A Comfort Check run after the work exists is a critique, and critique arrives too late to do anything but wound. By the time there’s a deck, somebody has spent three weeks on it, three other people have given notes, and the assumption you’re about to question is now load-bearing for everybody’s calendar. You won’t win that argument, and you shouldn’t, because the cost of being right at that point exceeds the value of it.
Run before the work exists, the same three questions cost nothing, because nobody has anything invested in the answer yet. Question one, asked at the start of a project, is a conversation. Asked at the end, it’s an accusation.
The practical version: the check belongs in the fifteen minutes after somebody says “we should do X” and before anybody opens a file.
Why it starts with the assumption
The order isn’t arbitrary. In 1984, Charles Lord, Mark Lepper and Elizabeth Preston at Stanford tested ways to get people past their own biases when they weighed evidence. Telling people to be fair and unbiased helped far less than you’d think. What worked better was one specific instruction: consider the opposite. Ask how you’d judge the same evidence if it had pointed the other way.
That’s question one. Naming the comfortable assumption is what makes its opposite thinkable, and you can’t consider the opposite of something you never wrote down.
The three ways people get it wrong
I’ve watched this run badly enough times to describe the failure modes precisely.
Failure one: answering question one with a strategy.
Ask a team for their comfortable assumption and they’ll tell you their plan. “We assume that our buyer is the CISO.” That’s a targeting decision. It might be wrong, but it’s a decision somebody made out loud, in a document, and can defend.
A comfortable assumption isn’t a decision. It’s the thing underneath the decision that nobody voted on. Not “we assume our buyer is the CISO” but “we assume the way to reach a CISO is content.” Not “we sponsor Black Hat” but “we assume a presence at the show is how a company our size becomes known.”
The test: if you can name the meeting where it was decided, it isn’t a comfortable assumption. You’re looking for the ones with no meeting.
Failure two: answering question two with an activity wearing a suit.
“Our true objective is to generate qualified pipeline.” That’s an activity with a number attached to it. Pipeline is a thing your organization produces, not a thing the market experiences.
The tell is in Chapter 6 and it’s this: if you could achieve it in full while the business got worse, it’s an activity. You can generate a great deal of qualified pipeline while remaining a company nobody can describe.
Failure three: answering question three with the thing you already wanted to do.
This is the most common and the hardest to catch in yourself, because it feels like the check worked. You had an idea before you started. You ran three questions. Your idea came out the other end. What a useful tool.
The protection is mechanical: question three has to produce at least two answers, one of which you don’t like. If the redesigned approach is a single option and it’s the option you walked in with, you haven’t redesigned anything. You have laundered a preference through a process, which is a thing marketing departments are world-class at.
Running it on work that isn’t yours
Most readers of this book will want to run this on somebody else’s project, which is a delicate business, because questions one and two are both, in the wrong tone, an accusation of not having thought about it.
Three rules that keep you employed.
1. Ask question two first, out loud, and question one only to yourself. “What are we actually trying to make happen here?” is a helpful question from any seat in the room. “What are we assuming that nobody has examined?” from a junior person is a career event. Get the objective on the table, and the assumption usually walks out on its own, because people can’t state an outcome and defend an activity in the same breath for very long.
2. Attribute the doubt to the work, never to the room. Not “I think we’re assuming X.” Try “if somebody outside the company looked at this, would they be able to tell it apart from the obvious version?” Same question. Nobody has to be wrong for it to get answered.
3. Bring the redesign, not just the question. The person who asks question one and stops is a critic. The person who asks question one and arrives with two versions of question three is a contributor, and the difference in how those two people are received is enormous and completely unfair and you should plan around it rather than resent it.
What the rest of Part Two is
One chapter per question, in order, each one going considerably deeper than a chapter about a single question should reasonably need to.
Then a chapter where the check fails, on a project of mine that cost real money, because a tool you have only ever seen succeed is a tool you haven’t been shown honestly.
The Comfort Check
Chapter 4: frameworks
1. The comfortable assumption. A method has to be complete to be useful.
2. The true objective. Have something available at the exact moment a comfortable decision is being made, which is never during a planning session.
3. The redesigned approach. Three questions instead of five steps, sized to fit in your head, run before the work rather than about it.