Set a Workload Boundary Without Dismissing a Colleague

Why does a work limit sometimes become a relationship conflict?

A colleague can hear “I cannot take this on” as information about capacity, but also as information about the working relationship: whether their request was taken seriously, whether the shared deadline matters, and whether they are now left carrying a problem alone. Those meanings can coexist. A refusal may be entirely accurate and still leave a coordination problem unresolved; a disappointed response may signal that the work has consequences, rather than prove that the limit was rude. The practical task is therefore twofold: keep the capacity fact clear and make room to discuss what the request changes for the work.

The distinction between task conflict and relationship conflict helps explain why those two parts matter. Task conflict concerns disagreement about the work itself: its priorities, content, or allocation. Relationship conflict concerns interpersonal tension, including friction that shifts attention from the task to the relationship. A request that cannot fit is initially a work-allocation problem. It can become personal when the exchange is understood as disregard, blame, or lack of cooperation. The categories describe different aspects of conflict; they do not tell us what a particular colleague feels, and a single disagreement can involve both.

In the field study reported in “Emotion regulation as a boundary condition of the relationship between team conflict and performance: A multi-level examination,” the researchers examined 39 teams. The publisher’s abstract says emotion-regulation skill at both individual and team levels moderated how task and relationship conflict related to performance. It reports that emotionally skilled individuals could make use of task conflict while limiting negative effects of relationship conflict, and that teams with highly skilled individuals used conflict effectively. This is relevant because it links emotion regulation with how groups handle conflict and its performance relationships. The accessible record is an abstract, however, and it describes team conflict and performance, not a test of whether a particular refusal sentence sounds dismissive.

“What Moderates the Relation Between Intragroup Conflict, Emotional Exhaustion, and Work Engagement?” examined questionnaire responses from 595 members of 91 workgroups. Its open paper reports hierarchical regression and moderation analyses: distraction-related emotion regulation moderated the relationship between relationship conflict and group emotional exhaustion, while cooperative conflict management moderated the relationship between task conflict and group engagement. The outcomes differ from the first study’s performance focus. Here, the reported patterns concern exhaustion and engagement at the group level, with different conflict-management conditions attached to each. The authors also call for more interpretive research. These results add a specific account of how conflict and regulation covary with group outcomes; they do not identify what one person’s boundary will make a colleague feel.

The comparison matters because the first study looks at emotion-regulation skill as a condition shaping conflict’s relationship to performance, while the second separates two specific associations: distraction-related regulation with relationship conflict and exhaustion, and cooperative conflict management with task conflict and engagement. They converge on the idea that conflict type and emotional handling matter to group outcomes, but they do not measure the same outcome or establish the same process. Reading them as interchangeable evidence for a single “good communication” technique would erase those distinctions. Neither study isolates capacity refusals, the wording used in them, or the emotional interpretation of a refusal.

Together, the studies support a bounded conclusion: emotion regulation may shape how people handle task and relationship conflict, but they do not establish that wording can prevent offense or determine an individual colleague’s response. Nor does disappointment settle the cause. The colleague may face a real dependency, an important deadline, or a workload allocation that has not been resolved. In that case the relationship signal deserves acknowledgment, while the underlying issue still needs a work decision. Treat the request as something to discuss—what is needed and what can change—rather than trying to manage the other person’s feelings as an outcome you can guarantee.

Sources: Emotion regulation as a boundary condition of the relationship between team conflict and performance: A multi-level examination; What Moderates the Relation Between Intragroup Conflict, Emotional Exhaustion, and Work Engagement?

What do you need to know before answering?

Before answering, separate four facts that often get compressed into a vague yes or no: what the colleague needs done and by when; what you have already committed to and its deadline; what part, if any, can genuinely fit; and whose decision would have to change the plan. This is a small capacity check, not a judgment about whether the request matters. A task can be important and still exceed the time available. Conversely, a tight week does not by itself show that no adjustment is possible; the answer depends on the work, deadlines, and authority involved.

Consider this illustrative collision: a colleague asks you to prepare a complete set of figures for a Friday review, while you already own a separate deliverable due Friday. “I can’t” gives a truthful limit but leaves the colleague unable to plan: they do not know whether the problem is the full scope, the timing, or any contribution at all. A more useful reply starts with the concrete facts: “I’m responsible for the [existing deliverable] by Friday. I can’t complete both pieces by then. Which part of the figures is essential for the review?” The brackets are placeholders, and the exchange is an illustration, not a reported event or a tested script.

That question distinguishes the request’s importance from your availability. If only a subset is needed, the scope might be reduced; if another person can own a portion, a handoff might work; if the entire task and both deadlines are fixed, the plan may require a priority decision. Each is conditional. Do not offer a partial contribution or transfer unless you actually have the time, information, and permission to do it. If none of the work can fit, say so plainly and identify the decision that remains open instead of implying that a solution exists when it does not.

