What are design deliverables in UX?
Design deliverables in UX are the tangible outputs a designer hands over, such as research findings, wireframes, prototypes and specs.
also calledUX deliverables · design artifacts · design outputs
A designer's thinking is invisible until it lands in something other people can open, comment on and build from. Deliverables are those things. They are the proof of the work, but more usefully, they are how a team agrees on what is being made.
- Deliverables are the concrete outputs designers hand to others, from research summaries to final specs.
- Each one should help somebody make a decision or build something.
- Match the set of deliverables to the project, instead of producing everything every time.
- Explain the reasoning and keep files current, or the handoff loses its value.
What counts as a deliverable
Anything you produce that someone else needs in order to do their job. The list changes with the project phase.
During research you might deliver interview notes, a persona, a journey map or a summary of findings. During design you deliver sitemaps, user flows, wireframes, mockups and prototypes. Near launch you deliver specs, annotated screens, exported assets and updates to the design system.
A deliverable is not always a pretty file. A one-page problem statement the whole team signs off on can be the most valuable thing you hand over in a month.
Why they matter beyond the paperwork
Deliverables turn opinions into things you can point at. A wireframe lets a stakeholder say "I thought this page would have a search box" before a developer writes any code, which is the cheapest moment to hear it.
They also create a trail. When someone asks six months later why the checkout has three steps, the flow diagram and research summary explain it without anyone needing to remember.
Choosing the right ones for the job
Not every project needs every document. A good habit is to ask three questions: who will use this, what decision does it help them make, and what happens if we skip it?
- A small team shipping fast might only need a flow, a few annotated screens and a clickable prototype.
- A regulated industry may need formal documentation and accessibility reports.
- A client project usually needs agreed deliverables written into the contract, so scope does not quietly grow.
If a document will not change anyone's action, it is probably busywork.
Common ways deliverables go wrong
The first is handing over polished files without explaining the reasoning. A developer who sees a design but not the constraints behind it will guess, and guesses drift.
The second is making deliverables nobody asked for, like a forty-slide research deck when the team wanted five key insights. The third is letting them go stale. An outdated flow chart is worse than none, because people trust it.
Finally, treating the deliverable as the goal. The goal is a better product; the file is just the vehicle.
Handing them over well
Put everything in one findable place, name files sensibly, and add a short note that says what the file is, what is decided and what is still open. A ten-minute walkthrough call often prevents a week of questions. Agree on format with the receiving team early, since an engineer may prefer inspect mode in a design tool, while a stakeholder wants a PDF.
Design deliverables: your questions, answered
What are examples of UX design deliverables?
Common ones include user research reports, personas, journey maps, sitemaps, user flows, wireframes, mockups, interactive prototypes, usability test reports, design specs and a style guide or design system. Which you need depends on the project's stage and size.
What is the difference between a deliverable and an artifact?
The terms overlap heavily. An artifact is anything produced during the work, including rough sketches for your own thinking. A deliverable is an artifact formally handed to someone else, often agreed in advance as part of the project scope.
How many deliverables does a UX project need?
As few as it takes to align the team and build the right thing. A quick feature may need only a flow and a prototype, while a full product redesign could involve a dozen. Start from the decisions that need support, not a fixed checklist.
What should a UX designer deliver to developers?
Final screens, interaction notes, states such as errors and empty views, exported assets, spacing and typography specs, and links to the design system. A short written summary of the logic behind tricky parts saves a lot of back and forth.
Who receives design deliverables?
Different people at different times: stakeholders approve direction, product managers check scope, developers build from them and other designers reuse them. Tailor the format and level of detail to who is reading.
More quick answers
Are wireframes a deliverable?
Yes, they are one of the most common ones. Teams use them to agree on structure and content before investing in visual design.
What is the difference between deliverables and outcomes?
Deliverables are the things you produce, like a prototype. Outcomes are the change they create, such as fewer support questions or more completed sign-ups.
How should deliverables be documented?
Keep them in a shared, searchable place with clear names, dates and a short note about status. Link them from the project's main brief so nothing is hidden in someone's drive.
Do deliverables change in agile teams?
Yes, they tend to be lighter and more frequent. Instead of one big handoff, designers share small pieces continuously, often straight in the design tool.
What is a prototype deliverable used for?
It lets people try the design before it is built, so stakeholders can react and users can test it. It is often the most persuasive thing in a project.
A wireframe in UX is a simple, low-detail blueprint of a screen that shows layout, content placement and functionality before any visual styling is added.
A prototype in UX is an early, interactive model of a product that lets you test how it works and feels before spending time building the real thing.
UX documentation is the written and visual record of research, design decisions and specifications that lets a team build and maintain a product.
A style guide in UX is a reference document that sets the visual and writing rules for a product, such as colors, fonts, spacing and tone of voice.
A user flow in UX is a diagram showing the steps a person takes through a product to complete a task, including decisions and possible detours.
A mockup in UX is a static, high-fidelity picture of a screen that shows the final look, including colors, type, images and layout, but not how it works.
Found this useful? A GitHub star helps other designers find it.