The document outlines an approach to efficiently solving problems in user experience at Flyt.io through a structured design sprint process. It emphasizes qualifying the problem space, creating user personas, and swiftly iterating on designs while minimizing delays in research feedback. The process is designed to be agile, involving rapid problem scoping and continuous feedback to iterate and refine solutions effectively.

1. Solving problems fast
Nick Gill - UX Researcher @ Flyt.io

2. Intro
● What we do at Flyt
● Problem to vision
○ Qualify the Problem Space
○ Personas and User Journeys
○ Jobs to be Done
○ Design Sprint

3. Problem to vision in one week
● Support development with speed
● Minimise lag from insights to scope
● Keeping research fresh

4. Sprints
● Google Ventures model
○ Agree on the problem to solve
○ Empathise with the user
○ Test the concepts
○ Feedback
○ Iterate

5. Sprints
● Traditional problems
○ Long planning process
○ Teams are siloed
○ Over the wall briefs

6. Sprint faster
Friday PM - Problem scope + planning

7. Sprint faster
Friday PM - Problem scope + planning
Monday - Ask the expert + user journeys

8. Sprint faster
Friday PM - Problem scope + planning
Monday - Ask the expert + user journeys
Tuesday - J/P/G, Crazy8’s, lo-fi proto

9. Sprint faster
Friday PM - Problem scope + planning
Monday - Ask the expert + user journeys
Tuesday - J/P/G, Crazy8’s, lo-fi proto
Wednesday - Internal tests, proto v2

10. Sprint faster
Friday PM - Problem scope + planning
Monday - Ask the expert + user journeys
Tuesday - J/P/G, Crazy8’s, lo-fi proto
Wednesday - Internal tests, proto v2
Thursday - External tests, iterate on the fly

11. Sprint faster
Friday PM - Problem scope + planning
Monday - Ask the expert + user journeys
Tuesday - J/P/G, Crazy8’s, lo-fi proto
Wednesday - Internal tests, proto v2
Thursday - External tests, iterate on the fly
Friday AM - Present findings, open forum

12. Sprint faster
Friday PM - Problem scope + planning
Monday - Ask the expert + user journeys
Tuesday - J/P/G, Crazy8’s, lo-fi proto
Wednesday - Internal tests, proto v2
Thursday - External tests, iterate on the fly
Friday AM - Present findings, open forum
● Document publicly, continuously
● Seek out feedback
● Realistic goals

13. Keeping research fresh
● Prioritisation
● Saying no
● UX consulting

14. Iterating the process
● Not perfect
● Time to adopt
● Evolving with the teams