In July of 2010, I was working inside a subsidiary of a media holding company, watching a team build a genuinely impressive piece of technology. The CFO stopped me in a hallway. He'd heard a demo was coming, and he wanted to see the thing the technology was actually for: the finished ad, assembled and running. I mentioned the conversation to the CTO a few minutes later. He told me they were demoing the backend instead, the system where you build the pieces, not the system where the pieces become something a CFO would recognize as the product. I told him that wasn't what the CFO was expecting. He told me I was out of line and the conversation was over.

The demo happened exactly as he said it would. It was a real technical achievement. The CFO pulled me aside afterward, furious, and asked what had happened. I told him the message had been delivered. Within a week, the project folded. The subsidiary closed.

He was right about the structure. He was wrong about the cost.

That hallway held two Structural Bearings stacked on top of each other, and neither one was a personality conflict. Proof of technical capability and proof of business value are both legitimate things to want from a demo, and nobody had named, ahead of time, which room they were walking into. I had the information, I delivered it, and the structure I was standing inside made it impossible for that information to be received, regardless of whether I was right.

Your team isn't arguing about who's unreasonable. They're standing on either side of a boundary nobody has named yet, and every meeting that ends without resolution is more evidence, not less, that both sides are functioning correctly.

What happens next isn't a workshop, and it isn't a report I write after studying your organization from a distance.

You apply first. I accept a deliberately small number of these each month, and the application exists to find out whether the tension you're describing is structural or interpersonal, because those two problems require entirely different work. If you're accepted, I send a short intake packet before we ever get on a call: how your organization is actually structured, where you sit inside it, who the people are that you'll eventually need this Brief to land with, and what your team actually produces. I read all of it before the session starts. None of the 90 minutes gets spent on discovery.

The session itself runs on video by default (a limited number of in-person sessions are available for local clients, by request), and it's recorded start to finish. We draft the Brief together, live, on a shared document. You leave the call with a preliminary version of it in hand, spoken aloud, tested against your own reaction in real time.

Preliminary, deliberately. I don't finish the naming inside the 90 minutes, and I want you to know that going in. After the call, I transcribe it and go back through everything, testing the wording against your full intake and the actual people who'll be in the room when you deliver it.

I run this discipline on my own team too. During a recent onsite, I asked my team directly where they felt the permission gap most. The answer came back fast: the roadmap, items my own manager had placed there to satisfy funding and visibility requirements, directional, not mandated. The team already knew that intellectually. They still couldn't act on it. Naming the tension out loud that morning didn't close the gap. What closed it was holding the same line, sprint after sprint, until the room's felt permission finally caught up to what everyone already knew.

A Two-Sentence Brief that's right on the first draft and a Two-Sentence Brief that survives being read to a skeptical room, more than once, are not the same document. I build the second one.

Within seven to ten business days, the final Brief arrives, along with a written guide for delivering it specifically to the people you named in your intake, and the recording and full transcript of our session are already yours by then.

What I won't do: talk about anything from your session outside this engagement, or use anything from it as a testimonial or case study, without your explicit permission first.

What you're getting a partial answer to right now, so you know what to expect:

The exact question I ask in the first twenty minutes that tells me where the boundary in your organization actually sits, not where you assume it sits.

Why the version you leave the call with isn't the one you'll actually put in front of your team.

What I ask for in the intake packet that most people offering this kind of session never think to ask for, and why it's the reason the delivery guide works for your specific room instead of a generic one.

I wrote an entire book on this method, The Edge Case. Some readers finish it, understand the Two-Sentence Brief as a concept, and still can't build their own. The book teaches the category of problem. It can't sit in the room with your specific tension. That gap, between understanding a method and applying it to your organization, is the entire distance between a book and this session.

The price is $3,000, for one 60-to-90-minute session, plus everything after it described above.

This isn't for you if you're looking for a project manager to clear a backlog, or a framework you can implement yourself without a live session, or if you're not the person in the room who can actually act on what gets named. If you're the one who can already see the tension clearly and can't yet get anyone else to see it, apply below.