Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a more rigorous dashboard for a stated stakeholder and decision. Requirements: gather requirements (state the DECISION, AUDIENCE, and questions it must answer); build a clean data model with a documented SEMANTIC layer (measures defined once, consistent definitions); include a metric using TIME INTELLIGENCE (year-over-year or a running total); apply an ANALYTICAL technique (segmentation, or a funnel/cohort) that surfaces a real insight rather than just totals; design the dashboard with clear HIERARCHY (key KPI top-left) plus a data-STORYTELLING element (a title/annotation stating the so-what); and add row-level security OR a documented metric definition for governance. Explain one insight and the action it implies.
A stated decision/audience/questions; a documented semantic layer with consistent, defined-once measures.
A time-intelligence metric plus a segmentation/funnel/cohort that surfaces a real insight (not just totals).
Clear visual hierarchy + a storytelling so-what; row-level security or documented metric definitions.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A governed, insight-driven dashboard ## Goal Build a more rigorous dashboard for a stated stakeholder and decision. Requirements: gather requirements (state the DECISION, AUDIENCE, and questions it must answer); build a clean data model with a documented SEMANTIC layer (measures defined once, consistent definitions); include a metric using TIME INTELLIGENCE (year-over-year or a running total); apply an ANALYTICAL technique (segmentation, or a funnel/cohort) that surfaces a real insight rather than just totals; design the dashboard with clear HIERARCHY (key KPI top-left) plus a data-STORYTELLING element (a title/annotation stating the so-what); and add row-level security OR a documented metric definition for governance. Explain one insight and the action it implies. ## Acceptance criteria - [ ] Requirements & model: A stated decision/audience/questions; a documented semantic layer with consistent, defined-once measures. - [ ] Insight & analysis: A time-intelligence metric plus a segmentation/funnel/cohort that surfaces a real insight (not just totals). - [ ] Design & governance: Clear visual hierarchy + a storytelling so-what; row-level security or documented metric definitions. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.