Shape the solution · Shape and justify the solution

Shape a solution hypothesis

Connect the documented problem to options, dependencies, and a validation plan.

Produce this

Solution hypothesis and validation plan

Finish with an artifact another professional can review, challenge, and act on.

Do the work
Sales situation

When to use this

Connect the documented problem to options, dependencies, and a validation plan. Use it when the decision matters enough that source authority, uncertainty, and human review must stay visible.

Choose the path

Match the depth to the consequence

Quick

Produce the minimum useful solution hypothesis and validation plan from the controlling sources and flag gaps.

Working

Compare sources, classify evidence, produce the solution hypothesis and validation plan, and run the task-specific checks.

Thorough

Add a countercase, conflict review, stakeholder challenge, and explicit validation plan before action.

Inputs and information boundary

Bring only what the task needs

  • The decision this work must support
  • Current, approved source material
  • Known constraints and open questions

Boundary: Approved customer information in an employer-approved environment; otherwise use public or fictional material.

Do not add credentials, unnecessary personal information, private security details, unapproved pricing, contracts, or customer material.

Do the work

Work sequence

  1. State the decision the solution hypothesis and validation plan must support.
  2. Select the controlling sources and record their date, owner, and authority.
  3. Separate customer evidence from seller interpretation before asking AI to synthesize.
  4. Build the solution hypothesis and validation plan and label Known, Inferred, Assumed, and Unknown.
  5. Challenge the result with contrary evidence and complete the verification checks.
Prompt pattern

Shape a solution hypothesis

GOAL
Form a testable response to the customer problem without declaring a product the answer first.

CONTEXT
The account, audience, decision, and current sales stage are [CONTEXT].

CONTROLLING SOURCES
Use only [APPROVED SOURCES]. Identify the source behind every material fact.

TASK
State the problem, desired outcome, constraints, options, evidence, dependencies, risks, assumptions, and validation steps.

CONSTRAINTS
Do not invent customer intent, authority, dates, budgets, pricing, commitments, product capabilities, legal conclusions, or missing facts.

REQUIRED OUTPUT
Solution hypothesis and validation plan

UNCERTAINTY BEHAVIOR
Separate Known, Inferred, Assumed, and Unknown. Show conflicts instead of resolving them without evidence. Turn important unknowns into questions.

VERIFICATION REQUEST
List the claims, calculations, names, dates, owners, commitments, and source conflicts a human must verify before acting. Construct the strongest evidence-based case against the proposed conclusion.
Completed fictional example

Northstar example

Fictional training material

For Northstar, the hypothesis compares phased operating improvements and platform changes against visibility, handoff, capacity, and migration constraints.

Verify before acting

Task-specific checks

Next human action

Make the next move accountable

Review the artifact with the accountable human owner, resolve the highest-consequence unknown, and record only verified facts in the system of record.

Why this works

The sequence starts with the decision and source authority, so fluent output cannot quietly replace evidence. The countercase turns uncertainty into focused customer questions.

Common failure

A weak AI request

“Create a polished solution hypothesis and validation plan and make it persuasive.”

This request has no controlling sources, evidence boundary, uncertainty behavior, or verification step. It rewards confident prose instead of dependable work.

Scenario exercise

Practice safely

Build two Northstar options and name the evidence needed to choose between them.

Open Northstar exercises
Related tasks

Continue the work