Metrics compete
Without hierarchy, every number appears equally important.
Selected case study · Scroll to explore
03 · Decision intelligence
Beyond the
Dashboard
A dashboard should not merely report what happened. It should help someone decide what to do next.
✦ The useful question comes after the chart.
The problem with reporting
Most dashboards stop at visibility. They place metrics on a screen and make the stakeholder perform the difficult work of interpreting context, finding the bottleneck, and deciding what deserves action.
Context disappears
A rate can look strong or weak depending on the funnel, objective, audience, and time window.
Action remains implicit
The report ends before the decision begins.
Decision model
Signal → Meaning → Action
A useful analytical experience does not hide the data. It creates a path through it.
Signal
What materially changed? Which metric or pattern deserves attention?
→
Meaning
Why did it happen? Where in the journey did behavior change?
→
Action
What decision, experiment, or operating change should follow?
Worked example
A funnel that looked active—but did not convert.
The value of the dashboard was not declaring that one lead was low. It was isolating where the journey broke and distinguishing audience interest from form friction.
0.54%clicked
82.1%opened form
4.3%completed
Decision
For the final push and future short-form events, test a direct path to the LinkedIn Event page instead of adding a separate lead-form step.
Live project
An analytical experience designed around the question after the chart.
This portfolio page provides the strategic framing. The live project is where the full interaction and visual storytelling can be explored.
Original live projectThe exact GitHub Pages experience loads in this frame. Use “Open full screen” if your browser blocks embedded pages.
What it proves
Analytical work can be technical, strategic, and deeply communicative.
This project connects the discipline of measurement to the craft of helping another person understand and act.
Metric architecture
Choose the measures that answer the business question rather than displaying every available field.
Information design
Create hierarchy, sequence, labels, and visual relationships that guide interpretation.
Diagnosis
Locate friction within a journey and distinguish symptoms from the likely operating problem.
Executive storytelling
Translate analysis into plain-English implications and recommendations.
Web implementation
Build a browser-based reporting experience using HTML, CSS, and JavaScript.
Decision design
End with the next choice, test, owner, or change—not merely the last chart.