Table of contents
Discover all posts easily with this table of content, grouped by topic. This is a living document.
Hi, it’s Budi.
Okay, here’s the deal: Moving forward, I’ll write with a more focused topic.
So far, I have been writing the newsletter depending on what’s the hottest topic in my mind. Sometimes I will talk about careers, sometimes executions. And I don’t think that’s a good reading experience for you.
The reason I write this newsletter is not to be another “noise”. We already have too many random posts on Medium and other platforms by various authors.
My goal is to share practical ideas to grow together with you. Therefore, I think it makes sense to go deep into a specific topic. I will still write Shorts that might be irrelevant to the topic I focus on, just to keep the newsletter fun.
Let me know what you think about this direction.
This is a living document to help you browse all posts easily. I will pin it on the homepage to help make it accessible. You can also see this as a roadmap for the upcoming posts I’m working on.
The topic that I’ll be focusing on: Product discovery.
In the next few months, I’ll focus on product discovery—it’s a practice to determine whether your team has a problem worth solving and a solution worth building. It’s how you reduce risk and uncertainty by gaining signals through users. (edited Aug 27, 2022)
Doing a product discovery is a technique to reduce that risk, a lot of products failed, 90% of startups died. However, product discovery is useful if you have a clear strategy and direction about what future you seek to make. You can start by differentiating the outcome and output in your vocabulary. I have mentioned how a field study helped our team to shape the strategy and get buy in from leadership.
Product discovery: Everything you need to know to start
Define the opportunity space to achieve the objective
Principle of product discovery
Why do products fail?
Use a PMF narrative as the anchor for your next product discovery
Start defining your audience, job to be done, pain, and workaround
How to define the target audience?
How to define the job to be done?
How do I choose which user pain to focus on?
Avoid solution jumping
Listen to users’ problems, not their solutions
Good vs. bad interview questions
Research questions vs. interview questions
A casual setting is the best way to learn
Ladder of evidence
Why your product must be different from the competitor?
Risk to reduce: Value, feasibility, viability, usability, ethical
How do you know if your solution works?
How to effectively conduct a design review?
Scope your design work with user stories
Writing user stories
On sprint planning
Mindset, concepts, and principles
Career and growth
Subscribe to make sure you don’t miss the upcoming posts. Join 1700+ practitioners—This newsletter is for people who want to solve hard problems and make meaningful impacts through tech products.
If you like my newsletter and are excited about the upcoming posts, consider sharing it with friends, or subscribing if you haven’t.
With a warm handshake,