Why highly engaged employees stop trying

The most engaged employee stops rescuing the deadline

For several weeks, Thomas fills in the missing sections of a shared report. His coworkers know they can rely on him, and the manager praises the team for meeting its deadlines. Eventually, Thomas leaves the document unfinished and says, “This time, I’m not going to be the sucker.” From the outside, this looks like a sudden loss of motivation. In his own account, it is an attempt to restore balance. The example shows why a reduction in effort does not always begin with an aversion to work. Sometimes it is a response to how responsibility has been distributed. Social loafing is the tendency to exert less effort on a collective task than on a comparable individual task. The sucker effect is a more specific mechanism: people limit their effort to avoid becoming the person who works on everyone else’s behalf. These concepts should not be equated with every difference in output. Employees have different tasks, experience, and resources, and invisible work can be highly demanding. Counting slides is not enough to assess actual contribution. Before concluding that someone is benefiting from other people’s effort, examine how visible the work is. Some tasks may take place outside shared meetings or require time that others cannot easily assess. One person quickly presents the finished product, while another removes the obstacles that made that product possible. A sense of inequality is therefore not automatic proof of an unequal contribution. It should not, however, be dismissed by simply insisting that everyone is working hard. The team needs a conversation about responsibility, workload, and interdependencies. Only then can it distinguish actual avoidance of work from a lack of resources or insufficient knowledge of what others are doing. Each situation calls for a different response.

Why shared responsibility sometimes dilutes effort

A classic meta-analysis by Karau and Williams shows that social loafing is not an inevitable feature of group work. Its severity depends on the conditions, including the importance of the task and whether individual contributions can be identified. It also matters whether people believe their own actions affect the shared result. Someone who believes their extra effort will make no difference or go unnoticed may be motivated differently from someone whose responsibility is clear. Karau and Williams, 1993. In practice, this does not require monitoring every minute. The team needs answers to simple questions: Who owns each part? When is it due? What happens if an obstacle arises? If the answer is, “We will somehow get it done together,” the most conscientious people may become the informal safety net for the entire process. As long as they keep repairing the gaps, the problem remains invisible. The manager sees a timely result, not the cost borne by those who repeatedly finish other people’s work.

When a sense of unfairness enters the picture

Schnake’s study of the sucker effect examines the importance of equal effort within a group. In everyday work, it is useful to distinguish a lack of motivation from self-protection against perceived exploitation. An employee may still value the team’s goal while refusing to accept a rule under which additional responsibility always falls to them. This does not mean their assessment of other people’s contributions is necessarily accurate. It does mean that the discrepancy should be clarified before mutual assumptions begin to drive behavior. Schnake, 1991. In our example, Thomas’s coworkers may not even know how much of their work he corrects. One may be waiting for data, another may have received conflicting instructions, while a third may indeed have grown accustomed to others rescuing the situation. The single label “lazy” would collapse all of these possibilities into one category. The conversation should therefore address the actual workflow: What was missing? When did the problem become known? Who was expected to respond? Only then can the team discuss accountability fairly. A practical problem emerges when rescuing the shared result becomes a permanent role for the same person. At first, the extra effort may come from a desire to help. Over time, others become accustomed to the task being completed regardless of their own involvement. The person who takes over the work must then choose between protecting the outcome and protecting their own boundaries. A manager should notice this dependency instead of praising only the willingness to make sacrifices. Recognition without a change in work allocation may entrench the problem. Agree on when assistance is a justified exception, how it will be reflected in the person’s workload, and what will happen when a commitment is repeatedly missed. Accountability should not disappear simply because someone else is capable of rescuing the situation.

How to stop rescuing without abandoning the team

An overloaded person can state the boundary in advance: “This week, I will complete my section. I do not have the capacity to fill in the others, so we need a decision about scope.” This gives the team time to respond and separates the boundary from last-minute retaliation. Make additional work visible instead of treating its invisibility as proof of professionalism. The point is not to account for every favor. It is to identify a recurring pattern that affects workload and performance evaluation. The manager should assign task owners, set interim deadlines, and establish a process for reporting obstacles. If someone does not fulfill an agreement, address the issue with that person rather than making another request of the most dependable employee. At the same time, preserve the ability to provide flexible support during genuine crises. The difference lies in whether the help is deliberately agreed upon and recognized or is automatically drawn from the same people. Fairness does not require identical effort every day, but it does require transparent rules and accountability for commitments over time.

Making contributions visible without turning busyness into a contest

It helps to discuss both the result and how the work was done: What was completed? What blocked progress? Where does the process need to change? Account for coordination, quality control, and help provided to others, all of which are easy to overlook. If the team measures only the number of completed tasks, it may reward people for choosing easy assignments and avoiding collaboration. Well-designed visibility helps people understand dependencies instead of encouraging theatrical displays of who works the longest. The goal is a credible picture of contribution, not a constant competition for the title of busiest employee. Reviewing agreements together does not have to mean micromanagement. Clearly identify the task owner, the deadline, and the point at which an obstacle must be reported. A lack of progress then becomes a topic for discussion before others are forced to act in a rush. Reporting a difficulty should not be penalized in the same way as concealing it. An employee who provides early notice of overload gives the team options. Someone taking over another person’s task again can, in turn, state which of their own priorities must be dropped in order to help. Making that cost visible allows the manager to decide instead of leaving the decision to informal pressure and the most responsible team member’s sense of guilt.

When a highly engaged person starts pulling back, ask whether they are trying to end their role as the team’s permanent rescuer. Clear commitments, recognition of hidden work, and accountability for unmet agreements can restore collaboration. A general appeal for more effort may deepen the problem if it is directed at people who already do too much.

Using Empatyzer to discuss an unequal workload

Empatyzer can help you prepare for a conversation about contributions to team tasks without opening with an accusation of laziness. In Talk to Em about a specific person, you can structure a description of an unmet agreement, its impact on your own tasks, and the change you need. It is also useful to ask about obstacles, because an apparent lack of engagement can have many causes. A leader can use Talk to Em about your team to prepare communication about accountability, mutual support, and the early reporting of difficulties. The available group profile can help adapt the explanation, but it cannot replace workload data. Em does not measure employees’ actual effort or decide who is doing a fair share of the work. It helps you name the problem and prepare questions. Defining the scope of tasks, providing resources, and consistently following up on commitments remain the responsibility of the people who organize the collaboration.