Organizational Life: The Tragedy of Overfunctioning

How responsibility gaps, invisible work, and well-trained dependency quietly exhaust the people who hold organizations together

There are small tragedies in organizational life that rarely look dramatic from the outside, and for which we are often blind. They do not begin with conflict, collapse, or resignation.

They begin silently, with one person answering one more question, fixing one more gap, remembering one more thing, protecting one more deadline, and carrying one more piece of responsibility that was never formally theirs. They begin with a hero (an exceptional individuality or a talent) who, as time goes by, becomes an invisible internal help desk, an initiator, an organizational memory, and sometimes even a scapegoat.

This is not some new, just invented topic, and you have probably noticed it more than once in your life. These patterns start showing up slowly, through different conversations, different people, different organizations, and different situations.

When I started noticing them in conversations with my colleagues, friends, and clients, at first they sounded like individual stories. One person said they were tired because they constantly had to remind others. Another said they no longer knew where their job ended and someone else’s responsibility began. A third one described how they were always the person who fixed things at the last moment, clarified unclear communication, prepared what others forgot, calmed down tension, protected deadlines, and somehow still remained unseen.

And then, after hearing similar stories more than once over 20 years, a pattern began to crystallize.

The Integrator: The One Who Holds Things Together

In almost every organization, if you look more closely, there is a person who becomes known as the one who “holds things together” – the integrator. This person knows where the information is, who promised what, what is still unfinished, who needs to be reminded, what may go wrong, which message needs to be softened, where conflict may appear, what needs to be prepared before the meeting, and what will need to be repaired after the meeting.

At first, this integrator may look like a gift to the organization. And in many ways, they are. They connect what is fragmented, stabilize what is unclear, and make cooperation possible where the system itself is not mature enough to do it on its own.

But when the organization starts depending on this person too much, the integrator slowly gets pushed into another role: the hero.

And “hero” is not always a compliment.

In organizational life, the hero is often the person who is expected to save the day again and again, while the conditions that create the need for saving remain unchanged. The hero is praised when something is rescued, remembered when there is a crisis, and used when the system needs someone to absorb the consequences of poor clarity, weak accountability, or unfinished managerial work.

Over time, the hero becomes an invisible internal help desk, an initiator, an organizational memory, and a necessary scapegoat.

This – the integrator – is not their formal role. It is the role that slowly forms around them when the organization starts using their capacity as a substitute for structure, clarity, ownership, and shared responsibility.

And precisely because this role is informal, it is often expected without being named, used without being measured, and exhausted without being protected.

The Performer: The One Who Carries the Narrative

The other side of the coin is there too. The one who does not necessarily carry the work, but knows how to carry the story about the work – the performer. The one who appears when there is something to narrate, present, claim, decorate, or perform. The one who knows how to be visible around other people’s preparation, responsibility, ideas, emotional labor, and results, and then enters the organizational stage as if the colors and feathers were their own.

Yes, there are people who do not carry their part of responsibility in the same way, but they know how to be visible. They know how to talk about work, position themselves close to important people, appear when the result is already visible enough to be discussed, take partial credit, or at least create the impression that they were more involved than they actually were.

Sometimes this looks like confidence or like communication skill. Sometimes it looks like loyalty and sometimes it looks like strategic presence. But underneath, there can be a very simple pattern: someone else worked, carried, thought ahead, prepared, repaired, and protected the result – while another person learned how to move through the system using other people’s work as a platform for their own visibility.

Overfunctioning and Underfunctioning

The integrator carries the function, the performer carries the narrative – it always takes two to tango.

In everyday language, we might call them the doers and the talkers. Only in organizational life, this is more than a difference between people who “work” and people who “talk.” It is a pattern of overfunctioning and underfunctioning.

One person starts taking on too many functions, including functions that do not belong only to them. Another person takes on too few, because the system allows their responsibility to be transferred to someone who will, out of conscientiousness, professional pride, fear of failure, loyalty, or internal pressure that things must be done properly, carry it anyway.

Overfunctioning often disguises itself as responsibility and most organizations like overfunctioning because, in the short term, it solves problems. The overfunctioning person will find a way, push through, repair, connect, finish, remind, prepare, calm down the client, support the manager, cover the colleague, protect the deadline, and save the situation.

The Cost of Always Managing

And precisely because they “always manage,” the organization stops noticing the cost. The cost is high as it costs:

• Mental energy – overfunctioning people do not only carry tasks; they carry constant anticipation. Their mind is rarely only in the present task. It is also scanning what could go wrong, who may forget something, where the gap is, which person may react badly, which deadline is silently at risk, and which problem will land on their desk if nobody else sees it in time.
• Emotional energy – they often become informal regulators of the system. They notice tension before others name it. They soften messages that should have been communicated more maturely and translate between people who do not speak directly. They absorb frustration, ambiguity, avoidance, and emotional immaturity. They often become the place where unresolved things go to be held, managed, or made usable.
• Professional energy – their own work becomes interrupted by everyone else’s unfinished parts. Instead of developing strategically, creating, learning, leading, or deepening their own contribution, they spend too much of their capacity compensating for weak structures, unclear accountability, poor planning, or other people’s avoidance.
• And it costs identity.

