by Braden Kelley and Chateau G Pato
Which Design Artifacts Are Worth Keeping — and Which Are Ceremony? (Short Answer)
Six design artifacts worth keeping: (1) problem/mandate brief, (2) lived contact evidence, (3) behavior hypothesis with kill criteria, (4) owned journey or service blueprint, (5) decision log, and (6) adoption/transfer card. Six that are ceremony: (1) conference-room personas, (2) unowned journey-map posters, (3) prototype-as-finish-line demos, (4) vision walls that never gate funding, (5) requirements novels / RACI theater, and (6) sticky archaeology without decisions. Soft landings keep evidence and owners. Ceremony keeps wallpaper.
An artifact earns its keep when it changes a decision, a behavior, or an owner. Everything else is ceremony with better typography.
How Do You Tell a Keep Artifact From Design Ceremony?
I have walked rooms full of beautiful design and still asked the only question that matters: does this artifact still earn a decision? Teams drown in deliverables. Soft landings keep what forces contact, mandate, falsifiable learning, ownership, kill decisions, and adoption. Hard landings accumulate ceremony — artifacts that photograph well, survive governance, and never change the median person’s work.
Keep-vs-ceremony test: Can you name the next decision this artifact forces? Who will act on it this week? What would you stop producing if the workshop never happened? If the answers are vague, it is ceremony.
When the method itself becomes costume, see 7 Ways Design Thinking Gets Misused. When generation is cheap and judgment is the design, see 5 Elements of Human-Centered Design That AI Cannot Own.
| Keep | Forces | Ceremony twin |
|---|---|---|
| 1. Mandate brief | What we can change | Persona deck nobody met |
| 2. Contact evidence | Jobs in their language | Empathy map from imagination |
| 3. Behavior + kill criteria | Learning with a stop date | Clickable demo as proof |
| 4. Owned blueprint | One seam + owner | Journey poster without operator |
| 5. Decision log | What we stopped/funded | Status deck of activity |
| 6. Adoption/transfer card | BAU owner + old-path kill | “Change plan” as cascade slide |
If it cannot force a decision, it is decoration.
1. Why Keep a Problem / Mandate Brief?
Artifact: One page — problem, who hurts, stakes, constraints, and what the team is allowed to decide, ship, or stop.
Forces: Mandate before methods. It kills ideation on forbidden ground.
Keep it alive: Update when sponsors change levers. Refuse workshops without it. Before you fund the next pilot, pair this brief with 11 Questions Before Funding Any Innovation Pilot.
2. Why Keep Lived Contact Evidence?
Artifact: Notes, clips, verbatim jobs, friction, and dignity costs from real people doing the work — not synthesized vibes.
Forces: Contact before solution. It grounds every later artifact.
Keep it alive: Revisit when the product drifts. Cite evidence in reviews the way finance cites numbers. Better framing questions live in 10 Design Questions That Beat a 40-Page Requirements Document.
3. Why Keep a Behavior Hypothesis With Kill Criteria?
Artifact: One falsifiable human behavior, a success signal, a cheap test, and a kill/continue date — an Experiment Canvas or equivalent.
Forces: Learning over demo applause. Premature scale gets a brake.
Keep it alive: No scale funding without a named behavior and a decision date. For runnable examples, see Experiment Canvas examples.
4. Why Keep an Owned Journey or Service Blueprint?
Artifact: A map or blueprint that names the journey/workflow owner, broken seams, and the next seam to fix — not a mural for the lobby.
Forces: Operating-model ownership. Orphaned handoffs become visible work.
Keep it alive: Review seams in steering. Retire maps with no owner.
5. Why Keep a Decision Log?
Artifact: A running record of tradeoffs — what we chose, stopped, deferred, and why — tied to evidence.
Forces: Truth over narrative polish. It prevents re-litigating settled kills.
Keep it alive: Open every design review with last decisions. Ceremony hates receipts. When the program starts performing for the deck instead of the work, see 11 Signs Your Transformation Is Managing the Deck, Not the Work.
6. Why Keep an Adoption / Transfer Card?
Artifact: BAU owner, redesigned work, old-path kill date, reinforcement ritual, and success behavior — equal weight to the product backlog.
Forces: Soft landing after pilot. It kills “innovation owns it forever.”
Keep it alive: No go-live celebration without a signed transfer card. Shelfware is what you get when adoption never becomes a design deliverable — see 12 Adoption Mistakes That Turn Good Tools Into Shelfware.
Ceremony 1. Why Are Conference-Room Personas Ceremony?
Looks like: Persona cards and empathy maps built from imagination, averages, or AI synthesis with no field contact.
Why it seduces: Fast, safe, printable — and it feels like design.
Instead: Fund lived contact evidence. Personas only as summaries after contact — never as substitutes.
Ceremony 2. Why Are Unowned Journey-Map Posters Ceremony?
Looks like: End-to-end maps that end at the workshop wall, with no operator for seams.
Why it seduces: Visible craft. Executives can point at “the journey.”
Instead: Keep an owned blueprint. Fix one seam before the next print.
Ceremony 3. Why Is Prototype-as-Finish-Line a Ceremony Artifact?
Looks like: Clickable or AI-generated mockups treated as validation because stakeholders smiled.
Why it seduces: It photographs well and feels like progress.
Instead: Keep a behavior hypothesis with kill criteria. Measure what people do — not what they clap for.
Ceremony 4. Why Are Vision Walls That Never Gate Funding Ceremony?
Looks like: North-star posters, future-state murals, and “innovation strategy” walls that never constrain budget or kill weak bets.
Why it seduces: Aspiration is cheap. Tradeoffs are expensive.
Instead: Keep the mandate brief and the decision log. Vision that cannot stop a bad project is ceremony.
Ceremony 5. Why Are Requirements Novels and RACI Theater Ceremony?
Looks like: Spec tomes and responsibility matrices that freeze assumed solutions and hide stakes.
Why it seduces: It feels rigorous. Audits love paper.
Instead: Mandate and design questions first. Specs follow a framed problem — they do not lead.
Ceremony 6. Why Is Sticky Archaeology Without Decisions Ceremony?
Looks like: Preserved walls of “How might we…,” affinity clusters, and photos of workshops as the work product.
Why it seduces: Proof of process. Facilitation theater.
Instead: Keep the decision log and kill criteria. If nothing was stopped or funded, the workshop was a meeting with snacks.
What Should You Ask Before the Next Design Review?
Five questions for artifact hygiene:
- Which artifact forces a decision this week?
- Where is the contact evidence?
- What behavior are we falsifying — and by when?
- Who owns the journey after applause?
- What ceremony will we stop producing?
Mantra: Keep the evidence. Retire the wall art. Design is what changes work — not what fills the Miro board.
FAQ: Design Artifacts Worth Keeping vs Ceremony
What design artifacts are worth keeping?
Design artifacts worth keeping are a problem/mandate brief, lived contact evidence, a behavior hypothesis with kill criteria, an owned journey or service blueprint, a decision log, and an adoption/transfer card — anything that forces a decision, a behavior, or an owner.
What is design ceremony?
Design ceremony is deliverable theater — personas nobody met, unowned journey posters, demo applause as proof, vision walls that never gate funding, requirements/RACI theater, and sticky archaeology without decisions — artifacts that photograph well but do not change the work.
How do you know if a design deliverable is useful?
A design deliverable is useful when you can name the next decision it forces, who will act on it this week, and what you would stop producing if the workshop never happened. If those answers are vague, it is ceremony.
Should you keep personas and journey maps?
Keep personas only as summaries after real contact — never as substitutes for field evidence. Keep journey maps or service blueprints only when they name an owner and the next seam to fix; unowned posters are ceremony.
What replaces design theater artifacts?
Replace design theater with mandate briefs, contact evidence, falsifiable behavior hypotheses with kill dates, owned blueprints, decision logs, and adoption/transfer cards — artifacts that change decisions, behaviors, and ownership after applause.
Image credits: Gemini
Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and Cursor to clean up the article, add images and create infographics.
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.