Product Lab
Kill it, fix it, or double down
A feature you shipped nine months ago has 4% adoption, a vocal set of enterprise users who love it, and a maintenance cost your engineering lead keeps raising. You have one slide at next week’s portfolio review. Make the call and defend it.
What to work through
- What evidence would change your mind? Name it before you look at the data.
- Who is the 4%, and what is the cost of taking it away from them?
- What does maintenance actually cost, in engineering time and in opportunity?
- One slide. What is the recommendation, and what is the one number behind it?
How to submit
Post your thinking in the challenge thread in #product-lab. A paragraph, a photo of a whiteboard, or a one-page template are all fine. Read two other submissions and react to them.
Two-Week Cycle
Day 1: Challenge posted
Brief goes up here, then we post it to #product-lab.
Next 7 days: Share your thinking
Post in the thread. Read two others and react.
In 2 weeks: Trainer reacts, live
A Productside trainer walks the submissions in Office Hours. Recap posted after.
Challenges are drawn from Productside group work and course exercises. Have one worth running? Let us know in #product-lab.
From the last challenge
Coming Soon
More in Productside Connect
Live Q&A with a Productside trainer. Submit your problems, participate in Q&A, discussion and polls.
Coming Soon
