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 I presented it and stale within weeks, built with two or three days of design time each round.
Process
Scheduled tasks pull the system's real state on a set cadence and assemble it into a live artifact. No compile step, no person keeping it current. The first version listed everything that changed, and nobody read it.
Research
The problem wasn't the deck. Design systems change every week and decks don't, so any fixed report was going to be wrong by the time someone read it. Once I saw that, building a better deck stopped making sense.
Design
The artifact applies the same judgment a good status update needs: not everything that changed is worth reporting, and an engineering lead wants different things than an exec. It just stays live instead of being an export.
Outcome
I don't build the deck anymore. Anyone can ask "where does this stand?" at any moment and the answer already exists and is already current.