Individual contributors often behave differently in rooms with executives than in rooms with their peers. Some get hyper-formal, over-explaining their work in minute technical detail. Some go the other direction, over-simplifying to the point of meaninglessness. Some get deferential — pausing for approval before finishing sentences, hedging every claim, performing humility rather than showing competence.

None of these help. And most executives can spot them instantly.

The translation layer between the work and the executive conversation is a learnable skill. It has specific components: business relevance, crisp framing, acknowledgment of tradeoffs, clear recommendation, and calibrated confidence. Underneath all of that, executives are listening for judgment: whether you understand the business, whether you know the limits of your own certainty, and whether you can help them make the call without defending your team as a reflex.

Business Relevance Comes First

The most common mistake ICs make with executives: leading with the technical implementation instead of the business consequence.

"Replacing the database migration library to use a deterministic retry pattern" might be interesting to your tech lead. In an executive conversation, it means nothing until you translate it. Leading with: "We have a stability risk in the checkout flow that could cause approximately 2% of transactions to fail during peak load. The fix requires a one-week engineering investment and will reduce that failure rate to near zero" — that's a business conversation.

Executives are not asking "what are you doing." They're asking "what's the state of the business and what should we be doing about it?" Your job in translating is to put your work in those terms. What does this mean for customers? For revenue? For risk? For the strategy we're pursuing?

Marty Cagan's framing from Inspired is useful: the executives' job is to protect the product outcomes. You're communicating so they can do that job better.

Acknowledge Tradeoffs

Executives respect honesty about tradeoffs more than false confidence in a single path. If you're recommending option A but option B has meaningful merit, say so. If the timeline is tight and quality will suffer, name it. If you're not sure, say that too.

The reason: executives are making resource allocation decisions constantly. They are weighing your ask against fifteen other asks. If they feel like your recommendation is omitting the downside, they'll discount it. If they feel like you've done the honest analysis, they'll trust your judgment more — even when the recommendation is complicated.

"Option A is faster but creates a tech debt cost we would pay in Q1. Option B takes two weeks longer but eliminates that debt. I recommend A given our Q4 pressure, but wanted you to see the tradeoff clearly." That's useful. "Option A is great, no issues" is not.

How to Answer When Challenged

A challenge is not automatically a trap. Often it is a test of the frame.

If they challenge the data, separate what you know from what you are still validating:

> The 1.8% number is from peak-load testing on Friday. What we do not know yet is whether it holds under promo traffic. We will have that read by Tuesday.

If they challenge the recommendation, show the tradeoff rather than repeating the conclusion:

> The reason I still recommend A is timing. B is cleaner technically, but it misses the launch window. If launch date matters less than long-term maintenance cost, I would switch to B.

If they challenge the team, avoid becoming a defense lawyer. You can protect the team from unfair assumptions without sounding tribal:

> The team did miss the first estimate. The root cause was not effort; it was an unmodeled dependency on Data. We have corrected the plan and added a Friday checkpoint so this does not surprise us again.

That answer owns reality, explains cause, and moves the conversation forward.

Pre-Brief When the Stakes Are High

If you are presenting to executives on a consequential topic, pre-brief your manager. Share the headline, recommendation, risks, and likely hard questions before the meeting. This is not permission-seeking. It prevents surprise, lets your manager strengthen the frame, and clarifies whether they want you to own the recommendation or simply provide the evidence.

A good pre-brief can be five bullets:

  • headline state
  • recommendation
  • key tradeoff
  • question I expect
  • where I need backup

That small step often turns an executive interaction from a performance into a coordinated decision conversation.

The Underlying Principle

Executives are not a different species. They have a different context and a different attention structure. The IC's job is to translate — to bridge the gap between the work and the decision-maker's frame. That translation is not about dumbing things down. It's about being clear about business relevance, honest about uncertainty, and precise in framing.

Communicate like you're trying to help the business make the right call — because you are.