The Answer Got Designed in the Room
A crit on a photo upload feature ended with a live redesign built from a pattern the product already owned. How the room got there, and what it says about running crit well.
Everything, organized by how you read.
The Answer Got Designed in the Room
A crit on a photo upload feature ended with a live redesign built from a pattern the product already owned. How the room got there, and what it says about running crit well.
Ship It in One Room First
We decided to ship a new secondary navigation pattern in one part of the product over honest dissent about long-term inconsistency. The reasoning, the data, and how the dissent shaped the rollout.
Prioritization Isn't Real Until the Swap Is Named
A harsh comment in an executive review turned into a week of thinking about trade-offs, who names them, and why addition without subtraction reads as capacity.
20 Minutes and $5 per Frame
One of our design leaders handed an AI a Figma frame and asked for design critique. The results draw a precise map of where AI design review works today, and where it doesn't yet.
From Review It to Break It
A one-word change to how you run crit: ask the room to break a working prototype instead of reviewing flat screens. The mechanics, the precedent, and a starting point for your team.
AI Development Starts with Discovery
AI inverted the economics of product development: demos got cheap, verification stayed expensive. A case for moving discovery to the front and putting an evaluation gate before build.
Protect the Phases
Early feedback that means to save time is usually the feedback that costs the most of it. On why phases deserve a doorman, and why the leader has to make the pushback cheap to say.
Turn-Down Service
The whole industry answers every AI product question with a chat window. For clinicians who spend their day in conversation, that's the wrong gift, and a case for ambient help over one more thing to talk to.
Skip the Courier
Two leaders asked me to carry their reorganization cases up the chain this week. Why I declined both, and why the refusal did more coaching than any case I could have delivered for them.
The Cheap Conversation
Strip the tooling away and my best AI habit is just briefing, the oldest management technology there is: spend the hour where mistakes are free, then delegate.
Two Spikes, One Role
We ran two finalists through an identical interview spine and still nearly picked wrong, because one panelist was measuring against a different job. What the debrief is really for.
Perforated, Not Erased
A field report from a Config Leadership Collective session on building AI-native orgs, and why roles perforate rather than disappear.
The Quiet Half
When work happens in public, the quietest strong thinkers can disappear. Making their work visible is a leadership job, not a performance to assign back.
Maintenance Mode Can Disappear
Maintenance felt like a permanent tax until a small builders pod cleared the backlog. The tax turned out to be a choice.
The Bottleneck Isn't the People
When a build goes sideways, we blame the people. Usually the real constraint is the system they're working inside.
Prototype First, Decide Together
Flipping the order so design and applied AI prototype before the handoff, putting the hardest decision next to something real.
Exceptions Are Pilots
A practical tool for moving a structure-averse partner: propose a pilot with a learning goal instead of asking for an exception.
Innovation Lives in the Front Yard
A designer felt blocked from innovating. The reframe that unstuck her: stop waiting for greenfield and look at the front yard you already own.
People First, Then Permissions
A complex roles-and-permissions UX crit, and the question behind the functionality: do you model a system around its own structure, or around the job the person is trying to do?
I Needed to See the Machine
I came into a demo of our new build system worried about prioritization. Seeing how it actually works dissolved that worry and surfaced a harder one.
The Foundations We Stopped Funding
Our reporting infrastructure hit a ceiling we chose a year ago. It's a small version of a pattern worth naming: funding the new while the foundations quietly degrade.
Visibility Is the Work, Too
The communication most ICs treat as overhead is what gets read as leadership. Three conversations this week on why visibility is a craft, not a soft skill.
Show Them the Real App
A prototype that doesn't look like the real product teaches engineers the wrong thing. The fidelity bar I hold for what goes to eng, and the toolchain that makes it reachable.
Aligned Isn't Owned
A decision everyone supports but no one owns is often worse off than one still being argued. Why agreement is the starting gun, not the finish line.
Your Roadmap Has a Navigation Ceiling
We treat information architecture as a tidiness virtue. It's really a capacity constraint: your navigation is the ceiling on how much product you can ship.
Show the Bridge, Not the Shore
A vision that only paints the destination is a wish, and wishes don't move people. The credibility lives in the path. Draw the bridge, not just the shore.
The Demo That Does Your Selling
Most demos perform: here's the thing, be impressed. The best ones leave room, so other people start building the idea in their own heads and join the work.
The Prototype Skipped the Thinking
Fast prototyping can skip the flows and journeys that do the actual thinking. Speed doesn't remove that step, it defers it to the worst possible moment.
The Version Is the Answer
General familiarity is cheap. Ask which version, and what changed in it, and you separate the people who've read about a system from the people who've shipped on one.
The Model Is the Easy Part
Why the Kasparov experiment, not the model leaderboard, is the right way to think about AI at work.
The Release Type We Forgot
A beta-tag standoff that turned out to be about institutional memory, not policy.
Maintenance Isn't a Demotion
Splitting innovation from upkeep is clean on a whiteboard and quietly corrosive on a team.
The Question Before the Pixels
The most useful question in a crit is whether the work should exist at all.
Tone Is a Material
A leader's tone isn't a soft skill on top of the work. It's the material a team's resilience is built from.
The Bar Doesn't Move
Why a flooded candidate market is exactly when you hold the hiring bar highest.
When the Save Indicator Is Doing Two Jobs
A save indicator that tried to show two different states at once, and the rule it broke.
Why We Didn't Roll Back
A launch-day bug, and why the hotfix was the conservative call, not the brave one.
Org Follows Strategy
When a roadmap creates dread, the ambition usually isn't the problem. The missing resource conversation is.
Comma, Not a Bow
Two small moves that decide whether crit feedback actually changes the work.
Handshake, Not Handoff
A four-part recipe for getting useful work out of AI, and the ingredient most people skip.
AI Adoption Is a Manager Conversation
Why a top-down AI mandate backfires, and the channel that already carries weight.
Purple Was the Missing Dimension
A cross-functional color decision won on brand strategy rather than taste.
Naming Is Information Architecture
Why one capability with several names is an IA problem, not a branding one.
AI Agents Reward Decomposition, Not Delegation
The real bottleneck to AI adoption on design teams is task decomposition.
The AI Users Respond To Is the AI They Can't See
Holding the tension between an AI-forward brand and users who prefer AI unlabeled.
The Scalability Argument Hiding in a Color Choice
A crit about button placement was really a debate about information architecture.
The Cost of Being the Optimistic One
A leadership assessment, a hard piece of feedback, and the cost of optimism.
Taking Point on AI Adoption Inside the Product Org
94 percent of what?
Trust, Not Access
A clinical product I'm partnered on right now wanted to ship an open-ended AI query interface.
Start with the Controversial State
The wedge is conservative. The destination is bold. Putting them in that order is the right move.
Where the Work Went
The velocity dashboard lies by omission. It captures the part of the work that moved fast and nothing else.
I'm Not Backfilling Designer X
A designer in one of our squads is leaving the team. I'm not backfilling the role.
Sacred Ground
There were six of us in the room.
The Lockout Spectrum
A spectrum for any forced rollout, sketched on a whiteboard during a 2FA push.
Accuracy Is Not Usefulness
A correct number with no call to action is functionally invisible.
Disagree and Commit Upward
The hiring criterion that decided a senior loop, and that isn't on most rubrics.
The Carver and the Joints
A reading list anchored on Christopher Alexander's Notes on the Synthesis of Form.
Exact Copy Informs Design
Typography, spacing, and rhythm aren't properties of the structure. They're properties of the words inside it.
Designers Pushing Code, One Quarter In
Early signal from a six-designer pilot. The autonomous-agent demo isn't the right shape yet.
The Database Test for AI Strategy
When AI shows up as a pillar in a strategy diagram, ask whether the rest of the diagram could function without it. If not, you do not have a pillar. You have a substrate, and substrates do not go in the pillar row.
A Great Design Gathering
Seven ideas, six quotes, and one book recommendation from sixty design leaders in a SoMa space under the Chatham House Rule. The most useful frame: AI does not automate design, it exposes what design was actually responsible for in the first place.
The Power Share Paradigm: Function, Form, Scale
Non-designers are doing design work, and gatekeeping does not work in 2026. The job is to teach, in a specific order: function first, form second, scale third. What gets shared is the access. What gets kept is the bar.
Tying Infrastructure to Churn
Stop pitching infrastructure investment as revenue acceleration. Start pitching its absence as churn. The math is more honest, and the conversation moves from speed to durability, where design leaders tend to do better.
Saying No When You Can't Stop
There are three kinds of darling worth killing: feature, process, and personal. The discipline of stopping is harder than starting, and it is the rate-limiting skill in any craft-led practice.
The Vibe Tribe is a Job Now
The people building things outside the official roadmap are usually quiet, easy to miss, and producing the work that will redefine the practice in eighteen months. Curating them is a real leadership job in 2026.
Designing the Bridge Role in Two Phases
We are hiring a design technologist. But we are not hiring the version of the role we eventually want. We are hiring the version the team is ready for, in a deliberate first phase, with a second phase already scoped.
Lovely Poetry and Lots of Exciting Things
Two tech leaders on my team opened an org-wide planning presentation this week by promising we were about to get "lovely poetry and lots of exciting things." They were not being metaphorical.
The Shelf Behind the Keynote
The three non-design competencies I talk about most when people ask how to prepare for design leadership, and what I recommend for each.
When Disabled Is the Wrong Signal
A designer brought a promo-activation flow to crit this week. The team had reached for a disabled checkbox to handle a pending state. It was almost right, and almost right is usually the most interesting place to start a crit.
Leverage as a Leadership Posture
When a CEO asks for leverage in a compression quarter, the word is doing more work than it appears to. Most leaders read it wrong. Here is the generative version, the four questions that distinguish it from the extractive one, and why the posture is also the retention story.
The Feedback That Stopped
When a teammate goes silent, it is rarely maturity. It is almost always withdrawal. Here is what that looks like, why it is more dangerous than open conflict, and the bounded repair that got two designers back in a room with each other.
When the Launch Is Real and the Team Is Thin
The hardest part of a big launch is not the product work. It is holding the cross-functional orchestration layer together when the people assigned to it are missing, overloaded, or not senior enough for the scope.
Translating the Boardroom for the People Who Do the Work
Every Monday morning I rewrite the CEO update for my design org. Here is why, how I do it, and the template you can steal.
Building Design Outcomes: From Conversation to Live Site in Two Hours
I built a portfolio site for my design leadership work using Claude Design, Claude Code, and Vercel. The full process, the walls I hit, and what the publishing workflow looks like now.
When Building Gets Cheap, Carrying Gets Expensive
AI is making it faster to ship features. That is not the hard part anymore. The hard part is deciding what deserves to exist.
What Verbosity in an Interview Actually Tells You
A candidate gave strong answers with real substance. Every single one took twice as long as it needed to. How I evaluated that signal and what I recommended.
When the Structure Is the Problem, Not the Person
We had the right designer doing the right work. The coordination was still breaking down. Here is the meeting where we stopped blaming execution and started looking at the org chart.