Tool 3.2: AI Job and Outcome Statement Quality Check
Learn how Blueprinter checks Job and Outcome Statements, identifies quality issues, and helps prepare them for customer prioritization.
Overview
During Step 2 (Discovery), Blueprinting teams interview customers to identify their needs and capture those needs as Outcome Statements.
Step 3 (Preference Research) builds on this work. The team brings together the outcomes identified across multiple customer interviews, prepares them for prioritization, and ultimately determines which needs are most important and least satisfactorily addressed.
Step 3 preparation can begin after all Discovery Interviews have been completed, or it can take place alongside the Discovery process. Teams may choose to process some interview results while additional interviews are still underway.
An important activity in Step 3 is preparing the Top Picks selected during Discovery.
Ideally, each Top Pick already contains a well-written Outcome Statement. However, some notes may still contain only raw customer comments, while others may have statements that are vague, ambiguous, or otherwise difficult to prioritize.
Blueprinter's AI Job and Outcome Statement Quality Check helps identify these situations and provides an opportunity to correct them before proceeding.
The feature recognizes both measurable Outcome Statements and broader Jobs-to-Be-Done statements.
How to Use the AI Quality Check
Step 1: Open Prepare Top Picks
Navigate to Step 3 (Preference Research) → 3.2 Prepare Top Picks.
The TP Staging Area contains sticky notes that were identified as Top Picks during Discovery Interviews.
These notes represent customer needs that will be considered for prioritization.
Step 2: Drag a note into the working area
Drag a sticky note from the TP Staging Area into the white working area.
Blueprinter automatically evaluates the statement at the beginning of the note.
One of three things will happen.
Situation 1: The statement is acceptable
If Blueprinter determines that the note contains an acceptable Job or Outcome Statement, it moves into the working area without interruption.
For example:
- Minimize the time required to replace a hydraulic pump.
- Install a replacement hydraulic pump.
Both are acceptable. The first is an Outcome Statement describing a measurable improvement. The second is a Job Statement describing something the customer wants to accomplish.
You can continue processing the next note.
Situation 2: The statement may need improvement
If the statement begins with a verb but has potential quality problems, Blueprinter displays a short explanation.
Common concerns include:
- Vague improvement: The desired improvement is not specific enough, such as "Improve mower performance."
- Subjective wording: The statement uses wording that may be interpreted differently by different customers, such as "Make the mower easier to operate."
- Multiple needs combined: Two or more independent needs are included in the same statement.
- Solution-focused statement: The wording prescribes a solution rather than describing the customer's job or desired outcome.
- Ambiguous meaning: The statement is unclear or could be interpreted inconsistently.
Blueprinter provides up to two specific concerns and offers three options:
Use as is: Accept the existing statement without making changes.
Edit manually: Modify the statement yourself.
Generate with AI: Ask Blueprinter to analyze the original customer verbatim and suggest one or more Outcome Statements.
These warnings are advisory. If you believe the existing statement is appropriate, you may continue using it.
Situation 3: No usable statement is present
Sometimes a Top Pick contains only the customer's original comments.
For example:
"When operators use these mowers, sometimes the mower tends to drift off to the left or the right. They find themselves continually making adjustments..."
Because this note does not begin with a Job or Outcome Statement, Blueprinter requires you to correct it before proceeding.
You have two options:
Edit manually: Write a Job or Outcome Statement at the beginning of the note.
Generate with AI: Have Blueprinter suggest Outcome Statements based on the original customer verbatim.
Unlike a quality warning, this situation requires a correction. At a minimum, the statement must begin with an appropriate verb.
Using AI to Generate Missing or Improved StatementsWhen you select Generate with AI, Blueprinter analyzes the original customer verbatim and suggests one or more Outcome Statements.
Review the suggestions and select those that accurately represent the customer's needs.
If you select multiple statements, Blueprinter creates a separate sticky note for each accepted outcome and places them in the working area.
Each note contains:
- The accepted Outcome Statement at the beginning.
- A blank line separating the statement from the original customer comment.
- The complete, unchanged customer verbatim.
If none of the AI suggestions are appropriate, you can instead write or correct the statement manually.
The original customer comments remain intact throughout this process.
Important Things to Remember
- Good statements pass automatically. You don't need to take any action when Blueprinter recognizes an acceptable statement.
- Both Job and Outcome Statements are allowed. A statement does not necessarily need a measurable improvement metric to be acceptable.
- Statements must begin with a verb. This is the minimum requirement for moving a Top Pick into the working area.
- Quality warnings are advisory. You can accept a questionable statement as written if you believe it is appropriate.
- AI suggestions require your approval. Blueprinter does not automatically replace an existing statement.
- Customer verbatims are preserved. Whether you make a manual correction or generate statements with AI, the original customer comments remain unchanged.
- One outcome per note. If AI identifies several distinct outcomes, you can create separate notes for each one.
Video Demonstration
Watch the video below to see how Blueprinter checks Top Picks, identifies potential quality problems, and helps you generate or improve statements before prioritization.