Executive Ecommerce
Dashboard
Most of dashboard work isn't SQL or charts - it's stakeholder iteration. A CEO asks for something vague. You translate into a concrete plan, ship a rough first draft, get reactions, iterate, polish. This project drops you into that loop. The reviewer plays the exec: their feedback on your first draft IS the stakeholder reaction you'll respond to. The deliverable is a portfolio piece that shows you can build dashboards *and* survive the conversation around them.
What you'll learn
- —Translate vague exec asks ('I want to know if we're growing') into measurable KPIs
- —Ship a fast, ugly first version on purpose - and resist polishing prematurely
- —Engage analytically with stakeholder feedback: address most of it, push back on some of it
- —Defend visual and analytical choices in writing, with rationale
- —Ship a portfolio that demonstrates dashboard skill *and* the analyst-stakeholder conversation
The 5 milestones
Each milestone is reviewed before you advance.
- 01
Set up your project repo
Before any analytical work: create a public GitHub repository, push the standard skeleton, and paste the URL into your workspace.
- 02
Requirements interview - translate the ask
Turn a vague exec ask into a concrete, signed-off KPI plan. No analysis yet, no charts - just the plan.
- 03
Rough first draft - ship ugly to the exec
Build the *rough* version. Don't polish. Submit for review and treat the feedback as the exec's reaction.
- 04
Iterate - engage with the exec's feedback
Read the M3 review as if it came from the CEO. Revise the dashboard. Defend what you're keeping; change what's worth changing.
- 05
Polish + portfolio
Final pass for recruiters. README, polished screenshots, optional public URL, executive summary.
Reading & references
Build your portfolio & get certified
Want more projects like this? Join our Data Analyst Work Experience Program to complete 5+ guided industry projects, gain real experience, and earn an internship certificate.