Too many tasks in progress? Pause work without losing the commitment

When several tasks are already underway, “do fewer things at once” leaves an awkward question: what happens to the work you stop doing?

Moving a card out of Doing can make the board look calmer without changing what someone expects from you. The unfinished report still has a deadline. The colleague waiting for your feedback still needs an answer.

Start by separating what you are working on now from what you have already promised. Then make any pause explicit: what stops, what remains owed, what triggers a review, and whose agreement is needed.

This guide walks through that change using one fictional work list. It is an editorial planning example, not a tested productivity intervention or an instruction to ignore assigned work.

A smaller Doing column does not erase unfinished work

Personal Kanban has two familiar principles: make work visible and limit work in progress. Smartsheet’s personal Kanban guide explains that foundation and ways to adapt a board.

There is an important counting distinction. PMI’s discussion of work in process treats started, unfinished work as WIP, including blocked work. Its discussion also cautions against treating numeric limits as the only solution.

For your own list, you can show both:

• Working now: the action currently receiving your attention.
• Started but unfinished: everything you have begun and still owe, including paused or blocked items.

Those are descriptions, not competing definitions of completion. Moving an item to Waiting can free attention for another action. It does not mean the unfinished obligation disappeared or that you reduced formal WIP.

If your team already has a defined workflow and counting policy, follow it. The personal record below helps you see commitments; it does not replace the shared system.

First, distinguish a promise from an option

A possible improvement you have not agreed to deliver can stay on a later list. An accepted task with a deadline is different, even if you have not started it.

Before pausing something, check:

1. What outcome did I agree to deliver, and to whom?
2. What is the real deadline, if there is one?
3. Have I started, or is it still an accepted request awaiting a start?
4. Is the next action available, blocked, or awaiting a decision?
5. Would stopping change someone else’s expected delivery?

You do not need a new app or five permanent columns. These distinctions can live in the notes on an existing task.

A worked example: three started tasks and a new request

Suppose it is Wednesday morning. The following details are fictional. The order illustrates decisions; it is not a recommended task count or an optimized schedule.

You decide to work on the report now. The landing-page revision is an unfinished commitment, even while it is not receiving attention. The budget note is blocked, with a real delivery obligation. The dashboard idea is an option.

That means one action is receiving attention and three started commitments remain unfinished. Calling only one of them “active” must not hide the other two.

Now your manager asks you to prepare a briefing for Thursday morning. You check the remaining work and believe the report and briefing will compete for the same available time.

The request cannot be resolved just by adding another card or moving the report into a quieter column. It needs a delivery decision.

Decide what can actually pause

Bring the conflict to the person who can authorize a change. For example:

I have the monthly report due Thursday at noon, with its final checks and sending still to do. The new briefing needs the same work window. Could we move the report to Friday morning, reduce the briefing’s scope, or find another owner for one of them? Until we agree a change, I’m treating the report’s deadline as unchanged.

This is an example to adapt, not a script that guarantees agreement. If different people own the two deadlines, involve whoever can reconcile those expectations. Your manager’s new request may not by itself change an agreement with someone outside their authority.

For this example, suppose the report recipient agrees to Friday morning and the manager confirms the briefing comes first. You can now pause the report with an agreed delivery change.

The landing-page revision still needs a feasibility check against Friday’s work. Moving one deadline can create a second collision. If it does, raise it before treating the new plan as settled.

Record the pause so you can inspect and reverse it

A useful pause record preserves the obligation and the place where work stopped.

There are now four started items if you begin the briefing: it plus the three earlier unfinished commitments. The pause made a trade-off visible; it did not magically lower that inventory.

For the report, keep the draft link and a brief restart note: “Final checks and sending remain; confirm no newer data arrived.” When you return, inspect the actual draft and sources before following an old instruction. The restart example goes into that check.

When the blocked work becomes available again

Suppose the approved figures arrive on Thursday. Do not automatically start the budget note while the briefing or report still needs attention.

First confirm that the figures answer the request. Then reconsider when the note needs to resume to meet Monday’s deadline. Arrival of an input makes an action available; it does not establish that it is now the highest priority.

Keep the input’s promised date, your follow-up point and your own delivery deadline distinct. The blocked-task example shows those dates separately.

If an interruption leaves the delivery at risk, reopen the agreement. Do not silently replace a deadline with the day you next hope to work on the task.

What if nobody agrees to a pause?

Keep both commitments and the conflict visible. State what competes for the same time, what remains unfinished and which decision is still needed.

Ask for a decision about scope, timing or ownership through the appropriate workplace route. If a decision is deferred, record who will revisit it and when. Do not record a requested deadline change as approved.

A task list cannot create authority or capacity. This example concerns ordinary professional planning; established incident-response, safety or on-call procedures take precedence where they apply.

Review unfinished promises before starting more

Before you pull another task into your day, inspect:

• work you paused and the condition for resuming it;
• blocked items whose inputs may have arrived;
• accepted work approaching its latest realistic start;
• any delivery change that is still only a request;
• tasks that are truly complete and can leave the unfinished inventory.

Use the work to-do list template if you need a simple record. You can apply these distinctions inside your current task system; no special pause feature or automatic decision-maker is required.

The useful outcome is a record you can explain: what you are doing now, what remains owed, and what has actually been agreed to change.