Introduction to Lean UX for co-hire. We've always been trying to put people first and now we've officially changed our development process to involve users in it and focus on the actual experience we're designing for them, rather than just the features we're developing.

1. Getting user-focused
Introduction to Lean UX
// Focusing on the actual experience being designed, rather than deliverables

2. What is it?
// UX + Agile + Lean Startup
“The practice of bringing the true nature of a product
to light faster, in a collaborative, cross-functional way …
building a shared understanding of the customer, their
needs, our proposed solutions, and our definition of
success … prioritizing learning over delivery to build
evidence for our decisions …”

3. Principles
// Team organisation, culture, design process
- Small cross-functional & problem-focused teams
- Outcomes, not output
- No rock stars, gurus, or ninjas
- GOOB: the new user-centricity
- Continuous discovery

4. Process
// Short iterative cycles
OUTCOMES,
ASSUMPTIONS,
HYPOTHESES
DESIGN IT
CREATE AN MVP
RESEARCH &
LEARNING
OUTCOMES,
ASSUMPTIONS,
HYPOTHESES

5. Assumptions
// Our best guess based on what we know today
“We believe allowing the companies to enter a personalised
note to candidates along with conversation requests will
increase the number of matches by 20%.”
“We believe a personal note from companies on conversation
requests will re-engage 5% of our inactive candidates.”

6. Assumptions
// 4 important types
- Business outcomes //success metric
- Users //personas
- User Outcomes //goals of people
- Features //product changes

7. Declaring Assumptions
// 1. Preparation
- Analytics reports //how the current product is being used
- Usability reports //why users are taking certain actions
- Information about past attempts //success and failures
- Business justification //how this will affect company’s performance
- Competitive analysis //how competitors are tackling the same issues

8. Declaring Assumptions
// 2. Problem Statement
- Our current goals
- The problem we want to address
- An explicit request for improvement that doesn’t dictate a
specific solution

9. Hypotheses
// Tactical and testable focused on features
“We believe (a 20% increase of conversations started)
//business outcome will be achieved if (candidates) //users (match
with companies) //user outcome with (the new personalised
note sent with conversation request) //feature”

10. Hypotheses
// Creating hypothesis statements
- The business outcomes you’re trying to achieve
- The users you’re trying to service
- The user outcomes that motivate them
- The features you believe might work in this situation

11. Hypothesis Table
// Putting all hypotheses together
WE BELIEVE THAT:
We will achieve …if this user… …can achieve… …with this feature
[business outcome] [persona] [user outcome] [feature]

12. Process
// Short iterative cycles
OUTCOMES,
ASSUMPTIONS,
HYPOTHESES
DESIGN IT
CREATE AN MVP
RESEARCH &
LEARNING
DESIGN IT

13. Design it!
// Collaborative Design
- Paper sketches
- Whiteboard sketches
- Conversation: Our most powerful tool

14. Process
// Short iterative cycles
OUTCOMES,
ASSUMPTIONS,
HYPOTHESES
DESIGN IT
CREATE AN MVP
RESEARCH &
LEARNING
CREATE AN MVP

15. MVPs & Prototypes
// The fastest thing we can get out the door that still works
- Technical RSD
- Focus on the core workflows that let you test your
hypothesis
- High-Fidelity Prototype on staging environment

16. Process
// Short iterative cycles
OUTCOMES,
ASSUMPTIONS,
HYPOTHESES
DESIGN IT
CREATE AN MVP
RESEARCH &
LEARNING
RESEARCH &
LEARNING

17. Feedback & Research
// Putting our MVP to the test
- Collaborative Discovery
- Direct Observations + Contextual Interviews
- USE and SUS questionnaires
- Continuous Learning
- Indirect Observations
- Site usage analytics
- Feedback Surveys

18. Next Steps
- Map current user journeys //identify gaps
- Define user groups //create draft personas
- Read more about Lean UX //methods used throughout the process
- Principles & Design Guidelines
- Collaborative Discovery Guide