Product investigation for teams that need the first test worth running.
Two weeks to investigate a product problem properly. I work through user behavior, the data, and the implementation, then give you findings and a concrete plan for what to change or test.
A few sentences are enough to start. Tell me what’s happening and what you need.
I follow the problem through the product, the data, and the code.
Who this is for, and what changes after.
Founders, product leaders, and product-led teams that know something is leaking, but are not sure whether the problem is activation, trust, conversion, retention, monetization, measurement, positioning, or implementation.
You walk away with a clear leak map, the evidence that can be trusted, the past conclusions that may need caution, the highest-leverage hypothesis, the first test plan, and what to stop chasing for now.
I investigate before recommending a fix. The work can lead into the product, the data, or the implementation.
The sprint is broader than one method.
Analytics, customer research, activation work, trust, conversion, experimentation, strategy, and implementation review are all investigative tools. The goal is to understand which mechanism is preventing users from reaching the outcome the business needs, or whether the team has already been acting on a leak that was not real.
- What this prevents
- fixing symptoms instead of leaks
- metrics drifting away from user value
- experiments being interpreted without context
- roadmap work based on partial evidence
See the diagnostic logic before you request a sprint.
A concise PDF showing what I check when product outcomes become unclear across goals, evidence, metrics, activation, user value, and roadmap assumptions.
What gets inspected.
Business Outcome
Clarify the outcome the product needs now: value, trust, conversion, retention, payment, booking, lead quality, or repeat usage.
User Value
Review what users actually come for, what progress they expect, and whether the journey creates enough value or trust.
Value Creation Logic
Map how the product should turn arrival, signup, trial, or usage into the outcome the business needs.
Activation Signal
Check whether the team has a meaningful activation moment rather than a shallow setup or signup metric.
Metric Hierarchy
Review whether the leading indicators and operational metrics explain the business outcome instead of creating noise.
Roadmap Assumptions
Inspect recent and upcoming roadmap bets against user value, business goals, and available evidence.
Decision Evidence
Check whether the evidence behind important decisions is complete, comparable, and interpreted correctly.
Funnel & Segment Logic
Review whether funnels, cohorts, and segments represent real product behavior and meaningful user states.
Experiment & Rollout Context
Assess whether tests, launches, and comparisons match the audience and context the team wants to act on.
Implementation Reality
Validate tracking and platform behavior where implementation can distort the evidence behind product decisions.
Ownership Gaps
Review where product, data, engineering, and growth handoffs make decision quality fragile.
How the diagnosis usually works.
Map the outcome
I identify the business outcome, product journey, metrics, past conclusions, and evidence your team is relying on now.
Inspect the leak
I review user value, activation, trust, conversion, funnel logic, segments, experiments, and implementation reality where it affects the outcome.
Name the hypothesis
Findings are prioritized by the leak most likely to affect conversion, retention, revenue, or the specific outcome you need.
Leave with a test
You get a first test plan, a 30-day action plan, and a view of what not to waste time on yet.
What I deliver.
Product Leak Map
A structured view of where users may be failing to reach value, trust, conversion, retention, monetization, or another business outcome.
Highest-Leverage Leak
A clear read on the most likely leak now, and why the visible symptom may be misleading.
Evidence Reliability Notes
Which metrics, funnels, experiments, or implementation details can be used confidently and which need caution.
First Test Plan
A concrete hypothesis, target metric, evidence needed, and test shape for the first useful move.
30-Day Fix-First Action Plan
Concrete next steps for product, data, engineering, or growth, written so the next action is obvious.
What To Ignore
Work that looks tempting but is unlikely to address the real constraint yet.
I can keep working with you as the product changes.
Some teams continue with a lightweight review rhythm after the sprint: helping implement the first test, interpret results, and keep improving conversion, retention, revenue, or the metric that matters as the product changes.
Request a Product investigation.
Product investigation is scoped to the product context. Send the situation and I’ll reply with the right shape for a 2-week diagnosis and first test plan.