"But unfortunately, we don't spend enough time understanding the problem because it’s easier to build solutions that move our KPIs."
I agree with that, sometimes we forget the problems and the users just to move KPIs. When this happens I always try to take a step back to understand the situation
Great article Will, in principle I agree with your points. However, personally being at a pre-seed startup I've felt the focus on delivery to be overwhelming in comparison to discovery. We're at a stage where the technology is so well defined by the founders that there's so scope for discovery to change "what" we're building.
Curious if you've had similar experiences working at early-stage companies.
"Remember that the goal of a discovery project is to create actionable product insights. This prevents the projects from becoming too academic or fluffy."
Hi Will, can you provide an example of non-actionable, "academic", or "fluffy" product insights that teams want to avoid while conducting discovery?
Hey, Will! Thanks for sharing that :)
A sentence caught my attention
"But unfortunately, we don't spend enough time understanding the problem because it’s easier to build solutions that move our KPIs."
I agree with that, sometimes we forget the problems and the users just to move KPIs. When this happens I always try to take a step back to understand the situation
This resonates so much with my product journey wrapping up the 90 Days. Thanks for sharing, Will!
This is a great article Will. Unfortunately not seeing many B2B orgs in favour of in-depth research!
This is a great article Will. Unfortunately not seeing many B2B orgs in favour of in-depth research!
Great article Will, in principle I agree with your points. However, personally being at a pre-seed startup I've felt the focus on delivery to be overwhelming in comparison to discovery. We're at a stage where the technology is so well defined by the founders that there's so scope for discovery to change "what" we're building.
Curious if you've had similar experiences working at early-stage companies.
"Remember that the goal of a discovery project is to create actionable product insights. This prevents the projects from becoming too academic or fluffy."
Hi Will, can you provide an example of non-actionable, "academic", or "fluffy" product insights that teams want to avoid while conducting discovery?