Think big and work small: How I’d connect ambition to small bets
Our reviewers evaluate writing services independently. Learn how we stay transparent, our methodology, and tell us about anything we missed.
Hold the ambition and the next step together
I use “think big and work small” to connect a meaningful product direction with a sequence of affordable learning steps. Thinking big gives the team a reason to care and a way to make trade-offs. Working small keeps an assumption from turning into a large irreversible commitment.
I would describe the outcome I want, the customer problem behind it, and the evidence that would tell me we are making progress. Then I would identify the riskiest assumption and choose the smallest slice that can test it.
Slice by learning, not by convenience
A small slice is not simply a smaller version of the final feature. I would ask what can be observed, used, or evaluated by a real user or partner. Sometimes the right slice is a prototype, a manual workflow, a limited audience, or a measurement change.
I would keep the team honest about what the slice proves and what it does not prove. Early evidence should refine the direction, not become a reason to claim certainty.
Keep the system aligned
I would share the larger intent with stakeholders while making the next commitment narrow. That reduces the temptation to build the entire imagined solution before the team has learned whether it solves a meaningful problem.
My bottom line
I think big about customer value and work small enough to learn responsibly. The Product HQ product manager certification supports this product judgment, and the Product HQ newsletter offers more practical guidance.
