The timeline was wrong.

My counterpart and I figured it out the same way you usually figure these things out — sitting across from each other in a side conversation, staring at the assumptions baked into a commitment date that nobody had actually checked against reality. The decommission of a legacy system. A hard date on a slide. And a list of constraints that made that date somewhere between optimistic and impossible.

Neither of us said much for a moment. We both knew what we were looking at.

That moment could have gone a few different ways. Surface it at the next executive check-in. Flag it in the all-hands. Let it hit a formal meeting and become everyone's problem in real time.

We didn't do that.

We spent the next twenty minutes building an alternative. Not the full answer — just enough of a frame that we could bring something, not just a problem. Then we split up. She took her leads. I took mine. Five to fifteen minute calls. Nothing formal. Nothing scheduled weeks in advance. Just: hey, I want to walk you through something before the bigger conversation.

By the time we sat down in a room with our product managers, the shape of the decision was already made. The meeting was structured so they could weigh in, ask questions, poke at the alternatives. And they did — a few of them added things that genuinely sharpened the proposal. But the outcome was never really in question. We had done the work before anyone opened a calendar invite.

That meeting went well. It almost always does, when you've done it right.


Getting the Corner Offices

The first time I understood this as a system, I was new in a role and a boss pulled me aside on my first week.

He called it getting the corner offices in agreement.

When leaders had corner offices, getting each of them aligned before a formal meeting meant you effectively had the decision. The formal meeting was still necessary — for visibility, for record, for the people who needed to feel consulted. But the outcome was already shaped.

The room was a ratification, not a deliberation.

I have never forgotten that conversation. It's the kind of thing that, once named, you cannot unsee. I started noticing it everywhere. In every project kickoff where something had clearly been decided before the kickoff started. In every steering committee where one person seemed strangely unsurprised by what was being proposed. In every difficult conversation that resolved unusually fast because someone had done invisible work in the days before.

And eventually I started doing it myself.

This isn't only an executive-level move. A product owner who syncs with her tech lead before a planning session with the full team — walking through what's coming, building a shared view of the approach — will run a smoother session. Same principle, same mechanic, two levels down.

The meeting before the meeting works at every altitude.


The Part Most People Miss

They think the pre-meeting is a pitch. They prepare a tight brief, request fifteen minutes, walk someone through their proposal, and wait for a reaction.

That's not it.

The actual move is asking questions. Not explaining your thinking — asking questions that surface theirs.

You are not leading someone to your answer. You are creating the conditions for them to arrive at it.

That distinction matters enormously. Human beings resist being told what to do, even when the answer is correct. Especially when the answer is correct. Something about being handed a finished solution triggers a defensive response — why didn't anyone ask me, what am I missing, what are the angles this person isn't seeing? The resistance isn't always rational. It doesn't have to be.

So you don't hand them the answer. You ask questions. You listen. You make real space for them to bring something you hadn't considered — because sometimes they do, and it makes the proposal better. And when they feel genuinely heard, when they've been part of the thinking, they show up to the formal meeting as someone who helped build this. Not someone being asked to approve it.

The formal meeting becomes a place where people who already believe in the idea get to say so in front of the group.


What It Costs

This doesn't work without competence and trust.

If you have a track record of being wrong, of overpromising, of bringing problems you haven't actually thought through — the pre-meeting calls stop landing. People take them, but they don't really listen. They wait for the formal room to see how the rest of the group reacts before they commit.

Trust is the infrastructure this runs on.

There's a second thing, harder to see until you've gotten it wrong. I've done the prework, built real alignment across a wide group — and watched it fall apart the moment it went upward. What I learned: it's not about how many people you bring along. It's about which ones. Horizontal alignment doesn't survive the room if the key decision makers aren't already with you. The influencers — the people whose read shapes how everyone else decides — those are the conversations that matter most. Get ten colleagues on board and miss the one person the room is watching, and you've done a lot of work for nothing.

It's not the size of the coalition. It's whether the right people are in it.

This isn't about seniority. It's about track record. The corner offices don't agree with you because you asked. They agree because you've earned the right to ask — through commitments you kept and problems you didn't manufacture.


The Uncomfortable Thing

I want to say something that is slightly uncomfortable to put in writing.

Influence and manipulation share a method. The pre-meeting conversation, the targeted questions, the careful sequencing of who hears what and when — these mechanics are identical regardless of what you're trying to achieve. The line between them is intent. Are you doing this because you've done the real work and you genuinely believe the direction is right? Or are you doing this because you want a particular outcome and you're running a playbook to produce it regardless of whether it's sound?

One is leadership. The other is something else.

I've been on the receiving end of both. The difference is usually apparent in retrospect. When the decision was good — when the person who shaped it in advance was right, and the people who got brought along got brought along to something that actually served them — it feels like momentum. When it wasn't, it feels like being managed.

The mechanics are the same. The difference lives entirely in the quality of the thinking behind it and the integrity of the person running it.

That's a significant moral weight to put on an informal phone call. But that's what it is.


Which means the whole system — the pre-meetings, the questions, the careful sequencing — is only as good as the person running it. Use it well and you build momentum. Use it poorly and people eventually figure it out. The invisible curriculum cuts both ways.

The room you walk into has already been shaped. The only question is whether you were part of shaping it.

— The Daring Dime


If this resonated — the next one will too. Subscribe below and I'll send it straight to you.