January 2026 · Strategy Process
The brief nobody pushed back on.
Everyone approved it in one round. No redlines, no hard questions. That wasn't alignment. That was the sound of a brief saying nothing.
January 2026 · Strategy Process
Everyone approved it in one round. No redlines, no hard questions. That wasn't alignment. That was the sound of a brief saying nothing.
The brief went out on a Tuesday. By Thursday, every stakeholder had signed off. No revisions. No questions. No one asking what that line on page three actually meant in practice. The project lead was thrilled. "Fastest alignment we've ever had." And I sat there with the sinking feeling I've learned to recognize: this brief is going to cause problems, and the absence of friction is the first symptom.
A brief that provokes no pushback is almost never a brief that got it exactly right. It is almost always a brief that got it exactly vague enough.
The mechanism is simple. When a brief uses language like "elevate the brand experience" or "connect authentically with our core audience," nobody pushes back because there is nothing to push back on. Those phrases are mirrors. Every reader projects their own interpretation onto them and walks away believing the brief agrees with what they already thought. The CMO reads "elevate" and thinks premium repositioning. The product lead reads it and thinks UX improvements. The sales director reads it and thinks they're finally getting the case study library they asked for six months ago.
Everyone agreed because they agreed with themselves. The brief was just the surface they all reflected off of.
I've seen this with an outdoor brand that wanted to "redefine what adventure means." Beautiful sentence. Completely empty. It meant backcountry mountaineering to the founder and weekend car camping to the growth team. The brief never forced that conversation, so the conversation happened later, in production, at ten times the cost.
A good brief should make at least one person in the room uncomfortable. Not hostile. Uncomfortable. That tightening in the chest that happens when you read a decision that has real consequences. Because a brief that makes real decisions necessarily closes doors, and closing doors is what people push back on.
"We are not a premium brand. We are a value brand with premium taste-level." That is a brief someone will argue with. Good. The argument is the alignment. Until the CMO and the product lead have fought about whether "value" is a liability or an advantage and come out the other side with a shared understanding, you do not have alignment. You have a document.
The briefs I'm proudest of are the ones that generated the most redlines. One brief for a consumer tech company came back with so many comments it looked like a crime scene. But every comment was a real question. "Do we really mean we're deprioritizing enterprise?" Yes. "Does this voice framework mean we stop using technical language in ads?" Yes. The friction was the work. By the time the brief was approved, everyone who signed it understood what they were signing, because they'd fought about it first.
First: include what you're not doing. Every brief should have a "this does not mean" section. Not buried in an appendix. On the same page as the strategy, in the same size type. "This does not mean we pursue the enterprise segment. This does not mean we compete on price. This does not mean the rebrand extends to the sub-brand portfolio." If nobody flinches at the exclusions, they're not specific enough.
Second: use language that can be wrong. "Connect authentically" cannot be wrong because it cannot be tested. "Lead with user-generated content over studio photography in all paid channels" can be wrong. It can be argued with, measured, and reversed. Briefs built from testable claims generate real reactions because real things are at stake.
Third: name the trade-off. Every strategy is a resource allocation, and every resource allocation has a loser. The brief should say who loses. "Investing in creator partnerships means pulling budget from the programmatic display line." Now the person who owns programmatic display has something to respond to. Their response is information. Their silence on a vaguer version would have been a time bomb.
I know the appeal of the clean approval. No notes. No drama. The project moves to the next phase on schedule. But schedule is not the same as alignment, and speed through the brief phase almost always shows up as chaos in the execution phase. The questions that didn't get asked about the brief get asked about the creative. Then about the media plan. Then about the launch. The friction doesn't disappear. It migrates downstream, where it's more expensive and harder to resolve.
Write the brief that starts a useful argument. Send it knowing that the first response will be "I have questions." Welcome the questions. They are the brief working. A document that everyone agreed with immediately is a document that hasn't done its job yet. Not alignment, but the comfortable illusion of it. And that illusion has a cost you won't see until it's too late to fix cheaply.