Delivery Playbook · Roles
Product and design roles
The UX/UI Designer, and how requirements work without a separate Business Analyst.
Owner: Delivery Manager · Last reviewed: · Next review: 28 April 2027
The UX/UI Designer helps the team build the right thing. They work closely with the client's product owner and with users, and they stay involved after Design to check what gets built. We do not have a separate Business Analyst. The team shares that work, as described below.
UX/UI Designer
TechSoftDesigns usable, accessible interfaces and flows, and helps the whole team understand the users.
Owns
- User flows, wireframes and design system
- Usability and accessibility of the interface
- Design specs for engineering
- User needs and acceptance criteria for what users see
Day to day
- Runs user interviews and workshops with the client
- Prototypes and tests with real users
- Writes and refines user stories for the interface
- Reviews implemented UI against the design
- Maintains reusable components and tokens
Use of AI: Uses AI for exploration and variants; final design decisions are made and checked by the designer.
Works with: Hands specs to engineers; joins reviews to verify the result.
Requirements without a Business Analyst
We work with AI coding tools such as Claude Code. They give good results only when the person using them understands the business. So requirements do not pass from an analyst to the engineers. Instead, everyone on the team learns the client's business and shares the requirements work. The client still confirms every requirement.
| Requirements work | Who covers it |
|---|---|
| Discovery workshops and user interviews | UX/UI Designer leads; Tech Lead and Delivery Manager join |
| Writing and refining user stories | Designer for user flows and screens; Tech Lead for technical stories; each engineer for the stories they will build |
| Acceptance criteria | QA writes them with the client; engineers confirm they can be tested |
| Business rules and edge cases | Engineers and the Tech Lead ask the client's team directly |
| Process, data-flow and journey models | Tech Lead for data and integrations; Designer for user journeys |
| Traceability from requirement to test to release note | QA |
| Checking delivered work against the requirement | QA and Designer, then the client at the demo |
| Discover | Design | Build with AI | Verify | Operate & improve | |
|---|---|---|---|---|---|
| UX/UI Designer | •• | ••• | •• | • |
Typical artifacts
- Problem statement, personas and process maps
- User stories with acceptance criteria (Given / When / Then where useful)
- Wireframes, clickable prototypes and design system components
- Traceability: requirement → story → test → release note
Related
Lifecycle
Stage 1: Discover
Agree the problem, the baseline and the desired outcome before committing to a solution.
Lifecycle
Stage 2: Design
Define what will be built, how it will be built and how it will be accepted.
Working agreements
Definition of ready and done
The checks at the start and end of a story that keep stories small, clear and truly finished.
