Walk through the key context first so they understand how you reached the recommendation Open with the recommendation in one sentence, then add only the context they ask for Cover all your material at pace — you can always slow down if they want more detail on something Ask what they already know about the topic before deciding where to start

Is substantially different — the frame, the language, the opening, and what you emphasise are rebuilt from scratch for each audience Is largely the same — the recommendation does not change so the core presentation should not either Differs mainly in the level of detail — you cut the technical specifics for the board Differs in formality — you are more structured with the board but the content follows the same arc

Explores the tensions before committing — you want them to understand the full picture before you state your position Acknowledges the complexity first, then arrives at a position with appropriate caveats Opens with your position and supports it with two or three specific reasons — clearly, without excessive qualification Depends heavily on context — you rarely state a position without first understanding what they are trying to decide

Continue — the most important information is coming and they need the full picture to evaluate it Stop immediately, name what you are sensing, and ask what would be most useful to focus on Speed up to get to the key point faster — the problem is length, not content Finish the point you are on and then check in — interrupting your own flow sends the wrong signal

Lead with the strongest evidence you have — if the case is rigorous they will follow the logic Acknowledge their likely concerns upfront — showing you understand their objections builds credibility before you make your case Open with the specific outcome this proposal delivers for the thing they care about most right now Tell a story or example that makes the problem concrete before you present the solution

Pause, ask them what specifically feels complicated, listen, and then adjust your explanation to address that precisely Simplify immediately — cut to the core point and deliver it in two sentences Feel the criticism land and lose your thread for the rest of the exchange Acknowledge their comment, finish your point briefly, and invite them to tell you where you lost them

People respond directly and specifically to what you said — the point landed where you intended The conversation moves on without directly engaging your point — you are not sure whether it registered People ask clarifying questions — you find yourself restating or expanding what you meant You are genuinely uncertain — you cannot always tell whether your point moved anything or simply added to the discussion

Accept it — senior leaders have limited bandwidth and some information loss is inevitable in time-pressured briefings Rethink the structure — specifically identify the moment they disengaged and ask yourself what your opening sentence should have been instead Follow up with a summary document — what did not land verbally may land better in writing Conclude that the topic was too complex for this format and request a longer meeting next time

Consider this exactly right — cutting detail to be brief risks oversimplifying and losing the nuance that makes your communication trustworthy Know this is true in written communication where the reader can set their own pace, but less true in verbal settings where their attention is finite Know that detail serves the communicator more than the audience in most cases — it signals effort, not clarity Know that brevity is itself the signal of rigour — it shows you have processed the complexity so the other person does not have to

Before following up, reread your original email and ask yourself whether it was clear about what you needed, when you needed it, and why it mattered to them Send a polite follow-up — people are busy and a gentle nudge is standard professional practice Raise it in the next meeting you have with them — some people respond better to verbal than written communication Wait another two days — following up too quickly signals anxiety

Open with positives before raising the issue — softening the delivery makes the feedback easier to hear and act on Send a written summary of your concerns first so they have time to process before the conversation Name the specific gap directly in the first two sentences — clearly, without preamble — then open the conversation Ask questions that allow them to identify the gap themselves — self-diagnosis leads to more genuine commitment to change

Ask them for a specific example — a particular meeting or exchange — and what exactly felt hard to follow in it Thank them and reflect privately on whether you agree — you want to assess the feedback before acting on it Feel defensive — you have not heard this before and you are not sure the feedback is accurate Take it seriously immediately — if one person experienced it, others almost certainly have and said nothing

Find one concrete, specific example that makes the abstract case real and anchor your recommendation to it Keep it concise — you have learned that brevity is what sticks, not depth Build a strong evidence base — the people in this room respond to data and rigour more than storytelling Prepare a clear one-page summary to leave behind — what does not stick verbally stays visible in writing

Thorough and detailed — you give people everything they need, though you know you sometimes give them more than they want Clear and direct — people know exactly what you are saying, what you are asking for, and what comes next Good in familiar settings but less consistent when the audience is senior or the stakes are high Thoughtful but sometimes arriving at the point later than ideal — you lead with context more than conclusion