Because after a while, the person may no longer be seen as someone with limits, needs, ambitions, and priorities. They become “the reliable one.” The one who can handle it. The one who always knows. The one who will not let things fall apart.

The Trap

At first, this may sound like recognition. Later, it can become a trap. The sentence “You are the only one I can trust with this” may sound like appreciation, but it can also become a very elegant way of transferring even more responsibility to a person who is already carrying too much.

The list of costs doesn’t end there… There is another very practical pain in overfunctioning that is often underestimated: people start treating the overfunctioning person as if they were Google, ChatGPT, an internal help desk, and organizational memory all in one.

They ask them questions before they try to find the answer. They ask for explanations of things that were already explained. They ask where the document is, what the process is, who said what, what was agreed, how something should be done, what happened last time, and what the next step should be. And because the overfunctioning person usually knows, remembers, connects, and explains, the system keeps coming back to them.

And a bulletproof way to dependency is created with something simple as repetition.

The pain continues … same things are explained, again and again, because others do not really learn, document, remember, or take ownership. The integrator becomes responsible not only for their own work, but also for other people’s orientation, memory, confidence, and sometimes even thinking process.

This creates a specific kind of exhaustion – the exhaustion of being constantly interrupted (many parents know this), of being used as a shortcut, of watching others outsource their learning to the person who already carries too much.

And this is where helping can turn into enabling, because … If every question receives an immediate answer, nobody has to build their own understanding. If every confusion is solved by the same person, nobody has to develop their own map. If one person always explains from the beginning, others can remain beginners for years without an end.

In healthy organizations, knowledge is shared, documented, transferred, and learned. In unhealthy patterns, knowledge lives inside the most responsible person and everyone keeps knocking on that person’s mind as if it were a common resource.

But a person is not a search engine. A person is not a system archive nor is an endless internal AI assistant for everyone who did not listen, did not write down, did not take ownership, or did not learn the first time.

This is also where the responsibility gap becomes visible… and we easily ask how come so many employees are irresponsible.

So if you honestly look at it asking a question is normal, learning is normal as is Asking for clarification. In healthy teams, people ask, explain, share knowledge, and support each other. The problem begins when questions are not used for learning, but for transferring responsibility.

The underfunctioning person – the Performer – does not ask in order to understand and then own the task. They ask in order to have someone else define the next step, carry the risk, and become the invisible guarantor of their action.

Later, if something goes wrong, the sentence is always ready:

• “I did it because she told me.”
• “He said I should do it that way.”
• “I only followed what was explained to me.”
• “That is what I understood from her.”

In that moment, the Integrator becomes responsible twice:

• First, they were interrupted and pulled into someone else’s task.
• Second time, if the task does not go well, their explanation becomes the excuse.

This is one of the most exhausting parts of overfunctioning: the person is not only used as a source of knowledge, but also as a place where responsibility can be deposited, as in a bank and this is very different from real collaboration.

In real collaboration, I may ask you for input, but I still own my work. I still think, check, decide and carry the consequences of my role. Your answer helps me, but it does not replace my responsibility.

In responsibility transfer, I ask you so that I do not have to fully stand behind my own action.

The tragedy of the Integrator is that the better someone carries the system, the less visible the system’s weakness becomes.

If one person always remembers, the organization does not have to build better memory. If one person always repairs communication, the organization does not have to build better communication. If one person always takes responsibility, the organization does not have to confront avoidance. If one person always saves the deadline, the organization does not have to question planning. If one person always regulates the emotional climate, the organization does not have to develop emotional maturity.

And over time, the Integrator becomes the invisible infrastructure of the organization, similar to a sorting machine – noticed only when it breaks.

What the System Teaches

This is not always conscious or malicious, sometimes it is simply systemic learning.

People learn what the system allows. They learn where responsibility can be avoided, who will cover the gap, what is actually rewarded and whether contribution matters more than impression, or whether impression can successfully replace contribution. It becomes embedded in organizational culture and this is why the topic is not only individual, but organizational.

A healthy organization does not allow responsibility to concentrate quietly in one or two exhausted people while others learn how to float. It makes work visible, clarifies ownership, names contribution, notices invisible labor, and does not confuse confidence with competence or visibility with value.

But, we know, many organizations do confuse these things.

They reward the person who speaks well about work more than the person who actually holds the work. They reward proximity to power more than responsibility. They reward appearance of involvement more than real contribution. They reward people who know how to be seen, while the people who make things possible remain in the background.

And everyone sees this.

Teams usually know who carries, who avoids, who takes credit, who appears only when success becomes visible, who leaves the difficult part to others, who is reliable and who is only loud. They know who creates value and who performs value.

When leadership does not see it or chooses not to see it – trust suffers. Because people can tolerate difficult work much more easily than they can tolerate unfairness that everyone pretends not to notice.

There is another layer of this pattern that appears very often with managers, especially with managers who are themselves the Integrators.

The Overfunctioning Manager

