How to Get Your Boss's Boss to Understand

Repeat the ask at the end with a short statement such as “To summarize, we are requesting approval of the design contract.” Without it, the discussion can drift into more questions or a polite request to come back next month.

Early disclosure is also an ethical choice. Withholding a known problem, even for a few weeks, erodes the trust that every future recommendation depends on.

Looking prepared shows empathy and builds synergy with decision makers. No one wants to waste their time.

Test each example before the presentation. Ask whether it explains the problem or simply makes the presentation more interesting. Replace it if it only does the second. One well-chosen example is worth more than several clever ones.

Imagine you are the one who must sign the bottom line. A direct report walks in with a recommendation. The slides show only the benefits of the preferred option, or they bury or omit the risks. The alternatives were quietly dismissed before the meeting started.

There is natural change occurring in the data and information because of complexity and uncertainty. The repeat of your presentation adds another dimension.

Two plus two can equal five in a well-run group. It can also equal three in a poorly run one. Group size and structure decide which. Keep subgroup size to three.

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.

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.

Lecturing is not generosity. It works against the board's process and against your standing as its trusted advisor. Answer the question, stop talking, and let the next question tell you what the board actually wants to hear.

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.

Resist the pull to respond immediately. Ask a clarifying question instead: "What's driving that concern?" or "What would resolve this for you?"

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...

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.