MODULE 05 — LEARNER WORKSHEET
Attempt the tasks before comparing the worked example. Keep work locally.

1. Start with the reader, decision and metric contract
 Read dashboard_brief.txt and metric_dictionary.txt. Write your own brief for the operations lead, choosing no more than four headline cards and two diagnostic views. For each card specify its source fields, eligibility rule, units, denominator where relevant and unavailable behaviour. State the initial filter and comparison window.   Deliverable:  a one-page decision brief and metric contract. Include two requested metrics that the source cannot support, and name the missing inputs rather than inventing substitute measures. 

My method / result / checks / remaining questions:


2. Build a clear reading order before styling
 Open dashboard_starter.html as a local wireframe and sketch your own version using the supplied brief. Label the decision/scope area, filter controls, four cards, two charts, explanation, evidence table and definitions. Draw a narrow-screen version using the same reading order.   Deliverable:  a desktop and mobile wireframe plus a short justification for the position of the channel warning. You may build in your spreadsheet or preferred local tool; editing HTML is optional. The scaffold has no calculated values or working filter controls. 

My method / result / checks / remaining questions:


3. Choose charts that preserve the comparison
 Create a monthly completed-value chart and a channel-AOV chart for the initial May/All view. Show units, zero baselines for bars, exact values and group counts. Supply a readable numerical alternative. Then explain what must change when April or Web is selected.   Deliverable:  two charts and their source tables, plus a note on whether your scale is fixed or recalculated per view. Include a corrected version of a misleading headline that treats an unweighted channel mean as actual AOV. 

My method / result / checks / remaining questions:


4. Make filters, comparisons and empty states consistent
 In your own prototype, implement or specify period and channel controls with a May/All reset state. Test May/All, April/All, combined/All, May/Web, May/Store and a deliberately empty selection. Record the expected totals, counts, AOVs, coverage and comparison availability for each.   Deliverable:  a state-test matrix and an explanation of how all dependent visuals and text update. Use expected_states.json after attempting the calculations. Include a failure example in which a May/Web card incorrectly compares against April/All, then show the corrected denominator. 

My method / result / checks / remaining questions:


5. Write explanations that match the selected evidence
 Write a 100–150 word explanation for May/All using observation → context → limitation → next action. Then write a 40–70 word version for May/Web. State which sentences must update with filters and which can remain as clearly scoped wider-fixture context.   Deliverable:  two notes and a corrected version of “The initiative increased profit by 18% and delivery improved.” Explain each unsupported part and replace it with the measures the source actually supplies. 

My method / result / checks / remaining questions:


6. Review calculations, accessibility and refresh claims
 Use review_checklist.txt and expected_states.json to review your prototype. Check all six main states, reset, table reconciliation, missing-versus-zero behaviour and one changed input on a disposable copy. Inspect keyboard navigation, text alternatives and narrow-screen reading.   Deliverable:  a test record with expected/observed results, a list of unresolved issues and a handover note. State honestly whether the source is a static fixture or a live feed; do not invent a refresh time or claim full accessibility certification. 

My method / result / checks / remaining questions:


7. Deliver a dashboard and a concise stakeholder walkthrough
 Build and submit to your own local evidence folder a complete dashboard, the source CSV, metric contract, 100–150 word decision note, state-test record and two-minute walkthrough outline. Include a desktop and narrow-screen view or an explicit limitation of your chosen tool.   Self-review:  metric correctness/reconciliation 0–2; layout/charts 0–2; filters/edge states 0–2; explanation/limits 0–2; reproducibility/usability 0–2. Aim for at least eight, with no zero in metrics or interaction. Work remains on your device; there is no course upload or automatic grading. 

My method / result / checks / remaining questions: