Thirty days is enough to understand the current system, test one meaningful improvement, and establish a useful review rhythm. It is not enough to redesign everything, which is precisely why the boundary encourages focus. Capacity planning balances demand, available skills, flow, and uncertainty so commitments remain credible.
Week one: understand reality
Capacity looks healthier than it is when plans count nominal hours while ignoring interruptions, dependencies, variation, and work already in progress. Begin by observing the work as it happens and separating symptoms from the conditions that repeatedly create them.
Measure actual arrival and completion patterns before converting headcount into promised output. Speak with the people who perform the work, receive its output, and handle its exceptions so the current picture reflects reality rather than policy alone.
Weeks two and three: test a better way
Capture the emerging approach in a rolling capacity view linking demand scenarios, constraints, skills, queues, and decisions. The artifact should make the next decision easier, not become documentation maintained for its own sake.
Keep the first change small enough to reverse and specific enough to evaluate. Give one person clear ownership, make constraints explicit, and agree on when the team will inspect the result.
Week four: decide what to sustain
Use throughput, queue age, utilization range, service level, and blocked time to understand progress from more than one angle. A measure belongs in the review only when a meaningful change would prompt a question, decision, or action.
End each review by recording what the team learned, what it will change, and what remains uncertain. Durable improvement comes from repeating that loop with discipline rather than launching a larger program.
