Hypothesis, Beta, Outcome Review
Review customer-facing work through its hypothesis, beta artifact, and outcome.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 99%
Structure review around three elements: the hypothesis being tested, a beta customer-facing artifact, and the intended outcome. Reforge broadened a product-review ritual to the entire company so functions such as marketing could expose real work to relevant cross-functional reviewers. Requiring an artifact prevents the session from becoming an abstract strategy debate, while the hypothesis and outcome establish the logic against which feedback should be evaluated. The owner remains responsible for the work and may accept, reject, or adapt comments; reviewers supply evidence and perspective rather than taking control. Repeating the ritual also teaches teams to present unfinished work and receive feedback constructively.
Origin
Brian Balfour described HBO as a Reforge-wide extension of its product review process on Marketing Against The Grain.
Core principles
- 01Feedback improves when reviewers can inspect a real customer-facing artifact.
- 02Every artifact should express a hypothesis and intended outcome.
- 03Cross-functional review can improve work without transferring ownership.
- 04Regular rituals surface work early enough to influence it.
How to run it
- 1
Form the hypothesis
State the customer problem, expected mechanism, and belief the project is testing.
Pro tip Make the hypothesis specific enough that reviewers can challenge it.
Watch out A vague ambition cannot anchor useful feedback.
- 2
Produce the beta
Create a customer-facing artifact that makes the proposed solution inspectable.
Pro tip Bring the smallest realistic artifact that exposes the important choices.
Watch out Do not substitute slides about future work for the work itself.
- 3
Define the outcome
Specify the change, learning, metric, or customer response the beta is intended to produce.
Pro tip Use an observable artifact outcome when direct measurement is inappropriate.
Watch out Do not evaluate the beta without agreeing on what success means.
- 4
Run the review
Invite the people relevant to the cross-functional initiative and collect focused feedback.
Pro tip Anchor comments to the hypothesis, artifact, customer, and outcome.
Watch out Avoid turning the session into unrestricted preference sharing.
- 5
Preserve ownership
Let the owner decide how to synthesize and apply feedback except in rare override situations.
Pro tip Record decisions and the reasoning behind rejected feedback.
Watch out Consensus ownership can leave nobody accountable for the final artifact.
In the wild
A marketer presents the hypothesis that buyers distrust generic automation claims, a beta landing page centered on transparent proof, and the desired outcome of more qualified demo requests. Product, sales, and operations leaders review the actual page while the marketer retains final ownership.
→ Feedback addresses customer-facing choices and expected value rather than abstract opinions.
Common mistakes
Reviewing plans without artifacts
Abstract discussion lets reviewers imagine different outputs and produces incompatible feedback.
Confusing feedback with authority
When every reviewer can dictate changes, ownership and coherence disappear.
Is it for you?
Best for
Cross-functional teams producing customer-facing product, marketing, or service artifacts.
Not ideal for
Confidential personnel matters or purely internal infrastructure with no meaningful customer-facing artifact.
From the transcript
“We call it HBO, standing for hypothesis beta outcome.”
“you can only bring customer-facing assets to that meeting to get feedback on those things.”
“the owner is the owner of that. This is a feedback session.”
From the episode
Brian Balfour Reveals How To Build An A+ Marketing Team From Scratch (#183)
Brian Balfour