Product strategy

Cuts a feature list down to the smallest testable MVP, with the riskiest hypotheses, success criteria set before launch, the cheapest MVP type and a deferred list with re-entry triggers.

Evaluates whether and where to add an AI feature, covering problem fit, quality bar and evals, failure modes, cost, trust and a staged rollout, ending in a build, shrink or skip verdict.

Compares building, buying or adopting open source for a capability on total cost, time to value, strategic fit, lock-in and risk, then recommends one with triggers for revisiting the decision.

Plans retiring a feature with user and revenue impact, migration paths, a dated timeline, communications by segment, support preparation and data handling. Use when reducing product surface.

Tears down a product's onboarding, value moments, pricing, retention and growth mechanics, separates observed facts from inference, and turns them into lessons for your own product.

Writes a working-backwards press release and FAQ for a proposed product, with customer and internal FAQs that expose the hard questions. Use when pitching a new initiative.

Writes five to seven ranked product principles a team can use to settle trade-offs, each with its meaning, what it rules out and an example decision, tested against real debates.

Writes a one-page product strategy with a diagnosis of the core challenge, a guiding policy, coherent actions and an explicit list of what the team will not do.

Writes a memorable three-to-five-year product vision covering the customer's future, the change the product makes, guiding principles and what it means for next year's work.

Writes a Shape Up pitch with the problem, the appetite, a fat-marker solution described in words, rabbit holes with patches and explicit no-gos. For teams using fixed-time, variable-scope cycles.