Design Thinking Vs. Lean Startup: Friends or Foes?
In recent years, two similar-sounding but distinct approaches to product discovery have emerged: Design Thinking and Lean Startup. Most of the literature and experience reports refer to one of them, with similar frequency, without really giving much guidance on when to use which one of these approaches. This creates a confusion whether one is using the right approach. While a method must not be used for the sake of using a method, it is important to understand why, if at all, a given approach is likely to be more effective in a given context.
In this talk, I will compare and contrast these two approaches and address the following key questions:
- Why do we have two (or more) approaches to product discovery?
- What, if any, are the fundamental differences between these two approaches?
- How can I decide which approach is likely to work better in a given situation?
The talk will focus on contemporary literature, expert guidance, industry data points, and author's own experiences, and will provide action guidance for the practitioners to apply in their daily work.
Outline/Structure of the Talk
- Introduce the topic and highlight the dilemma of product discovery - 5 min
- Fast intro to Design Thinking - 5 min
- Fast intro to Lean Startup - 5 min
- Compare and contrast these two approaches: 10 min
- Industry examples: 5 min
- Conclusions and guidance: 5 min
- Q&A: 10 min
Learning Outcome
The key learning outcomes include:
- What is product discover in today's context?
- How Design Thinking and Lean Startups address product discovery?
- How can I decide which approach is likely to work better in a given situation?
The talk will focus on contemporary literature, expert guidance, industry data points, and author's own experiences, and will provide action guidance for the practitioners to apply in their daily work.
Target Audience
Designers, Entrepreneurs, Product Managers, UX Researchers, Technologists
Video
Links
My previous talks:
Videos: http://www.youtube.com/playlist?list=PL28C3EBDAE6525074
Slides: http://www.slideshare.net/Managewell/presentations
schedule Submitted 6 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_downNaresh Jain - Rapid User Validation using MVP Hacks
105 Mins
Workshop
Intermediate
You have a great idea and you want to build the product and launch it in market as soon as possible. Before anyone else can launch it. Great! But building the product takes time, money and opportunity cost. While building and launching a successful product, several things can go wrong:
- Have you really understood the core problem from the user's point of view?
- Will your users like the user experience?
- Have you validated your core-loop which makes your product very engaging?
- Is your business model flushed out and validated?
- And so on...
So how do you minimise these risks?
In this 90 mins workshop, you will run some real tests with real users to de-risk yourself and gain validated learning.
-
keyboard_arrow_down
Naresh Jain - Lessons Learned by Quitting TDD
45 Mins
Experience Report
Advanced
By working with some of the most successful tech-product companies, I realised that code is NOT an asset, it's a liability. We should strive hard to minimise code. In 2011, when I started to hack on ConfEngine, I questioned my belief in TDD. I had also started playing around with APL style Array-Programming and Functional Programming. I felt, may be, I was getting a bit too dogmatic about TDD and automated tests in-general. As a thought experiment, I decided to build ConfEngine without ANY automated test. At first, it was really scary not to have the safety-net of automated test (something I took for granted for almost a decade.)
As I scaled ConfEngine without any automated tests, I had certain interesting realisations:
- How to embrace Simplicity and Minimalism WITHOUT automated tests
- Why Throwing Away Code frequently helps you achieve a better decoupled-design and how this helps in better experimentation
- Fear of Refactoring WITHOUT Tests is over-rated (Good IDE and safe-refactoring techniques can take you a long way)
ConfEngine grew from a pet-project to a 8 member product team. It has over 60K users and has done financial transactions worth over half-million USD. And we continue to push forward without ANY automated tests. Its not perfect, but it has certainly helped me challenge my dogma around TDD.
Background: In 2001, I stumbled upon the Test Infected paper. For the next 2 years, I struggled to really apply the test-first concept on real projects. Finally in 2003, I felt that I had fully internalised TDD and was able to apply on almost all projects. Then I started playing around with FIT and FitNesse, using ATDD on some of the projects. In 2006 I published "Avatars of TDD" paper in which I explained various styles of TDD and its design implications. Until 2011, I was a very big advocate of TDD, ATDD and BDD. I still like those practices, however I would not recommend it in all projects.
-
keyboard_arrow_down
Scott Ambler - The Disciplined Agile Enterprise: Harmonizing Agile and Lean
90 Mins
Talk
Advanced
An agile enterprise increases value through effective execution and delivery in a timely and reactive manner. Such organizations do this by streamlining the flow of information, ideas, decision making, and work throughout the overall business process all the while improving the quality of the process and business outcomes. This talk describes, step-by-step, how to evolve from today’s vision of agile software development to a truly disciplined agile enterprise. It argues for the need for a more disciplined approach to agile delivery that provides a solid foundation from which to scale. It then explores what it means to scale disciplined agile strategies tactically at the project/product level and strategically across your IT organization as a whole. Your disciplined agile IT strategy, along with a lean business strategy, are key enablers of a full-fledged disciplined agile enterprise.
-
Joel Tosi
Anand Murthy Raj
Jutta Eckstein
Balaji Ganesh N
