Learning objectives
After this session, you should be able to:
- Explain why a convincing pitch starts with the problem, not the solution.
- Recognise the two failure modes of a pitch and how to avoid them.
- Translate your in-depth research into a problem statement the board recognises as their own.
- Apply the modes of persuasion, the four truths of a story, and the narrative map to structure your pitch.
- Anticipate the board’s questions and rehearse your answers.
Introduction
Relevance
Great ideas are a dime a dozen. What separates the dreamers from the doers is the ability to convince others to get behind the idea. This could mean securing funding, getting buy-in from colleagues, or attracting customers.
Without that ability to sell,
your ideas are likely to stay just that: ideas.
A pitch is not a presentation of work already accepted; it is the moment at which the work is decided. The board has limited time, conflicting priorities, and no obligation to engage with the depth of your investigation. The pitch is the bridge between what you have learned and what they can authorise.
This unit is designed to help you cross that bridge.
Setting
This is your unique opportunity to present your idea to the board.
You have 12 minutes to raise the funds for the market-ready development of your solution.
The board will judge your solution along three dimensions:
- desirable (it sufficiently addresses relevant parts of the challenge),
- viable (it creates business value for the company), and
- feasible (it can be implemented within a reasonable timeframe).
Note: Only your group knows the idea, the background, and the full process.
Present in a way that is easy to follow.
The three judgements run in parallel in the board’s mind, but they are not independent. Desirability is the gate. If the board does not believe the problem matters in the way you frame it, viability and feasibility lose meaning; their assessment of cost, risk, and timeline collapses onto a problem they are not convinced is worth solving.
A strong showing on two of the three does not compensate for a weak showing on the third; all three must clear the bar.
Two ways to lose the board
The asymmetry
You have spent weeks on the problem.
The board will spend twelve minutes on it.
Your group has investigated the challenge, talked to stakeholders, and tested ideas.
The board has not.
That gap is your central communication problem.
Through your research, interviews, and prototyping, you almost certainly understand the problem in more depth than anyone else in the room, sometimes including the people who briefed you in the first place. That is the whole point of the assignment.
The board, however, has a different perspective. They sit above many initiatives at once and see the challenge through the lens of a few priorities they have already chosen for themselves: cost, growth, risk, a strategic bet, a regulatory deadline. Their view of the problem is not wrong; it is narrower and differently weighted than yours.
If you simply pour out your depth on the board, they will not follow you. If you walk on stage assuming they share your map of the problem, you have already lost them.
Two failure modes
Problem understanding fails
Even the best solution lands in a vacuum. The board never feels the pain your solution would solve.
Solution falls short
A sharp problem framing raises expectations. A weak solution then disappoints the board twice: once for the problem, once for itself.
A pitch fails in two distinct ways, and the remedies differ.
Failure mode 1: weak problem framing. You present a solution to a problem the board does not feel. They may concede in the abstract that the problem exists, but they do not see it as urgent or as a fit for their priorities. From that moment on, every solution detail registers as a “nice technical exercise” rather than as a strategic move. No demo, however impressive, recovers from this.
Failure mode 2: weak solution. You set up the problem cleanly, the board leans in, and then the proposed solution does not match the bar you raised. This is in some ways the worse failure: you have invested the board in caring, and then under-delivered on that caring. A solution that would have been “acceptable” against a soft problem framing now looks “inadequate” against a sharp one.
The takeaway is not that the problem matters and the solution does not. The order matters. Problem first, solution second; and the solution must be commensurate with the way you have framed the problem.
Implication
You have to earn the right to talk about your solution.
The price of admission is a problem framing the board recognises as their own.
This is also why the first minutes of the pitch are disproportionately important. You earn (or fail to earn) the right to spend the remaining ten minutes on your solution within the first two.
Practically, this changes how you draft the deck. Most student groups start with the solution slides because that is where they have invested the most effort. The discipline of this unit is to draft the problem slides first, get them right, and only then build the solution slides to match.
Problem first
Make the problem stick
Make your
problem statement
stick.
Demonstrate understanding of the stakeholders, their values, and their interests before you offer a solution.
A problem statement is “sticky” when the board can repeat it after the pitch without looking at the slides. That is the test: not whether you are happy with the wording, but whether they can carry it out of the room.
A sticky problem statement has three properties:
- It names a specific stakeholder, not “the company” or “users”.
- It describes a consequence the board cares about, not a symptom only you find interesting.
- It is short enough to be repeated in one breath.
A workable template
For [stakeholder], who [situation/pain],
the challenge is [problem].
If unresolved, [consequence].
The board cares because [board’s priority].
Five short clauses; no jargon; no solutioning yet.
The template is a scaffold, not a script. Its job is to force you to name the four ingredients the board needs in order to feel the problem: who, what hurts, what happens if we do nothing, and why this slots into the board’s existing priorities.
The last clause is where most student pitches under-invest. It is the clause that connects your depth to the board’s slice. If you cannot complete the sentence “The board cares because…”, the board probably will not, either.
Whose problem?
- Whose pain is sharpest?
- Whose authority releases the budget?
- Whose support do you need after the pitch?
These are often three different people.
Lead with the first; address the second; do not forget the third.
A typical mistake is to write the problem statement for the end user (whose pain is sharpest and most vivid) and then deliver it to the board (whose authority releases the budget). The two need not be the same person, and the pitch must satisfy both.
Lead with the end user’s pain because that is what makes the story land. Then translate it into the board’s frame: cost, growth, risk, strategic fit. The board will not feel the pain on the end user’s behalf; they will feel it through the lens of consequence for the organisation.
The board sees a slice
What you know:
- Full problem space
- Multiple stakeholder views
- Trade-offs explored
- Dead ends ruled out
What the board cares about:
- A few prioritised dimensions
- Strategic fit
- Speed and cost
- Risk
Connect their slice back to your depth, not the other way around.
The asymmetry is not a problem to be hidden; it is a resource. Your depth lets you confidently say, “Yes, we considered alternative X; here is why it does not solve the part you care about.” The board does not need to see every alternative you considered, but they need to feel that you have, and that you can defend the choice.
The order of operations is critical. Start in the board’s frame; then prove, with brief evidence, that the broader investigation supports the framing. Reversing the order, with exhaustive depth first and “and so therefore your priority is served” at the end, almost always loses the room.
Persuasion
Modes of persuasion
Aristotle suggested that any spoken or written communication intended to persuade contains three key rhetorical elements:
Logos
Appeals to the audience’s reason, building up logical arguments.
Ethos
Appeals to status or authority so that listeners trust the speaker.
Pathos
Appeals to the emotions, e.g., making the audience feel concerned or hopeful.
A good pitch does not pick one mode; it weighs them differently for different audiences and moments.
- A board pitch is logos-heavy (numbers, value mechanics, risk) with ethos supporting it; the team has done the work and earned the right to recommend a course of action.
- The problem section is where pathos belongs, briefly and concretely: a single stakeholder voice, an episode, a vivid number, so that the board feels the problem before they evaluate the solution.
- Pathos without logos in a board context reads as theatre. Logos without pathos reads as a report and rarely moves money.
Four truths of a story
Guber (2007) argues that a story persuades when it carries four truths:
- Truth to the teller: you must believe your own problem framing.
- Truth to the audience: speak to the board’s priorities, not yours.
- Truth to the moment: twelve minutes, in a boardroom, with a decision pending.
- Truth to the mission: anchor your idea in business value creation, not in the elegance of the technology.
The four truths are a checklist to run over the draft of any pitch. The two students most often miss are truth to the audience and truth to the mission.
Truth to the audience is exactly the asymmetry discussed above. Students tend to tell the story they would want to hear; the board needs the story they can act on.
Truth to the mission is the one most easily smuggled past you by your own enthusiasm. In an IT-enabled value creation course, the mission is value, not technology. A pitch that lingers on the architecture, the model, or an agent’s mechanics is failing this truth; the board cares about what those mechanisms produce.
The other two are usually safe in a student project: you believe in your work (truth to the teller) and you understand the format (truth to the moment).
Story elements
Behind every good story is a well-thought-out structure that forms its backbone. The essential elements are:
Characters
Setup or conflict
Sequence of events (plot)
Resolution
For a pitch, the elements map cleanly onto your structure:
- Characters: the stakeholder(s) whose pain anchors the problem, and the team that will own the solution.
- Setup / conflict: the problem statement and the consequence of inaction.
- Plot: your approach, the prototype, the evidence that it works.
- Resolution: the implementation plan and the value the board will see.
A pitch with no character is a feature list with a slide deck. A pitch with character moves the room.
Narrative map
The narrative map is a five-element backbone for any persuasive story. Each element corresponds to a question the board silently asks:
- Focus: what is this fundamentally about? Not the technology; the value at stake.
- Conflict / challenge: what is the problem, and why does it persist?
- Opportunity: what changes once we act?
- Approach: how will we get there in practice?
- Resolution: what does success look like, and for whom?
Delivery
Show, don’t tell
Show, don’t tell.
- Use valid facts and figures.
- Demonstrate your prototype rather than describe it.
- Make the value proposition tangible: a number, a workflow, a screen.
A demo is a special opportunity in your twelve minutes. It converts logos (this is how it works) and pathos (you can see it working) at the same time, and it adds ethos (we built it; we know it). Plan the demo as a tight, scripted slice. An unrehearsed demo destroys ethos faster than any other element of a pitch.
Sell yourself
When you are selling your idea,
the audience must first buy you.
Make sure the audience trusts that you have recognised the problem correctly and can lead the solution to success.
Ethos in a student pitch comes from three things: the depth of your problem framing (you have clearly done the work), the crispness of your team’s allocation of speaking time (everyone owns a part competently), and your handling of Q&A. A team that defends its choices without becoming defensive earns the room. A team that flinches under one tough question loses it.
Look ahead
Everything starts with an idea,
but this is only the beginning.
Present a roadmap: a plan for translating the idea into actions and results.
The roadmap addresses feasibility directly. It does not need to be detailed; it needs to be credible. A two- or three-step horizon with named milestones is usually enough at this stage. The board reads the roadmap as a proxy for “do these people understand what comes after the pitch?”
Time budget
A defensible default split for a 12-minute pitch:
| Section | Time |
|---|---|
| Hook and problem | 3 min |
| Approach and solution | 3 min |
| Prototype demo | 3 min |
| Value, roadmap, ask | 2 min |
| Buffer | 1 min |
Two warnings about the budget.
First, overrunning the problem section is the single most common mistake. It sounds safe (“we want to make sure they get it”), but it eats the time you need for the demo and the ask.
Second, the buffer is non-negotiable. A pitch that lands at 11:30 looks composed. A pitch that races to 12:00 looks stressed and erodes ethos at exactly the moment you need it.
Evaluation criteria
The main criterion is how convincing your pitch and solution are.
In addition, we look at:
- The problem is clearly and comprehensively defined, with a strong understanding of the stakeholder(s) and their needs.
- The proposed approach to value creation is logical, complete, and well aligned with the problem and stakeholder needs.
- The solution is well developed, addresses the problem effectively, and reflects the characteristics of a viable MVP.
- The team communicates clearly, confidently, and professionally, telling a convincing story and using effective visuals.
- The presentation is well structured with clear flow, transitions, and effective use of time.
- The presentation is free from language, spelling, or formatting errors and demonstrates high attention to quality.
The criteria are roughly ordered by the sequence in which they are scored during the pitch. The first two, problem and approach, dominate. A pitch that does not clear them rarely recovers on the strength of the other four.
Key takeaways
- Problem first. You earn the right to talk about your solution by framing the problem in a way the board recognises.
- Mind the asymmetry. You see the full problem; the board sees the slice that matches their priorities. Lead with their slice; back it with your depth.
- Two failure modes. A weak problem kills any solution; a strong problem framing raises the bar your solution must meet.
- Story moves money. Modes of persuasion, four truths, and the narrative map are deliberate tools, not decoration.
- Rehearse the questions. The pitch is often decided in Q&A, not in the prepared minutes.