Build and challenge a business case
Make benefits, costs, risks, assumptions, and evidence gaps visible.
Business-case outline and challenge log
Finish with an artifact another professional can review, challenge, and act on.
When to use this
Make benefits, costs, risks, assumptions, and evidence gaps visible. 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 business-case outline and challenge log from the controlling sources and flag gaps.
Working
Compare sources, classify evidence, produce the business-case outline and challenge log, 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 business-case outline and challenge log 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 business-case outline and challenge log and label Known, Inferred, Assumed, and Unknown.
- Challenge the result with contrary evidence and complete the verification checks.
Build and challenge a business case
GOAL Create a transparent business case without inventing customer financial values. 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 Organize expected outcomes, benefit logic, cost categories, risks, assumptions, evidence gaps, sensitivity questions, and a validation plan. CONSTRAINTS Do not invent customer intent, authority, dates, budgets, pricing, commitments, product capabilities, legal conclusions, or missing facts. REQUIRED OUTPUT Business-case outline and challenge log 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
Northstar has no validated savings figure. The case can describe cost categories and outcome measures, but numbers remain assumptions until customer-supplied.
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 business-case outline and challenge log 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
Remove the unsupported cost-and-risk reduction claim from the Northstar proposal and build a validation plan.
Open Northstar exercises