Four layers between raw data and a decision
This is the structure taught throughout the course. It is not a plugin or a chart type. It is a way of organizing a dashboard so each layer does one job, and together they carry a viewer from a number to an action.
Why four layers instead of one big chart
Most dashboards fail quietly. Not because the data is wrong, but because everything is presented at the same level of importance. A viewer has to do the work of separating signal from context from conclusion, every single time they open the screen.
The Decision Layer framework splits that work into four distinct layers, each with a clear job. Once a team internalizes the separation, building a new dashboard becomes closer to filling in a known structure than starting from a blank canvas.
Signal Layer
The small set of metrics that genuinely move the needle for the decision at hand. Usually no more than five or six numbers, chosen deliberately rather than inherited from whatever the data source happened to export.
Context Layer
Comparison points that give the signal meaning: prior period, target, or a relevant benchmark segment. Without this layer, a number like "3.2% conversion rate" tells a viewer almost nothing on its own.
Decision Layer
A short, explicit framing of what the combination of signal and context implies. Not a recommendation engine, but a clearly labeled space where the team records what the pattern suggests should change.
Action Layer
The place where a decision becomes a tracked commitment: what will be tested, adjusted, or paused, and by when. This layer closes the loop back to the next reporting cycle.
You rarely start from a blank screen
Most participants arrive with a dashboard that already exists, often several years old, patched together by different people over time. The framework is applied as a retrofit exercise rather than a rebuild from zero.
The first pass usually involves labeling every existing element as belonging to one of the four layers, or to none of them. Elements that fit no layer are the ones most often cut. What remains gets reorganized so each layer sits in a consistent position across every dashboard the team maintains.
This consistency matters more than it sounds. Once stakeholders learn where the Decision Layer sits on one dashboard, they stop hunting for it on every new one.
Curious how this applies to your reporting stack?
The framework is covered in detail across the first three weeks of the cohort, with time built in to apply it to a dashboard you already maintain.
See the full curriculum