A firm can look busy and still have unused capacity. Work may be waiting for a decision, a complete intake, or a file that lives in another system. At the same time, the people doing the work may be absorbing the delay through late nights. Capacity planning helps leaders see the difference between demand and friction.
Why does this matter?
Woven Legal's burnout article describes burnout as something that creeps in through long hours, missed lunches, and silent resignation. That is a useful operational warning. A capacity view should include the human signals that numbers miss. If the only measure is hours worked, the firm can reward the conditions that make work less reliable.
What should you review first?
List the recurring work for the next planning period. Group it by matter stage, owner, and approximate effort. The first list can be rough. Its purpose is to show what arrives repeatedly and what arrives as a surprise.
Mark the waiting points. A task that takes twenty minutes but waits three days is a capacity problem for the client and the team. Track the reason for the wait: missing information, review queue, unclear priority, or a dependency outside the firm.
How do you put the idea into practice?
Review workload with the people doing it. Ask which tasks are draining because they repeat, interrupt, or require too much context switching. Treat those observations as operational evidence. A calendar can show occupied time, but not the cost of starting over.
Choose one capacity change. It might be a new priority rule, a protected review window, a better intake field, or a defined support assignment. Check the effect after a short period. If the change shifts work elsewhere, adjust the plan rather than declaring success.
Which questions should the team ask?
- What work repeats and what work is truly new?
- Where does work wait for a decision?
- Which interruptions create rework?
- What would make next week feel more predictable?
What does a simple working model look like?
Swipe or scroll to see all columns →
| Review | Useful question | Evidence to keep |
|---|---|---|
| Demand | What is arriving? | Work categories and volume |
| Attention | Who can move the work? | Available owner time |
| Waiting | Why is work paused? | Reason and age of queue |
| Health | What is the team experiencing? | Short check in and trend |
Where can outside support fit?
Woven Legal's home page frames its support around increasing capacity and reducing payroll pressure, while its process page describes an operations team that helps firms use technology and lean methods. Whether support is internal or external, the useful question is what recurring work can move with a defined owner. Capacity improves when the system creates fewer avoidable waits.
What should happen next?
A capacity plan should help people make a good decision before the work becomes an emergency. Keep it simple, review it with the team, and use it to choose one change. The point is steadier work, not a new dashboard.
A small change is easier to judge than a broad promise. Write down the starting condition, give one person ownership, and set a review date. Keep the record close to the work. When the team sees a clearer path, repeat the pattern in the next place where work waits. This is how an operating system grows: through small decisions that remain visible after the meeting ends.
A small change is easier to judge than a broad promise. Write down the starting condition, give one person ownership, and set a review date. Keep the record close to the work. When the team sees a clearer path, repeat the pattern in the next place where work waits. This is how an operating system grows: through small decisions that remain visible after the meeting ends.
A small change is easier to judge than a broad promise. Write down the starting condition, give one person ownership, and set a review date. Keep the record close to the work. When the team sees a clearer path, repeat the pattern in the next place where work waits. This is how an operating system grows: through small decisions that remain visible after the meeting ends.
A small change is easier to judge than a broad promise. Write down the starting condition, give one person ownership, and set a review date. Keep the record close to the work. When the team sees a clearer path, repeat the pattern in the next place where work waits. This is how an operating system grows: through small decisions that remain visible after the meeting ends.
A small change is easier to judge than a broad promise. Write down the starting condition, give one person ownership, and set a review date. Keep the record close to the work. When the team sees a clearer path, repeat the pattern in the next place where work waits. This is how an operating system grows: through small decisions that remain visible after the meeting ends.
A small change is easier to judge than a broad promise. Write down the starting condition, give one person ownership, and set a review date. Keep the record close to the work. When the team sees a clearer path, repeat the pattern in the next place where work waits. This is how an operating system grows: through small decisions that remain visible after the meeting ends.
Questions, answered.
What is the first step in plan law firm capacity without turning burnout into a metric?
Capacity planning starts with a clear view of recurring work, available attention, and the delays that make a team feel overloaded. Track a small set of signals, review them with the people doing the work, and change scope or ownership before adding more hours. Capacity is a system question, not a stamina contest.
How can a firm keep the change practical?
Start with one recurring process, name an owner, and set a review date. Use evidence from the people doing the work before expanding the change.