Many managers are surprised when they realize that every answer they give too quickly may be teaching their people to come back for the next answer. They are used to being interrupted, to being asked, to solving things, to know, to being the person who can connect the dots faster than everyone else and because they are capable, they often respond immediately.

It feels efficient, unfortunately, most of the time just in a short run.

Long term, the manager becomes the source of answers, not the developer of thinking. The team learns to ask before thinking deeply enough. People learn to bring half-processed questions, unclear options, and unfinished responsibility, because the manager will organize the thinking for them.

This is where managerial work has to shift from giving fish to teaching people how to fish.

A manager who constantly gives answers may believe they are being useful, available, and supportive. But if the same people keep returning with the same type of questions, without learning, documenting, deciding, or owning the next step, then the manager is not only supporting them. The manager may be maintaining their underfunctioning, and that is not an easy realization.

Because their identity is frequently built around competence, speed, responsibility, and usefulness. They feel valuable when they solve. They feel in control when they answer. They feel needed when people come to them and sometimes they also feel guilty if they do not respond immediately.

From Rescuer to Developer

But is leadership only about being the person who knows? Leadership is also about building people who can think, decide, learn, and carry responsibility without constantly returning to the manager as the central brain of the system.

That requires different managerial tools. Instead of immediately answering, the manager can ask clarifying questions, such as: What have you already tried?, What do you think is the best next step? What information are you missing? and How would you solve this if I were not available?

These questions may feel slower at first, but they build capacity. They move the employee from dependency to ownership. They move the manager from rescuer to developer. They move the organization from personal memory to shared learning.

And this is one of the most important practical difference between overfunctioning management and mature leadership:

The overfunctioning manager becomes the answer – the mature leader builds the system in which people learn how to find, think through, and own the answer.

This is not about placing blame, although it is tempting to describe one side as responsible and the other side as irresponsible, one side as hardworking and the other as lazy, one side as the victim and the other as the problem. To our disappointment organizational patterns are rarely that simple.

This is why awareness is so important. Not to shame the person who underfunctions. Not to glorify the person who overfunctions. Not to blame managers who answer too quickly because they are used to being useful.

Seeing the Dance

The point is to see the dance, just try and ask the right questions:

Who asks in order to learn, and who asks in order to transfer responsibility? Who helps in order to support development, and who helps in a way that maintains dependency? Who carries because it is truly their role, and who carries because they are afraid of what will happen if they stop? Who avoids ownership, and who enables that avoidance by constantly rescuing the situation?

When we see the pattern, we create the possibility to change the next move. The goal is not to stop helping, it is to stop replacing other people’s ownership with our own over-responsibility.

There is also an art in managerial work that many Integrator managers find difficult: the art of not immediately doing.

Wu Wei: The Art of Not Immediately Doing

In Taoist philosophy, there is the concept of Wu Wei, often understood as action without forcing. In leadership, this could mean resisting the automatic impulse to answer, solve, rescue, and take over, so that another person can think, learn, decide, and own their work.

For an overfunctioning manager, sometimes the most developmental action is not the answer they give, but the answer they do not give too soon. There is a moment in this pattern when the Integrator has to learn how to break the chain of verbal pressure.

Because many responsibility transfers do not happen through formal delegation. They happen through repeted questions, interruptions, unclear requests, repeated explanations, and sentences that look innocent on the surface: “How should I answer this?”, “Is this well written?”, “Should I call him?”, “Can you explain it again?”, “Can you quickly check?”, etc,

Breaking the chain does not mean refusing to help, it means refusing to take over the thinking process. At first, this can surprise people.

Especially when they are used to getting immediate answers and especially when the manager or colleague has been trained by their own overfunctioning to respond quickly, solve quickly, and carry quickly.

But this pause is important. It is the small space where responsibility can return to the person who owns the task.

In that sense, breaking the chain of verbal pressure is not passivity. It is a managerial and psychological intervention. The art of not rescuing too soon and the discipline of not becoming the answer every time someone brings uncertainty.

Maybe the tragedy of overfunctioning does not begin to loosen with a big decision, a dramatic conversation, or a perfectly designed organizational intervention.

Maybe it begins much smaller – with noticing and then, maybe, with one experimental pause. Not as punishment or coldness. Not even as a refusal to help, but more as a friendly experiment with responsibility.

The next time someone brings uncertainty, maybe do not become the answer immediately. Ask what they have already tried. Ask what they think the next step is. Ask what information they are missing. Ask what they are taking responsibility for. Let the silence work a little, and give the other person the gift of freedom to meet their own task.

And if, while reading this, someone came to your mind – someone who always answers, fixes, remembers, explains, carries, and somehow still thinks they should do even more – maybe offer them this knowledge as a small gift.

Because the tragedy of overfunctioning does not loosen when capable people stop caring. It begins to loosen when capable people stop replacing everyone else’s ownership with their own over-responsibility.

Maybe this is how the Integrator slowly returns from hero to human – one pause at a time.

---

This text was originally published on LinkedIn as part of the Invisible Bridges newsletter and is republished here as part of my professional blog archive.