Learn why it's important to have the whole team involved in a design thinking exercise. That means people from development, QA, product and project management, market research and marketing, and design and user research, as well as subject matter experts and other specialists.
- Design thinking processes can be performed in as little as one intensive week, or can take as long as you feel is necessary to really understand and validate solutions to your users issues. Representatives from every discipline need to be involved in a design thinking exercise. Business, IT, Marketing, Legal, Design, User Research, Testers, Ops, and so on. This is the only way to ensure that all the different perspectives are covered, and that everyone is on the same page.
There are some other groups in your organization who need to be aware of what you're doing so they can give input. But they probably don't need to be there all the time, every day. I like to run 20 minute demos every morning to show what we did the day before. Some people you should invite to those demos are Legal, your Internationalization or Localization team, Technical Architects, and any other specialist groups who'll need to be involved later in the process. Obviously some of these roles might not exist in your organization.
There might be reasons why some of these people wouldn't attend. I'm giving you this list as an indication of the breadth of experience that you want in the room when you run this session. After hearing me say that, you're already thinking that this is an expensive undertaking, because it takes time from all these people's schedules. The thing is, they'll all be involved at some point. It's either now, up front, gaining a common understanding, or it's later on in a never-ending line of meetings where you have to go over the justifications for the project time and time again.
And to be honest, what else really should these people be doing at the definition phase of a project? Design thinking helps every discipline get clearer about what their role will be, what tasks they need to perform, and what type of support they'll need to provide as the project moves forward.
Along the way, you'll learn who should be involved, what activities you need to perform, and how to observe users, come up with great ideas, test solutions with prototypes, and plan development. Plus, discover how to avoid the common issues that can get in the way of a successful design thinking session, and the traps that people fall into when using the process for the first time.
- Assembling a team
- Finding a location
- Watching real users
- Mapping the customer journey
- Identifying pain points
- Coming up with good ideas
- Testing ideas with real customers
- Planning development
- Understanding the benefits of design thinking