Ask one concrete question when the colleague may know a dependency or deadline you do not: “What has to be ready first, and what depends on it?” Their answer may change what is feasible. Then compare the requested task and date with your existing commitment and date, and name the real available capacity. This gives both people enough information to discuss a workable adjustment—or to recognize that the work must be reprioritized—without treating a limit on time as a verdict on the request or the person making it. It also keeps the next step tied to the actual constraint: scope, timing, ownership, or authority. If the facts are still incomplete, pause on a promise and get the missing detail before agreeing to a date.

What can you say that gives the colleague something to plan around?

A useful response gives the colleague four pieces of information in a short order: that you heard the request, what work is already committed and when it is due, what capacity you actually have, and what decision or alternative could keep the work moving. For example: “I understand you need the draft figures for Thursday’s review. I’m finishing the client summary due Thursday, so I can’t take on the full set by then. I could check the two priority figures Wednesday afternoon; if you need the full set, which of my current deadlines should move?” The details are placeholders for an illustrative script, not a quotation from research or a validated formula.

The opening acknowledgment names the request rather than judging its importance. That helps the colleague hear that the task has registered, even though the answer will be constrained. Naming the existing commitment and date makes the limit legible: the issue is a collision between pieces of work, not a vague unwillingness to help. The capacity sentence should be plain enough to plan around. If only a defined portion fits, say which portion and by when; if no portion fits, do not imply that a small contribution is available. Specificity prevents an offer from becoming a second promise you cannot keep.

Then give the other person a real next move. A feasible partial contribution can preserve progress when it fits your schedule and supplies something the work actually needs. If the full request still has to be done, asking which commitment should move makes the trade-off explicit. That question is appropriate when the colleague can set priorities; if neither of you has that authority, the unresolved choice belongs with whoever does. Avoid offering an alternative merely to soften the refusal. A proposal that is not workable adds uncertainty instead of helping anyone plan.

The TIME article “6 Ways to Set Boundaries at Work—Even When It’s Uncomfortable” gives practitioner advice about telling a manager when accepted work no longer fits and offering a feasible contribution. Its coworker examples concern interruptions and privacy. Those situations are useful context for speaking plainly, but they do not address this peer-to-peer task-allocation gap, and TIME reports no comparison showing that a particular wording changes a colleague’s reaction. The sequence above is an application to this situation, not a research-tested script.

When no alternative is genuinely available, keep the same acknowledgment and capacity facts, then leave the decision visible: “I understand the full analysis is needed Thursday. I’m committed to the launch report through Friday, and I can’t take on the analysis as well. I don’t have spare capacity for a portion; can we ask Priya to decide which deadline moves?” Replace the name and details with the actual decision-maker and commitments. A brief answer is enough when the request and trade-off are clear. A long defense can bury the choice under explanations, while a concise account lets the colleague respond to the actual constraint. The wording can be considerate and still leave them disappointed; it gives them information to plan with, not control over how they feel.

Sources: 6 Ways to Set Boundaries at Work—Even When It’s Uncomfortable

How can you stay responsive without agreeing to work you cannot do?

After stating the limit, listen for information that could change the work decision. “This is urgent” tells you how the colleague sees the timing; it does not yet explain what must happen sooner, what depends on it, or whether an existing commitment can move. Ask about the dependency rather than debating whether the request deserves urgency: “What has to be ready first, and what will be blocked if it waits until Friday?” If the answer reveals a genuine deadline or changed commitment, reconsider the options against that fact. Staying responsive means updating your understanding, not automatically accepting the task.

For example, imagine a colleague replies, “The review moved to Wednesday, and the figures are needed before the finance team can sign off.” You might answer, “So the figures are a Wednesday dependency for sign-off. I’m still committed to the client summary then. Is a first-pass set enough for finance, or does the whole set have to be ready?” This reflects the request in concrete terms and checks whether scope changes the choice. If only the full task will work and both commitments remain fixed, keep that capacity statement steady and bring the competing dates to whoever can reprioritize them. Repeating the limit calmly is clearer than adding new reasons each time.

Acknowledging impact is separate from agreeing to do the work. “I can see this puts the review under pressure” recognizes the consequence the colleague described; it does not promise that you will absorb the task. If they sound disappointed, let them answer before filling the pause with explanations. You can ask whether you have understood the main concern, then respond to the concrete issue they name. The aim is to keep the conversation about the actual dependency and decision, without treating their emotion as proof that your limit was wrong or as something you can settle with one perfect sentence.

