Prompt Design
Designing what a product asks a model, and what it asks the user — the interface layer around a prompt, not just the wording of one.
Design DisciplinesPrompt design has two halves that get conflated. One is the system prompt — the instructions, context and constraints the product sends on the user's behalf, which is engineering work. The other is the interface: what the product asks a person for, how much of the prompt they see or control, and what they can adjust when the output is wrong. That second half is design, and it is usually skipped in favour of an empty text box.
An empty box is the worst available starting point. People do not know what the system can do, what phrasing works, or how much detail helps, so the first attempt is poor and the second is abandonment. Structured inputs, worked examples, suggested starting points and visible constraints all outperform a blank field — and where the output is wrong, letting someone adjust one dimension (“shorter”, “more formal”, “only from these documents”) beats asking them to rewrite a paragraph of instructions.
In practice
An email assistant offered a free-text box for tone. Users typed things like “good” and “normal” and got unusable output. Replacing it with four tone presets plus an optional free-text refinement raised the share of generated drafts sent without editing from 12% to 41%.
Where teams get it wrong
- An empty text box as the entire interface.
- Hiding all constraints, so people discover limits only through failure.
- Asking users to rewrite instructions when adjusting one parameter would do.
- Placeholder examples nobody can reuse, instead of clickable starting points.
- Treating prompt design as wording alone, ignoring what the product asks the person for.
Learn more
You may ask
Frequently Asked Questions
What is the difference between prompt design and prompt engineering?
Prompt engineering is writing the instructions sent to the model. Prompt design covers the whole interface around it — what the product asks the user, what they can see and control, and how they adjust an output that missed.
Why is an empty text box a bad AI interface?
It gives no signal about what the system can do or what phrasing works, so the first attempt is usually poor. Structured inputs, examples and visible constraints produce better results and far less abandonment.
Related terms
All terms- AI Product DesignDesigning products whose behaviour is probabilistic — where the system can be confidently wrong and the interface has to account for it.
- Generative UIInterfaces assembled at runtime by a model, rather than laid out in advance by a designer.
- Human in the LoopKeeping a person in the decision path of an automated system — reviewing, approving or correcting before an action takes effect.
- Empty StateWhat a screen shows when it has no content yet — the first screen every new account sees, and usually the last one anybody designs.
Defined by Mara Last reviewed .
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us