Product management

Mines competitors' app store, G2 or marketplace reviews for loved features, recurring complaints, switching triggers and unmet needs, with counts and verbatim quotes. Use to find openings.

Writes jobs-to-be-done statements and maps the forces of progress (push, pull, anxiety, habit) and the switching timeline from customer interviews, with evidence for each.

Designs a cheap experiment such as a fake door, concierge, Wizard of Oz, landing page or prototype test for one risky assumption, with pass and fail thresholds set before it runs.

Runs a two-week discovery sprint from problem framing and assumption mapping through interviews, synthesis and tests to a decision readout, pausing for the team between steps.

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.

Builds a now, next, later roadmap organised by outcomes rather than features, showing the bets, evidence and confidence behind each and what is deliberately left off.

Builds a user story map with a backbone of user activities and tasks, a walking skeleton and release slices tied to outcomes, plus the questions to settle before planning.

Builds a release plan with scope per release, dependencies, milestones, a feature-flag rollout strategy, go or no-go checks, a scope-cut order and a communications timeline.

Maps stakeholders for a product initiative by influence and interest, with their concerns and decision roles, and builds a sequenced alignment plan with messages and meetings.

Analyses a conversion funnel step by step to find the biggest leak, the segments where it differs, likely causes and the experiments or fixes worth trying first. For PMs and growth teams.

Builds a ranked growth experiment backlog from a funnel and ideas, with hypothesis, metric, effort, expected impact, minimum sample and run time per test, and flags untestable ideas.

Finds a product's activation moment from usage and retention data, defines an activation metric with an action, threshold and time window, and plans how to validate it.

Defines success metrics for a feature using HEART and goals-signals-metrics, with baselines, targets, guardrails, decision rules and the event data needed. Use before building or launching.

Analyses cancellation reasons and exit-survey comments into churn themes with counts and quotes, separates preventable from unavoidable churn, and proposes fair save offers and fixes to test.

Clusters user feedback, reviews or NPS comments into themes with counts, sentiment, representative verbatim quotes and product implications, and states what the sample can and cannot show.

Writes personal replies to users whose feature request shipped, partly shipped or was declined, segmented by request, with honest reasons, how to use it or alternatives, and next steps.

Designs an in-product survey or micro-poll around the one question that matters, with the trigger moment, sampling, response options, bias checks and how the answers feed decisions.

Plans how to communicate a price change, covering impact by segment, grandfathering options, notice timeline, the customer email, support macros, account talk tracks and churn monitoring.

Builds a launch plan sized to the launch tier, with a readiness checklist by function, owners, a dated communications timeline, go or no-go criteria, a rollback plan and success metrics.

Writes a product demo script built around the audience's pains, with setup checklist, story arc, three wow moments, recovery plans for failures and a strong close, timed to the slot.

Takes a launch from positioning to a tiered plan, launch assets, a go or no-go readiness review and a post-launch retro, pausing for approval between steps.