Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

The crucial coordination and support tasks that act as "glue" for a team are often deemed non-promotable. Companies systematically reward individuals for visible, feature-focused work while overlooking those whose collaborative efforts enable overall team success.

Related Insights

Focusing on individual performance metrics can be counterproductive. As seen in the "super chicken" experiment, top individual performers often succeed by suppressing others. This lowers team collaboration and harms long-term group output, which can be up to 160% more productive than a group of siloed high-achievers.

Coordination work does not disappear when roles like project coordinators or scrum masters are eliminated. Instead, a 'coordination vacuum' is created where essential tasks are either dropped or haphazardly absorbed by unprepared team members, leading to widespread inefficiency and chaos.

"Glue employees" are team members with high EQ who proactively help others and prioritize the team's success. They are multipliers but often go unnoticed because they aren't traditional "star" performers. Leaders should actively identify them by asking team members who helps them the most and then reward them accordingly.

Being visibly good at a critical but unfunded job doesn't earn a promotion or raise. Instead, it imposes a "competence tax," where you are informally drafted into performing that role permanently and for free on top of your official duties.

At Menlo, peer-driven promotion decisions hinge on a crucial question: "Does the rest of the team perform better when you are part of that project?" This evaluates an individual's value based on their ability to elevate others, prioritizing team amplification over solitary excellence.

Organizations rationalize not funding facilitator roles by claiming technology will automate the work or arguing team members should "step up" and take initiative. Both are ways to avoid paying for necessary, people-centric labor.

The "brains in jars" mental model treats developers as isolated, interchangeable units, ignoring collaboration and social dynamics. This simplistic view leads to burnout, low productivity, and an inability to solve complex problems because it devalues essential work like mentoring and learning out loud.

Instead of identifying who is "best" at a task, managers should focus on who "keeps getting asked" to do it. This question reveals critical but informal roles, hidden dependencies, and employees burdened by the "competence tax."

While seemingly harmless, celebrating individual heroes sends a subtle message that solo performance is the ideal. To genuinely foster a collaborative culture, leaders should shift all recognition to team-based achievements, making it clear that working together is non-optional for success.

When companies eliminate formal coordination roles like Scrum Masters, the essential work is offloaded onto team members who are not paid, trained, or formally recognized for performing these critical functions, often to their detriment.