Presentations
Killing the Status Deck No One Trusted Anymore
Live reporting that stays current because no one has to build it by hand.
Status source
The live data behind the report: what's shipped, what's changed, adoption signals, open items, pulled directly from the design system's actual state.
Scheduled refresh
The cadence that keeps the artifact current on its own, without a person compiling a new version each time.
Editorial layer
The judgment applied to what's worth surfacing to an engineering lead versus a product stakeholder versus an executive, so the update stays useful rather than noisy.
Live artifact
The finished view stakeholders can open at any time and trust reflects the current state, not the state as of the last quarterly deck.
Challenge
Reporting design system status was its own quarterly project — a deck that was accurate the day it was presented and stale within weeks, built at the cost of real design time.
Process
Scheduled tasks pull the system's real state on a set cadence and assemble it into a live artifact — no manual compilation step, no person needed to keep it current.
Research
The mismatch was structural: design systems evolve continuously, but status decks don't. Any fixed-cadence report was bound to be wrong by the time someone read it.
Design
The artifact applies the same editorial judgment a good status update needs — not everything that changed is worth reporting — while staying live instead of a static export.
Outcome
Recurring reporting effort dropped to near zero, and any stakeholder could ask "where does this stand?" at any moment and get an answer that already existed and was already current.