One evidence-led teammate for the full UCD pipeline.
One AI teammate turns transcripts into eleven connected UCD artefacts and a working prototype, with evidence and approval carried through every step.
UCD Bot
Design · Vercel · Live
At a glance
Problem
One-shot AI outputs drift from source evidence and disconnect the artefacts that make a UCD process coherent.
Role
Product strategy, agent UX, pipeline model, interaction design, content, front end.
Stack
Next.js, Vercel, Eve web chat, stage-gated workflow, session memory, OAuth tool connections.
Status
Live, with an open web chat.
The problem.
Generic chat can draft an insight or a user story, but it does not preserve why that output exists or make the next artefact depend on an approved version of the last one. UCD work is a chain of decisions. Break the chain and a polished prototype can still solve a problem nobody observed.
0→1.
Turned eleven recurring UCD artefacts into one ordered workflow, from research synthesis and problem definition through journeys, system planning, and prototype.
Made source quotes and prior artefacts inputs to each next step so findings can be followed back to evidence instead of relying on conversational memory.
Added a human gate between stages; the agent assembles the work, but the practitioner decides whether it is good enough to continue.
Connected the agent to Figma, Miro, Notion, Mural, and Google Drive after OAuth, while keeping writes explicit and user-directed.
Under the hood.
The agent uses bounded stages with defined inputs, outputs, and approval state. Integrations are OAuth-connected and read or write through explicit user intent. The product describes session memory narrowly—as project context and decisions—so persistent context does not become an unsupported promise to retain everything.
Interaction.
Message it like a teammate
The entry point accepts transcripts, workshop notes, and conversation logs in the way a practitioner would brief a colleague, without requiring a special prompt language.
Stages replace scrollback
Discover, problem framing, specification, and prototype are presented as durable states with inputs and outputs, not as messages that disappear up a thread.
Receipts stay attached
Themes and insights cite source words; later artefacts cite the approved work before them. Traceability remains part of the interface rather than an appendix.
Memory excludes secrets
Session notes keep project context, preferences, and decisions while credentials, OAuth secrets, and sensitive personal data are explicitly excluded.
What shipped.
- Eleven connected artefacts, quote-level evidence links, human approval gates, role playbooks loaded on demand, tool connections, and a working-prototype output. Live.
- One connected route from raw evidence to a testable primary flow
- A paper trail that teams can inspect and defend
- Agent UX
- Pipeline design
- Interaction design