When Too Many Tasks Stop the Work: Clarity, Scope, and the Question of What Transfers FA

A practice-based inquiry into overloaded attention, discussable priorities, complete slices of work, and learning across contexts

About this essay

This essay begins with my own experience, extends to an observation I encountered in three different companies, and describes an exploratory practitioner inquiry conducted in only one of those companies. To protect confidentiality, I have not included company names, exact employee counts, verbatim conversations, precise numerical results, or identifying workflow examples. The purchasing example is deliberately constructed; it is not the story of a particular employee.

The intervention was not a controlled study. There was no comparison group, random assignment, validated outcome measure, independent evaluator, or formal test of long-term transfer. I was simultaneously a consultant, conversation partner, intervention designer, and observer. The account can therefore generate hypotheses and make practice more discussable, but it cannot establish causality or support broad generalization. Published research helps me interpret what I observed; it does not retrospectively turn the work into an academic experiment.

There are days when the problem is not a lack of time, ability, or willingness.

The problem is that too many unfinished demands are present at once.

I first noticed this in myself. I could have a programming task, an organizational task, an executive responsibility, and several smaller commitments waiting in different parts of my life. In principle, I had enough time to complete several of them. In practice, seeing all of them together sometimes produced the opposite of action. I felt late before I had begun. Instead of selecting one task and moving, I remained mentally surrounded by the whole field.

Later, while working with organizations, I heard versions of the same experience from other people. The details differed, but the pattern was familiar: work kept arriving, priorities remained partly implicit, several processes stayed unfinished, and the person carrying them began to experience the workload not as a sequence of choices but as one undifferentiated burden.

That observation led me through a path that has become characteristic of how I work: notice a pattern, resist explaining it too quickly, speak with people close to the experience, read what research can and cannot clarify, design a small change in the environment, and return to the people involved to ask what happened.

The intervention produced encouraging observations. More importantly, it left me with a harder question:

Did people acquire a durable way of working, or did a supportive environment temporarily make better action possible?

Table of contents
  1. The problem first appeared in my own work
  2. From one personal pattern to observations in three companies
  3. I began with one-on-one conversations, not a solution
  4. Intervention one: make priority a two-way conversation
  5. Intervention two: finish a complete vertical scope
  6. Completion felt different—but I will not explain it with an unmeasured brain claim
  7. What seemed to change after the interventions
  8. Awareness was not an abstract idea; it was built into the work
  9. The context was teaching too
  10. What a team can try without pretending this is a universal formula
    1. 1. Make every new priority displace or reorder something
    2. 2. Give both sides responsibility for the conversation
    3. 3. Define a scope by a usable end state
    4. 4. Keep the ordinary scope within one working day
    5. 5. Review both flow and experience
    6. 6. Track what happens after the scaffold is reduced
  11. The most important result was the next question
  12. References

The problem first appeared in my own work

The word overload can be misleading. It suggests that the total volume of work is simply greater than the available capacity. Sometimes that is exactly the problem, and no productivity method can repair an unreasonable workload.

But my experience contained another possibility. On some days, the amount of work was substantial but still manageable. The paralysis came from multiplicity: different kinds of work, several open loops, uncertain ordering, and the feeling that choosing one task meant neglecting all the others.

This distinction matters because the remedies are different.

If the demand truly exceeds capacity, the organization must reduce, redistribute, delay, or resource the work. If the capacity exists but attention is fragmented by unfinished and ambiguously ordered commitments, then visibility, sequencing, and completion may release some of that capacity. Often both problems coexist, so a responsible intervention must not use “better prioritization” to hide chronic understaffing.

Research on task switching gave me one useful language for part of the experience. Sophie Leroy describes attention residue: after moving away from an unfinished task, part of one’s attention can remain attached to it, reducing performance on the next task. Experimental work on task switching has also documented switching costs under controlled conditions. These studies do not prove that every overwhelmed employee is experiencing the same mechanism, but they challenge the idea that multiple open tasks are cognitively free simply because they are written in a task manager.

Still, the most important evidence for my inquiry did not begin in a journal. It began when I recognized the same pattern in conversations at work.

From one personal pattern to observations in three companies

