Why not a component or a prompt?

A component the team cannot ship without is a dependency with a title; the day the leader is in a board meeting, the feature waits. A prompt is the customer layer, changed the same day and stale with the next model, so the leader becomes the maintainer of the artifact that changes most often. Both are real making. Neither scales past the leader's calendar.

What is the replacement test for a leader's real work?

The next ten outputs shipped against the piece with the leader out of the room. It is the opposite of Neeman's test. The team being slower without you is the symptom Marco Di Santo described on October 20, 2026, the builder who became the place every correction waits.

How big is the monthly piece?

One surface. Three columns from the design handbook's You Cannot Mock a Distribution: best case, worst case you would still ship, and what the product refuses. A rubric with three to five criteria and at least 20 real cases, graded pass or fail per dimension, calibrated with two people on five outputs. The first block takes an afternoon; the fight over the worst-acceptable column is where the month goes.

What number replaces headcount on the leadership update?

The percentage of live surfaces with a current constraint set, from the handbook's Team Shape chapter. Written judgment keeps operating on surfaces nobody is looking at that week, so the percentage is the thing that scales when the team does not, and a leader who adds one surface a month is making in public.

What a Design Leader Should Build Each Month

What should a design leader build with their own hands each month?

THE SHORT ANSWER

One constraint set for one live surface: the worst output you would still ship, what the product refuses to do, and a rubric with three to five criteria and at least 20 real cases scored pass or fail, calibrated by two people sorting five outputs the same way. Patrick Neeman's October 28, 2026 piece on UX Collective is right that smaller teams want leaders who make, and his own paragraph on evaluations becoming the specification describes this artifact. His test for real work, that the team would be slower without the leader's piece, is the one to drop, because it selects for the leader on the critical path. At Smartcat I spent a month fighting over the worst translation we would auto-send without a human; the line that month produced ran on every job nobody reviewed, with no one waiting on me. The test is that the next ten outputs ship against the piece with the leader out of the room, and the number to report is the percentage of live surfaces with a current constraint set.

A constraint set for one live surface, with 20 real cases, and the share of surfaces covered as the number you report.

The sentence on the Kill List, the replacement test, and the Smartcat month are in Kill 'The Team Would Be Slower Without It' as the Test of a Leader's Real Work. The rubric sizes are in Figma's Trial Closed 70% of the PM Gap. The Gate Is the Rubric, Not the Designer., and the handbook chapters The Rubric Is the Spec and Team Shape(coming Jan 20) carry the method and the number.

Last reviewed 2026-10-28 · 1 min read

What should a design leader build with their own hands each month?

SOURCES

THE LONG VERSION

RELATED ANSWERS