# Design is decisions, not screens > A screen is the receipt. The decision was the purchase. When a designer shows me a screen, I ask what decision it represents. Often there isn't one. Source: https://umairalikhatri.com/writing/design-is-decisions-not-screens/ Author: Umair Ali Khatri Updated: 2026-08-31 --- [← All writing](https://umairalikhatri.com/writing/) Notes # Design is decisions, not screens 31 August 2026 ยท 4 min read Design is decisions, not screens. A designer shows me a screen. I ask what decision it represents. Often there isn't one. There is a layout that looked right. It was borrowed from a product that solved a different problem for different people. The screen is the receipt. The decision was the purchase. I can hold the receipt and still not know what was bought. ## The receipt and the purchase A screen is easy to admire. It has color, spacing, a clean grid. It looks finished. That is the trap. A finished look is not a finished thought. Behind every good screen sits a decision, or it should. Who is this for. What are they trying to do here. What did we choose not to show them, and why. A decision has an owner and a reason. A screen without one is decoration. It falls apart the first time a real person touches it. Take a dashboard packed with twelve cards. The purchase was not twelve cards. It was a bet on what the user checks first. If nobody made that bet, the cards are guesses arranged in a grid. So I do not start with the pixels. I start with the call the pixels are supposed to carry. ## Borrowed screens Most weak screens are copied. A designer saw a pattern in a product they admire and brought it home. The pattern worked there for a reason. Different users, different context, a different job to be done. Lift the surface and leave the reason behind. Now you have a screen that looks right and works wrong. I ask one question in these moments. What is that built on. Sometimes the answer is solid and I learn something. Sometimes the room goes quiet. The quiet is the useful part. A copied screen is not a crime. A copied screen with no reason under it is. ## The questions I ask I do not hand my team the answer when they can reach it themselves. So I ask what a thing is built on. I ask what the user will do once they have it. I ask them to say more about that. Three questions, over and over. They are slow on purpose. Each one moves the work back from the pixels toward the choice. That is where design happens. Watch what the questions do in a room. A designer starts defending the layout. Halfway through, they stop. They have found the hole themselves. A designer who can defend a choice does not need me to approve the screen. That is the point of asking instead of telling. ## Why it is slow Teaching a team to work this way takes a long time. It is faster to fix the screen myself. Point, say move that, change this, ship it. Faster, and worthless a month later. I would be fixing screens forever. Judgment does not transfer in a review note. It transfers when someone makes a call, watches it meet a real user, and feels the gap. So I slow the review down. I trade this week's polish for next year's independence. Most weeks that trade looks like a bad deal. Over a year it is the only deal worth making. ## What survives the redesign Every screen I have approved will be redrawn. Fashions turn. Tools change. A new lead arrives with new taste. The screens do not survive. The reasoning does. A team that knows why it made each choice can rebuild the product and keep the intent. A team that only has screens starts from zero. This is the part I care about. Not the artifact. The judgment that made it. Redesigns are cheap now. The thinking under them is not. ## Write it down A decision in one person's head does not survive either. That person leaves. The reason leaves with them. So I ask the team to write the decision next to the screen. Who, what, what we cut, why. It reads like extra work. It is the cheapest insurance a design team can buy. A written decision can be argued with. A screen can only be liked or disliked. Argument is how a team gets better. This is also why I make design systems agent-ready. A decision an agent can read is a decision that outlives the file it shipped in. ## The work I do I lead a design team. My stated job is helping people move from designing screens to making clear, thoughtful decisions that respect the user. That sentence sounds soft until you sit in a review. It is the hardest thing I teach. AI made it harder and more urgent. A model can produce fifty clean screens before lunch. I wrote about that in [AI is not replacing designers](https://umairalikhatri.com/writing/ai-is-not-replacing-designers/). Screens are close to free now. The decision behind them is the scarce thing. Reading a system for the decisions it encodes is [the work I sell](https://umairalikhatri.com/work/). ## The bar So here is what I want from the team, and from myself. Bring me the decision, not the screen. Tell me who it is for and what they will do next. Show me the screen last, as proof of the decision. A screen with a decision behind it is design. A screen without one is a guess in good clothing. That is the bar. Written for my team, and the ones I am still teaching to ask the question. If any of this feels familiar, say hello. [All writing](https://umairalikhatri.com/writing/)