UX Deliverables

UX deliverables are the artifacts a design process hands to other people — wireframes, personas, journey maps, empathy maps, briefs, audits. Each one exists to settle a decision. That's the whole test, and most of the debate about which deliverables a team "should" produce dissolves once you apply it: an artifact that settles nothing is documentation of work, not work.

This page covers what each common deliverable decides, how to tell a working one from decoration, and which ones you can safely skip.

What each artifact decides

• Wireframe — decides structure. What is on the page, what it's called, and what ranks above what. Deliberately unstyled so reviewers argue about hierarchy rather than color.
• Persona — decides who the design is optimizing for when two segments want different things. Only load-bearing if built from research.
• Journey map — decides where in the end-to-end experience the losses happen, including the parts that occur outside your product.
• Empathy map — decides how a pile of raw observations gets organized before anyone tries to synthesize it.
• Design brief — decides what the project is for and what it is not for, in writing, before work starts.
• Content audit — decides what already exists and what should die.
• UX audit — decides what to fix first, in priority order, against evidence.

Telling a working artifact from decoration

Three questions separate them, and they apply to every item above.

What changed because this exists? A persona that never resolved a scoping argument didn't do the work. Neither did a journey map nobody reopened after the workshop.

Would someone outside the room understand it? Deliverables travel. The version that only makes sense with its author narrating has failed at the one job that distinguishes it from a conversation.

Is the confidence it projects earned? This is the dangerous one. Polish reads as rigor. A beautifully rendered persona built from three assumptions carries more authority in a meeting than a rough one built from twelve interviews, and the room usually can't tell the difference. Where the evidence is thin, say so on the artifact itself.

The templates

Each of these is a working starting point rather than a blank canvas:

• Wireframe kit — components for settling structure before appearance.
• User persona — with prompts that make the evidence behind each claim explicit.
• Journey map — stages, actions, and the emotional line across them.
• Empathy map — says, thinks, does, feels.
• Design brief — scope, constraints, and non-goals in writing.
• Content audit — inventory plus a keep, fix, or kill verdict per item.

For the content audit specifically, how to run a content audit covers the process the template supports.

Which ones to skip

The cost of a deliverable isn't producing it. It's the review cycle it triggers and the confidence a polished one manufactures. Skip an artifact when:

• Its decision is already settled and uncontested.
• You'd have to invent the inputs. A persona from imagination is worse than none, because it launders a guess into evidence.
• The next step would answer the question faster. A prototype in front of five people beats a document arguing about what they'd do.

The design thinking hub covers where these artifacts sit in the process, and research methods covers how to get the inputs that make a persona or a journey map load-bearing rather than decorative.

A deliverable checklist

• What decision does this settle, in one sentence?
• Who reads it without you in the room?
• Is every claim on it traceable to something you observed?
• Where the evidence is thin, does the artifact say so?
• Is there a cheaper artifact that settles the same decision?

Related reading: design systems for the deliverables that outlive a project, and UX audit for the artifact that ranks everything else.

Get a prioritized audit you can actually act on →