Why busy teams don't always deliver more

A team spends its day completing tasks, yet the final deadline keeps slipping. The first response may be to demand more speed or hire more people. Before doing that, follow a deliverable through the process.

Total time includes execution and waiting. A task can finish at one stage and spend days awaiting information for the next. Another may be returned repeatedly because completion criteria change during the work.

How busy each person is does not, on its own, explain what limits the result. Observe how tasks move through the process and where they stop advancing.

Choose a deliverable and follow its path

Imagine a fictional agency where communication materials take too long to be published. The creative team finishes drafts quickly. They then wait for review by someone who also works in sales and customer support.

To understand the delay, record when the task arrived, when it was worked on and when it could move forward. Separate working time from idle time. Note the reason for waiting instead of recording only that a delay occurred.

Track several different cases. Urgent work may follow an exceptional route; simple work may hide problems that appear only on larger tasks. Compare where waits recur and which conditions differ between cases.

Record returns too. A task sent back for revision consumes capacity at a stage it has already passed. Without that record, the process may look faster than it is.

Look for the constraint under current conditions

In the example, increasing creative output could make the review queue grow. More work would be finished locally, with little change in the amount published.

The reviewer may be an important constraint, but the team still needs to understand why. Does only that person have the necessary information? Are the criteria unclear? Could approval be distributed or removed? A queue reveals a difficult passage without automatically explaining its cause.

Several constraints may exist, and they can vary by task. Naming a single bottleneck too early narrows the investigation. Look for an intervention that improves the observed flow within a defined context.

Examine work that comes back

If review returns many drafts, reducing the approval queue may be insufficient. The team needs to know what is missing before production begins.

Unclear requests, scattered information and conflicting criteria can create rework. Compare a task that advanced with one that came back. Which condition existed in the first? Which information arrived late in the second?

An initial meeting can help if it resolves a real uncertainty. Adding a meeting to every task also takes time and can create another wait. Assess the intervention by the specific problem it should prevent.

Pay attention to work in progress

Starting something new while another task waits for a response can seem efficient. With many tasks open, the team also has to track outstanding items, recover context and rearrange priorities.

A limit on work in progress may be worth testing. Reducing new arrivals can focus effort on finishing existing work and make obstacles more visible.

The limit must account for urgency and the nature of the work. If a task awaits a slow external response, advancing another may be reasonable. Recognize the choice and track how many parallel tasks the team can sustain.

Measure something that represents delivery

Counting materials produced by the creative team helps observe that stage. To assess the whole process, track what was published and how long it took, alongside the required quality.

A single measure can redirect effort. Rewarding only volume may produce more items that need reworking. Rewarding only speed may encourage incomplete delivery.

Choose observations that help explain flow: the age of open tasks, reasons for returns and time from request to completion, for example. They answer different questions and need interpretation in context.

Test a small change

The fictional agency could reserve regular review time or establish criteria that allow some materials to be approved without one person's involvement. The investigation determines which option to test.

Agree on a period and monitor the effects. Did the queue shrink? Did more drafts come back? Did the problem move to another stage? A local improvement may create a cost elsewhere.

Use the problem investigation worksheet to record a real path. Choose a delayed deliverable, reconstruct its waits and compare it with one that advanced. That comparison gives you a more concrete basis for changing the process than asking everyone to work faster.