The Invisible Work That Holds High-Performing Teams Together

person-centred leadership
Home » HR Blog » The Invisible Work That Holds High-Performing Teams Together

Imagine two employees working in the same department.

The first consistently exceeds their individual performance targets. Their accomplishments are easy to measure, their results appear prominently in monthly reports, and their manager frequently mentions them during team meetings.

The second produces solid work but rarely tops the performance charts. However, they’re also the person colleagues approach when they need help solving a difficult problem. They mentor new employees, share knowledge across departments, and often notice potential issues before those issues become expensive mistakes.

When promotion decisions arrive, which employee is more likely to stand out?

The answer may depend on what the organization measures.

Individual performance is relatively straightforward to document. Contributions that improve the performance of an entire team can be much harder to identify, particularly when they happen through informal conversations, mentoring relationships, and everyday cooperation.

For leaders trying to build high-performing teams, this creates an important challenge: some of the work that makes an organization successful is also the easiest to overlook.

Why Traditional Performance Metrics Miss Important Contributions

Most organizations need measurable performance indicators.

Sales teams track revenue, customer service departments monitor resolution times, and project managers evaluate deadlines, budgets, and deliverables.

These measurements provide useful information about individual and organizational performance. Without them, managers would struggle to evaluate progress or identify operational problems.

But performance metrics rarely capture every contribution that matters.

Consider an experienced employee who spends thirty minutes helping a colleague understand a complicated process. That assistance may prevent several hours of rework, but the time spent helping could make the experienced employee appear less productive according to their individual metrics.

Similarly, someone who identifies a potential problem early may prevent a project delay that never appears in a performance report.

The value exists, but it isn’t always visible.

This distinction becomes particularly important in organizations where employees depend heavily on one another.

A software developer may help colleagues troubleshoot difficult issues. A senior nurse may support less experienced team members during demanding shifts. A project coordinator may resolve communication problems between departments before they escalate.

In each case, the employee’s contribution extends beyond their assigned responsibilities.

The difficulty is determining how to recognize those contributions without turning every helpful interaction into another performance metric.

The Research Behind Helping Behavior at Work

Organizational psychologists have studied these contributions through the concept of organizational citizenship behavior.

The term generally describes discretionary workplace behaviors that support the organization or its members beyond narrowly defined job requirements.

Examples include helping colleagues, sharing useful information, supporting organizational initiatives, and voluntarily taking responsibility for problems that affect the wider team.

A foundational 1997 review by organizational psychologist Philip Podsakoff and colleagues examined research on organizational citizenship behaviors and their potential relationship with organizational effectiveness.

The researchers discussed how these behaviors can contribute to organizational functioning by supporting coordination, helping coworkers, and reducing the need for certain forms of managerial oversight.

The implications are interesting because they challenge a purely individual approach to performance.

An employee’s value isn’t necessarily limited to the tasks they personally complete. Their actions can also influence how effectively other people complete their work.

That doesn’t mean every helpful employee is automatically a high performer or that organizations should abandon individual accountability.

It means leaders need a broader understanding of contribution.

An employee who consistently helps others succeed may be creating value that conventional productivity measurements fail to capture.

When Being Helpful Becomes an Unofficial Job

There’s another side to this issue.

Employees who develop reputations for being reliable, approachable, or knowledgeable may gradually become responsible for more informal work than their colleagues.

They’re asked to help onboard new employees, review difficult assignments, resolve interpersonal disagreements, and answer questions that fall outside their official responsibilities.

Initially, these requests may seem minor.

But small requests accumulate.

An employee who spends several hours each week supporting colleagues has fewer hours available for the work against which their own performance is measured.

This creates a potentially frustrating situation: the organization benefits from the employee’s willingness to help, but the employee may receive little acknowledgement for the time and effort involved.

In a widely discussed Harvard Business Review article on collaborative overload, researchers Rob Cross, Reb Rebele, and Adam Grant examined how demands for collaboration can become concentrated among a relatively small number of employees.

Their analysis highlighted how excessive requests for assistance can create bottlenecks, overwhelm highly sought-after colleagues, and interfere with individual productivity.

