- BLUE HELP
- Discovery Interviews (Step 2)
- How to handle confidential info in an interview
-
Blueprinting Center & Methodology
- What is New Product Blueprinting?
- How is Blueprinting learned and applied?
- Blueprinting Center
- Blueprinting E-Learning Course
- How can I become Certified in New Product Blueprinting?
- 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?"
-
Blueprinter® Software
-
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)
-
Everyday VOC
-
Minesweeper® De-risking
1. Should you sign an NDA for a Discovery interview?
You don't need--or even want--an NDA. But your customer may.
In many industries, it’s common practice to cover supplier-customer discussions under a non-disclosure agreement (NDA). And this is especially true if technical people are meeting from each side. This is done to protect intellectual property in situations such as these:
- A clever technical idea arises from the discussion. Later, without good documentation, conflict could arise as the supplier and customer try to sort out who “owns” this idea.
- For an idea to patentable, it must be useful, non-obvious and novel (new to the world.) If the supplier’s idea is discussed without an NDA, the idea becomes part of the public domain, and is therefore no longer “novel” and patentable.
But if you are conducting a Discovery interview, do you need an NDA to protect yourself? No, because you’re going to stay strictly in “outcome space,” not “solution space.” Even if the customer offers a solution, you’ll ask, “What would that do for you?”... to quickly move back into outcome space.
So your preference should be to conduct the Discovery interview without an NDA... to avoid slowing the process down engaging lawyers, getting approvals, etc. But what if your customer wants an NDA? We'll cover ways to handle this in the next BlueHelp article, How to handle customer requests for an NDA.
Keywords: NDA, non-disclosure agreement, CDA, confidential disclosure agreement, lawyer, legal, patent, novel, outcome space, solution space, secret information, confidential information