ChatDiagram
Essayer gratuitement
Strategy · Finance

Revenue decline hypothesis tree

A revenue decline hypothesis tree separates the main drivers of a commercial result into claims that can be checked. A team can distinguish acquisition, conversion, retention, price and reporting explanations rather than react to the total alone. Each branch should lead to a measurable comparison, such as cohorts, pipeline stages, discount records or the finance close. The tree is useful in a business review because it clarifies what is known, what is only assumed and who will validate each assumption.

Type Arbre de décisionNorme Howard-Raiffa / CART-sklearn / taxonomyMoteur schematex-decisiontreeMis à jour 24/09/2026
Revenue decline hypothesis tree
Drawing preview
La demande

“Create a revenue decline hypothesis tree that tests new-customer volume, conversion, customer churn, contraction, pricing, discounts, and reporting changes.”

Essayez ensuiteAdd a branch for currency effects.Change monthly revenue to gross margin.
Ce que contient ce dessin

Comprenez les décisions qui le sous-tendent.

01Validate reporting

Confirm that periods and source data are comparable.

02Test acquisition

Separate lead volume from conversion and sales capacity.

03Test retention

Segment cancellations and spend contraction.

04Test price

Compare realized price and discount changes.

Use when a revenue result needs structured diagnosis before a commercial response.

Voir tous les modèles de arbre de décision →

FAQ

Questions fréquentes

What are common revenue drivers?

Customer volume, conversion, retention, expansion, realized price and reporting treatment are common starting points.

Should I include actions in the tree?

Keep the tree focused on hypotheses and tests; select actions after evidence supports a cause.

Who should review it?

Sales, customer success, marketing and finance can each validate a different branch.