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.

Grades the validation evidence for a product idea from compliments and hypothetical promises up to past behaviour and real commitments, then says what is known and the next test.

Coaches a new or accidental product owner through their first discovery project one question at a time, from framing the problem to who to talk to, what to ask and how to make sense of it.

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.

Acts as a product manager for AI features who starts from the user problem, defines quality with evals, designs for wrong answers and uncertainty, and watches cost, latency and user trust.

Reframes a nonprofit or public programme as a product - who it serves, the outcome they need, evidence, riskiest assumptions and small tests - adapted to funder reporting and volunteer capacity.

Assesses product-market fit from retention curves, the very disappointed survey, usage depth and qualitative signals, by segment, and recommends what to do next.

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.

Splits an internal tools or platform team's capacity across requesting departments with a scored intake, a run-the-business share, a buffer and a published allocation others can challenge.

Audits feature and date promises found in contracts, sales emails and call notes into a register with source, wording strength, owner, risk and revenue at stake, and drafts honest follow-ups.

Prepares a roadmap briefing for a board, trustees or co-op committee covering the few bets that matter, cost, what was cut, risks and the decisions asked, plus answers to likely questions.

Builds a physical product roadmap with EVT, DVT and PVT gates, tooling and part lead times, certification, factory slots and retail deadlines, showing the latest safe date for each decision.

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.

Reviews a proposed KPI or target for ways people could hit it while harming customers, quality or other teams, then adds counter-metrics, review rules and a safer wording.

Chooses metrics for a two-sided marketplace by stage, such as liquidity, match rate, time to first transaction and take rate, with definitions, balance checks and health measures for both sides.

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.

Analyses technician visit notes for a physical product into failure modes, parts, use conditions and repeat visits, separating product faults from installation and misuse and flagging safety patterns.

Analyses an in-home use test of a consumer product - diaries, questionnaires and check-in notes - against an action standard, with novelty decay, attribute diagnostics and safety signals.

Analyses on-site search queries to find unmet needs, missing products or content and zero-result terms, clusters them and ranks the fixes by search volume and business value.

Writes a one-off briefing for store, call centre, clinic or field staff on a product or service change - what changes, a one-line explanation, likely questions and what to do if it goes wrong.

Defines launch tiers for a company, from major launches to silent releases, with criteria, the activities and owners for each tier, edge-case rules and a checklist for tiering new features.

Takes an open-source project from readiness fixes to a channel plan, per-channel drafts, a launch-day run sheet and a two-week review, pausing for the maintainer's approval between steps.

Plans rolling out a product, process or service change across stores, branches, clinics or depots in waves, with pilot criteria, readiness checks, halt rules, learning loops and rollback.