If your first reply came out curt or left the colleague unsure whether you had heard the request, repair the delivery directly: “I answered too abruptly. I understand the figures are needed for sign-off, and I should have said that before explaining my capacity. I still can’t complete the full set by Wednesday; let’s check what can move.” That correction clarifies the interpersonal miss while keeping the work fact intact. Use it when the delivery caused confusion, not as a ritual apology for having a limit. Respectful wording cannot guarantee the colleague will feel comfortable or agree with the outcome. It can leave both people with a clearer account of the need, the available capacity, and the decision that remains.

Who can actually change the work plan?

The next question is about authority as much as capacity: can you and your colleague make the adjustment you are discussing? The NIOSH record for “Organization of Work: Generic Job Stress Questionnaire” lists quantitative workload and workload variance separately from role ambiguity, role conflict, and decision control. That separation is useful here because a crowded workload and an unclear decision right are different problems. Two colleagues may agree that a deadline is impossible and still lack permission to move it.

The workload measures sharpen the diagnosis before anyone decides who should act. Quantitative workload concerns how much work is assigned; workload variance concerns how unevenly demands arrive or change. A colleague asking for one extra deliverable may expose a short-term collision, while a stream of changing requests can point to a broader capacity pattern. The questionnaire keeps those dimensions distinct, so a discussion of this week’s deadline should not be mistaken for proof that the whole workload is manageable. For the immediate choice, identify which work and date create the pinch, then ask who can adjust them.

Role ambiguity means uncertainty about what responsibilities or expectations apply. In a workload conversation, it can leave both people unsure who owns the task, who may change its scope, or who is expected to resolve a collision. Before bargaining over dates, name the open responsibility: “Are you asking me to own the whole analysis, or does the project lead decide who takes each part?” If ownership is genuinely shared, the colleagues can clarify it together. If an assignment was set by someone else, agreement between peers may not change the obligation that is creating the conflict.

Role conflict describes incompatible expectations attached to a role: for example, two assigned pieces of work each require the same hours or both have fixed deadlines. The term does not mean the colleagues are personally in conflict. It identifies a practical collision in what the work requires. Ask whether either commitment can change, and by whom. When both people can revise scope, timing, or ownership, direct negotiation can produce a real adjustment. When neither can move the assigned work, or both dates remain incompatible, the missing step is a priority decision from the person who can alter those assignments.

Decision control is the room a person has to make choices about how work is done. A colleague may control the order of their own tasks but not the delivery date promised to a client, the staffing level, or another team’s dependency. That boundary matters: a peer can offer useful information without holding the authority to settle the trade-off. NIOSH catalogs decision control as a distinct measure; it does not give a threshold for escalation. The routing rule here is an editorial inference from those separate constructs: negotiate directly when both colleagues can make the proposed change; bring the options to the responsible priority-setter when they cannot.

Make that request concrete rather than asking a manager to solve an abstract feeling of overload. Bring the two tasks, their owners, the deadlines, and the specific choice that remains: reduce the requested scope, move one date, transfer ownership, or keep the current plan and accept its consequence. The manager may not know a technical dependency the colleagues can explain. Invite correction—“Have I missed something that makes Thursday fixed?”—and let the person responsible for priorities decide once the dependency is clear. This preserves the colleague’s input while locating the final choice with someone able to make it stick.

Sources: Organization of Work: Generic Job Stress Questionnaire

Why can a reasonable limit still meet resistance?

A clear account of your capacity can make the decision easier to understand; it cannot make every constraint disappear. In “Prompting, Facilitating, and Legitimizing: How Work-Life Flexibility Policies and Relational Others Shape Boundary Management,” interviews with 45 UK academics working in hybrid arrangements describe how other people and workplace policies can support or undermine work–nonwork boundaries. The study concerns how participants manage the boundary between paid work and life outside it. A colleague’s request to add a task is a different boundary problem, so these findings offer context about the role of surrounding relationships, not direct evidence about how a peer will respond to a refusal.

The study’s three terms—prompting, facilitating, and legitimizing—describe different ways that context enters boundary management. Other people can prompt someone to consider a boundary, make it easier to carry out, or signal that maintaining it is acceptable; flexibility policies can also enable or validate choices. The account is relational: a boundary is lived among people and arrangements. For task limits, the parallel is only a question to investigate: does the colleague have room to accept the limit, and does the work system leave a workable alternative? The study does not answer those questions for this kind of request.

The useful connection is modest. The earlier conflict studies describe relationships between emotional handling, conflict, and group outcomes; the boundary-management interviews show that a person’s ability to maintain a limit can depend partly on what others and organizational arrangements make possible. Together they caution against treating one well-phrased message as control over the outcome. A colleague may remain upset because the work still has a consequence, or because the arrangement makes the limit hard to respect. The interview study does not establish that a particular policy determines a peer’s reaction, and the conflict evidence does not identify a sentence that prevents resistance.