Across three different companies, I noticed employees becoming stuck in the presence of accumulated work. Sometimes a manager had assigned several tasks without explicitly revisiting what was already in progress. At other times, the accumulation had been produced by the person’s own workflow: several activities had been started, but the final steps required to close them had been deferred.

The result was not always visible as inactivity. People could remain busy all day while completion steadily moved further away. A process might advance in one place, pause before documentation, continue elsewhere, wait for accounting, and return later as an urgent loose end. Each piece appeared small. Together they created a landscape in which no one could easily answer:

  • What am I actually committed to now?
  • Which work should move first?
  • What is finished rather than merely started?
  • What must stop if something new becomes urgent?

I observed this broad issue in three companies. The closer inquiry described below, however, occurred in only one. That boundary is important. Similarity across settings made the question worth following; it did not make the settings equivalent, and it did not justify presenting one intervention as a result replicated three times.

I began with one-on-one conversations, not a solution

In the company where I had sufficient access to investigate further, I arranged one-on-one conversations with employees. I did not begin by announcing a theory about task overload. I asked more indirectly about their work, how their days were unfolding, where they felt progress, where they felt stuck, and how work was affecting the rest of life.

A recurring pattern became clearer. People described work arriving faster than it became organized. They did not always know how a new request related to existing commitments. Some felt unable to tell a manager, “I cannot do all of this now.” The difficulty was not only operational. It was relational and interpretive:

  • Would saying I cannot reach this task make me look incapable?
  • Is asking about priority a form of resistance?
  • Does accepting a new task mean promising to complete it immediately?
  • Is the manager aware of everything already on my list?

This was a critical discovery. A priority problem was being carried as a private emotional problem. The employee was expected to resolve competing organizational demands alone, while also managing the fear of how limitation might be interpreted.

The intervention therefore could not be only a better list. It needed to change the language available between people.

Intervention one: make priority a two-way conversation

We introduced a simple two-sided practice.

When a manager assigned a new task, the employee was expected to make existing commitments visible. The response could sound like this:

I am currently working on A, B, and C, in that order. Where should this new task sit? Should it replace one of them, or should I begin it after them?

The manager carried a parallel responsibility. Before assuming that the task could simply be added, the manager was expected to ask:

What else is currently in progress? Do we need to review the priorities together before you take this on?

The symmetry mattered. If only employees were responsible for raising the issue, hierarchy, habit, embarrassment, or simple forgetfulness could keep the conversation from happening. If only managers were responsible, an incomplete picture could remain hidden. Each side became a guardrail for the other.

This was not permission to refuse all new work, and it did not remove managerial authority. It changed an unspoken collision into a visible decision. A genuinely urgent task could move upward, but something else would move downward, pause, be reassigned, or receive a new deadline. The organization could finally see the trade-off it was already making.

The practice also gave employees a way to speak without framing the conversation as a personal failure. They did not have to say, “No, I cannot cope.” They could say, “Here is the current order of commitments; let us decide where this belongs.”

Research on psychological safety is relevant here, but I use it cautiously. Amy Edmondson’s work connects a shared sense of interpersonal safety with learning behavior in teams. I did not measure psychological safety, and the company did not suddenly become free of power differences. What the protocol did was narrower: it made one potentially risky conversation legitimate, expected, and mutual. Sometimes changing the accepted sentence is one way of changing what can happen in the relationship.

Intervention two: finish a complete vertical scope

The second problem was not only how work was prioritized. It was how work was divided.

People often grouped similar beginnings together and postponed the less visible steps required for completion. To explain the alternative, I used the image of cutting a layered cake vertically. A proper slice contains something from every layer, from the top to the base. In the same way, a work scope should move through all necessary stages until it produces a usable, closed result.

Consider a deliberately fictional purchasing example. A purchasing employee needs to obtain ten different items. One approach is to place all ten orders first. When the deliveries begin to arrive, ten sets of follow-up work appear: checking the goods, recording inventory, registering invoices, informing accounting, resolving discrepancies, confirming receipt, and closing documentation. The person may stay active while the unfinished tail grows behind every order.

