One overlooked benefit of design thinking is how it improves communication between team members, and from the team to management and the rest of the organization. The early testing that is part of the design thinking approach also allows for fast course correction when the team finds issues. Better communication means lower project risk.
- If you follow a design thinking process, it only takes a couple of weeks to show results. You'll have clear project goals and the thing you plan on building will already have been prototyped and tested. With technical team members involved from the beginning, feasibility is less of an issue. Costing will be clearer because you'll have a plan with set phases and built in test points and metrics. You've reduced the risk right from the first iteration. There's still an opportunity to fail, but you've reduced the potential for that to happen.
As you move forward, you'll have multiple opportunities to measure, so multiple opportunities to change direction and deliver the right product. Communication is vital. It would be hard to over-communicate, both among team members and to the broader organization. The more people who know what you're planning on delivering, the more likely it is you'll find issues or conflicts early enough to take evasive action. The artifacts you create during the design thinking process will make it much easier to communicate.
Each one, from your initial experience map summarizing the customer journey through to your paper prototype, showing a proposed solution, lets people from outside the team understand, and more importantly, contribute to your deliverables. Of course you might want to make prettier versions of some of these artifacts so you can take them to meetings and show them to people, but there's some real value in keeping the original versions up on the wall in your team area. It shows that you really did do all the messy work to make this design happen, and it's easier for anyone from the team to just walk someone through the story map, experience map, design charrette output, or storyboards to help them understand why the team's taking a particular direction.
In this course, Chris Nodder explains where design thinking fits into product development and what it can help you achieve. He describes each step in the process, from identifying the problem you want to solve and brainstorming solutions, to prototyping, development, and release. Learn about the pros and cons of this approach and how to overcome challenges such as organization inertia and silos. Done right, design thinking can start your organization moving toward broader user-centered design techniques such as information architecture, content testing, usability testing, and marketing research.
- Agile, lean, and design thinking
- Preparing to sell design thinking to your organization
- Finding the real problem
- Correcting course
- Offshoring and outsourcing
- Getting past organizational inertia and silos
- Tracking your success