Build a performance dashboard

Build a performance dashboard for Black Friday planning that compares year-over-year revenue, mobile vs desktop conversion rate, top five SKUs by revenue, and hourly traffic during the peak sales window. Share it with Priya in operations, Marco in merchandising, and Sasha in paid search with view-only access. Freeze the dashboard baseline to last year’s Black Friday for comparisons and validate that product SKUs map to our catalog IDs before publishing.

Before I hand the Black Friday dashboard to Priya, Marco, and Sasha, make it actionable: put year-over-year revenue and percent change at the top, highlight mobile conversion gap, and add a simple playbook note for when hourly traffic exceeds last year’s peak. Ensure SKUs reconcile to the catalog, label any data that is sampled, and make the peak-hour chart easy to export to the war-room spreadsheet.

I started the Black Friday performance dashboard but SKU mapping to catalog IDs is incomplete and Priya needs it for ops planning. I’m afraid publishing now will mislead decisions, but I don’t know which missing mappings matter most. Which quick triage will reduce risk: prioritize top revenue SKUs, check category-level totals, or publish with a clear caveat?

For every sale we scramble the week before to fix SKU mapping, currency mismatches, and hourly granularity for a single seasonal dashboard. Where are we wasting time and credibility — in late data reconciliation, no pre-season checklist, or unclear ownership — and which two habits should we change so season dashboards are ready two weeks early?