A vertical-scope approach asks for a different sequence:

  1. choose one item;
  2. order it;
  3. follow it through arrival and verification;
  4. complete inventory, invoice, accounting, communication, and documentation steps;
  5. close the scope;
  6. then begin the next item.

Real work is not always this linear. Dependencies, batching economies, supplier constraints, and role specialization can make another design more efficient. The example is not a universal rule for purchasing. Its purpose is to make one principle visible:

Do not define progress only by how much work has been opened. Define a scope by what can be completed and delivered end to end.

We added a practical size constraint. A normal scope should be small enough to complete within one working day—roughly eight hours. If it could not be completed in that time, the person should usually divide it further. A two-day scope could be acceptable when the work genuinely required it; a three-day scope was an exception for unusual dependencies, not the default unit of planning.

The purpose of the limit was not surveillance or extracting more output from every hour. It was to make “done” frequent enough to remain visible. A person with ten complete scopes could say, “Three are finished; seven remain.” That is different from having ten partially advanced processes and no reliable account of what is actually complete.

Completion felt different—but I will not explain it with an unmeasured brain claim

During my early reflection on the intervention, it was tempting to say that completing a scope gave people a “dopamine hit.” That phrase is common in productivity discussions, but it would be more specific than my evidence permits. I did not measure neurochemistry, and a satisfying explanation should not become more scientific-sounding than the observation itself.

What I could observe and hear was simpler. Completion gave people visible evidence of progress. At the end of a day, they could identify something that had moved from open to closed. Work no longer appeared only as a growing remainder. Research by Teresa Amabile and Steven Kramer on everyday work experience similarly emphasizes the motivational importance of progress in meaningful work. Their findings offer a plausible lens; they do not prove the mechanism operating in this company.

This distinction is part of the inquiry itself. I want to follow experience far enough to learn from it, but not so far that a compelling story outruns the evidence.

What seemed to change after the interventions

After roughly a month, I returned to one-on-one conversations with the same group of employees. I am deliberately not publishing exact counts, individual statements, or numerical performance claims. What follows is a pattern-level account of what I observed and what participants reported.

The atmosphere of the conversations had changed. People described greater clarity about what they were doing and what would come next. Work appeared to be moving with less accumulation. Some employees were completing more than we had expected, while also reporting a better sense of control and less of the feeling that the day had ended with nothing finished.

The priority protocol reduced one kind of pressure: the private burden of accepting every request as though all requests had the same deadline. The scope practice reduced another: the burden of carrying many nearly finished processes whose remaining steps were difficult to see.

The two interventions reinforced each other:

  • priority dialogue clarified which commitment should move;
  • vertical scope clarified what completing that commitment meant;
  • short scopes made progress visible;
  • follow-up conversations helped people notice their own working patterns.

But several alternative explanations remain. The improvement may partly reflect increased managerial attention, the novelty of the intervention, clearer expectations, my presence as a consultant, social desirability in the interviews, a temporary change in workload, or other organizational changes I did not isolate. I also did not systematically record negative cases: people for whom the practice was less useful, difficult to sustain, or experienced as additional control.

The responsible conclusion is therefore not “this method makes employees productive.” It is narrower:

In this setting, making priorities discussable and work completable was followed by encouraging changes in clarity, reported experience, and observed completion. The pattern deserves better measurement and longer follow-up.

Awareness was not an abstract idea; it was built into the work

In an earlier practitioner reflection, Can Awareness Open Space for Change?, I explored whether seeing a recurring pattern—without immediately being judged or told how to fix it—can create room for different action.

This organizational experience gave that question a more operational form.

People did not become aware through a lecture about self-management. The environment repeatedly placed certain realities in view:

  • the tasks already in progress;
  • the ordering of those tasks;
  • the trade-off created by a new request;
  • the boundary of a complete scope;
  • the difference between started and finished;
  • the pattern of how each person responded when work accumulated.

Reflection research suggests that deliberately articulating experience can improve learning beyond simply accumulating more experience. Again, this does not validate my intervention retrospectively. It helps explain why the one-on-one conversations mattered: action created experience, but conversation helped turn experience into something people could examine and name.

My working interpretation became:

Visibility did not automatically solve the work. It made the work—and the person’s relationship to it—available for choice.

