Shape a solution hypothesis
Connect the documented problem to options, dependencies, and a validation plan.
Solution hypothesis and validation plan
Finish with an artifact another professional can review, challenge, and act on.
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.
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.
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.
Work sequence
- State the decision the solution hypothesis and validation plan must support.
- Select the controlling sources and record their date, owner, and authority.
- Separate customer evidence from seller interpretation before asking AI to synthesize.
- Build the solution hypothesis and validation plan and label Known, Inferred, Assumed, and Unknown.
- Challenge the result with contrary evidence and complete the verification checks.
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.
Northstar example
For Northstar, the hypothesis compares phased operating improvements and platform changes against visibility, handoff, capacity, and migration constraints.
Task-specific checks
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.
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.
Practice safely
Build two Northstar options and name the evidence needed to choose between them.
Open Northstar exercises