Planning Growth Systems with clear bottleneck and cutoff rules

What rules stop growth experiments before they overload the system?

In addition to a goal, a growth system needs a current bottleneck hypothesis and observable signals of failure. Additional inflows are only expanded when delivery, quality, and profitability can withstand the increased workload.

Implementation case: "False bottleneck"

A campaign increases qualified inquiries, but at the same time, the waiting time for technical review increases. The experiment is not rolled out further until the bottleneck in the review process is resolved; otherwise, additional reach would only create a backlog.

Preliminary Decision

• Change in the identified bottleneck signal along with subsequent delivery and quality impact.

• Experiments that reach their predefined termination condition and yet continue running.

False Bottleneck

• False Bottleneck – More traffic is purchased even though qualification or delivery capacity limits the impact.

• Delayed Stop – Quality and support issues are only recognized as growth costs after widespread expansion.

• Activity Metric – Reach or registrations increase without resulting in a viable business outcome.

Operational Limit

1. The current value flow is tracked to the business result, and its most significant bottleneck is documented.

2. For a limited experiment, the impact signal, operational limit, and termination decision are defined before the start.

3. After evaluation, only the documented bottleneck effect is expanded; side effects remain part of the same decision.

Named Bottleneck

• Preliminary Decision – Expansion, adjustment, and cessation are tied to defined findings rather than retrospective interpretation.

How "Planning Growth with Bottleneck and Cessation Rules" relates to related decisions

Separating Internal Operational Logic from Customer Presentation Expands on the "Identified Bottleneck" checkpoint. The guiding question is: Which information belongs in operations and which in customer presentation?

A complementary perspective is offered Evaluating Conversion Optimization with Business Results Instead of Click-Through RateAnswers the question: "How do you evaluate conversion optimization based on business results instead of click-through rate?"

If you want to put "Planning Growth with Bottleneck and Cut-off Rules" into practice, you can refer to Robust Website Systems This document focuses on "Price Logic and Growth Limits" and "Named Bottleneck."

Conclusion: Planning Growth with Bottleneck and Cut-off Rules

Growth is a change in the entire system, not just its inflow. Bottleneck and cut-off rules protect operations and results from uncontrolled expansion.

Sources and Further Information

The classification of "Planning Growth with Bottleneck and Cut-off Rules" is based on the following official documentation and standards.

• Example Error Budget Policy — Google SRE WorkbookThe template rule combines measurable reliability goals with pre-agreed consequences when a budget is exhausted.

• Reliable Product Launches at Scale — Google SREThis chapter structures launch readiness through capacity, dependencies, observability, rollback, and clearly assigned responsibilities.

• Handling Overload — Google SREGoogle SRE describes capacity limits, controlled rejection, and load limiting to prevent overload from unpredictably destabilizing the entire system.