Product management, from strategy to launch
The Product Leaders work group takes product management questions in group chats. Leaders who ran product at Slack, Figma, Webflow and Atlassian work through the job from strategy to launch: deciding what to build, getting the team behind it and telling whether it worked. They also weigh how AI is changing the way product teams are staffed.
Updated
Questions Answered
The choices a good product strategy has to make
A good strategy names a customer problem, makes one clear choice about the value to deliver first and says what the team will set aside, clearly enough that teams can use it in daily decisions.
Telling a real product strategy from a dressed-up roadmap
A strategy shows up as decisions about who the team builds for, which requests it declines and where people are staffed, made before the results are certain.
Customer interviews that lead to a different build
Interviews change the build when they feed a decision someone owns, test a working prototype with realistic data, and are read against the segment and the job each customer came from.
What to cut from an MVP, and the one part to build well
Decide how high the bar for viable is, cut breadth until one segment does one job on one surface, and build the moment the test depends on well enough that the result means something.
Handling feature requests without letting them write the roadmap
Give every request a home, rank only the near-term work, and judge each ask by the problem behind it and the segment it comes from rather than by how often it is repeated.
Judging a new feature against the bar set before launch
Decide what a win looks like before the feature ships, read the result against that bar on a date set in advance, and check that the product as a whole gained.
Getting stakeholders to agree on scope, and keeping it agreed
Write the scope decisions where everyone can see them, make every addition a choice with a cost, and check that agreement is real before the team treats scope as settled.
Giving a delivery date for a project still full of unknowns
Give a range and the decisions that move it, resolve the unknowns on the path to customer value first, and re-forecast as each milestone comes back with real input.
How AI is changing who sits on a product team
It depends on the company and the stage of the bet. Small pods with wide roles suit new bets, while large products keep their specialists and run into new limits on judgment and code review.
Writing a product brief the team can build from
A useful brief lets engineers and designers make good decisions without the PM in the room. It says who has the problem, the outcome wanted, the trade-offs already made and what is still open.
Ask a Work Group
Don't see your question? Ask the group whose members answered these.
More Work Groups
Not the right group? Ask another one instead.
Product Leaders
