Stakeholder Framing: Make the Pitch Relevant

Last updated: November 4, 2026

A proposal can contain strong facts and still fail because its decision-makers are being asked to judge it through the wrong lens. LeadershipNow’s discussion of persuasion focuses on this hidden layer: the frame that tells stakeholders what problem they are looking at.

For project leaders, framing is not presentation polish. It determines whether a business case becomes a priority, a budget request or another item politely deferred.

The frame sits behind the argument

Most people notice the visible parts of persuasion: the evidence, the recommendation and the sequence of slides. The frame is less visible because it operates like a window. The audience sees the argument through it and rarely notices the structure shaping the interpretation.

A project request framed as technical improvement asks stakeholders to think about workflow efficiency. Framed as customer protection, it asks them to consider risk. Framed as a compliance requirement, it raises a different category of obligation.

These interpretations need not be dishonest. They are different ways of presenting the same underlying work. The problem arises when the sponsor selects a frame without checking whether it connects to the decision-maker’s concerns.

Your preferred frame may be the weakest one

Deep involvement creates attachment. The project team may understand the technical problem better than anyone else in the room, but that expertise can also make one interpretation feel like the only rational one.

The source warns against communicating from your own perspective when decision-makers are likely to use a different frame. The overlap between the two may be smaller than expected.

For a new product line, the delivery team may see innovation as the central point. Finance may focus on the payback window. Operations may ask whether the product can be delivered without significant disruption to the existing business. Sales may wonder whether sufficient demand can be generated.

Each perspective contains a legitimate evaluation criterion. The task is not to make everyone value innovation equally. It is to translate the proposal so its relevant merits are visible within the criteria each group uses.

Map the audience before building the pitch

Early preparation should include two inventories: the frame guiding your own view and the frames decision-makers are likely to apply.

The first helps you recognize what you may be taking for granted. The second identifies where translation is required.

Suppose your goal is to establish why a proposed service should receive priority. List the main stakeholder groups and the question each is likely to ask. Finance may need a payback window. Operations may need to understand delivery constraints. Customer-facing leaders may need evidence of demand.

Then connect the proposal to those questions. Do not hide uncertainty, but do not present evidence in a form that makes its relevance hard to see.

This matters because people do not evaluate information in isolation. The source’s reference to Kunda’s 1990 research on motivated reasoning indicates that a message threatening existing beliefs can prompt people to look for reasons to dismiss it. Information aligned with identity, goals and concerns is more likely to be persuasive.

Reframe the proposal, not its facts

Different frames should not create different versions of the truth. They should reveal different relevant parts of the same proposal.

For finance, this may mean making the assumptions behind the payback window explicit. For operations, it may mean explaining the effect on current delivery and the resources required. For sales, it may mean identifying the intended customer segment and the evidence available about demand.

This approach preserves a crucial trade-off: the proposal may appeal strongly to one group while exposing unresolved questions for another. Framing should not conceal those tensions. It should make them available for the decision that needs to be made.

Without that translation, the sponsor may transmit its own frame while the groups that control resources never see the issue as they do. The proposal can then lose relevance before its merits are properly considered.

A worked example for an agile product pitch

Consider a product owner seeking leadership approval for a new product line. The natural frame is customer innovation. That may be accurate, but it leaves important questions unanswered.

Before building the presentation, define the audience’s likely frames. Show finance the assumptions behind the payback window and distinguish verified inputs from unresolved ones. Show operations how the launch affects current delivery and what capacity it requires. Show sales the intended customer segment and the available evidence about demand.

The aim is not certainty at every point. It is a decision-ready view of the proposal, with evidence, assumptions and risks tied to the criteria leadership is using.

The same method applies to internal process changes. A Scrum team may describe a revised definition of done as a quality improvement, while stakeholders may interpret it as a schedule threat. Show the work required, the delay risk and the evidence behind the standard.

Decision checklist: test the frame before the meeting

Use this checklist before the pitch:

• Name your frame:** What problem, opportunity or future are you proposing?
• Contrast it with the audience’s likely frames:** What will each decision-maker need to judge?
• Identify relevant criteria:** Which concerns, values, measures and interests govern action?
• Translate without distortion:** Which facts and assumptions speak to those criteria?
• Keep trade-offs visible:** What remains unresolved for each stakeholder group?
• Define the decision:** What choice are you asking decision-makers to make?

The checklist turns framing from a slogan into preparation. It also exposes weak pitches early, when the frame can still be adjusted instead of merely defending facts buried inside the wrong argument.

Watch what happens after the pitch

The strongest proposals do not require every stakeholder to see the world identically. They make the proposal understandable from the perspectives that govern action.

Watch whether your next business case opens with the problem, the recommendation or a stakeholder-specific concern. If its emphasis never changes by audience, it may be transmitting your frame rather than connecting with the people who decide.

Also watch what the room asks. Repeated questions about timing, cost or disruption may reveal that the frame did not address the criteria driving the decision. Those questions are diagnostic: they show where the proposal must be translated next.

The bottom line is blunt: a persuasive case can still lose if decision-makers do not see themselves in the argument. Find their frame, show the proposal through it and leave the trade-offs visible.

Key takeaways

• Make the underlying frame explicit before adding more supporting evidence.
• Identify the questions each decision-maker is likely to ask.
• Translate the proposal into relevant measures, constraints and risks.
• Keep uncertainty and trade-offs visible instead of disguising them as certainty.