Single Decider

A single decider is the one named human who carries final approval power on a design project. The brief lists their name first, followed by up to three consulted people who provide input but cannot override the decider. This person signs the one page constraints sheet. Their signature binds them to the done condition, the out of scope list, the budget kill number, the timeline kill date, and the one metric that matters. When the delivered work meets the acceptance artifact standards the decider says done and the project ends. No further rounds. No silent scope expansion. The single decider removes the ambiguity that lets projects drift for months. Design is choice making under constraint. Without one person willing to make those choices the team spends its time managing politics instead of pixels. The role appears in every strong brief because it makes all the other answers real. Skip naming the decider and the document is still a wish list no matter how pretty the mood board looks. If the decider changes mid project the kill criteria triggers a five day window for the new decider to re sign the constraints sheet or the work pauses. This mechanic turns the brief into an operating system instead of decoration.

A single decider is not a group. It is not the leadership team or the founder circle or any other polite fiction that spreads accountability so thin that nobody feels it. It is not the person who approves the strategy deck but disappears when the visual work starts. It is not we will get alignment at the final review. Those setups turn every decision into a negotiation. The team produces three options instead of one strong direction. Feedback arrives untethered to the original constraints. The project doubles in size while the one metric stays flat. Committees optimize for consensus. A single decider optimizes for clarity and speed. If the named person lacks either the taste or the authority to defend hard calls then the brief must be updated before work begins. The discipline is brutal on purpose. Comfortable briefs produce uncomfortable results six weeks later when the client asks for one more round and the team has no signed document to push back.

Concrete example one comes from Linear in 2024. The team shipped a major update to their keyboard driven workflows with one engineering manager serving as single decider for the entire experience. The constraints sheet named that manager and listed two consulted designers. The done condition was a shipped feature with zero reported friction in the first 30 days and specific command latency targets. The work shipped on the kill date. The metric moved. No post launch redesign requests appeared because the decider had skin in the game from day one. Stripe offers a parallel case from their 2022 billing dashboard refresh. One product leader owned every approval decision. The brief specified the exact file types in the acceptance artifact, a live Stripe test mode link, and a component library with 14 locked patterns. When that leader signed off the project closed. The team invoiced against the sold number instead of the kill number. The one metric, self serve setup completion rate, jumped 29 percent in the first quarter after launch.

Vercel demonstrates the model on their edge network marketing pages. The head of product marketing acts as single decider for every campaign site launch. The brief includes a hard out of scope list that blocks feature requests from sales. The decider reviews against the one metric of sign up conversion from the landing page. Projects stay inside the timeline because everyone knows the name at the top of the sheet. Anthropic used the same approach for Claude 3 interface updates in early 2024 with one research lead as single decider on eval gated releases. The design team delivered specific loading states and error messages tied to measurable benchmarks. Releases hit their dates and user activation numbers rose. We saw the opposite problem with a 2023 engagement for a Series B project management tool. No single decider was named. The brief listed four stakeholders with equal weight. The project ran four months past the kill date. Budget went 35 percent over. The final shipped product satisfied each stakeholder individually but failed to move the activation metric. The company later admitted the lack of a single decider caused every delay. They rebuilt their brief template the following month and have not missed a ship date since. A climate tech startup we advised in 2024 named their executive director as single decider for a new donation platform. The project shipped in five weeks, respected every out of scope line, and lifted conversions 41 percent against the one metric.

Use the single decider model on any project that must ship real work to real users by a real date. Insist on the name before you write the first line of copy or draw the first wireframe. Put it in the brief, read it at kickoff, pin it in the project channel. Route all feedback through that person so opinions stay tied to the constraints instead of becoming new requirements. This protects both sides from surprise and disappointment. The decider must have authority, availability, and taste aligned with the one metric. If those three traits do not live in one person then the project is not ready. Avoid the single decider approach during early stage ideation where the goal is to generate volume. A two day design sprint benefits from many voices. A four week brand identity project does not. If the client cannot name a decider during scoping, treat that as your kill criteria. Walk away or charge a premium that accounts for the expected scope creep and timeline slips. The brief filters bad fits before the first invoice. Freelancers should demand it even more strictly than agencies because their time is finite and one endless revision loop can sink an entire quarter.

Committees negotiate design into mush. A single decider ships it.