Your people are at capacity, but nobody can say what capacity actually is. Work gets assigned on the assumption that there is always room for one more thing, and the plates are invisible.
New requests land on already-full plates. Everything is in progress and little is finished, because starting is easy and finishing competes with the next new start. "We are slammed" is said constantly and measured never, so it cannot be planned around, only endured. This guide makes capacity visible, shows current load against it so overload becomes a fact rather than a feeling, limits how much work is in flight at once, and disciplines what gets taken on. The result is an organization that commits to what it can actually deliver and finishes more by starting less.
Plan two to three hours for the initial baseline and load inventory, then short recurring reviews. Bring the people whose capacity is in question, because capacity assessed without them tends to be optimistic. You do not need a time-tracking system. You need an honest accounting.
If you do not yet know what matters most, fix that first in Priority Clarity and Alignment. Managing capacity without clear priorities just produces a cleaner list of things you still cannot finish. If overload is really caused by an inefficient process, that is operational efficiency. If it has already become burnout, address that in culture and team health alongside this work.
You cannot manage a number you have never named. For each person or team, build a realistic working capacity, not a theoretical maximum. Start from available hours, then subtract the unavoidable: meetings, administrative overhead, interruptions, and a buffer for the unplanned work that always arrives. What remains is true capacity for committed work, which is usually far less than the headline number. Express it in whatever unit fits how you assign work, hours, days, or number of concurrent significant efforts.
Open the Capacity and Load Map →Plot everything currently in flight against the baseline so the gap becomes visible. Inventory every active commitment, initiative, recurring obligation, and significant task, and place it against the capacity it consumes for each person or team. Then read the result honestly. Where committed load exceeds baseline capacity, you have quantified overload, and you can see exactly where and by how much. This view almost always reveals two things: total load well above total capacity, and a few individuals carrying far more than their share. Both are now visible instead of assumed.
Continue in the Capacity and Load Map →Install the core capacity discipline: limit how much work is in progress at once. This is the single highest-leverage move in the guide. The reason little gets finished is that too much is started; capping work-in-progress forces the organization to finish before it begins, which raises throughput even though it feels counterintuitive. Set explicit limits on how many significant efforts a person or team can have in flight, sized to the baseline. The rule that makes it work is "stop starting, start finishing." Then move the excess out of "in progress" into a clearly parked backlog. Parked is not dropped; it is explicitly not-now. The discomfort of parking work is the discipline doing its job.
Open the Work-in-Progress Limit Worksheet →Limits on work in flight only hold if there is a gate on what is allowed to start. Define a standard filter every significant new request passes before it is accepted: does it clear the priority bar, is there capacity available or must something be parked to make room, and who owns it given current load. Each request resolves to one of four outcomes: accept now, accept by parking something explicitly named, defer to a stated point, or decline. The key shift is that "yes" now has a visible cost, traded against something else and stated openly rather than absorbed silently. Equip people with respectful language for defer and decline, because the discipline fails if saying no feels impossible.
Open the Commitment Filter →Capacity drifts: parked work resurfaces, limits get quietly violated under pressure, and load climbs back. Set a recurring review, commonly weekly for fast-moving teams or aligned to your operating cycle. At each review, refresh the load map, check whether the limits are holding, pull parked work into flight only as capacity genuinely frees, and re-tune limits if the baseline has changed. Watch for the warning signs that discipline is eroding, limits exceeded "just this once," parked work creeping back unannounced, or the filter being bypassed for urgent requests. Name the erosion early, because it compounds.
Confirm limits each cycle with the WIP Limit Worksheet →You can state your team's real capacity, and current load against it, as numbers rather than feelings. Work-in-progress is capped, the excess is parked in a named backlog, and new commitments are priced against capacity before they are accepted (Systems: Level 2 to 3, Measurement: Level 2 to 3).
With capacity under control, the next constraint is usually carrying the in-flight work to done. Move to Execution Cadence and Initiative Completion, or if meetings are eating the reclaimed capacity, tackle those first. Execution Cadence and Initiative Completion →