If the colleague pushes back, first check for a missing fact that could change the decision: a new dependency, a narrower deliverable, or a date that has moved. Ask about that specific point and update your view if the information changes what can fit. If it does not, restate the capacity fact without reopening the same negotiation: “I understand the full set is needed Thursday. I’m committed through Friday and can’t complete both.” This keeps the discussion anchored in the work rather than turning their frustration into proof that your limit was unfair.

Then check whether the proposed trade-off is yours to make. If you and the colleague can change the scope, timing, or owner, settle the adjustment together and make the new commitment clear. If the assignment cannot move by agreement between you, take the competing tasks and dates to the person who sets priorities. A policy or supportive relationship may make a boundary easier to maintain, but neither substitutes for a decision about work that exceeds available capacity. You can acknowledge the inconvenience and still leave that decision with the person who has authority to make it.

Sources: Prompting, Facilitating, and Legitimizing: How Work-Life Flexibility Policies and Relational Others Shape Boundary Management

How do you know the boundary changed the plan?

The boundary has changed the plan only when the work itself has a different owner, scope, or deadline—or when the person with authority has made clear that it will not change. A calmer exchange can feel like progress while leaving the same two assignments on the same person for the same dates. Before ending the conversation, say back the operational result: what you will do, what you will not take on, what has moved, and who will tell anyone affected by the change. If no commitment can move, name that as the unresolved decision instead of letting polite agreement imply the capacity problem has disappeared.

Keep the confirmation brief enough to use: “Owner: [person]. Task and scope: [work included]. Due: [date]. Still to decide: [which commitment moves / who decides]. [Person] will tell [affected colleague or team] by [date].” Fill only the blanks that apply. If the task is split, make each owner and piece of work explicit; if the deadline is unchanged, write that too. A note is useful because it gives both colleagues the same account to plan from and makes a missing choice visible. It is not proof that the workload is now feasible. If the note still assigns incompatible work to one person, the conflict remains open. Include a handoff date when the next owner needs time to act; “someone else will pick it up” leaves a gap. If only part of the task is changing, describe the boundary of that part in ordinary work terms, such as which figures or pages are included. Specific scope prevents a partial offer from quietly expanding back into the whole assignment.

The study “Regulating emotions at work: the role of emotional intelligence in the process of conflict, job crafting and performance” examined 293 employees across industries in South Africa using cross-sectional data. It reported relationships among task conflict, job crafting, emotional intelligence, and performance, including a link involving task crafting and in-role performance. Those findings describe associations in that sample; because the measures were analyzed cross-sectionally, they cannot establish that EQ caused the work outcomes or show that carefully phrased boundary conversations improve performance. The study did not test workload-boundary wording. It therefore supports keeping emotional skills and job performance connected as a research question, while the actual confirmation of a changed plan still comes from the work decision itself.

If the same collision keeps returning, or the agreed note leaves the task and deadline untouched, bring the specific conflict back to the manager or other person authorized to set priorities. Show the owner, requested scope, competing commitment, due dates, and the choice still required. Ask that person to confirm which assignment changes—or to state that the current plan stands and who owns its consequences. This keeps the colleague’s request visible without turning repeated, courteous conversations into an informal transfer of extra work. The confirmation that matters is a decision someone can act on, not simply evidence that everyone spoke calmly.

Sources: Regulating emotions at work: the role of emotional intelligence in the process of conflict, job crafting and performance

What should you do before your next reply?

Before replying, write down three things: the request and its due date, the commitment already on your plate and its due date, and who can decide what moves if both cannot fit. If there is no real capacity collision, answer the request directly. If a collision exists and the choice is beyond your authority, ask for prioritization instead of silently taking on both tasks. A private note can be as simple as: “They need [task] by [date]. I already own [commitment] by [date]. [Name or role] can decide whether [specific item] moves.” You do not need to settle the whole exchange in advance; the point is to enter it knowing which facts are firm and which choice still needs an answer. If the date or requested scope is unclear, make that your first question.

When these situations recur, a private reflection can help you notice how you respond to emotional situations and which behavior you might practice next. The 32-item Emotional Skills Profile separates recent-behavior reflection from judgments on authored scenarios. Explore the Emotional Skills Profile at /assessment, or read the report guidance at /report. The profile can give you a structured prompt for self-reflection; the priority decision still belongs in the actual conversation with the person who can change the work plan. Use the result as a starting point for noticing behavior and choosing a practice, not as a verdict about your ability or a promise that a colleague or workload will change.