Design Outcomes Weekly reflections on the real-time work of supporting a design org.
Vilhelm Hammershøi’s Strandgade, Sunshine: a pale grey room where a tall window throws squares of sunlight across the bare floor, a closed panelled door on the right, and one woman in black standing beside a white-covered table at the left edge.

A quorum of one is how a team feels once it can’t see what everyone else is doing.

Why this matters

Teams told us they miss the quarterly review they used to complain about, because what they missed was never the slides, it was knowing what everyone else is doing. Here’s the rituals we’re rebuilding to keep the transparency and drop the theater.

Vilhelm Hammershøi, Strandgade, Sunshine, c. 1906. Cleveland Museum of Art

They Missed the Meeting They Complained About Why teams miss the quarterly review they used to complain about, the 3 tiers of ritual ownership we’re moving to, and the public de-commitment habit that beats silent slippage. Teams told us they miss the quarterly review they used to complain about, because what they missed was never the slides, it was knowing what everyone else is doing. Here’s the rituals we’re rebuilding to keep the transparency and drop the theater. Before you kill a heavyweight ritual, write down the job it was doing for the org besides the one it was named for. Then keep that job alive somewhere cheaper: documents over slides, status pulled from systems of record, and a public list of what you’ve stopped doing.

They Missed the Meeting They Complained About

Why teams miss the quarterly review they used to complain about, the 3 tiers of ritual ownership we’re moving to, and the public de-commitment habit that beats silent slippage.

We retired a heavyweight quarterly business review this year, and this week I heard the strangest thing about it: teams miss it. The review was slide-heavy, backwards-looking and expensive to prepare, and people said so at the time. Now some of the same people are saying they don’t know what’s going on across the org anymore. Both complaints are right, because the ritual was doing 2 jobs under 1 name: the slides were theater, and the visibility was load-bearing.

In our product leadership meeting this week we started designing the replacement, and I offered a model I lived at a previous company.

Everyone gets together once or twice a year for a roadmap check-in, every team lead speaks to how they’re going to attack their challenges, and the transparency comes along for free.

The hybrid I’m pushing for keeps that and drops the production: show up with the documents the team already has, and make the session an overview narrative in place of a slide performance. The old review earned its resentment from the weeks of deck-making it demanded, and none of that work was the part anyone missed.

What came out of the discussion is a 3-tier model of who owns which rituals. The frame that connects team goals to company priorities is owned at the top, by 1 or 2 leaders, so there’s a single version of it. Org-wide rituals get designed together and launched as 1 coordinated set, because the fastest way to confuse an org is to shotgun new ceremonies at it one at a time; the bar our product executive set was that the org hears 1 answer, launched collectively. And team-level rituals stay free: invent whatever works in your area, and share it so the other teams can steal it.

Two habits keep the replacement from growing back into theater. The first is to pull status from the systems of record teams already use in place of levying new artifacts on them: one of our product leaders made the case that even an imperfect automated pull beats asking every team to go do a bunch of reporting work again. The second is to de-commit in public. The norm we agreed to is that it’s okay to say we’re not doing something right now, but at least we’ll all know we’re not doing it. A visible list of what you’ve stopped doing informs the org as much as a roadmap does, and it’s the part most planning rituals leave out.

One more ingredient earned its place this fall: put a real customer in the planning room. The best planning sessions I was part of this season opened with a practicing clinician telling their own story, and the gut check that followed, on what we want to build next year and what is actually useful, was sharper for it. A dashboard summarizes a customer, while a person in the room keeps the roadmap conversation attached to a day someone actually lives. I wrote in Answer What You Can about keeping people talking while the structure around them moves. Rituals are the standing version of that promise, so when we rebuild one, the test is whether the visibility survives even when the slides don’t.

Filed under TD The Decision — What we chose, and why.