Quick-to-read LEAN UX textbook
Lean is one of the ways to increase the success rate of a project. Nothing difficult. In the whole process, it is to combine what can be combined and subtract what is unnecessary. Lean UX formulates hypotheses, creates MVPs, runs experiments, and organizes feedback. By constantly cycling through these four stages, we figure out what users need in the market. In order to apply this methodology, the entire organization must be aligned in their thinking toward the same goal.
Some seemingly unnecessary questions are mixed in, but they are still full of powerful questions. Clearly define who you're solving the problem for, tell us how great the benefit is to make short, frequent moves to a purpose organization, and how you can apply it to your team in practice. It's an old book that's been published, so there are occasional nonsensical parts, but the overall context is still convincing.
Author: Jeff Godelph, Josh Saydon,
Translated by: Sooyoung Kim
impressive part
3 elements of problem description
- product goal
- The problem the stakeholder is trying to solve
- what you need to improve
user assumption document
- Who are the users?
- Where are our products used in their lives?
- What problem does our product have to solve?
- When and how are our products used?
- Which features are important?
- How should our product look and be used?
In the assumption stage, the proto persona is determined, refined and refined to create the target persona.