How do you balance investing in large, foundational projects that take time to deliver value with pursuing smaller, quick-win features that can immediately delight users? Any frameworks or strategies you recommend?

Our team is prioritizing several large, high-impact projects backed by strong data and customer insights, but they’re taking a long time to deliver value as we are a startup with limited resources. How do you balance these large projects with smaller, quick-win features that delight users but may not move major metrics?

Answer

2 Answers

Building 0-1 Products

Tanguy Crusson

Atlassian Head of Product, Jira Product Discovery • 1y

Great question. It's really hard to prioritize small, iterative product improvements against large new features/bets. In my experience you need both, as well as a few other aspects. The way we do it in my teams is to think of it as balancing investment levels between different buckets, and to dedicate capacity to each of these buckets. Otherwise it's a constant struggle. We've tried to describe it in this section of the Atlassian product discovery handbook talking about ideas, and that one about ...Read More

7,077 Views
Bruno Gobbis

Nuvemshop Director, Product Growth | Formerly Superhuman, RD Station, IBM, Bosch • 1y

Great question! That is also something I'm always trying to find the sweet spot. Balancing big bets vs. quick wins is a constant battle. I like working on it by using a combination of strategic allocation and frameworks to ensure we can do both in a sustainable way: Strategic capacity allocation method (Boulders, Rocks, Pebbles): One approach I love is thinking of our initiatives as boulders, rocks, and pebbles. Boulders are the large foundational projects (multi-month, high uncertainty, potenti ...Read More

2,047 Views