How to Get Your Boss's Boss to Understand

Understanding the decision maker's personality is not enough. We need to understand the personality profiles of the decision maker's inner circle and how that group behaves under pressure. Before your next major recommendation, identify who the decision maker actually turns to when things get uncertain.

I use a double diamond for exactly this moment. Just as the group settles into what looks like consensus, reopen divergence deliberately. Ask a pointed question that reintroduces a dropped option. Or bring back an earlier dissenting voice and ask that person to restate their concern. Run the group through a second, smaller diamond before you close.

The exercise works because it’s hands-on, and it keeps working long after the session ends.

A team will not reach implementable solutions until the frame includes what people are actually afraid of, not just what they say they want.

Treat something as not being in the model as synonymous with not being in the problem frame.

I normally ask the group to sketch the physical boundary first, since it is the more familiar concept. We then push into the operational boundary.

Being asked to remain in the room is satisfying. It can also be nothing more than politeness, not a request for your input. Know the difference. If your role was to inform.

The lesson is that an early-user edge was never going to last, but the judgment about when AI helps and when it quietly misleads is a better asset for the long run. Tools commoditize. Judgment compounds.

Executives and boards ask questions to test judgment, not to audit method. Give them the direct answer first. If nuance is required, say so in one sentence and offer to follow up. Their question is a request, not an invitation to perform the whole analysis on their time.

Boards and senior executives rarely say no directly. They ask a narrower question than the one you expected. They move to the next agenda item without a follow-up. They thank you for the presentation without committing to the recommendation. None of that is an oversight.

Your first layer of backup is people. And it’s your job, as the lead presenter, to make sure they have your back. Your backups should understand the core message and their simple message for speaking if you defer to them. They do not need to be polished speakers.

Technical professionals are trained to think chronologically. We like to build the case, explain the method, and walk through the model. That instinct works in peer discussions but not in executive settings. Executives want the point...

A problem written on a flip chart belongs to the group. Ideas added to the chart become shared contributions instead of personal claims. This stimulates collaboration and reduces the tendency for people to defend their positions.

Executives appreciate presenters who are confident enough to let their work stand on its own.

FINESSE is rooted in systems thinking. Effective communication is a system of interrelated parts, not just the sum of individual skills. None of the “bones” needs to be perfect; they just need to work together to produce clarity and confidence. This reduces the pressure on any single person to be flawless and focuses on building a dependable communication system.

Accessibility should be a first‑order consideration, not something squeezed in as time allows.

Posture is the visible expression of your internal attitude. It shows up in your tone, structure, pacing, and your willingness to accept that the burden of meaning rests on you. Communicating to senior management is disciplined. It acknowledges hierarchy, respects time, and focuses on delivering decision ready content.

This is good news for technical professionals. You don’t need to be the most polished speaker in the room. You don’t need to be the most charismatic. You don’t need to deliver the perfect slide. What you need is a communication system you trust.

The burden of clearly communicating technical information is on you, not the receiver of the message.

Remember, if a simple model provides the insights needed for the decision, there is nothing wrong with calling it “good enough.”