How to pitch your manager using purpose, preference, and protocol

Executive overview

Most people pitch their manager the way they themselves like to be pitched, rather than the way their manager actually receives information. The real work is thinking at a higher altitude — understanding what your manager cares about, how she's measured, and what case she'll need to make to her own boss.

The manager is your biggest customer. Research her accordingly.

Three lenses — purpose, preference, and protocol — frame every effective pitch. None is sequential; all interact.

Purpose: build a business case, not a list of reasons

• Altitude means stepping up from your floor to your manager's floor — roof lines and patios are invisible from there.
• Ask: who is the ultimate decision maker? If your manager needs to pitch upward, design for that audience too.
• Distinguish a business case (affects the business, survives the next level up) from a personal reason (helps me or my team).
• Force the question: why would she care? Why would this matter to her? Keep asking until the case either holds or collapses.
• Look for clues about your manager's priorities in staff meeting language, calendar entries, and recurring topics — especially in remote contexts where informal signals are scarce.

Preference: match how your manager thinks and decides

• Some managers move fast and skip details; others want every step. Match their pace, not yours.
• Find out how your manager makes decisions — values, data, precedent — and lead with that.
• Presentation format matters: slides, email, verbal conversation, or a text message. Use the format they actually engage with.
• Adaptability is a leadership skill, not a concession. "It's not about you" applies to every pitch.

Protocol: prepare the ground before you speak

• Get intel in advance. Likely objections, unasked questions, and political context are usually discoverable — talk to peers, adjacent teams, and allies.
• Build those relationships before you need them; waiting until pitch day is too late, especially in remote environments.
• Clarify what you are actually asking for: a recommendation, a set of options, or approval for a specific path. Ambiguity on this point kills pitches.
• Use inclusive language — "we" not "I" — to signal that this is a business conversation, not a personal ask.
• Speak the organisation's language. Unless you are deliberately introducing new terminology, match the words your culture uses.

The want-obstacle-resolution story structure

• Want: State clearly what the business is trying to achieve. Your manager needs to know what you want before engaging with the problem.
• Obstacle: Name what is preventing it. A clearly articulated obstacle is what makes people lean forward.
• Resolution: Your proposal. It is the answer to the obstacle, not a free-floating idea.
• This three-part structure also helps you define the problem out loud — something many pitchers skip, leaving the manager uncertain whether there is a real business case at all.

Mindset: one pitch does not make or break a career

• A failed pitch delivered well still builds credibility for future conversations.
• Treat pitching as a regular part of the job, not a high-stakes singular event.
• Anxiety scales inversely with practice — the more frequently you pitch, the lower the stakes feel in any single moment.
• Focus on the work, not the outcome: showing up as someone who thinks at altitude and builds a rigorous case compounds over time.