THE CODEX JOURNAL
When a Workplace Exception Becomes Your Job
Illustrative photograph: Timothy Huliselan / Pexels · Licence
Reading tools & contents
The second exception is a design decision
A colleague is away. The client needs an answer, and you know enough to send it. Helping makes sense. The following week, a similar message arrives directly in your inbox. By the third week, colleagues tell newcomers that you handle these questions. The first request was made openly. The transfer of responsibility happened through routing, repetition and assumption.
This is a particular kind of workplace boundary problem. The person may enjoy the work and be willing to do more of it. The difficulty is that nobody has made a decision about where the work belongs. Its apparent success conceals the trade it required. Perhaps you finished another task later, borrowed help from a colleague, or answered something beyond your authority and hoped the answer would hold. The organization sees a problem resolved. It may never see what had to move.
A workaround can make its cause invisible
An exception frequently reveals a gap between a process and an actual need. It might expose a missing backup, a vague approval path or a team that owns the first half of a task and has nowhere to send the second. Helping once can supply useful information about that gap. Helping indefinitely can remove the symptoms that would cause anyone to examine it.
Look for the promise other people now make in your name. A colleague says the response will be ready by noon because you managed that once. A manager includes the extra service in a plan because it appeared in last month’s results. Neither person may be trying to exploit you. They are using the evidence they have. If they only see output, their picture of capacity will be incomplete. Describe the conditions under which the result happened and which of those conditions can recur.
Ownership requires three separate answers
A recurring responsibility needs capacity, authority and a mandate. Capacity tells you what time and resources are available. Authority tells you which choices you can make without someone else’s decision. A mandate tells everyone what outcome you are expected to own. The three answers can diverge. A person given a new inbox may have no ability to set response times. A person expected to solve problems may only have access to enough information to forward them.
Consider which missing answer creates the friction. If the issue is capacity, putting your name on a task list leaves the problem intact. If the issue is authority, asking for quieter inboxes will not resolve the decisions that keep returning. If the issue is the mandate, polishing a workflow risks making a confusing assignment more efficient at involving the wrong people. Once the gap is named, the conversation can move from your personal availability to what the service actually requires.
Use the next request to surface the choice
A request often arrives just when there is least room to discuss the recurring pattern. An immediate decision and a decision about future ownership can be made separately. You might be able to complete today’s task while saying which other item would move. You might be able to help identify a person who can decide while leaving the final answer with that person. The exact response depends on the stakes and the alternatives available.
Follow up when there is enough time to review the pattern. Bring a few examples rather than reconstructing every grievance. Describe who asked, the work it generated, the authority it required and what was deferred. Ask whether the team wants a standing service. If so, agree how it will be resourced, when someone else covers it and which cases belong elsewhere. An explicit plan gives colleagues an alternative destination when the next request arrives.
One week of cover becomes an operating assumption
Mara, a designer at a small studio, covers the project inbox while a producer is travelling. She answers routine questions and resolves a delivery confusion by checking with two colleagues. When the producer returns, clients still reply to Mara. Teammates add her to messages because she has the latest context. Soon she is answering for projects she never worked on.
A month later, a client asks her to promise a new delivery date. She cannot see the full production schedule or move other bookings. Her manager asks her to be more proactive. Mara brings three examples to their planning meeting, including one where she delayed design feedback while waiting for scheduling approval. The examples show what she can answer from the design brief and where her involvement merely adds a person to the chain.
The producer resumes ownership of delivery dates. Mara stays available for design questions and helps write a brief handoff for common cases. The studio also learns that the original leave cover needed access to the schedule and a clear decision maker. The next absence has a named backup. Clients get a more reliable answer, and Mara’s role can again be described in terms other than whatever happened to arrive.
A useful new role deserves an explicit offer
Sometimes the pattern reveals an opportunity. Someone who steps outside their assignment may discover work they are good at and want to keep. That is a reason to discuss the role openly. Continuing on the original terms may preserve the ambiguity over whose priorities come first and which expectations will count when work is reviewed.
Try asking what changes if the responsibility genuinely belongs to you. Which current commitments shrink? Which decisions move with it? Who needs to hear that the assignment has changed? What happens when you are away? Useful answers show whether the workplace is creating a viable role or simply relying on personal effort to hold several assignments together.
Test the boundary at the point of handoff
Think of an exception that has repeated. Write down the reason it was originally exceptional and the first moment someone treated it as standard. Identify one decision you are presumed to own and one piece of information you would need to own it well. If you were unavailable on the next occasion, where would the request go? The answer measures how far the work has become part of an actual system.
A conversation can begin with a specific observation. “These requests now come to me each Thursday. They take the time we allocated for reviewing new work. Can we decide who should own them and what moves if I continue?” A concrete choice gives the other person something to answer. It also makes cooperation visible. The next exception can still be a worthwhile favour, with a clear end and a person responsible for what follows.