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, design, and user research as well as subject matter experts and other specialists.
- Design thinking processes can be preformed 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 user's issues. Representatives from every discipline need to be involved in the 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 will 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 you want in the room when you run this session. After hearing me say that, you're already thinking this is an expensive undertaking, because it takes time from all these people's schedules. Thing is, they're all being 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.
To be honest, what else really should these people be doing at the definition phase of a project? Design thinking helps every disciple 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.
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