- What is New Product Blueprinting?
- How is Blueprinting learned and applied?
- How does Blueprinting fit with a stage-and-gate process?
- How does Blueprinting fit with strategic planning?
- How does Blueprinting fit with Design Thinking?
- How does Blueprinting fit with Lean Startup?
- How does Blueprinting fit with Minesweeper de-risking?
- How does Blueprinting fit with LaunchStar product launch?
- What innovation metrics should we use?
- What is "Jobs-to-be-Done?"
Market Segmentation (Step 1)
Discovery Interviews (Step 2)
- How to plan Discovery interviews
- Preparing your interview team
- Convincing customers to be interviewed
- How to handle confidential info in an interview
- How to conduct a Discovery interview
- Finding & using a digital projector for interviews
- How to conduct a customer tour
- How to debrief & follow-up a Discovery interview
- Engaging your sales colleagues in interviews
- Engaging distributors in interviews
- Interviewing customers down the value chain
- How to interview remotely with web-conferences
- How to interview at trade shows & other venues
- Interviewing in different global cultures & languages
- How to listen well during customer interviews
- How to probe during customer interviews
- How to gather economic data during interviews
- How to create & use Current State questions
- How to identify Must Haves (MH)
- How to select Top Picks (TP)
- How to use Trigger Maps
- How to form Outcome Statements
Preference Interviews (Step 3)
Rest of Blueprinting (Steps 4-7)
VIDEO: Tool 1.5 - How to Define Project Scope
Your project scope should have an audience and a topic. The topic is either a product or a job-to-be-done.
From a data entry perspective, there's not much to Tool 1.5. You just type in your scope. It should have an audience as well as a topic. And these two should align. If you select "Design Engineers" as your audience, then your topic could be a product, such as a zero turn radius mower, or a job-to-be-done, such as "Design a zero turn radius mower."
A product-based perspective will be preferred when your scope of innovation is relatively modest and when technologies are stable. However, if interested in disruptive innovation or defining a longer term road map, then a jobs-perspective is a better option. It is not a difficult process, but it is something that requires some thought. And if you do use a jobs-based route, expect to spend time with your team to ensure that you've picked the job correctly.
This video expands and this concept and demonstrates how to complete Tool 1.5 within the software.