Why invisible work does not lead to promotion

The person without whom everything would fall apart

Ewa onboards new employees, prepares notes, remembers deadlines and organizes meetings with partners. Whenever someone gets stuck, she helps. In her annual review she is told that she is “indispensable support,” but that she needs a larger independent project to earn a promotion. The problem is that her calendar is filled with the tasks that enable other people to lead projects of that kind. This example shows the gap between work’s value to the group and the work for which an organization grants formal recognition and development opportunities. Researchers use the term tasks with low promotability. This does not mean meaningless work. It refers to activities that contribute less to promotion decisions than other available assignments. Their value depends on the role and the organization’s system. Preparing training materials may be a key achievement for a learning and development professional but an invisible extra for a specialist assessed solely on sales. An invisible task is not an unnecessary one. Someone must document agreements, help a new colleague and attend to the matters on which everyday cooperation depends. The problem lies in the relationship between what the organization needs and how it distributes recognition and opportunities. If certain activities keep going to the same people, they may consume time that could have been spent on assignments valued more highly in promotion decisions. It is therefore not enough to encourage everyone to be more helpful. The organization must identify who actually performs support work, how often and at what cost. Only then can the workload be divided fairly. General praise for being an indispensable helper may reinforce a role that the employee would like, at least partly, to leave behind.

How tasks keep finding the same people

Babcock and her co-authors analyzed gender differences in volunteering for such tasks, being asked to do them and agreeing to those requests. Their research highlights the role of social expectations and the way work is allocated. It does not show that every woman is more likely to help or that men do not perform support work. What matters is the mechanism by which expecting someone to agree can direct successive requests toward the same category of people. Babcock et al., 2017. A similar pattern can arise without any formal instruction. Someone asks during a meeting, “Who will take the notes?” Everyone waits for the person who usually does it to volunteer. Their reliability becomes the argument for assigning the task to them again. Over time, refusing may require more effort than agreeing because it violates an established expectation. The organization gets the outcome it needs without making an explicit decision about who bears the cost. This is precisely why encouragement to set personal boundaries cannot solve the whole problem.

The hidden cost is a lost opportunity

In Ewa’s case, the question is not only how much time helping takes. It is also what she cannot do during that time. If a developmental project requires uninterrupted blocks of work, frequent small requests can effectively crowd it out. Each request may look minor, but together they create a distinct role profile. The employee becomes known for supporting other people’s achievements and is later judged for lacking achievements of her own. This is a problem in the design of responsibilities, not necessarily in her ambition or self-promotion skills. Not every support task must be rotated in exactly the same way. There may be valid differences in competence, availability or job scope. Those differences should nevertheless be named and reflected in workload and assessment. If someone is responsible for onboarding new employees, they should have time for it and criteria by which that contribution is recognized. If the task is additional and serves the whole group, a method of sharing it should be agreed. “She does it best” is not an adequate permanent justification if that same work receives no value in development decisions. The way tasks are allocated also matters. “Who will take care of this?” may sound neutral while in practice triggering the familiar wait for the same person. Someone volunteers because they do not want to hold up the meeting, and their willingness is later treated as a natural preference. Being able to perform a task should be separated from wanting to fill that role indefinitely. An employee may be good at organizing other people’s work and still need access to projects that build their own skills. The leader should ask rather than assume that a capable performer is happy with the arrangement. Rotating some responsibilities, or explicitly recognizing them in workload and performance assessment, may help.

How to make the work visible

For several weeks, record the types of support tasks you perform, roughly how long they take and whether they arise from your role, a request or your own initiative. The aim is not to put a price on every act of kindness. It is to reveal a pattern that would otherwise disappear into the flow of daily work. In a conversation with your manager, compare this picture with the assessment criteria: “Onboarding and coordination take up a substantial part of my week. How will we reflect that in my goals, and what will we scale back so that I can lead a project?” You can also respond to a new request by discussing priorities: “I can take this on if we move task X. Which is more important?” This makes the cost of the decision visible instead of presenting agreement as cost-free availability. If requests come from many directions, you may need an overall agreement with your manager. An employee should not have to negotiate the entire system of interdependencies alone, especially when refusing affects whether they are judged to be “collaborative.”

What the manager should change

A leader can allocate recurring responsibilities openly rather than asking for a volunteer every time. The team should define which tasks are important to its results and how they will count in assessment. If a company says it values collaboration, it should be able to show how collaboration affects recognition decisions. At the same time, people who are constantly busy supporting others must still have access to developmental assignments. A thank-you does not compensate for the lost chance to gain experience needed for the next role. Refusing may be easier when framed in terms of priorities rather than the value of the task itself. An employee can explain that taking on another organizational matter will delay the agreed project and ask which is more important now. This reveals a cost that previously remained invisible. Not every request for help needs formal negotiation. The issue is a recurring pattern in which additional responsibilities repeatedly displace other goals. A manager can also ensure that development opportunities do not go only to those who have time because other people maintain the shared infrastructure around them. A fair allocation requires looking at the whole body of work, not only the most visible project outcomes.

Invisible work becomes a problem when it is continuously needed, unevenly distributed and poorly recognized. Addressing it requires examining promotion criteria and the cost of lost opportunities. Collaboration should be valued in practice, not only when someone is needed for yet another extra task.

Using Empatyzer to discuss invisible responsibilities

Empatyzer can help you prepare for a conversation about workload and access to tasks that support development. In Talk to Em about yourself, you can organize which responsibilities you repeatedly take on, why saying no is difficult and what you would like to change. A useful outcome is a practical description of the cost that does not diminish the importance of support work. Talk to Em about a specific person can then help you prepare a request to your manager to change the allocation or agree priorities. You can also rehearse a response to the next request that clearly sets out the options available. Empatyzer does not automatically record tasks or determine who performs the most. The conversation must be grounded in your own examples and work data. The tool supports communication; decisions about rotating responsibilities, recognizing contributions and granting access to projects remain the organization’s responsibility.