What Happens When You Throw a Demand at a Model

The Demand

A demand looks like this: "Build me a landing page." Or "Fix this bug." Or "Write a report on market trends." Short. Direct. Feels clear. In my head, it is clear. I know exactly what I want. The landing page has a hero section, a pricing table, a testimonial carousel, and a contact form. I know the color scheme, the font, the spacing, the copy tone.

None of that is in the demand. All of it is in my head.

What the Model Receives

The model receives "build me a landing page." Five words. No role. No context. No limits. No format. It is the most general thing I could say. So now the model has to make every decision I did not make.

What framework. What style. What content. What layout. What actions. What speed targets. What browser it works in. What rules it follows for accessibility. What screen sizes it fits. Every choice the model makes on its own pulls the result away from what I wanted. There are dozens of these choices in a single landing page.

The result is a landing page. Just not my landing page. It is the model's landing page. It is the average landing page. It is the most likely landing page when I gave zero limits. And the most likely version of anything is almost always ordinary.

The Mechanical Explanation

When the model gets a demand with no details, its attention spreads out wide. There is nothing specific to lock onto. No limits to cut down the choices. No format to shape the answer. The model looks at all the possible outputs and picks one from the middle. The middle of any range is the average. Averages are, by definition, not special.

When the model gets a prompt with real details, its attention focuses. The limits cut away most of the choices. The role tells the model what kind of expert to act like. The context pins down the decisions. The format shapes the output. What is left after all that focusing is a much smaller, much better range of answers.

Demand vs Specification

A demand says what you want. A specification says what you want, how you want it, who is making it, what the limits are, what format to use, and what the context is. The gap between a demand and a specification is like the gap between pointing at a building and handing someone the blueprints.

I stopped throwing demands. I started writing specifications. The model stopped giving me noise. It started giving me exactly what I needed.