# When Capacity Is Fixed, Control Timing Instead ## Claim When you cannot add capacity to a system under load, you can still raise effective throughput by choosing when deferrable work happens rather than trying to make everything happen at once. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source**: [[3. Resources/Readwise/Articles/Game Time A Playbook to (Unsuccessfully) 10x in a Week and (Successfully) 10x in a Year|Game Time — a playbook to 10x]] > [!quote] > Throughput that our system could handle is a function of capacity and time. Two variables, and under a deadline usually only one is available. Capacity is bounded by budget, provisioning lead time, and whatever your dependencies will give you. Time is bounded by nothing except your willingness to decide that some work does not have to complete right now. The talk's companion finding shows why this is not obvious in practice: > [!quote] > Just because you've cached the HTML doesn't mean you've cached what happens after it loads. The work that saturated the system was work nobody had counted, because the primary path looked cached. Timing control only helps once you can see which work is genuinely deferrable — which requires knowing what actually executes, not what you believe you optimised. ## Scope & conditions - Holds where a meaningful share of work is deferrable without changing the user-visible outcome — analytics, indexing, notifications, derived data, most write-behind. - Fails where everything is genuinely synchronous to a user action, in which case the constraint is real and only capacity moves it. - The precondition is visibility: you cannot defer work you have not inventoried, and the uncached-secondary-request case is the standard blind spot. - Deferral has a cost — staleness, and a queue that must eventually drain. It buys peak headroom, not free throughput. ## Links - [[Product & Startup Instincts MOC]] — the lever still available under load when buying capacity is not an option - [[3. Resources/Permanent Notes/Weak Links Cap Aggregate Gains Even Under Widespread Automation]] — the general form: throughput is set by the constraint you did not move - [[3. Resources/Permanent Notes/A Serverless Function That Cannot Wait Must Hand the Job to a Callback]] — applies-in: the architectural expression of deferring work off the critical path - [[3. Resources/Permanent Notes/Tooling Cannot Be Faster Than the API It Polls]] — contrasts on where the ceiling sits when the constraint is external