Built from years of watching good data get ignored
This course did not start as a course. It started as a repeated observation across marketing teams: the reporting was never the problem. What people did with it was.
A recurring pattern across very different teams
Before this course existed, its ideas were tested informally, inside internal workshops for marketing operations groups and agency reporting teams. The pattern kept repeating. A dashboard would be technically excellent, accurate data, clean visuals, correct pipelines, and still fail at its actual job. Meetings would end with more questions than decisions.
The common thread was almost always structural. Dashboards were organized around data sources rather than around the decisions people needed to make. A paid social tab. An email tab. A website analytics tab. Each one internally consistent, none of them built to answer "what should we change this week."
That observation became the starting point for a different way of teaching dashboard design, one that treats layout and hierarchy as seriously as the underlying metrics.
Reporting exists to shorten the distance to a decision
Everything taught in this course traces back to one working principle: a dashboard's job is not to display what happened. It is to reduce the time between "here is the data" and "here is what we do about it." That principle shapes layout choices, metric selection, and even the language used in annotations.
Structure before styling
Color and chart type get attention, but the grid and hierarchy of a dashboard do the real work of guiding attention toward what matters.
Fewer metrics, more context
A dashboard with six well-chosen metrics and clear framing tends to get used more than one with forty metrics and none.
Decisions are the audience
Every screen is designed around a specific decision someone needs to make, not around a department or a data source.
Iteration over perfection
Dashboards should be treated as living documents that get revised as the questions a team asks change over time.
Governance matters
Without ownership and versioning, even a well-designed dashboard drifts back into sprawl within a few reporting cycles.
From informal workshops to a structured cohort
Internal sessions
Early versions were run as internal workshops for operations teams working through their own dashboard backlog.
Small group testing
Sessions opened to small mixed groups from different companies, which surfaced how differently teams define "actionable."
Framework documentation
The recurring structure was written down as a repeatable framework, later named the Decision Layer approach.
Cohort format
The current six-week cohort format was built to give the framework enough time to be applied, critiqued, and revised.
A small teaching team, not a lecture hall
Sessions are led by practitioners who have spent years inside marketing operations and analytics roles, not exclusively as trainers. Group sizes stay small enough that critique sessions can address the specific dashboards participants bring, rather than a generic case study.
Guest sessions occasionally cover adjacent topics, such as how finance teams read marketing reporting differently than marketing teams do, or how agencies structure recurring client dashboards without rebuilding them from scratch every month.