The Chart Before the Board
A vendor chart claims technician productivity rose 12% after ORION-2. Reconstruct the metric and replace the board message with what the evidence can support.
- ROLE
- Strategy Analytics Partner
- TIMEBOX
- 60–90 minutes
- COMPLEXITY
- Focused / 2 of 5
- ROTATION
- Brief 8 of 16
The decision has already reached your desk.
The vendor renewal deck says technician productivity improved 12% after ORION-2 went live. Its headline chart uses completed stops per planned route hour and labels the pre/post change an optimizer impact.
Routes, route stops, work orders and visits have different grains. Stops can be rescheduled, planned hours are not paid hours, and the deployment date overlaps changing route mix and operating conditions.
The board packet closes in one hour. You may replace the vendor claim with one chart, one title and two supporting bullets. The full procurement analysis can follow later.
Decide what the board can be told about the ORION-2 productivity change and whether the 12% causal wording should remain.
The revised slide must remain legible at presentation distance. It may contain one primary chart, one title, and at most two supporting bullets.
Run the brief as a controlled assignment.
The workbench mounts only the listed source neighborhood and supplies neutral starter worksheets. It does not grade the conclusion or reveal the mechanisms planted in the larger assignment.
- Open the dedicated brief workspace and confirm the brief ID in the queue.
- Establish table grain, cutoff and control totals before joining or modeling.
- Make at least two distinct evidence moves and test a credible rival explanation.
- Leave the requested polished artifact, then export the workspace or portfolio package.
The source files are shared; the draft workspace is not. Changing to another full assignment drops brief mode deliberately.
Real tables. A deliberately bounded neighborhood.
These Parquet files already belong to Meridian’s public 96-table estate. Use the mounted schema.table names in SQL or Python; download links are provided for learners working in a local DuckDB environment.
GRAIN / One technician-vehicle route per date.
CAUTION / A route is not a job, visit or paid shift. Planned and actual measures answer different questions.
GRAIN / One planned or realized stop on a route.
CAUTION / Reschedules and repeated work_order_id values require a declared reconciliation policy.
GRAIN / One service work order.
CAUTION / Final status and resolution fields are post-assignment outcomes and do not share route grain.
GRAIN / One physical visit associated with a work order.
CAUTION / Visits are restricted facts and are not interchangeable with planned stops.
ANALYSIS CUTOFF / Routes dated 01 Jan 2024–31 Dec 2025
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
What does one completed stop represent, and how do reschedules change the numerator?
- 02
Which route-hour denominator matches the business claim, and what alternative denominator changes the result?
- 03
Do monthly and regional trajectories support a clean before/after story or expose a rival explanation?
Leave work another analyst can review.
Artifact presence can be recorded; analytical quality remains a human judgment. A complete brief has evidence, reasoning and a decision—not merely executed code.
- 01Metric reconstruction
Reproduce the claimed productivity measure with a grain contract and compare it with one defensible alternative.
- 02Chart audit and replacement
Identify the material claim problems, then produce one chart with honest scale, timing and annotations.
- 03Board message
Write the replacement title and no more than two bullets separating observed change from attribution.
Review the reasoning after a real attempt.
The debrief does not contain an official answer. It identifies defensible analytical moves, common failure modes and questions a reviewer may use to challenge the handoff.
SPOILER-GATED REVIEW / REVEAL AFTER YOUR FIRST HANDOFF
DEBRIEF REVEALED / THIS MAY CHANGE HOW YOU APPROACH THE BRIEF
A board chart is an analytical claim. Its grain, denominator, comparison window and causal wording matter as much as its visual treatment.
Defensible approaches
- Pre-aggregate stops to route or work-order grain under a declared reschedule policy before joining to routes.
- Plot the metric through time around go-live and inspect regional heterogeneity or alternative denominators as falsification evidence.
- Use descriptive wording for observed change unless the design supports attribution, and keep the board visual focused on the material decision boundary.
Common traps
- Repairing the chart style while retaining a fanout-prone numerator.
- Using planned route hours as technician labor without acknowledging what that denominator measures.
- Labeling a pre/post association as ORION-2 impact or overloading the replacement with every diagnostic.
Reviewer questions
- Would a reasonable viewer infer more certainty or improvement than the data supports?
- Is every reconciliation choice visible where it affects the claim?
- Does the message tell the board what changed, why it matters, and what management is doing next?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEA polished productivity chart was making a stronger causal claim than its data. I rebuilt The Chart Before the Board from The Analyst.
