Making Invisible Work Visible

One of the easiest mistakes a manager can make is confusing visibility with impact.

The people who contribute the most to a team's success are not always the people speaking the most in meetings, presenting the most updates or promoting their own achievements.

In many cases, the opposite is true.

Some of the highest-performing people I've worked with over the years were also the quietest.

Every successful team has people who naturally command attention. They communicate confidently, lead discussions and are comfortable presenting their work. Those are valuable skills and deserve recognition.

However, every successful team also has another type of contributor.

Some of the most valuable people in a team are remarkably easy to miss. They're the colleagues who quietly volunteer for difficult customers, stay a little longer when a major incident threatens delivery, mentor new team members without being asked and freely share knowledge that helps everyone around them succeed.

They rarely ask for recognition because their focus isn't on being noticed—it's on solving problems.

When a Brief Update Hides Difficult Work

One example has stayed with me throughout my career because it perfectly illustrates how easily managers can underestimate where the real value is being created.

Imagine a technical stand-up or programme meeting.

One person spends ten minutes explaining a relatively straightforward issue. There are questions from the team, suggestions from different departments and a lengthy discussion before everyone agrees on the next steps.

By the end of the conversation, everyone in the room knows that person is working on something important.

A few minutes later, another colleague gives their update:

“I'm working on the database migration. No blockers. I just need ten minutes with Sarah later to validate one change.”

Thirty seconds later, the meeting moves on.

To someone without enough technical understanding, the second update can sound almost insignificant. After all, it didn't generate discussion and there didn't appear to be any major concerns.

In reality, that person may be leading one of the most technically challenging and highest-risk pieces of work in the entire programme.

A successful database migration involves planning, testing, rollback strategies, validation, risk management and coordination across multiple teams.

The fact that the update was brief doesn't make the work simple. More often than not, it means the difficult thinking has already been done before the meeting even began.

Managers Need Enough Understanding to Recognise Complexity

This is one of the reasons I believe managers should maintain enough technical understanding to appreciate the complexity of the work their teams perform.

I don't believe managers need to be the strongest technical experts in the room. In fact, in high-performing teams they usually shouldn't be. Their role is different.

But they do need enough understanding to ask good questions, appreciate complexity, remove blockers and recognise exceptional work when they see it.

Otherwise, there is a real risk of judging contribution by confidence rather than impact.

The Work That Never Appears on a Dashboard

The same principle extends well beyond technical teams.

Some of the most valuable work within any organisation is almost invisible because it never appears in dashboards, project plans or executive presentations.

It quietly becomes part of the reason the team performs well.

• Mentoring new colleagues until they become confident and productive.
• Improving documentation that prevents others from repeating the same mistakes.
• Reviewing someone else's work before it reaches a customer.
• Preventing incidents before they ever become escalations.
• Building trust with customers during difficult situations.
• Helping teammates solve problems without expecting recognition in return.

None of these activities attract much attention.

Yet every one of them improves quality, reduces risk and raises the performance of the entire team.

Recognition Shapes Culture

This is where managers have one of the greatest opportunities to influence culture.

We can't always offer promotions, salary increases or bonuses the moment someone deserves them. Budgets, organisational structures and timing don't always make that possible.

Recognition, however, is different.

Recognition isn't about rewarding visibility.

It's about recognising value.

Every time we recognise someone's contribution, we're doing more than thanking an individual. We're reinforcing the behaviours we want to see repeated across the team.

Recognition isn't just feedback for one person—it's a signal to everyone else about what success looks like within the organisation.

If we consistently recognise collaboration, mentoring, ownership and knowledge sharing, those behaviours become part of the team's culture.

If we only recognise the loudest voices or the most visible achievements, we shouldn't be surprised when visibility becomes more important than teamwork.

Recognition Should Be Specific and Deserved

The best recognition is specific, genuine and deserved.

It might be acknowledging the person who stayed behind during a critical incident, highlighting someone who quietly mentored a new colleague over several months, or documenting consistent contributions so they are remembered during promotion and compensation discussions.

People don't expect recognition every time they do their job.

They do hope that when they consistently make a difference, someone notices.

Creating an Environment Where Talent Becomes Visible

One of the best examples I've seen came from a customer I worked with several years ago.

One of the Senior Technical Specialists on the programme was exceptionally talented. They consistently delivered high-quality work, solved complex problems and were someone others naturally turned to when things became difficult.

What they weren't was the loudest person in the room.

During larger meetings they tended to listen more than they spoke. If you judged their contribution purely by how much they participated in discussions, it would have been easy to underestimate the value they brought to the programme.

Fortunately, their manager didn't make that mistake.

Rather than waiting for recognition to happen naturally, they deliberately created opportunities for this individual to become more visible.

They invited them to customer lunches, industry seminars and informal discussions where their expertise could be shared in a more relaxed environment. They recognised their contributions publicly when it was deserved and made sure others understood the impact they were having behind the scenes.

Something interesting happened over time.

As their confidence grew, they began contributing more during discussions. They challenged ideas, brainstormed solutions and shared perspectives that had previously remained unspoken.

Their technical ability hadn't changed—it had always been there—but the environment around them had.

Looking back, I don't think that manager simply recognised talent.

He created an environment where talent could become visible.

That investment didn't just benefit the individual. It benefited the customer, strengthened the team and improved the organisation.

Great managers don't wait for great people to become visible. They help make them visible.