東京工業大学

エンジニアリングデザインプロジェクト

エンジニアリングデザインコースの必修科目であり、約半年間をかけたPBL型の授業です

Pitch Template

Slide0 (Title):

  • Product Name and Tag Line
  • Photo of your Prototype
  • Desgin Prompt
  • Corporate Partner (if any)
  • Team Name
  • Team Members
  • Date
  • (For the regular classes)
    • The number of recent interviews
    • Total number of interviews
    • The number of recent user tests
    • Total number of user tests

Slide1: Prototype

  • Photo of your Prototype
  • Show and describe your prototype very concisely.
  • Clearly state the people (target users) who will get the value.
  • It would be better to use a Elevator Pitch Template below.
For [ target user ] who [ situation or needs ],
the [ product name ] is a [ product category ],
which has [key benefit ].
Unlike [ competitive alternative ]
our product has [ unique differentiation ].

Slide2: Background

  • Clearly state the situation (context) you are researching.
    • [WHO] under the condition of [WHAT] is doing [HOW]. Because [WHY].

🔨 toolkit

Slide3: Unique Insight

  • Tell us what only you know through the user research.
  • You can use the last line of POV as insight.
    • But actually / However / We wonder if this means ...
  • You can use HMWQ as a part of the insight.

🔨 toolkit

Slide4: Design Principles

  • What kind of “Design Principles” have you set to design the solution?
  • You can use HMWQ as Design Principles.

🔨 toolkit

Slide5: Solution

  • Features and Specifications.
  • Describe the concrete benefits (especially user experience rather than product itself) you provide.
  • What are your differentiating factors?

🔨 toolkit

✔️ checklist

  • Is your product tangible? / そのプロダクトはタンジブルなものですか？
  • Does your product include engineering elements? / そのプロダクトにはエンジニアリング要素が入っていますか？
  • Is the product feasible for your team? / そのプロダクトはチームで実現可能なものですか？
  • Are there some similar products and the differentiating factors of your product? / そのプロダクトの類似製品と差別化要因は何ですか？
  • Does the product successfully provide the value? / そのプロダクトは本当に価値を提供していますか？

Slide6: User Story

  • Draw your story boad using a four-panel comic format or Story Spine format.

🔨 toolkit

✔️ checklist

  • Is it clear that new experiences or behaviors brought to users by providing the value? / その価値を提供することで、ユーザーに生まれる「体験や行動」は明確ですか？
  • Is there a story how your product improved experience or behavior of the user? / ユーザーの体験や行動が変わったことを示す物語はありますか？

Slide7: Voice of User

  • How much does it solve the problem? Give us some evidences.

🔨 toolkit

✔️ checklist

  • Are there any data that supports your success (e.g. the result of user test). / 成功を裏付けるデータ（ユーザーテストの結果など）はありますか？

Slide8: Future Work

  • Do you have any future plan?

🔨 toolkit

Slide9: Ending and Call To Action

  • Photo of your prototype (again).
  • What do you want the audience to do next?
  • DO NOT end with just “Thank you” slide.

Tips for the pitch

  • You should have at most 3 pages per a slide (the title slide must be one page)
  • You can insert the video anywhere you want.
    • It is appropriate to put it after the elevator pitch slide.
  • You SHOULD use the format of POV and/or HMWQ, but you SHOULD NOT use design thinking jargon (e.g. POV, HMW, or so) in your presentation.
    • POVやHMWQのフォーマットは使用すべきですが、デザイン思考の用語（例：POVやHMWQなど）はプレゼンに入れてはいけません。
  • When creating a slide with a team, it is better to make it with something that everyone can edit at the same time, such as Google Slides. In addition, Google Slide looks different fonts if you use different OS, but you can solve it by using Japanese web fonts. Select [Japanese] from the [Other Fonts …] menu and select the font you want to use. / チームでスライドを作るときは、Googleスライド等みんなで同時編集できるもので作ったほうがよいです。なお、Googleスライドは使用するOSが違うとフォントが違って見えますが、日本語のウェブフォントを使うと解決できます。［その他のフォント…］メニューから［日本語］を選択して、使いたいフォントを選んでください。

References