Altitude: Why the Same Story Needs Three Different Decks

The same idea. Three completely different presentations.

An engineer, a VP of Product, and a CEO need to walk away from the same meeting with the same conclusion — but the presentations that will get them there are not the same presentation. They require different vocabulary, different levels of abstraction, different types of evidence, and different emotional registers.

This is what I mean by altitude. It's one of the most underutilized concepts in presentation design, and the failure to get it right is responsible for a specific type of meeting failure that feels confusing in the moment: the room isn't against you, they're just not with you. They understand what you're saying, but they're not landing where you need them to land.

Usually, that's an altitude problem.

The three altitudes

Altitude is the level at which a conversation happens. Different roles operate at different altitudes by necessity, not preference — it's a function of what decisions they're responsible for and what information they need to make them.

The ground level is operational. Engineers, analysts, and implementation leads live here. They need specificity: how does this work, what are the dependencies, what are the failure modes, where are the edge cases. They trust precision. They distrust generalization. A presentation that skips the technical detail feels to them like a presentation that's hiding something.

The middle altitude is managerial. Directors and VPs operate here. They need to translate between strategy and execution. They need to understand both the "what" and the "how" at a level that lets them manage the people doing the implementation and report up to the people setting the direction. A presentation that's too technical feels like being buried in implementation detail. A presentation that's too strategic feels like a slide deck that can't be executed.

The high altitude is executive. CEOs, board members, and C-suite leaders operate here. They need to understand consequences, not mechanisms. They're asking: what does this change? What does it cost if we don't? What does success look like in six quarters? They trust pattern recognition and strategic framing. They distrust decks that feel like they're educating them on things they already know. The fastest way to lose the room at the executive level is to explain something they've already grasped.

The Chevron case: calibrating for multi-level rooms

Some of the most demanding presentations are the ones where the audience spans multiple altitudes simultaneously. The Chevron New Energies project was exactly this: the stakeholders in the room included both technical sustainability leads who could speak in detail about carbon intensity metrics and renewable hydrogen infrastructure, and senior leaders who were evaluating the strategic positioning of a division within a company navigating enormous public and regulatory scrutiny.

The instinct is often to find a middle ground — a level of specificity that's high enough to satisfy the executives and low enough to include the technicians. In my experience, this almost never works. The middle ground satisfies no one fully. The executives feel the presentation is too detailed. The technicians feel it's too superficial.

The better approach is to design the deck with explicit altitude shifts. Open at the executive altitude — the strategic framing, the thesis, the consequences. Establish the "why this matters and what changes." Then descend to the managerial altitude when you need to show the implementation logic — the initiatives, the timelines, the resource requirements. Reserve the technical altitude for appendix material that the practitioners can review but the executives don't need to sit through.

Structure this deliberately and the presentation works for everyone in the room, because everyone knows which sections are meant for them.

OPMG and the C-suite translation challenge

The OPMG Connected Data project was a nearly pure altitude problem. The team responsible for the data architecture operated at the technical level by necessity — they had built something complex and they thought about it at the level of data flows, taxonomy structures, and model architectures. When they described it in those terms, it was accurate and impressive. It was also completely inaccessible to the CMO, CTO, and CRO who needed to fund and champion it.

The request I was brought in to address was essentially: translate this technical achievement into executive language without losing the substance.

This is the altitude problem in its clearest form. The answer is not to simplify the content. It's to reframe the content at a different level.

What does an enriched first-party signal mean to an engineer? It's a data object with an appended contextual layer that improves model accuracy. What does an enriched first-party signal mean to a CMO? It's the difference between a customer who gets an ad that's relevant to what they're thinking about today versus one who gets an ad that's relevant to what they were doing six months ago. Same capability. Different altitude.

We built the deck in two layers — the executive layer and the practitioner layer — with clear visual signals indicating which was which. Decision-makers could move through the executive layer and have a complete, coherent experience without engaging with the technical detail. Practitioners could use the same deck to go deeper into the sections relevant to their work.

The outcome: for the first time, the senior leadership in the room left the session with a clear understanding of what the capability was worth — in business terms, in revenue impact terms, in strategic positioning terms. And the technical team felt their work had been represented honestly, not dumbed down.

Why executives resist depth (and what to do about it)

There's a specific dynamic in executive presentations that catches presenters off guard. The more enthusiastically they go deep on a topic — showing expertise, demonstrating rigor, presenting the research — the more the room seems to withdraw.

This feels like rejection of the content. It's actually a signal that the altitude is wrong.

Executives develop, over time, a finely tuned alarm for presentations that are trying to educate them in areas where they've already formed a view. This alarm isn't arrogance. It's efficiency. An executive who sits in twenty presentations a week cannot afford to re-examine every foundational assumption every time a presenter wants to demonstrate expertise. They've already built their mental model of the landscape. They need to know where your presentation fits within that model — not a lecture that implies they need to rebuild the model from scratch.

This is why altitude-calibrated presentations begin at the strategic level and only descend for the specific elements where depth is necessary to support a decision. Show the view from the top first. Then offer the ladder down for the people who need it.

How to identify the right altitude before you build

There are three practical questions I use to calibrate altitude for any presentation.

First: what decision is the room authorized to make? The altitude required to present to the decision-maker is the altitude at which that decision gets made. If the decision is "do we allocate budget to this initiative," it gets made at the business case level — ROI, timeline, risk. That's the altitude. If the decision is "which implementation approach do we use," it gets made at the technical level. The decision defines the altitude.

Second: what would a "no" sound like? If the audience's objection would sound like "I don't understand how this works" — that's an altitude mismatch downward. You went too high. If the objection sounds like "I don't have time for this level of detail" — that's an altitude mismatch upward. You went too low. The shape of the potential objection tells you where you are relative to where you should be.

Third: when does this audience typically make decisions? Executives often decide before the last slide. Managers need to finish the deck. Technical leads want to see the appendix. Knowing where in the presentation the decision is likely to happen tells you where to put your most critical argument.

The same story, different register

The final thing altitude requires is a shift in emotional register, not just informational depth. This is easy to get wrong.

At the executive altitude, the primary emotion you're trying to create is confidence — in the thesis, in the team, in the investment. At the managerial altitude, you're trying to create clarity — about what's required, what's achievable, what the path looks like. At the technical altitude, you're trying to create trust — that the people who built this know what they're doing, that the details hold up under scrutiny.

These are different emotional jobs. And they require different kinds of evidence, different types of language, and different visual approaches. Confidence is built with strategic conviction and strong framing. Clarity is built with structure, sequence, and specificity. Trust is built with precision, completeness, and the willingness to engage with complexity.

The best presentations I've seen calibrate not just the information but the feeling — and they do both at the altitude that's right for the room.