Lean UX PPT
Overall, it’s a combination of Lean Startup & Agile Development. It means the practice of bringing together a product to light faster, in a collaborative, cross-functional way. As in Scrum practice, we work in the continuous feedback loop of iterations via customers feedback at the end of every sprint review cycle.
Overall, it’s a combination of Lean Startup & Agile Development. It means the practice of bringing together a product to light faster, in a collaborative, cross-functional way.
As in Scrum practice, we work in the continuous feedback loop of iterations via customers feedback at the end of every sprint review cycle.
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
What is Lean UX?
Insights on its Principles
Meaning
• It’s a combination of Lean Startup & Agile Development
• It means the practice of bringing together a product to light faster, in a
collaborative, cross-functional way.
• As in Scrum practice, we work in the continuous feedback loop of iterations via
customers feedback at the end of every sprint review cycle.
• Ultimately it will helps to build a product design organization that is more
collaborative, more cross-functional, and a better fit for today’s Agile reality.
Principles of Lean UX
A. Team Organisation
1. Cross-functional team
2. Small, dedicated & collocated
3. Self-sufficient & empowered
4. Problem-focused team
B. Guide Culture
1. Moving from doubt to
certainty
2. Outcomes, not output
3. Removing waste
4. Shared understanding
5. No rock stars, gurus, or ninjas
6. Permission to fail
A. Team Organisation
1. Cross-functional team
• Its Similar to Agile Methodology
• It’s a combination of different roles to create your products like developers,
managers, designers, content writers, marketing, QA, and many more, who
make up a part of LEAN UX teams.
• Basically, it’s collaboration & continuous involvement or communication
between each other and this goes on from day one of the project until the end
of the engagement.
Purpose
• To avoid pit holes in the process.
• LEAN UX & Agile will help the team to share information informally, which creates
collaboration earlier in the process & drives higher team efficiency.
• For Example, Projects passes in way like
Project Manager → Design Team → Developer Team → QA → Final Out Come
(Without any feedback iteration or market analysis)
Eventually, project outcomes will differ from what a customer or end-user actually
needs.
A. Team Organisation
2. Small, dedicated & collocated
• Small team – Maximum 10 members.
• All dedicated to only one project
• Working at same location
Benefits
• Communication
• Focus - keeps team members focused on the same priorities all
the time and eliminates dependencies on other teams
• Camaraderie
• Help the team track status, changes, and new learning
• allows the relationship to grow among team members
A. Team Organisation
3. Self-sufficient & empowered
• No external dependencies
• Give all the capabilities or freedom to operate to your team
• Give enough tools to create and release software/products
• Give openness & courage to them to figure out how to solve
the problems
Result
• Increases efficiency, freedom & learning curve amplifies
• Team can interact with customers directly in order to get
the freedom they need to create effective solutions.
A. Team Organisation
4. Problem focused team
• Team has been given a problem related to business, rather
than a set of features to create, which is also one of the core
values of the Agile manifesto and LEAN UX
Benefits
• We can unleash potential of team for problem-solving by giving them
actual business problems.
• Team will interact with each other and come up with better MVP
solutions for the product
• Helpful for the team to stay on the same page and be aware of the
project status and feature
B. Guide Culture
1. Moving from doubt to certainty
• In Lean UX everything is assumption until we prove it
• We gain clarity as we work
• Sometimes assumptions are easy to spot and sometimes its very
difficult and cost a lot of time and efforts on bad assumptions.
• In conclusion, by validating assumptions we can make complex
software development process a bit easy.
B. Guide Culture
2. Outcomes matters, not output
• Outputs – Features & Services
• Main goal – To achieve outcome
• Outcome – Create a meaningful and measurable change in
customer behavior.
• Lean UX is trying to achieve this outcome and measures its
progress.
B. Guide Culture
3. Removing waste
• Main principle of Lean Manufacturing
• It removes anything that does not contribute to goal.
• Value creation and waste removal technique can help
the team to keep their laser focus where it belongs.
B. Guide Culture
4. Shared Understanding
• It builds over time as the team works together
• it reduces the team’s dependencies on second-hand reports
and detailed documents to continue its work.
B. Guide Culture
5. No Rock starts, Gurus or Ninjas
• It emphasise on equal contribution in team
• No Stars or star performers
• Lean UX seeks team cohesion and collaboration
B. Guide Culture
5. Permission to Fail
• Allows new ideas to get the solution.
• And that’s ok if it fails
• So team has a healthy environment to experiment with their
ideas.
Conclusion
• It is favourable for any organisation to adopt this Lean UX
techniques.
• It will give fruitful results and give the best solutions for not
only the team but the business problem as well.
Thank You
https://www.tridhya.com/
You can Reach us by,
Office No 401 to 405 Fourth Floor "ONE WORLD WEST"
200 S.P. Ring Road, Bopal(Ambli), Ahmedabad-380058
+91 9638992877
info@tridhya.com
Change language