This is an important distinction for managers.

Encouraging collaboration is generally desirable, but relying too heavily on the same helpful employees can become counterproductive.

The solution isn’t to discourage people from assisting their colleagues. It’s to make sure the responsibility for collaboration is distributed fairly and that employees have sufficient time and resources to meet their own objectives.

A team shouldn’t depend indefinitely on one person being willing to absorb everyone else’s problems.

Recognition Reveals What an Organization Actually Values

Employees pay attention to which behaviors receive recognition. If managers consistently celebrate individual sales figures, employees may conclude that personal revenue generation matters more than supporting colleagues. Similarly, when promotions depend almost entirely on individual output, employees may become reluctant to spend time helping others.

This doesn’t necessarily happen because employees are selfish. People respond to the expectations and incentives established by their working environment. Over time, recognition practices can influence which contributions employees prioritize.

Yet individual performance is only one measure of an employee’s value. Teamwork, dependability, leadership, and peer recognition are among the categories explored by ⁠Martin Awards, reflecting the different ways employees contribute to organizational success.

Consider a department that celebrates its highest-performing salesperson while overlooking the colleague who regularly helps newer representatives improve their conversations with customers. Both employees contribute to the department’s performance, but only one may receive public acknowledgement.

For managers, the question is whether their recognition practices reflect the full range of contributions that make teams successful or primarily reward achievements that are easiest to measure.

Addressing this doesn’t necessarily require elaborate recognition programmes. Sometimes it begins with managers becoming more deliberate about noticing who contributes to collective success.

Why Peer Feedback Can Reveal What Managers Miss

Managers rarely observe every interaction within their teams.

They may attend formal meetings, review completed projects, and evaluate performance reports, but much of the cooperation that keeps work moving happens outside those settings.

Employees often have a more detailed understanding of how their colleagues contribute to everyday operations.

They know who answers difficult questions, shares useful resources, helps resolve misunderstandings, and remains dependable during demanding periods.

That makes peer feedback a potentially valuable source of information.

Research published by Gallup and Workhuman in 2024 examined the relationship between workplace recognition, feedback, and employee experiences.

Their report on building human-centered workplaces found that 46% of surveyed employees reported receiving recognition from peers at least a few times per month, compared with 38% who reported receiving recognition from managers that frequently.

The research also explored how meaningful feedback and recognition relate to employee engagement and workplace relationships.

These findings don’t establish that peer recognition automatically improves organizational performance. However, they reinforce the importance of considering feedback from sources other than direct supervisors.

For leaders, the practical lesson is straightforward.

If you want to understand how employees contribute to a team, ask the people who work alongside them.

Peer feedback can reveal valuable behaviors that aren’t immediately apparent in performance dashboards.

Of course, peer recognition needs thoughtful implementation. Popularity, personal relationships, and workplace politics can influence who receives praise.

That’s why feedback should focus on specific contributions rather than vague impressions.

Instead of asking employees to nominate their favorite colleague, managers might ask:

  • Who helped you overcome a difficult work-related challenge recently?

  • Who shared knowledge that made your work more effective?

  • Who contributed to a successful outcome without receiving much public acknowledgement?

  • What specific action did that person take, and why was it useful?

Questions like these encourage employees to identify observable behaviors rather than simply naming people they like.

The Difference Between Collaboration and Constant Availability

One of the biggest mistakes leaders can make is assuming that helpful employees should always be available.

Collaboration requires time, attention, and energy.

An employee who is frequently interrupted may struggle to complete complex work, even when every interruption involves a legitimate request for assistance.

Over time, this can create tension between being a supportive colleague and meeting individual responsibilities.

Managers can address the problem by creating clearer expectations around collaborative work.

For example, teams might establish designated times for mentoring, develop shared knowledge resources, or rotate responsibility for answering common questions.

An organization that depends heavily on informal expertise might also benefit from documenting processes that currently exist only in the minds of a few experienced employees.

These adjustments can reduce unnecessary interruptions while preserving access to valuable knowledge.

They also help organizations avoid confusing constant availability with effective teamwork.

Someone who immediately responds to every request isn’t necessarily contributing more than a colleague who helps establish systems that reduce the need for repeated assistance.

