Design
We explore, validate, and refine solutions that meet the agreed goals. Design work provides enough clarity to guide build without locking down unnecessary detail too early.
Roles
- Phase owner: Design Lead
- Supported by: Project Manager, Tech Lead
- Informed: Sponsor, AM, Projects Coordinator
- Primary Client contact: Project Manager
Typical activities
- Information architecture and content strategy
- Technical design
- Wireframes
- Visual design approach of key elements
- Prototypes, design reviews, and user testing (where possible)
- Preparing materials to support development (annotated wireframes, spec docs)
Deliverables
| Deliverable | Owner | Shared With | Format | When |
|---|---|---|---|---|
| Wireframes | Design Lead | Client (for review) + Dev team | Figma / PDF export | During Design; shared at review point |
| Visual design approach | Design Lead | Client (for sign-off) | Figma / PDF | Before Specification starts |
| Technical approach document | Tech Lead | Internal team + PM | Google Doc | Before Specification starts |
| Content Strategy / IA doc | Design Lead | Both | Content Strategy IA template | During Design phase |
| Updated SoW | PM | Client | Template | — |
Templates
| Template | Owner | Audience |
|---|---|---|
| Content Strategy IA doc | Design Lead | Both |
Tools and platforms
- Figma/Figjam — wireframes, visual design, prototypes
- Figma — prototypes and client review
- Google Docs / Project Drive— technical approach, content strategy
- TBC — user research+ testing
- Harvest — time tracking
- Google Docs / Project Drive — design decisions and annotations
- Project Rocket channels and meetings
Checkpoint
-
Design direction agreed internally ↳ Required output: Internal design review sign-off noted in decision log
-
Design direction agreed by client ↳ Required output: Client feedback documented; sign-off email saved in Drive
-
IA is agreed ↳ Required output: New site map
-
Open questions that affect build feasibility are identified ↳ Required output: Listed in risk register or design notes
-
Major interaction patterns are settled ↳ Required output: Annotated wireframes or prototype link shared with Dev
-
Scope has not silently expanded ↳ Required output: PM has confirmed backlog still reflects agreed scope
If design uncertainty would materially affect build effort, we address it before moving on. This does not mean that all design has finished - UI design and other design may well take place as part of the Development and delivery phase - but it does mean that the scale of any remaining design is settled and the overall direction is fixed.
Handover
| From | Design Lead + Project Manager |
| To | Backlog Steward |
| Mechanism | Design walkthrough meeting with Tech Lead, Backlog Steward, and PM. Design artefacts linked in project workspace. |
| Design Lead | Present all design artefacts. Flag open questions and any known design work still to come during build. Confirm the scale of remaining design work. |
| PM | Ensure handover meeting is scheduled. Confirm that artefacts are accessible and the project workspace is current. |
| Tech Lead | Review design artefacts for technical feasibility. Flag blockers before Specification begins. |
| Backlog Steward | Attend the design walkthrough. Begin breaking design into stories with acceptance criteria. |
Last updated: