Join daily insight on Substack.

Before you spent hours of designing or creating or building something whether it is a product / service / programme, etc… How do you know that what you are doing is meaningful?

Let’s learn from Jeff Gothelf, author of Lean UX: Designing Great Products with Agile Teams in 2013. And I will explain more… how to bring the idea into our real-world experience design, based on my insights to help you get more results.

When you get project brief or requirement such as a set of deliverables, instead of straight go into the design production, think differently. You are looking to produce impact, changes that help on people’s life, improve the business, and make make desirable outcome.

Lean UX goal is NOT to create ANY Product. The goal is to create a well-designed product through frequent team collaboration, iteration and users feedbacks.

1. Business Problem Statement

Not all problem are created equal, when you ask people, “What problem do you encounter?” “Oh, it’s problem A, B, C, ….” But see from different perspective, you don’t want to become a commodity, just do what users asked. So think, “What problem are worth solving?”

2. Business Outcomes

“What problem are worth solving?” That you, your team, your company, can solve it better than anyone else in the market. Instead of becoming everything for everyone, you become the one that creating a product / service / program / platform, etc. so memorable… of solving one problem extremely well.

3. Users and Customers

There are many measurable changes in human behaviour. When you set the indicators of success. Who are you trying to help? Let’s create a list of multiple persona (or avatar) types, an imaginary user who will be delighted, will be helped, by using your product or services. 

4. Users Benefits

Remember, your users don’t need features, they need to achieve user’s goals. Your customers aren’t going to buy your product specification, they are buying your product results.

5. Solution Ideas

“I don’t think that’s good idea.” This are the statement you get when you design without the steps 1, 2, 3, 4 above. So when generating solutions, you want to find what’s initiatives, opportunities, possibilities of making these ideas happens. You are NOT competing for the best ideas with your team, but working together to create What ideas possible?

6. Creating a Hypothesis in Lean UX

Hypothesis is like an objective to be tested from your assumption. When the team agree on hypothesis, we save time by not debating our own viewpoint. Hypothesis in writing is like you’re telling a story.

Convince yourself before you try to convince anyone else…”I believe that we will achieve this outcome for our user because they are solving this problem with this solutions.”

7. What’s the most important thing we need to learn first?

From each hypothesis, look for riskiest assumptions. By creating this product / service / programme, etc. You can think what is important to learn:

  • Minimise waste, building something that drive learning quickly.
  • Constant collaboration, bring the entire team to do project together.
  • Rapid experiment, organised thinking and lesson learned along the way.

and so much more…

8. What’s the least amount of work we need to do to learn the most important thing?

Least amount of work doesn’t mean doing nothing, but instead building Minimum Viable Product (MVP – that I will explain next time.) Or you can also build prototype, an example basic expression of your product, you can test it out, see reactions, gather feedbacks and doing iterative ways to continuously grow your ideas and get more results.

So why do you learn Lean User Experience?

Remember, your goal is to create Well-Designed Product, and this is happened when we increase collaboration, streamline our thinking process, reduce time-to-market, and validate our assumptions. Building something that people love doesn’t have to be painful, but can also become enjoyable learning process along the way. – Awesome UX Designer.

Leave a Reply

Your email address will not be published. Required fields are marked *