Phases Four & Five - Prototype & Test

[github-learning-lab[bot]]

This pull request is about the Prototype & Test phases of Design Thinking. Let's kick this topic off with a challenge question!

Only high-fidelity prototypes are of value in Design Thinking.

• [ ] True, it's worth the time to always build out the most accurate simulation of the final product as possible.
• [x] False, quickly generating even the simplest prototype allows teams to gather feedback faster.

---

I'll respond when you check one of the boxes above.

[github-learning-lab[bot]]

Answer :crystal_ball:

It's false! One of the main reasons for prototyping is to fail fast. Even a simple pencil & paper prototype can help teams to discover that they're on the wrong track. As prototypes evolve user testing becomes more involved, but their feedback should be incorporated right from the beginning. Prototyping allows for this kind of continuous feedback loop with users and other stakeholders from the start.

This approach helps teams avoid getting stuck in limbo or "analysis paralysis" like Dilbert's colleagues.

Read more detail about how to use prototype and test as part of Design Thinking in this pull request.

---

:keyboard: Activity: Prototype & Test

1. Review the additions about the Prototype & Test phases of Design Thinking in the Files changed tab. That's where the content for these topics in our Design Thinking Toolkit will come from.
2. Approve this pull request
3. Merge this pull request
4. Delete the branch

---

I'll respond when you merge this pull request.

[github-learning-lab[bot]]

You can find your next steps in your next pull request.