We are focusing on this general set of steps, which cover the basics of design processes really well.

Scale for Minimum Viable Product (MVP)

Not all projects are created equally. Sometimes processes are assumed to be prescriptive. Every step has to be followed exactly. Newer processes take this into consideration more, and the concept of a Minimum Viable Product (MVP) has become common. When a project is constricted by resources or has a narrow scope, we should still look at each factor of the design, and each phase of the process. We just don’t have to pull out every tool in the toolbox. Look at what method or tool will provide the most value to accomplish the goal.

Figure 4 MVP from jussipasanen.com/tag/mvp/

Henrik Kniberg’s illustration puts it another way. Instead of focusing on one part of the product (wheels) focus on the simplest form of transportation. The same goes for process. If you have a small project, or short timeline, you don’t have to develop all new personas and workflows. Start with something that already exists, and focus on exploring the problem rather than the whole picture.

Discovery

This phase is focused on digging into the “problem” to be solved. A problem can be solved by identifying a new way to accomplish a task, or by refining an existing solution. Your purpose is to find out what users really want and need in order to identify requirements. You are trying to look at the breadth of the project.

Lean UX results in a hypothesis at the end of this phase that summarizes the intent of an initial research phase, whatever it is called. The hypothesis follows a format:

We believe that <feature> is essential for <demographic> users. This will achieve <goal>. We will have demonstrated this when we can measure <goal> <metric>.

METHODS

Brainstorm

User Interviews

Subject Matter Expert Interviews

Competitive Benchmarking

Observation of Users

Literature and Study Reviews

DELIVERABLES

User Stories

Personas

User Flows and Use Cases

Hypothesis

KEY STAKEHOLDERS

Design Team

Business Analyst

Product Manager

Define / Ideation

In the definition or ideation phases, you are analyzing all the information you gathered in the first phase. This is the first time “converge” comes into play. Sift through all the information with your team to figure out what really stands out. Ask what surprised you and your teammates. This will help you to see things through the eyes of your users and really understand the problem.

METHODS

Design Sessions

Sketching

Reviews

User Testing

DELIVERABLES

Sketches

Wireframes

Content Hierarchy

KEY STAKEHOLDERS

Design Team

Product Manager

Subject Matter Experts

Develop / Implementation

Diverging in this phase is about establishing the depth of your product. You’ll take the best one or two concepts from the define or ideate phase and flesh out all the details, pieces and parts. And then test with users, as well as reviewing with stakeholders, to select the best solution for your users.

METHODS

Prototyping

Reviews

User Testing

DELIVERABLES

High Fidelity Prototypes

Content / Text Strings

Annotations

Graphic Assets

KEY STAKEHOLDERS

Design Team

Product Manager

Subject Matter Experts

Development Team

Deliver

In this final phase, you’ve converged on the final solution and are ready to hand off your fully defined design to your development team. You’ll work with them to ensure that the specifications are clear, understood, and implemented as you’ve intended.

METHODS

Quality Control Testing

Validation Testing

DELIVERABLES

Fully Functional Software

KEY STAKEHOLDERS