Challenge a growth hypothesis against the metric tree
Use a documented metric hierarchy to question a proposed growth initiative before the team prioritizes it.
How this works
Use a documented metric hierarchy to question a proposed growth initiative before the team prioritizes it. Use this before prioritizing a growth initiative when the proposed activity's connection to business outcomes is unclear. The review should reveal assumptions and side effects rather than confidently predict impact.
Map the intervention to a documented metric tree, identify the causal steps and propose a bounded validation test. Separate leading indicators from final outcomes and check for tradeoffs. The assistant critiques the logic; the team decides strategy and commitment.
Before you start
Metric tree
Obtain definitions, formulas and ownership for relevant metrics.
Initiative brief
Describe the proposed change, audience and intended outcome.
Evidence context
Collect prior experiments or observations relevant to the assumed mechanism.
Prepare the inputs
- hypothesis
- Required
intervention, audience and expected behavior change
Avoid outcome-only statements with no mechanism.
- metric_definitions
- Required
formula, denominator, period and owner
Check that metrics are operationally measurable.
- supporting_evidence
- Required
prior data and experiments
Separate correlation from causal evidence.
- constraints
- Required
guardrails, capacity and test limits
Do not invent an acceptable business tradeoff.
Implementation, step by step
Map the proposed change
- Identify the user behavior the initiative is expected to influence.
- Connect it to the metric tree through explicit intermediate steps.
Checkpoint: The mechanism is visible.
Challenge causal links
- Ask what must be true at each step and what evidence supports it.
- List alternative explanations and assumptions that could break the chain.
Checkpoint: The hypothesis has testable uncertainties.
Check metric quality
- Inspect denominators, lag, seasonality and possible gaming.
- Distinguish activity measures from outcomes the business actually values.
Checkpoint: Measurement risks are documented.
Design a bounded test
- Propose comparison, observation window and guardrail metrics appropriate to the initiative.
- Leave thresholds and resource commitments for owner agreement.
Checkpoint: The test can produce interpretable evidence.
Prepare the review
- Summarize the mechanism, evidence gaps, tradeoffs and decision options.
- Keep priority and commitment with the team.
Checkpoint: The initiative is ready for a reasoned discussion.
Decisions along the way
Metric is only a proxy
State the gap to the intended outcome and add a downstream check.
Positive movement harms a guardrail
Present the tradeoff rather than declaring success.
No credible measurement exists
Recommend a measurement or discovery step before scaling.
What you will produce
hypothesis-review.md
MarkdownA structured critique of the initiative.
Include: mechanism · metric_path · evidence · assumptions · tradeoffs
validation-plan.md
MarkdownA proposed test for owner approval.
Include: comparison · metrics · window · guardrails · decision_rule
Check the result
- Verify metric formulas and denominators.
- Trace each claimed causal link to evidence or an explicit assumption.
- Check guardrails cover plausible negative effects.
- Confirm success criteria are agreed before interpreting results.
When something goes wrong
Metric tree is outdated
Resolve definitions with owners before analysis.
Prior experiment differs materially
State the transfer limit instead of reusing its effect estimate.
Data cannot support the proposed comparison
Revise the test or label the result observational.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: review a plan to send more onboarding emails.
Inputs
The initiative predicts higher activation. Metric tree defines activation as completing a first project; email opens are only a leading indicator.
Expected result
Synthetic result: map email to user action to completed project, test activation alongside unsubscribes, and avoid calling a higher open rate proof of business success.
Run a small pilot
Start small
Review one initiative before a small experiment.
Record the baseline
Record assumptions discovered and measurement changes.
Agree success criteria
Agree critique usefulness and test interpretability before using the format broadly.
Stop or revise
Stop impact claims when the causal path or metric definition is unresolved.
Keep the scope clear
- The assistant supports strategic critique and cannot set company priorities.
- Plausible mechanisms and correlations are not proven effects.
Check before using
The assistant supports critique; it does not own strategy. Verify the metric definitions and avoid presenting plausible mechanisms as proven effects.
Business activities
- Review business performance
- Plan products and business changes
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Proposed hypothesis · Metric tree and business objectives · Relevant evidence and assumptions
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow