Double Diamond Discovery - Part 4 and final by@NickO

Double Diamond Discovery - Part 4 and final

Nick Oneill HackerNoon profile picture

Nick Oneill

Father. Husband. Hyperactive. Creative. Enthusiastic. Loyal. Passionate. Funny.

This is the fourth and final post in my series on an approach to product discovery - Double Diamond Discovery (again thanks to the British Design Concils super awesome framework). So far I have posted an overall view and then expanded on Diamond 1 (D1) and Diamond 2 (D2). This final post discusses the delivery track ( and how this feeds back into the discovery track. In the diagram above there are two steps after discovery - “Delivery” and “Learn”. Although we want to have a ‘ship to learn’ ( mindset I need to emphasize most of the learning is done in D2 where learning is cheap and fast. There are always many new things to build/fix/improve so it’s easy to ship and forget. But shipping is only half the job.

Shipping is only half the job.

Most of our discovery work will have a handful of users and mostly qualitative feedback so although we may have done a thorough job in discovery and are ready to ship with confidence, most of the time we are not shipping with certainty. No matter how much discovery you do, even AB testing with statistical significant results, shipping is the only way to answer the question “Do our customers use the feature?”.

Delivering production quality software ( provides feedback at scale - but only if appropriate instrumentation to capture the metrics (e.g. our key results) are implemented. We need to setup a dashboard in the analytics tool to easily view and draw understanding from the usage behaviour. I suggest spending 15min every day looking at the dashboard and sharing the interesting metrics with the team.

Do a deep dive

Do a deep dive into the usage data with the full team - design, engineering, product, analytics and data science. What is the data telling us? What can we learn? How can we take these learnings back into discovery? What is the adoption? The engagement? The retention? Are the key results moving?

And then... how does the adoption, engagement, retention vary between users?

And then... is there a segment of users highly engaged? What are the characteristics of that segment? Which of those characteristics makes the software more useful? If the segment is large enough focus your future efforts on that segment (be careful not to create custom solutions for each segment - although this is great consultancy work its lousy product management).

Fiddle with the dashboard, look for patterns, look for the “hm… that seems a bit odd”. Dig in and become one with the data {-_-}.

As mentioned in step 5 of the ground work we need to setup a recurring meeting to review the outcome of what we have shipped and reflect/share/capture what we have learned.

Take these insights from the data and the lessons learned back into discovery. Rinse and repeat.

Good luck.

Nick Oneill HackerNoon profile picture
by Nick Oneill @NickO.Father. Husband. Hyperactive. Creative. Enthusiastic. Loyal. Passionate. Funny.
Read my stories


Signup or Login to Join the Discussion


Related Stories