The first version of this framework was made basically on the spot, while talking with a client and grouping the notes by topic. Then I noticed that they are kinda the same topics each time, so I created the template to cover what I want to discuss. It went through a couple of iterations and get to this one.

We use this framework every time we start a new project, generally in a 45-60 minute meeting. We fill all the boxes out and it ends up looking something like this. We talk about the product, target audience, problems, advantages, goals - important parts of basically any business.

Once our meeting is done and everything is filled in, I'll take time to review, make connections, and understand what's going on. The outcomes of this exercise are the baseline for what happens moving forward.

First, we talk about the product, then we talk through each step of this framework. It's designed to cover all necessary aspects of product development in an easy-to-use exercise.

Our product in this case was a platform that automated a recruiting agency's hiring for medical staff. We developed a cohort system for different workshops and you can see how they describe things about the product.

Something really interesting is WHY do they want to solve these problems? We find this is really important in maintaining long-term passion about the product.

We use red notes to highlight things they might want but are missing, or things that aren't working at the moment, and purple for things that are really important or significant.

This is where I drop notes that don't quite fit elsewhere, but that are important. In this example, Satvic is the brand, so this section ended up focusing on how the brand came to be, hence the "Satvic journey" heading. It can be adjusted for other uses as needed.

Throughout the many times we've used this, because of the discussion format, we've never had an issue using this framework. It's part of a longer process - more info on that 

Daniel Andor

This is the framework I use to walk clients through a thorough product discovery process, setting up the entire remaining development of the product.

The first version of this framework was made basically on the spot, while talking with a client and grouping the notes by topic

We use this framework every time we start a new project, generally in a 45-60 minute meeting.

First, we talk about the product, then we talk through each step of this framework

Something really interesting is WHY do they want to solve these problems? 

This is where I drop notes that don't quite fit elsewhere, but that are important. In this example, Satvic is the brand, so this section ended up focusing on how the brand came to be, hence the "Satvic journey" heading

Throughout the many times we've used this, because of the discussion format, we've never had an issue using this framework

Why do you want to solve this problem? Why is it important for you?

Why does your product or service matter to your customers?

Opportunities we can exploit / What would make the business grow 10x?

What has to be true to reach your vision?

Discovery Walkthrough at Satvic Movement

Discovery Chat

The Product

Personas / Target Audience

Problems we solve

Why do you want to solve this problem? Why is it important for you?

Sign up to see more