If you're working with offshore or outsourced teams, you're already aware of how a little communication issue can cause big project delays and a ton of rework. The artifacts you produce during a design thinking exercise can help you show remote teams exactly what user interaction you mean them to build, so they can deliver the right thing first time.
- In larger organizations, development teams are often either in different cities, or even different countries. Communicating over distance, and over time zones can be really painful. Especially, if there's also a language or culture barrier. With the design thinking approach, you have a set of artifacts that can help other team members who get involved as the project progresses to easily understand the reasons behind your design decisions. The experience map which shows the existing customer journey, incorporates all the issues and cultural sticking points that make it clear why the problems exist in the first place.
The prototype shows the intended interaction that will resolve those pain points. Often, I have found that the biggest issue in outsourcing comes at the interaction level. The outsourced team can interpret a specification document, but the interfaces they deliver often look like a jumble of form fields, or the result from a SQL query. By showing them the intent of the interaction, and a visualization of how it should progress, it's much more likely that they'll create an interaction flow that meets your customers' needs.
Seeing videos of user testing sessions, or even just a video walkthrough of the experience from the paper prototypes can help even more. Once team members see the product in action, even in such an early form, they're much better able to see how their contribution fits into the whole process. And the story map provides an overview of the team's intentions, both in this phase of development, and in the future. Walking a remote team through the map helps them understand the bigger picture of the work they're involved in.
So they can see how their piece fits in with everything else that's being worked on. That way it's more likely that the stuff they deliver will integrate rather than looking and feeling like a completely different product. How much easier are these artifacts to understand than a document with lots of boring specifications listed out, and no real context. The answer is much easier. It's actually no real surprise that outsourced and remote teams have difficulties delivering quality code and interactions currently given the low bandwidth nature of the communication we tend to have with them.
The design thinking artifacts help make sure that everyone truly understands what the product's goals are. How it should look and behave. And what's expected of them at each stage of the release process.
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