Leadership Programme for Women Setting Workplace Boundaries: The Work That Keeps Returning

There is a particular kind of work that arrives without ever quite becoming a formal priority. It is the request to organise the session, smooth the handover, pick up the unclaimed action, respond to the late message or be available because nobody else is. A leadership programme for women setting workplace boundaries is often sought at the point when these requests have become routine. Yet the useful question is not only, ‘How can I say no more firmly?’ It is, ‘What in this operating system keeps routing this work back to me?’

That distinction matters. A boundary can be a clear personal decision, but recurring boundary pressure may also signal a problem in task allocation, decision rights or availability norms. If the work is important, it needs an owner, capacity and a place in the plan. If it is not important, it needs permission to stop. Treating every repeat request as a test of an individual leader’s assertiveness leaves the design of the work untouched.

When a leadership programme for women setting workplace boundaries meets a routing problem

Consider a senior manager asked, again, to chair an employee network meeting, settle a cross-team disagreement and prepare a briefing that another function needs. Each request can sound reasonable alone. The pattern emerges when they all arrive through the same person, with no shared rule for deciding who owns them or what existing work should move.

Experimental research on low-promotability tasks found that, in mixed-sex environments, women were more likely than men to volunteer, be asked to volunteer and accept requests to volunteer for work that people preferred someone else to do. The researchers identified beliefs about women being more likely to say yes as an important driver. This does not mean that every request to a woman is biased, or that every task lacks value. It does mean that a repeated stream of apparently small requests deserves examination as an allocation pattern, not only as an individual habit.

Low-promotability does not mean worthless. Committee work, onboarding, coordination, community-building and problem-clearing can be necessary to a functioning organisation. The issue is whether the work is deliberately recognised, fairly distributed and weighed against the leader’s stated accountabilities. When it is simply routed towards the person thought most likely to absorb it, the boundary conversation has already started before she receives the request.

The work that keeps returning has a recognisable shape

Recurring requests often share three features. First, ownership is vague: several people could do the task, so it goes to the most responsive person. Second, urgency is asserted but the trade-off is hidden: the task is presented as immediate without anyone naming what will be delayed. Third, the request comes wrapped in relationship language: ‘You are so good at this’, ‘It will only take a moment’ or ‘Could you just help us out?’

Those phrases are not proof of bad intent. They may reflect a genuinely stretched team. They can nevertheless obscure a management decision. A request that changes a leader’s workload, time or availability is a request for a priority decision. Someone with the authority to set priorities should be able to identify the owner, the expected standard, the deadline and the work that will make room.

A short pattern log can make this visible without turning every interaction into a dispute. For several weeks, note the type of request, who initiated it, whether it sits in the formal role, what made it seem urgent, who had authority to decide and what work changed as a result. The purpose is not to build a case against colleagues. It is to distinguish an occasional favour from an operating norm that repeatedly transfers unplanned work to one person.

Separate capacity, priority and ownership

A useful response does not have to be a blunt refusal. It can return the decision to the right place. Instead of debating whether the request is reasonable, a leader can ask questions that clarify the operating choice: Who is accountable for this? What outcome is needed? Which current priority should move? Is there a rotating allocation? Who can confirm the decision?

This changes the conversation from willingness to work to the design of the work. It also gives colleagues information they may not have had. A peer who asks for help may not know that three other requests have already displaced planned responsibilities. A manager may need to decide whether the work belongs in the role, whether a different function owns it or whether it should be paused.

The same distinction helps with tasks that are meaningful but unevenly allocated. A leader might agree to contribute while asking for a defined scope, a time limit and rotation for future requests. She might say that she can review a draft but cannot take ownership, or that she can take on the task if another deliverable is re-prioritised. These are not scripts that guarantee a favourable response. They are ways of making the choice and its trade-off explicit.

Make availability an operating agreement, not personal goodwill

Digital communication makes an availability boundary particularly easy to personalise. A message sent late can feel like a request for an immediate response, even when no response was intended until the next working day. In telework guidance, the International Labour Organization describes the right to disconnect as the ability to disengage from work and not engage in work-related electronic communications outside working hours. It also identifies the lack of clear boundaries between paid hours and personal life as a significant challenge in telework.

The practical implication is not that every role can use the same rule. Some leadership positions include agreed escalation, global teams or exceptional incidents. The question is whether the organisation has made those conditions clear. Who is on call? What counts as urgent? Which channel should be used? When is a reply expected? Who covers absence? Without these agreements, availability becomes a private negotiation conducted message by message.

A leader can make her own response pattern legible: for example, acknowledging what channel is monitored during agreed hours, naming when a decision will be considered, or directing genuine escalation to the designated route. But the organisation owns the wider conditions. It is not reasonable to rely on one person’s goodwill to supply a coverage model, an escalation protocol or permanent surplus capacity.

Ask the organisation to carry its side of the boundary

UK Health and Safety Executive Management Standards frame demands, control and role as work-design issues. The demands standard includes workload and work patterns, and says organisations should provide adequate and achievable demands in relation to agreed hours. The role standard says organisations should make requirements clear, make them compatible where possible and provide a way to raise uncertainties or conflicts.

For a manager, this provides a better agenda than a vague request to ‘protect boundaries’. Bring a specific pattern: recurring activity outside the agreed role, competing deadlines, unclear decision ownership or an expectation of response outside agreed hours. Then ask for an operating decision: a priority order, named ownership, a rotation, a resourcing change, a documented escalation route or a review of the role. The answer may involve constraints, but the constraint should be visible and owned rather than silently absorbed.

Senior leaders can also notice the distribution they create for others. Who is repeatedly asked to coordinate, mentor, take notes, handle the difficult follow-up or cover a gap? Is this work captured in allocation conversations? Are volunteers recognised without being relied upon as the default? Fairer boundaries are not produced by telling individuals to become less helpful; they depend on managers designing requests, roles and rewards more deliberately.

Map the pattern before choosing the next conversation

There is no universal boundary response because the source of the pressure may differ. A peer request may call for a scope conversation. A manager’s instruction may require a priority decision. A persistent out-of-hours norm may require team-level agreement. A pattern of low-promotability work may call for an allocation review. The relationship, authority and consequences determine what can usefully happen next.

Start by mapping one recurring request rather than trying to solve an entire workload at once. What is being asked? Who benefits? Who could own it? What authority does the requester have? What formal work would change? What expectation about availability is being assumed? What decision would make the request clearer or fairer? This map turns a familiar feeling of being pulled in too many directions into a concrete leadership and organisational question.

That is where boundary work becomes more precise. The aim is not to become unavailable, detached or endlessly accommodating. It is to make priorities, ownership and availability discussable in the place where work is actually designed. When the work that keeps returning is visible, a leader and her organisation have something more useful to address than her ability to say no.