What you learn to do
Three things you’ll be able to do that you can’t today.
Say your ideas so they land the first time. Change the frame so the work stops resting on you. Prototype your idea so people can walk through it before you build it. Each is something you learn by doing it in session, not by watching me. Here is what each one looks like from your chair, what it buys you, and how the help comes.
Say it so it lands the first time.
If you can’t say it, others can’t see it. In session we take the sentence you use to explain what you are doing and work it word by word: what each word makes a listener picture, and what it makes them feel. Then you say it to me as the person who most needs to hear it, and we watch where it lands and where it slides off. It usually takes a session or two to nail. The help comes as feedback before it counts: you give me the ten minutes you are worried about, the way you plan to give it, and I tell you what came across and what didn’t. Three passes usually does it, and the same exercise runs for a hard one-on-one, a board update, or a video message. Then your team can repeat your direction correctly without you present. Decisions stop climbing back up to you. The meeting you used to re-explain in three follow-ups happens once. If your team needs you in every meeting, the direction isn’t clear enough yet, and this is how it gets clear.
Change the frame so the work stops resting on you.
A frame is what you include, what you leave out, and where you aim what you have built. Change any of the three and the same facts tell a different story. A colleague who trained at Disney once had me hold an empty picture frame up during a talk: close, then far away. Same room, different picture. The classic case is the slow elevator. Framed as an engineering problem, you buy a faster elevator, which is expensive. Framed as a boredom problem, you hang a mirror, which is cheap, because people look at themselves and the wait feels shorter. In session we hold the frame up to your problem and move it, on purpose, until the cheaper answer shows. Noticing that a frame is wrong is a skill you can start using this week. Sensing what the new frame should be is a craft, and it grows with every frame you watch change, which is why we do it together first, and often.
The help comes as a sounding board: you bring the idea in whatever shape it is in, I say it back to you, how it works, where it is inconsistent, how it sounds, and you fix what you heard and go again, five or six times in an hour instead of once. After a few months you start hearing your own ideas back before you say them out loud, which is when you stop needing me for this one. Then the payoff that matters most in a bigger job: a frame simple enough to say is simple enough to hand over. Once the people around you can see what belongs in the picture and what doesn’t, the work spreads across a team instead of resting on you, and results come faster without you working harder.
Prototype your idea so people can walk through it before you build it.
Whatever you want to introduce, a strategy, a service, a brand, a new way of running your team, people take it in faster when they can experience it than when they are told about it. So in session we build a version of it far enough to step into. We might write the press release your team publishes a year from now, dated, with the customer named and what their morning looks like, and you hand it to your team and ask what would have to be true by that date. We might draw the meeting while you describe it, because ten people picturing the same idea are picturing ten different things, and a disagreement found on a drawing costs a redraw, not a rebuild. We might design the first hour of a new hire’s first day as carefully as a store. I have built prototypes like these for a restaurant chain, a drive-thru the technology of the day could not yet support and that is now standard, and for a lens maker, a store its leadership walked through in cardboard before a dollar went into construction. The same method works at the size of one leader’s year, and the details get worked out while changing them is still cheap. The help here is the one most leaders never got: learning to design your part of the company, not just run it. I learned it beside Stephan Haeckel at IBM in the 1990s. His idea, sense-and-respond, starts from a fact: when change outruns prediction, forecasting stops working, and the business itself has to notice earlier and respond faster. Draw your part of the company as promises, who owes what to whom and what counts as done; sense earlier, so the promise about to break is caught before the numbers say so; and lead by declaring the purpose and the boundaries, so the people around you, and now the AI agents, can act without waiting for you. Your calendar opens up, and the people around you grow. It is the hard skill nobody teaches on the way up, and it is the one boards and CEOs notice.
The condition under all three: confidentiality. Everything you say in our sessions stays there. That is what lets you say the rough version, the doubt, the thing you cannot say at work. And once you have said it out loud, you can see it well enough to work on it.
