In Part 1, we talked about what Lean UX is and why companies sometimes build things people don't even want.
Now in Part 2, we get into something more practical: how teams actually design and test ideas in real life.
My name is Nayama, I'm a UX/Product Designer, and in this post I'll explain Chapters 4 and 5 of the book Lean UX: Applying Lean Principles to Improve User Experience in a simple and easy way.
Watch the video version here:
Chapter 4 — Collaborative Design
Designers Don't Work Alone
A lot of people think designers work alone and come up with perfect ideas.
That's not how it works in real life.
In Lean UX, design is a team effort.
That includes:
- Developers
- Product managers
- Stakeholders
- Researchers
Everyone helps shape the final solution.
Collaboration Is Not Chaos
At first, this might sound confusing.
It can feel like "everyone will start changing the design."
But that's not the idea.
Collaboration is not design by committee.
It does not mean random opinions.
It means the whole team understands the problem together.
That shared understanding leads to better decisions.
Real Example — Email Didn't Work
In my experience, our team used email to share design ideas.
This created problems:
- Long messages
- Confusion
- Missed feedback
- Late responses
Sometimes something felt approved, and then days later everything changed.
The problem wasn't the team. It was the system.
A Better Way — Working Together in Real Time
We switched to using a tool like Miro.
It's like a digital whiteboard where everyone can:
- Add ideas
- Use sticky notes
- Organize thoughts
- See everything in real time
Instead of sending ideas back and forth, we started thinking together.
This made a big difference.
Why This Works
Before, the process was:
"This is my final design."
Now it became:
"Let's solve this together."
That shift improves both speed and quality.
Messy Work Is Better at the Start
This is one of the most important ideas:
Messy work is better in the beginning.
When a design looks too perfect, people don't want to change it.
But when it looks unfinished, people feel comfortable giving feedback.
That's what you want early in the process.
Design to Learn, Not to Impress
Instead of trying to impress people with a perfect design early on:
Focus on learning early.
This is important because:
- Things change fast
- Feedback matters
- Time is limited
Waiting too long to get input can lead to wasted work.
Design Studio
The book introduces a method called Design Studio.
It's a group activity where:
- Everyone sketches ideas quickly
- Everyone shares
- Everyone gives feedback
- Everyone improves ideas together
It helps teams work faster and stay focused on the problem.
The 6-Up Method
A simple technique:
Divide a paper into 6 sections and draw 6 different ideas.
This forces you to move past your first idea.
Most of the time, the first idea is not the best one.
Chapter 4 — Key Takeaway
Good design does not come from one person.
It comes from:
- Collaboration
- Feedback
- Iteration
The goal is not to be the smartest person in the room.
The goal is to build the best process.
Chapter 5 — MVPs & Experiments
What Is an MVP?
MVP stands for Minimum Viable Product.
It means the smallest version of an idea you can create to test if it works.
It is not about being perfect.
It is about learning.
Simple Example
Imagine you want to create a clothing brand.
Instead of:
- Making a full collection
- Building a full website
- Buying a lot of inventory
You start with one product and show it online.
That is your MVP.
The real question is:
Do people actually want this?
The Main Idea
Do not build everything first.
Test first.
Many teams spend months building something before knowing if anyone cares.
Lean UX helps avoid that.
The Lean UX Cycle
The process works like this:
- Start with an idea
- Build a small version
- Test it
- Learn from users
- Improve and repeat
This cycle helps teams learn quickly and reduce risk.
You Don't Need a Full Product
You can test ideas without building a full product.
You can use:
- Landing pages
- Ads
- Signup forms
- Fake features
These are fast ways to check if people are interested.
The "Button to Nowhere"
A simple example:
You add a button for a feature that does not exist yet. If people click it, that means they want it. If they don't, you avoid wasting time building it.
Prototypes
A prototype is a simple version of your idea.
It helps you test how people interact with it.
It is not meant to be final.
Low vs High Detail
You can create:
- Simple sketches
- More detailed designs
But more detail does not always mean better results.
Simple versions are often enough to learn what you need.
The Mindset Shift
Most people want everything to be perfect from the start.
Lean UX asks a different question:
Do people even want this?
Chapter 5 — Key Takeaway
Design is not about being right.
It is about finding out if you are wrong as early as possible.
Strong teams focus on learning quickly.
Final Thoughts
Lean UX helps teams:
- Avoid wasting time
- Test ideas early
- Build better products
It replaces guessing with learning.
What's Next
Part 3 will cover the final chapters:
- Integrating Lean UX and Agile
- Making Organizational Shifts
This is where everything connects to real teams and real companies.
If this helped you understand Lean UX better, you are already thinking more like a product designer.
Comments
Be the first to leave a comment.