Review pipeline assumptions
Inspect portfolio definitions, data quality, forecast assumptions, and concentration risk.
Pipeline assumption and risk review
Finish with an artifact another professional can review, challenge, and act on.
When to use this
Inspect portfolio definitions, data quality, forecast assumptions, and concentration risk. 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 pipeline assumption and risk review from the controlling sources and flag gaps.
Working
Compare sources, classify evidence, produce the pipeline assumption and risk review, 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 pipeline assumption and risk review 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 pipeline assumption and risk review and label Known, Inferred, Assumed, and Unknown.
- Challenge the result with contrary evidence and complete the verification checks.
Review pipeline assumptions
GOAL Identify records and assumptions needing human review without scoring employees. 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 Confirm grain and definitions, identify missing or stale fields, duplicates, concentration, forecast assumptions, stage inconsistencies, and the records needing accountable review. CONSTRAINTS Do not invent customer intent, authority, dates, budgets, pricing, commitments, product capabilities, legal conclusions, or missing facts. REQUIRED OUTPUT Pipeline assumption and risk review 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
The Northstar duplicate workstream inflates totals and missing stage definitions prevent reliable stage comparison.
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 pipeline assumption and risk review 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
Explain how the Northstar duplicate and undefined stage distort a portfolio view.
Open Northstar exercises