Project namePITCH DECK (FOR INTERNAL PROJECTS)

Introduction

Preparing for a Management Team presentation can be a pretty daunting task. Whether it’s your first time sending a pitch deck to the MT or you’re presenting it in front of the whole company, a solid structure is fundamental for a coherent and commanding presentation.

Communicating your message with clarity is everything. Given that you have limited time to present and captivate Vice Presidents, presenting with passion, simplicity and power is paramount. We suggest that you organize your pitch deck in the following order as a general guideline. Remember, you only have a short amount of time for this pitch so practice until it’s perfect and stay focused!

Project purpose

The project purpose can be seen as an elevator pitch and stems from the idea that you should be able to deliver a short summary of your project within the time it takes for an elevator ride, so about 30 seconds.  Challenging right? You have a mere 30 seconds to hook the VP and convince them that your idea is worth their time. Experienced VPs will weed out good ideas from the bad ones within the first minute so keep it simple and captivating. We suggest you follow this simple formula:

This project solves [problem] by providing [advantage], to help [target] accomplish [target’s goal]. This project is justified by saving on [cost center] to get [benefit].

Problem

Describe the custuomer (the user) ,Describe the pain of the customer (or the customer’s customer), Outline how the customer addresses the issue today.

“The problem” is your most important asset so it’s imperative to make the VP feel the pain point. Why is this an important problem to solve and how does it affect the end user? One great technique is to use storytelling at this stage and call from personal experiences. More often than not, if it’s a problem you are experiencing and are passionate about, other people have experienced the same problem and the message will ring true.  Keep it punchy, visual and always keep in mind the point of view of the end user.  If it makes sense to engage the VP then do so; ask them how often they have this problem and how they feel about it. Don’t overload the VPs with information, just make sure they feel how terrible this problem is and how no one is currently addressing it in an effective manner.

Solution

Demonstrate your project’s value proposition to make the customer’s life better.  Show where your product physically sits. Provide use cases.

How is your project’s product going to improve the company by fixing this problem? How does the world look after your solution is implemented? Is everyone happy? Remember KISS.  Many people lose their shit at this point and start to get way too technical without actually showing how the product is solving the problem at hand. Keep it visual and to the point. If you have a great design-based product then do a quick demo, but make sure it’s not too long and don’t get lost in the features and complexities, you will lose the VPs. Oh, and make sure the demo works.  You would be surprised how often people make this fatal mistake.  Mission: make them understand why your project solves the problem far better than anything else.

Why now

Set-up the historical evolution of your company regarding your project.Define recent trends / changes in the company that make your solution possible.

But also, Why not now? Why should you wait?

User base size

Identify/profile the user you cater to. Internal user / external user?

Onshore / offshore?

Clients?

HQ or base?

Will this project affect the whole Company or only a small group of engineers? Give an idea on the impact

Alternatives

List alternatives to solve this problem List competitive advantages of this project

This isn’t the only solution to the problem. If it is, you’re probably lost.  You need to show why this project is Batman and everyone is just wearing a cape. How are you solving the problem differently? Be realistic and don’t knock the alternatives. VPs don’t want to hear you criticize the others, as alternatives help grow the overall validity of the problem, but they do want to know why this project is the best way to go. There is always one alternative and that is: Do Nothing.

Product

Product description (form factor, functionality, features, architecture, intellectual property).Development roadmap.

Business Case

How is the investment in this project justified? Keep it high level and in words, only use figures if you have them. This is a pitch, an outline business case and detailed business case will follow when the project starts, but you should be able to provide a short description on the justification.

Team

If you have an idea on who should be in the Project Board and Project Team already, add them here.

Execution strategy

An idea isn’t worth anything without its execution. Give a brief overview how this project will be executed

Don’t’ forget to provide a rough time frame: 2 months or 2 years?

What are the main steps to be taken in this project to get to the end result?

Needs

What do you need to be able to realize your project’s potential? What do you need that you don’t currently have and why? Of-course you need budget, but you also might need commitment, decision power, Board room support.

Expect tough questions and investigation from the VPs as to why you think you will need €X amount for your project.