In one 90-minute session, I map the load on both sides of the tension, name the structural constraint making it permanent, and give you a Two-Sentence Brief™ that changes how your leadership team thinks about the problem.
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 he knew what he was doing, that I was out of line, and that 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. "What happened. That demo was a disaster." I told him the message had been delivered, and dismissed. 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.
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 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, at a higher price), 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. At an onsite in Dallas, I asked my team where they felt the permission gap most. The answer came fast: the roadmap. Items my manager had placed there to satisfy funding and visibility requirements. Directional, not mandated. They knew that already. They still couldn't act on it.
I had spoken with my manager before Dallas, and she knew what I was going to ask. That morning I asked her, in front of the whole team, how she actually thinks about roadmap items. She answered matter-of-factly, a little surprised the question needed asking: she commits at a high level to secure funding long before anyone knows what will get built, and what gets built inside those resources is an engineering question.
Hearing it from me would have been information. Hearing it from the person who actually runs the business clock was permission.
Naming the bearing starts the work. It doesn't finish it. The muscle to hold the line installs one sprint at a time. 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, printed on a card made to be carried into a room and read aloud, along with a written guide for delivering it to each person you named in your intake. The recording and the 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.
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.
Cancel any time before your call and you receive a full refund. Once the call has taken place, the fee is not refundable, and missing a scheduled call without cancelling counts the same as attending it.
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.