Both may be valuable, but their contributions look different.

How Leaders Can Make Invisible Work More Visible

Recognizing informal contributions doesn’t require managers to track every conversation or introduce complicated new reporting systems.

In fact, excessive measurement could undermine the collaborative behavior leaders are trying to encourage.

A more practical approach is to incorporate questions about team contributions into existing management processes.

Include collaboration in performance conversations

Performance reviews can examine how employees contribute to the success of colleagues alongside their individual objectives.

This might involve discussing mentorship, knowledge sharing, problem-solving, or participation in cross-functional projects.

The important consideration is specificity.

An employee shouldn’t receive a strong collaboration rating simply because they’re friendly or well-liked. Managers should identify concrete examples of how their actions supported the team.

Make mentoring an acknowledged responsibility

Organizations often expect experienced employees to mentor newcomers without formally accounting for the time involved.

When mentoring is important to the business, it deserves appropriate recognition in workload planning and performance discussions.

Managers can establish clearer expectations, allocate time for mentoring activities, and evaluate whether those arrangements are working.

This also helps prevent informal mentoring responsibilities from falling disproportionately on a small number of employees.

Recognize contributions without encouraging overwork

There’s a difference between appreciating an employee who supports colleagues and celebrating someone who routinely sacrifices their own time to compensate for organizational problems.

Leaders should be careful not to reward unsustainable working patterns.

If an employee is repeatedly staying late to help others complete their responsibilities, the underlying issue may involve staffing, training, or workflow design.

Recognition alone won’t resolve those problems.

In some situations, the most meaningful acknowledgement is adjusting workloads, providing additional resources, or distributing responsibilities more fairly.

Ask employees what recognition means to them

Not everyone wants public praise.

Some employees appreciate being acknowledged during team meetings, while others prefer a private conversation or an opportunity to take on a meaningful new responsibility.

Managers should avoid assuming that one form of recognition will be equally meaningful to everyone.

The goal is to communicate that a contribution has been noticed and valued, not to create a performance for the benefit of the wider organization.

The Risk of Rewarding the Wrong Behaviors

Recognition programmes can create unintended consequences when the criteria aren’t carefully considered.

Imagine an organization that introduces an award for the employee who helps the most colleagues each month.

At first glance, the idea seems reasonable.

But employees might begin prioritizing visible acts of assistance over less noticeable work. Others may feel pressure to participate in unnecessary collaborations simply to demonstrate that they’re being helpful.

Meanwhile, someone who develops a useful training resource that prevents dozens of recurring questions might receive less recognition than a colleague who answers those questions individually.

The first employee has reduced the team’s dependence on repeated assistance. The second has demonstrated availability.

Which contribution is more valuable?

The answer depends on the circumstances, but the example illustrates why managers should avoid treating easily counted activities as perfect measures of impact.

Effective recognition requires judgement.

Leaders need to consider not only what employees did, but also whether their actions produced useful outcomes and supported the organization’s broader objectives.

That requires a more thoughtful approach than simply counting tasks, meetings, or nominations.

High-Performing Teams Depend on More Than High Performers

Organizations need employees who deliver excellent individual results.

They also need people who share knowledge, support colleagues, identify problems early, and help create an environment where others can perform effectively.

These contributions aren’t competing priorities.

A strong team benefits from both individual accountability and collective support.

The challenge for leaders is recognizing that not every valuable contribution appears in a dashboard.

Sometimes an employee’s greatest impact is reflected in another person’s improvement, a problem that never escalated, or a new colleague who became productive more quickly because someone took the time to help.

Those outcomes can be difficult to attribute to a single individual.

But difficulty measuring something doesn’t make it unimportant.

Leaders who pay attention to the work happening between formal responsibilities may develop a more complete understanding of how their teams actually succeed.

And that understanding can influence everything from performance reviews and promotions to workload planning and leadership development.

The strongest teams aren’t necessarily those with the largest collection of individual stars.

They’re often the ones where employees have the knowledge, support, and working relationships needed to help one another succeed.

Get the latest insights from ITD’s team of experts delivered to your inbox

Post Image