Discovery vs Delivery



Subscribe to our newsletter

By subscribing, you agree with Revue’s Terms of Service and Privacy Policy and understand that Manolo Recio Sjögren's newsletter will receive your email address.

Discovery vs Delivery
By Manolo Recio Sjögren • Issue #7 • View online
Hey Friends 👋
Thanks for sticking around. This newsletter now has 20 new subscribers - if you are new, welcome to the party 🥳.
Inside this week’s issue:
  • 💡 Discovery vs Delivery — This week I bring a piece by Marty Cagan, partner at Silicon Valley Product Group on the distinction between product delivery and product discovery.
  • ✍️ Threads of the week — I’ll be sharing the best threads on business, productivity, finance and entrepreneurship.
  • 📖 What I am reading — The Psychology of Money. Possibly the best book about Finance that I have come across. Simple language and full of insight!

💡 Discovery vs Delivery
Here is fact in case you didn’t know: The majority of new products/features end up failing to achieve market traction or lose engagement after an initial spike. Many teams often find out way too late that what they are building isn’t really what users need.
By incorporating product discovery to their development process, engineering teams can avoid this trap by refining their ideas based on their customer’s existing pain points and needs. I’ll explain further below:
🤜🤛 Product teams are faced with two challenges
In order to build software that actually provides value to their users, product teams need to:
  1. Discover what to build – So they don’t waste their efforts on products/features that are ignored by their users (building production-ready software takes time).
  2. Ensure that they deliver robust and scalable software – Software that is reliable, maintainable, secure, has the right analytics implementation, etc.
These two challenges seem to be at odds as teams on the one hand need to learn fast with rapid discovery while at the same time delivering stable and robust software which is time-consuming.
Generally speaking, modern software teams have become better at the delivery challenge as they have adopted techniques to deploy small incremental changes which allows them to release periodically with confidence. This is not a process that you’d like to mess with.
🧭 How product discovery reduces uncertainty
To avoid wasting the team’s engineering efforts on building stuff that your customers don’t want we run discovery activities in parallel.
With product discovery, we simply want to get our ideas in front of real users customers early and often so they can be validated before they are written down as backlog items.
Instead of running experiments in production, you could invite a set of customers to spend some time talking to them in person, discuss what their main pain points are and test new ideas with experimental versions or even dummy prototypes.
Getting your ideas in front of customers early and often doesn’t require the developer’s time and will allow you to define a product roadmap based on backlog items that have been validated by your own customers.
Here is the link to the article.
You can also read it on my website
✍️ Threads of the week
Self-development (becoming the best possible version of oneself) has been one of my main interests over the past few years. I will be sharing the best advice I bump into on Twitter in my newsletter. By the way, you should follow me, if you aren’t already.
On productivity – Now that I have a family of 4 that I want to spend time with, I need to come up with techniques to make sure that I get the most important things done in time! Here is a great thread on how to become more productive 👇
Sahil Bloom
I’ve been searching for ways to get more focused and efficient with my time…

Here’s one simple productivity trick I’ve discovered:
On self-development – I have been following Blake for a while now. He shares insights on business, productivity and building a better you. The thread below has great pieces of advice 👇
Blake Burge 💡
Advice I wish I'd listened to years ago: 🧵
📖 What I am reading: The psychology of money
The psychology of money by Morgan Housel
The psychology of money by Morgan Housel
When I started learning about finance I thought that I needed to learn about maths, data and formulas. This book has taught me otherwise.
Divided into 19 easy-to-read short stories the book describes in simple language how financial decisions are made in real life. From boom-and-bust cycles to the 2008 financial crisis, the book describes with simple language people’s tendency to make financial decisions based on personal history, pride or ego.
🇬🇧 Link to Amazon 👉 The Psychology of Money
🇪🇸 Link to short video in Spanish 👉
🤗 And that's all for this week
Thanks for reading. If you enjoyed this issue, please remember to share it online 👉 Share on Twitter or Share on Facebook.
Have a great day,
Ps. If this was shared with you, you can subscribe here.
Did you enjoy this issue?
Manolo Recio Sjögren

Thoughts and principles on product development straight to your inbox. Subscribe to improve your product skills!

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue