This document outlines a proposed process for user experience (UX) design that focuses on rapid iteration through user feedback loops rather than one-time user testing. It involves 9 steps: 1) establishing a shared product vision through strategy workshops, 2) user research to inform design and validate assumptions, 3) data analysis to organize findings and draw insights, 4) low-fidelity sketching to generate ideas through fast iterations, 5) high-fidelity sketching to show designs and allow user testing early on, 6) prototyping to further validate hypotheses with users before building, 7) evaluation to confirm outcomes and hypotheses are met, 8) multivariate testing and optimization during development, and 9) communication throughout including UX standups,

2. Minimising risk: - Focus on outcomes, not features
- Rapid iteration, not one design
- User feedback loops, not user testing after build
- Validating hypothesis’, not being opinion led
What is the process for?

3. What is the process?

4. Why should we strategise? - Shared product vision
- Identifies the desired outcomes
- Directs the design
1. Strategy

5. Previous collaboration points
- Product owner inception workshop
1. Strategy Proposed collaboration points
- Product owner inception workshop
- Hopes and fears workshop ( 30min - 1hr )
- User journey mapping workshop ( 1hr – 2 hrs )
- How might we / hypothesis workshop ( 1 - 2 hrs )
Previous outputs shared
- Product feature vision board (From product
owner)
Proposed outputs to be shared
- Product feature vision board (From product
owner)
- Hopes and fears outcomes
- Problem statement
- Hypothesis’ and expected outcomes
- Competitor analysis

6. Why should research be at the heart of
every project?
- Informs design
- Starts validating assumptions
- Reduces costs & development time
2. Research

7. Previous collaboration points
- None
2. Research Proposed collaboration points
- Stakeholder interviews ( 30min - 1hr per stakeholder )
Previous outputs shared
- None
Proposed outputs to be shared
(quantity and type of outputs dependant on project)
- Value UX proposition
- Competitor analysis report
- Survey report
- User testing report
- Relevant MVT testing results
- Stakeholder interview outcome
- Further relevant research

8. Why do we need to analyse the data? - Organises the ‘what’
- Draws insights
- Continues to validate assumptions / hypothesis
3. Analysis

9. Previous collaboration points
- None
3. Analysis Proposed collaboration points
- Persona workshop ( 30mins - 1 hr )
- User experience mapping workshop ( 1 – 2hrs )
Previous outputs shared
- Personas
Proposed outputs to be shared
- Heuristic review
- Affinity mapping
- Personas
- User experience mapping outcome
- Metrics analysis
- Session recording insights

10. Why low fidelity sketches? - Generates lots of ideas (fail-fast)
- Visualise ideas
- Communicates designs
- Better collaboration
- Faster iterations
4. Low Fidelity Sketch

11. Previous collaboration points
- None
4. Low Fidelity Sketch Proposed collaboration points
- Crazy 8’s session ( 2-3 hrs )
- Crazy 8’s design voting ( 5 - 10 mins )
Previous outputs shared
- None
Proposed outputs to be shared
- Crazy 8’s features output
- Crazy 8 designs
- Crazy 8’s voting outcome and reasoning

12. What’s the point of high fidelity
sketches?
- Shows how designs will work on screen
- Gives us the ability to User Test early on in
the process
- Can show user flows, interaction and
touchpoints
- Faster than designing on a computer
- Allows for more critique, as still very
‘rough’
5. High Fidelity Sketch

13. Previous collaboration points
- None
5. High Fidelity Sketch Proposed collaboration points
- Sketch walkthrough and voting ( 10 – 20 min )
- User journey walkthrough ( 30min – 1 hour )
Previous outputs shared
- None
Proposed outputs to be shared
- Sketch user flows
- User testing results

14. Why can’t we just build it? - Reduces the cost of learning
- Reduces the time taken to learn from the designs
- Allows us to validate majority of remaining
hypothesis through user testing
- Reduces development rework
6. Prototyping

15. But we want to build the next sparkling
new thing!
- Validates that we’re meeting expected outcomes
- Validates remaining hypothesis
- Gives insight for MVT and optimisation
7. Evaluation

16. - Hypothesis led
- Research driven
- Should have the ability to re-start the process loop /
drive change into dev
8. MVT and Optimisation

17. Change to current communication
points.
- Scrum of Scrums
- Get space on the board for UX work
- Improve existing space for current ABT tests to
include upcoming tests
- Bake in time to talk through existing test results
- Management Meetings
- Present back at key points in projects (e.g. post
user testing to show reason for design
direction)
- Communicate resource availability and
predicted timelines
- Communicate case studies of previous project
9. Further Actions
- UX Standups
- To be used to demo previous days work and open up
designs for critique on a daily basis
- Agreement in changing MVT traffic allocations.
- Product Standups
- Ensure a UX presence at all product stand ups

18. Thanks for listening!
Do you have any questions?