Guide
5 mistakes teams make with the Double Diamond

Five ways teams go wrong with the Double Diamond: running it as a one-way line, cutting discovery to a workshop, writing problem statements too vague to design against, leaving users out of the Develop phase, and treating the 2019 principles as decoration. Use it as a quick review before a discovery project starts, or when a launch missed and you want to know which phase was skipped.
Where this appears
What's in this guide
- Treating it as a straight line: It is a loop. New findings in Define can send you back into Discover.
- Squeezing the first diamond: Less than 3 to 4 weeks of real research on a big decision, and you are confirming guesses.
- Writing vague problem statements: Improve the experience is not a problem statement. Name who struggles, with what, and where.
- Leaving users out of Develop: Co-design and prototype tests stop you building a neat answer to a wrong reading of the problem.
- Treating the 2019 principles as decoration: Teams that treat them as optional report worse outcomes than teams that treat them as requirements.
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
html
<a href="https://www.koji.so/visuals/double-diamond-common-mistakes"><img src="https://www.koji.so/visuals/double-diamond-common-mistakes/double-diamond-common-mistakes.png" alt="List of five Double Diamond mistakes: treating it as linear, squeezing discovery, vague problem statements, no users in Develop, ignoring the principles." width="1200" height="790" /></a>
<p>Source: <a href="https://www.koji.so/visuals/double-diamond-common-mistakes">5 mistakes teams make with the Double Diamond</a>, Koji</p>




