Sharebird
Sign Up / Sign In

Product Development

5 Answers
Puja Hait
Puja Hait
Google Product LeaderSeptember 13
I would say there is no substitute to real user data.   User research is table-stakes. But in my experience, not always representative of "actual" usage, so don't overindex on specifics. Rather validate if the problem statement is indeed important for the user segments. Because if it is, then ......Read More
2154 Views
7 Answers
Brandon Green
Brandon Green
Buffer Staff Product ManagerMarch 10
I think the quote has validity in some contexts and less in others. If you are building a 0-to-1 product in a company where the culture is anxious about, say, the brand impression your "embarrassing MVP" may invoke, that may be a fear you need to help alleviate as a PM. However, there are other c......Read More
439 Views
7 Answers
Brandon Green
Brandon Green
Buffer Staff Product ManagerMarch 9
I don't think I have a great answer for this; I think there are a few possible points to consider though, and I think it ultimately comes down to how you understand the user/market problem your company is positioned to solve with its product(s). 1. Is that problem best solved by a single produc......Read More
581 Views
7 Answers
Brandon Green
Brandon Green
Buffer Staff Product ManagerMarch 10
So, in my experience of building 0-to-1, I've never had to do this before exploring a potential new product 😅 and candidly, I really don't like doing it because any projections are in my experience educated guesses based on inherently flawed source data - historical data that may not apply anymor......Read More
560 Views
6 Answers
Ravneet Uberoi
Ravneet Uberoi
Founder & CEOAugust 31
One way I like to prioritize problems is based on the level of risk these will pose to the final solution. Which are the riskiest assumptions or riskiest bets that will affect the success of your product? (Risk can be defined crudely in terms of Low, Medium, High or in some cases you might have a......Read More
2765 Views
2 Answers
DJ Chung
DJ Chung
Atlassian Senior Product ManagerAugust 9
This is a continual process! It is important to have regular syncs with the engineering team to discuss progress, open product questions, and review next steps. I don't think this can be done in stand ups, but rather having a weekly 30 min sync has worked for me.  I don't think it's possible t......Read More
923 Views
5 Answers
Ingo Wiegand
Ingo Wiegand
Samsara Vice President of Product Management - SafetyMarch 31
* I generally like to break product problems into smaller, independent pieces to help me more effectively prioritize and isolate critical ‘must do’ work * One potential way to approach a problem decomposition like this is to think of three distinct categories of feature work: a) items ......Read More
1010 Views
1 Answer
C. Todd Lombardo
C. Todd Lombardo
Appcues VP of ProductJuly 27
We have something we call a "common roadmap discovery doc" that has a set of questions around the problem that the PM, the designer and a tech lead (engineer) all work on together. The doc has questions about the problem to solve, the evidence we have around why it's important, the technical chal......Read More
418 Views
6 Answers
DJ Chung
DJ Chung
Atlassian Senior Product ManagerAugust 9
At the beginning of the project. Before we start implementation, I make sure to define:  * What problem are we trying to solve and for whom? * Why is this problem important to solve? * What is the business impact?  * How does this project ladder up to the broader product/company strategy? *......Read More
634 Views
2 Answers
DJ Chung
DJ Chung
Atlassian Senior Product ManagerAugust 9
For a visible project that has the attention of upper leadership, I think of 3 checkpoints with leadership: 1. Showcasing the vision at the beginning of the project Once I have nailed down the problem to solve, why it's important to solve, how it contributes to broader business goals, and you......Read More
913 Views