That is close to what I mean by awareness in practice. It is not merely knowing that prioritization is useful. It is being able to see, in a real moment, what is already committed, what is being added, what will be displaced, and what pattern one is about to repeat.

The context was teaching too

At first, I could have described the outcome as employees learning two skills: how to negotiate priorities and how to divide work into scopes. But that description locates the change almost entirely inside the individual.

The company had also changed the conditions around the individual.

It had created a context in which asking about priorities was no longer treated as avoidance. Managers were expected to participate in the conversation. Work was represented in complete slices. “Done” became more visible. One-on-one reflection provided a place to examine the experience. In other words, people were not only learning a technique; they were working inside a temporary social and operational structure that made the technique easier to perform.

This is where the successful intervention became a research question.

Suppose one of those employees moves to another team or company. The new manager assigns tasks without discussing existing commitments. Asking for priority is interpreted as resistance. Work is organized around batches of beginnings rather than end-to-end completion. Colleagues reward visible busyness more than closure. What happens then?

Several possibilities are plausible:

  • the person may preserve the whole practice and help reshape the new environment;
  • preserve the underlying principle but adapt its language;
  • continue scoping personal work while abandoning the priority conversation;
  • recognize the old overload pattern but feel unable to act differently;
  • use the practice only when conditions become supportive again;
  • or gradually return to the dominant habits of the new workplace.

Research on transfer has long distinguished between acquiring something in one setting and maintaining or generalizing it elsewhere. Work-environment factors are part of that problem, not background noise. Research on far transfer also cautions against asking whether “transfer” happens as though it were one uniform event; what changes in domain, physical setting, social setting, time, and function all matter.

This concrete experience is one path that led me toward the broader question developed in What Remains When the Learning Space Disappears?:

When a supportive learning or working context changes, what capacities persist, what practices adapt, what behaviors become too costly to perform, and what can later be reactivated?

The question matters because a temporary improvement is not worthless. A supportive context may reveal a real human capacity. But we should not mistake performance carried by the environment for a fully portable transformation inside the person.

What a team can try without pretending this is a universal formula

The intervention can be translated into a small set of experiments. They should be tested with attention to workload, power, role design, and unintended effects.

1. Make every new priority displace or reorder something

Do not allow “urgent” work to accumulate outside the existing plan. Ask what moves down, pauses, changes owner, or receives a new deadline.

2. Give both sides responsibility for the conversation

Employees should surface current commitments. Managers should actively ask about them. A protocol that depends only on the less powerful person speaking up is fragile.

3. Define a scope by a usable end state

Write what will be true when the scope is complete. Include the final documentation, communication, verification, and handoff required for closure—not only the most visible production step.

4. Keep the ordinary scope within one working day

Split larger work until completion can occur frequently enough to be seen. Keep exceptions explicit rather than allowing every large task to become an indefinite open loop.

5. Review both flow and experience

Ask not only, “How many tasks were completed?” Also ask, “Where did work accumulate? Which conversations felt risky? What did people notice about their own patterns? Did the process increase clarity or merely create another form of monitoring?”

6. Track what happens after the scaffold is reduced

A practice has not necessarily transferred because it works while the consultant, manager, template, or meeting is present. Remove or change supports gradually and observe what people retain, adapt, or stop using.

The most important result was the next question

I began with a personal experience of stopping in front of too many tasks. I then noticed a related pattern in three companies. In one company, I moved closer: I held one-on-one conversations, read the problem through relevant research, designed two small changes, and returned to the conversations after people had lived with them.

The intervention suggested that task overload is not always only a matter of quantity. It can also be a matter of invisible trade-offs, socially risky conversations, fragmented completion, and a lack of structures that help people see where they are.

Yet the experience also prevented an easy ending. The better the environment worked, the more important it became to ask what the environment was carrying.

That is why I do not see the unresolved question as a weakness in the story. It is the most valuable outcome of the inquiry:

If clarity, completion, and reflective practice help people work differently inside one context, what must happen for those capacities to survive, adapt, or become active again in another?

I do not yet have a final answer. I have a more precise question, a practice-based origin for it, and a stronger reason to keep following it.

References