Start from the situation, not the framework. You will not think "I should use the Assumption Audit." You will think "we made this decision three months ago and I am not sure it is working." Find your situation below. Follow the arrow.
You are about to make a decision
Budget allocation, programme change, pilot launch, resource shift
→
Decision Brief
Confidence vs Consequence Matrix
Data Requirements
Write the Decision Brief first. Structure the question with options, owner, and deadline. Plot it on the matrix. If low confidence + high consequence: design a test, do not commit. Define your must-have data before looking at any dashboard.
You need evidence for a decision question
You have the question but not the answer
→
Inquiry Mode Classification
Qlik Answers
Qlik Predict
Prompt Guide
Classify your question first. Exploratory or Problem-Specific → Qlik Answers (what is happening, why). Comparative or Confirmatory → Qlik Predict (which option is better, is our assumption valid). Use the Prompt Guide to sharpen before you type.
You need to check whether a past decision is still working
Quarterly review, initiative check-in, or something feels off
→
Assumption Audit
Leading Indicator Check
Evidence Check
Go / Adjust / Stop
Run the Assumption Audit: confirmed, untested, or contradicted? Check leading indicators: are the early signals moving? Run the Evidence Check: has new information arrived that you were not looking for? Then decide: Go, Adjust, or Stop.
Someone said no to your data request
Budget refused, IT says the systems cannot do it, leadership is not interested
→
Objection Handling
Justification Pitch
Constructive Escalation
Ask: "What would make it yes?" Identify the objection type (resource, priority, technical, political). Reframe using the Justification Pitch: decision at stake, what data is needed, cost of not having it, value it creates. If blocked, use the Constructive Escalation template.
You need to brief leadership on a recommendation
AD briefing, workplan presentation, programme review, FY26 proposal
→
Context / Tension / Evidence / Recommendation / Consequence
Two minutes, five elements. Context (what happened). Tension (what conflicts). Evidence (what the data shows). Recommendation (what to do, explicitly). Consequence (what happens if you do not). End with the limitation statement: "This analysis does not account for..."
A KPI or dashboard number looks wrong or confusing
Numbers going in unexpected directions, conflicting signals, something does not add up
→
Upstream Question Model
Early Warning System
Logic Model
Trace backwards from the outcome. What had to happen before this number moved? Use the Upstream Question Model to find where in the causal chain the problem sits. Check the early warning indicators: which dimension is breaking (engagement, programmes, service depth, collection, quality)?
Your quarterly or annual review is coming up
FY26 workplan cycle, MDDI reporting, programme review
→
Assumption Audit (all active initiatives)
Leading vs Lagging Check
CE Melissa's Test
Before the review, audit every active initiative. For each: are the original assumptions confirmed, untested, or contradicted? Are you reporting lagging indicators (outcomes) or do you also have leading indicators (early signals)? Apply CE Melissa's test to every report: who looks at it, how often?
You are sitting in front of Qlik and do not know where to start
First time using the tools after training
→
Prompt Guide Checklist
Decision Brief
Blind Spot Documentation
Do not start with the tool. Start with the question. Open your Decision Brief. Classify the inquiry mode. Write the prompt using the Prompt Guide starters. Name your blind spot. Then type. The tool amplifies the question. It does not replace it.