Design Outcomes Weekly reflections on the real-time work of supporting a design org.
A black-and-white 1925 photograph of a young woman seated in profile at a hotel telephone switchboard, a headset over her braided hair with 2 feathers tucked into it and a striped blanket around her shoulders, both hands on the board’s keys and plugs.

Crit is the exchange no one sees, where designers connect teams that can’t see each other.

Why this matters

Crit is the only recurring room where every team’s work is visible at once, and that makes the designers in it the people who connect teams that can’t see each other. Here’s how we’re protecting that role, and what we’re building for the people who want in.

Bain News Service, Helen of Many Glacier Hotel, June 26, 1925. Library of Congress, Prints and Photographs Division

Crit Is the Connective Tissue Why crit makes designers the connective tissue of a product org, the insurance claims workflow that proves it, and what we’re doing now that our product partners want a room like it. Crit is the only recurring room where every team’s work is visible at once, and that makes the designers in it the people who connect teams that can’t see each other. Here’s how we’re protecting that role, and what we’re building for the people who want in. Treat crit as your org’s sensing instrument: the one room where every team’s work is visible side by side. When another function asks to join, don’t hand over the room. Design them a ritual of their own, and share the recording.

Crit Is the Connective Tissue

Why crit makes designers the connective tissue of a product org, the insurance claims workflow that proves it, and what we’re doing now that our product partners want a room like it.

Because design crit lets us see all the work across every single experience, it puts us in the connective tissue role across the entire platform. I said that in our Monday team meeting this week, and the example that prompted it is worth retelling. Two of our designers heard a group practice owner ask about diagnosis codes during a customer conversation. The answer wasn’t theirs to give: the question actually belonged to the billing side of the product, with a team they don’t work with day to day. They dug into what was going on anyway and brought what they found to the people who own that area. Nobody assigned them that work. Crit and the channels around it had let them see where the question belonged, and they treated carrying it there as part of the job.

That seeing is a structural fact about design, and I want us to act like it. A product org mostly looks down its own lanes: a squad knows its roadmap, its metrics and its tickets. Crit is the one recurring room where the lanes sit side by side, so the people in it are the first to notice when a question from one lane already has an answer in another. The coordination that follows is a job in itself, and my message to the team was that it’s not a start doing, it’s a continue doing. Some of them worry that posting everything they learn is noise. Anytime it feels like you’re troubling people with how much you’re sharing, remember you’re not. It’s important information to get out there.

“Because crit lets us see all the work across every single experience, it puts us in the connective tissue role across the entire platform.”

The role is getting noticed, which brings a complication I didn’t expect. Since we merged our 2 weekly crits and product managers started joining (I wrote about that merge in Do, Try, or Consider), the room is full, and this week one of our design leaders heard that our product partners have been talking about taking the format over for themselves. Their first reaction was the right one: there’s no room, get your own. That sounds territorial, and it isn’t. Crit works because the people in it share a discipline of looking: they know how much a note should weigh, how to mess with someone’s file in front of them, how to disagree about a label in public. Doubling the room’s population dilutes the exact thing the visitors came for.

So the answer we’re working on is to design our product partners a ritual of their own. A product executive has been asking for the same thing from the other direction: a monthly deep dive into one product area, end to end, before anything gets built, recorded so the walkthrough can be shared in a broad channel and watched by everyone who wasn’t there. What I appreciated was how he framed the rollout: we need to increase rigor across the board, and we have to do it in a way that brings people along, because most teams have never seen the expectation they’re being held to. A recorded review does that without adding a meeting to anyone’s calendar.

The 2 rooms end up with clean jobs. Crit stays the place where design sees everything and routes what it finds, and the product review becomes the place where everyone else sees what good looks like before the build starts. If another function ever asks to join your crit, I’d read it as the compliment it is, and then I’d build them their own room.

Filed under CN Crit Notes — Feedback, with the reasoning shown.