Lean UX - Why bigger is not always better
We’ve been doing work with a lot of clients recently using a ‘Lean UX’ methodology to define their website purpose and high level architecture.
When I first propose this approach to clients who may not have the immediate cash flow for a full scale build the first question I get is always ‘What is Lean UX and why should I do it’?
The answer is different for each client, as is the process but at a high level I usually explain the process to clients as below.
Lean UX differs to the traditional project approach in that rather than jumping head-on into the project – a costly and time intensive proposition – Lean UX approaches the task by first defining the main value proposition of the website and then outlining high level user flows. Our clients typically use the process outcomes and design mock-ups to secure stakeholder or investor support for their project.
In essence, we change our approach from a detailed requirement-by-requirement interrogation and documentation of the site concept to a high-level approach focussed on testing assumptions about who the site is for, what the site is supposed to achieve for those users and from there define key site flows and architecture. As an example, we’re not looking at stuff like which footer links to include and what order to include them but instead focussing on the value proposition of the site concept and ensuring that it translates to user experience.
we’re not looking at stuff like which footer links to include and what order to include them but instead focussing on the value proposition of the site concept and ensuring that it translates to user experience.
There’s no typical workshop agenda in a Lean UX workshop as deliverables differ from client to client but as an example a typical workshop agenda may include:
Key Lean UX Workshop Agenda
- Vision and goals
- Personas and scenarios
- Defining an Elevator pitch
- Confirming competitor positioning, vision and goals
- Full customer journeys
- Key flows and screens
- Feature and scope checks and prioritisation
- Brand building activity
Key Lean UX Workshop Outputs
- Business goals
- Personas, scenarios
- Flows, screens, feature scope
- Creative direction
- MVP! MVP! MVP!
What’s not shown here is the hard work that takes place in the workshop – think butchers paper and markers, sticky notes, lively debate, coffee and muffins, then more scribbling ideas down on butchers paper followed by more coffee until we nut out who the website is for, what it should be doing for them and how it’s going to do it. It’s a process that requires a high level of client engagement to produce a quality outcome.
After the workshop, is where we typically take over and start to develop a prototype based on
workshop outcomes.
The main difference between Lean UX prototypes vs traditional examples is the focus on high level flows. It allows us to work with clients to draw out, test, re-iterate and re-test at a faster rate and with less expense. We end up getting a more thoroughly refined concept when we’re not carrying the weight of thinking about accounts logins, how forms will work etc.
So what happens next? Following the Lean UX process you’re in a position to where you know exactly what it was you want to build, for who it’s being built, have a clear plan to do so and fully understand the rationale behind the plan. It’s an empowering position to be in that can help you when speaking to developers by keeping the conversation focussed on the MVP concept, thereby reducing excess development time and cost when it comes time to execute.
