Start with something familiar
A kiosk sells more drinks on the day it posts a discount sign. That day is also hot, and a school race passes nearby. The increase is real, but the sign may not deserve all the credit. Repeating the offer on a cold quiet day may produce a different result. A useful plan names the other changes and explains which conditions need to recur before expecting the same uplift again.
Words to know: Confounding, Scenario, Demand.
Show a baseline bridge
A promotion plan starts with demand expected without the event and adds an explicit incremental effect. Northstar baseline forty with a twenty-five-percent uplift gives fifty. Keep the ten-unit addition separate. Record dates, price, channel, displays, distribution, and whether the affected customers already appear in the baseline or firm orders.
A promoted week of seventy versus normal forty does not prove thirty incremental units caused by promotion. Distribution, weather, holidays, or stock availability may also change. When events always occur together, the data may not identify their separate effects. Describe what the comparison shows without claiming more than the evidence supports.
Inspect controls and spillovers
Suppose a promoted region rises from forty to seventy while an untreated region rises from thirty to forty-five. Changes are thirty and fifteen, leaving a difference in changes of fifteen. A causal interpretation requires comparable untreated trends and no other unequal shocks. One before and one after observation cannot establish those assumptions.
Promotions can pull demand from later weeks or shift customers between Northstar SKUs. Inspect the event window and follow-up weeks at both product and company levels. A large uplift on one SKU can coexist with a small company increase. More units also need not mean higher margin; commercial evaluation requires its own price and cost inputs.
Keep uncertainty explicit
Use conditional cases when evidence is limited. Baseline forty plus uplift assumptions zero,ten,twenty gives forty,fifty,sixty. These are not automatically probability intervals. State what would make the high case plausible, such as verified extra stores. Do not average scenarios into an expected value unless defensible probabilities are supplied.
Afterward, preserve the original forecast and record whether the offer actually ran as planned. Stockouts can hide demand during the event. Separate execution differences, measurement limits, and forecasting error. Replacing an original uplift with the observed difference destroys the record needed to learn whether the adjustment process helped.
- Define target
- Check evidence
- Calculate
- Challenge assumptions
- Record decision
Separate uplift from coincidence — worked case
All inputs below describe fictional Northstar bottles. Keep the stated units and timing when reproducing the calculation.
| Region | Before | During | Change |
|---|---|---|---|
| Promoted | 40 | 70 | 30 |
| Control | 30 | 45 | 15 |
- 1. Promoted change = 70 - 40 = 30.
- 2. Control change = 45 - 30 = 15.
- 3. Difference in changes = 30 - 15 = 15.
Fifteen is an adjusted comparison; causal interpretation needs additional assumptions.
Assumptions
- Periods and quantities use the definitions stated in this example.
- Only explicitly supplied events or adjustments are included.
Where this can fail: The arithmetic checks the stated assumptions; it does not establish that uncertain future events will occur.
Build, test and explain a plan
Six weekly A baselines are forty each. Promotion weeks three and four add ten each in the base case; week five loses six to pull-forward. B baseline twenty each; B loses three in each promotion week. No other changes. All units are bottles unless stated otherwise. Use a spreadsheet or ruled paper. Eight hours includes construction, comparison, writing, and teach-back; this is a planning estimate, not an experimentally validated completion time.
Use paper or a spreadsheet. The estimates below include the study and worked example already on this page.
| Estimated hours | Activity |
|---|---|
| 0.5 | Study the lesson and write a data dictionary defining every field, time bucket, unit, and cutoff. Separate observed facts from assumptions. Identify two ways a colleague could misread the target and rewrite its definition to prevent those errors. |
| 0.5 | Reproduce the worked example independently, showing formulas and intermediate values. Compare against the answer and keep a correction log explaining each difference. Check one result a second way using a total, balance, or direct manual calculation. |
| 3 | Build weekly baseline and adjusted demand for A,B,total. Keep uplift, pull-forward, and cannibalization separate. Compare six-week and promotion-only totals. Keep inputs separate from formulas, label every origin and target, and add independent row and total checks. Produce an annotated chart with at least two observations tied to specific rows; include a brief explanation of why each check matters. |
| 2 | Low/base/high assumptions are A uplift [0,10,20] per promotion week, A week-five loss [0,6,12], and B loss [0,3,6] per promotion week. Then cap A shipments at forty-five in each promotion week while preserving demand. Preserve each variant separately. Create an output comparison table and explain which changed assumption caused each movement. Identify a scenario that affects timing differently from totals and state what the planner should do with that distinction. |
| 1 | Write a 400-word decision memo using your own numerical outputs. State the proposed action, evidence, two limitations, an owner for the next check, and a measurable condition that would change your recommendation. Attach the model so a reader can audit every cited value. |
| 1 | Prepare a five-minute teach-back using one worked row and one scenario comparison. Explain it aloud to a colleague or recording. Write three skeptical questions, answer them with evidence, and revise the memo or model where your explanation exposes an unsupported assumption. |
Your deliverables
- Auditable input and formula model with checks
- Scenario comparison and annotated chart
- Decision memo, correction log, and teach-back notes
Check your practice work
- Base A [40,40,50,50,34,40], total 254; B [20,20,17,17,20,20], total 114.
- Company baseline total 360; base 368, net increment eight.
- Linked low/base/high totals are 360,368,376.
- Shipment cap hides ten base-case A demand units across the two promotion weeks, assuming no later recovery.
- Difference-in-changes calculation is fifteen, with causality unresolved.
Keep these three ideas
- Build promotion scenarios without treating a before-after difference as causal proof.
- Keep original evidence distinct from modeled values and assumptions.
- A precise output remains conditional on definitions and timing.
Common mistakes
- Overwriting the original evidence after a revision.
- Reporting a number without its unit, period, cutoff, and assumptions.
Optional video study
Build promotion scenarios without treating a before-after difference as causal proof.
- Show a baseline bridge
- Inspect controls and spillovers
- Keep uncertainty explicit
One half of the module narration, with a distinct Northstar calculation and a bridge to the paired lesson.
Open the module media & quizPut this idea to use
Carry your assumptions into a practical tool, then compare your result with a short guide.
Open a related planning toolRead the related planning guidePractice with the planning gameThis saves a completion marker in this browser only. It does not verify time spent.