A team submits a proposal on Friday. The manager thanks everyone, the client is pleased, and the project appears to have gone well. In the background, two colleagues spent Thursday evening completing sections they had expected other people to provide. One is frustrated; the other has stopped mentioning how often this happens.
The result tells the manager little about how the work was distributed. There may have been unclear ownership, conflicting assignments, missing skills, or reduced effort from someone who expected colleagues to finish the job. Understanding which explanation applies matters before deciding what to change.
What Social Loafing Describes
Social loafing is a reduction in individual effort when people work collectively compared with working individually or having their contributions assessed separately. It describes a pattern under particular conditions, rather than a permanent characteristic that can be inferred from a colleague's personality.
In experiments published in 1979, Bibb Latané, Kipling Williams, and Stephen Harkins examined clapping and shouting tasks. They found reduced individual effort in group conditions and distinguished that reduction from losses caused by coordination. The distinction matters: a group can accomplish less than expected even when its members are trying hard.
Those tasks are different from preparing a proposal or maintaining software. They help establish the phenomenon, but they do not provide a way to diagnose a particular employee from missed deadlines, quiet meetings, or a small number of completed tasks.
The Conditions Around Collective Effort Matter
Steven Karau and Kipling Williams' 1993 meta-analysis of 78 studies found that social loafing varied with factors including the potential for individual evaluation, task meaningfulness, and expectations of co-workers' performance. The findings support examining the situation in which people contribute rather than assuming that every group produces the same response.
For a manager, that suggests useful questions. Does each person understand how their work contributes to the outcome? Can they see a meaningful role for their effort? Are contributions recognised in a way that reflects the work? These are starting points for investigation, not a guarantee that a particular management practice will resolve the problem.
In the proposal team, a person asked to provide analysis may believe it will be rewritten regardless of what they submit. Another may assume the project lead owns the entire document. Both situations deserve a conversation, although neither account alone establishes social loafing.
Establish What Was Actually Agreed
Before interpreting a missing section as a lack of commitment, check whether somebody accepted responsibility for producing it. A request that the whole team prepare a proposal by Friday leaves several decisions unstated: who gathers evidence, who develops the recommendation, and who integrates the sections.
Role ambiguity can leave work untouched because several people believe someone else owns it. Giving a task a named owner helps only if that person understands the expected result and has the time, access, and authority to deliver it.
For the next proposal, the team could agree that one colleague will produce a cost estimate with its assumptions by Wednesday, another will review the customer requirements, and the lead will combine the material on Thursday. Each commitment should include a way to raise a blocker before the handover is due. The purpose is to make coordination possible while there is still time to adjust.
Look for Work That the Final Document Hides
Visible output is an incomplete account of contribution. A person may have checked disputed figures, helped a colleague understand the brief, resolved a customer question, or reviewed a draft that someone else published. Those activities can be essential even when they produce few individually attributable pages.
The manager needs an account broad enough to include that work without requiring people to justify every minute. Ask what was delivered, what support was provided, what changed, and which dependencies remained unresolved. Compare the answers with the person's other commitments before drawing conclusions about capacity or effort.
The same principle applies across office and remote work. Meeting attendance, rapid replies, and an online status show particular forms of availability. They do not establish the quality or extent of someone's contribution. Agreed outcomes and contextual discussion provide a stronger basis for understanding the work.
Discuss Repeated Gaps Privately and Specifically
When a pattern remains after expectations are clear, address it directly. Describe the commitment, what happened, and its effect on colleagues. A conversation about the proposal might begin with the observation that the cost estimate arrived a day late on two occasions and the reviewers had to complete it after hours.
Then examine the explanation. The person may be waiting for information, managing another deadline, or uncertain how to do the analysis. They may also have chosen to give the task less attention because they expected someone else to cover it. The next step should follow the evidence rather than an assumption about their motivation.
Agree on a concrete adjustment and a point to review it. That could mean changing priorities, arranging support, narrowing the task, or making the existing expectation explicit. If commitments continue to be missed despite reasonable support and clarity, the manager still needs to address the performance issue. A psychological label is unnecessary for discussing the behaviour and its consequences.
Stop Making Reliability an Unlimited Obligation
Sometimes urgent work must be reassigned. The problem becomes harder to see when reassignment happens silently and the person receiving it keeps all their original commitments. The proposal is completed, but the team's apparent capacity now depends on extra work that was never planned.
When responsibility changes hands, record what moved and decide what the receiving person can defer. Review recurring transfers after the deadline, including why they were needed. This makes it possible to help a colleague without turning help into a permanent expectation that the same people will absorb every gap.
The standard should be sustainable contribution within agreed responsibilities. Someone who declines extra evening work has not thereby demonstrated reduced effort. Planning for rest and recovery helps keep a team's definition of reliability from becoming a requirement for continual availability.
Preserve the Reasons to Help Each Other
Individual ownership should leave room for shared work. If recognition follows only assigned deliverables, mentoring, review, and assistance can disappear from the account of success. A person who helped three colleagues finish may look less productive than someone who completed a smaller task alone.
Recognise specific contributions to the outcome, including work that enabled others to proceed. Ask whether responsibilities were balanced and whether people could raise difficulty early. The behaviour an organisation rewards helps communicate what it actually expects from collaboration.
For the proposal team, improvement would mean more than another on-time submission. Sections would arrive with enough time for review, blockers would be raised while someone could act on them, and changes in ownership would be explicit. The colleagues who previously worked late would be able to complete their responsibilities within a realistic plan.
Social loafing offers one explanation for reduced effort in groups. Its practical value comes from prompting a closer examination of how contribution is organised and understood. The team still needs evidence about its own work, a fair response to individual circumstances, and a manager willing to address patterns that leave the same people carrying the unfinished tasks.