Who Is Hanuman in Your Company?

Every company has people whose contribution is easy to notice. They present the plan, lead the meeting and receive the applause. Then there are people the organisation depends on in quieter ways. When a project stalls, colleagues find them. When pressure rises, they stay steady. They know how the system really works, yet they rarely advertise their importance.

That raises a useful question: who is Hanuman in your company?

The comparison should be used with respect. In the Ramayana, Hanuman is associated with strength, service, courage, loyalty and humility. In a workplace conversation, the metaphor points to someone whose capability may be greater than their visibility and whose effort is directed towards a purpose beyond personal credit. It is not a label to place on an employee, nor an invitation to turn devotion into unpaid labour.

A "Hanuman" at work may not have the loudest voice or the highest title. Their value becomes clear in moments such as these:

• a customer issue crosses three departments and nobody knows who should act
• an old process fails and the written guide is incomplete
• a new manager needs the history behind a sensitive decision
• a colleague is overwhelmed and needs practical help without public judgement
• a deadline is at risk and someone must separate the real problem from the noise

The dependable contributor often brings context, calm and follow-through. They may connect people who do not usually work well together. They may remember why a rule exists and also recognise when the rule no longer serves the work.

None of this means the person is flawless. It means their strength is easy to underestimate if the company measures contribution mainly through presentation, proximity to leaders or self-promotion.

Most organisations do not intentionally ignore dependable employees. Their systems simply make certain work easier to see.

Public wins are visible. Prevented problems are not. A dramatic recovery gets attention; the person who noticed the risk two weeks earlier may receive little credit. Managers remember who spoke in the review meeting, even when someone else did the analysis, coached the team or protected the client relationship.

Quiet contributors can also become victims of their own reliability. Because they rarely refuse, more invisible work comes their way: fixing handovers, onboarding colleagues, taking notes, calming conflict and remembering details. The organisation becomes dependent on them without changing their title, pay or development plan.

That is not recognition. It is extraction dressed as trust.

The goal is not to crown one employee as the office hero. It is to notice where strength, responsibility and trust already exist.

Ask practical questions:

Who do people seek when the process breaks?

Track where colleagues go for context and help. The answer may reveal informal expertise that does not appear on an organisation chart.

Who makes other people more effective?

Look beyond individual output. Who explains the problem clearly, shares knowledge and helps a colleague recover without taking over?

Who stays useful under pressure?

Calm is not the absence of concern. Notice who can name the risk, choose the next step and communicate without spreading panic.

Who carries responsibility without collecting credit?

Compare project accounts from different people. Does someone consistently recognise the team's contribution, admit their own part in a problem and close the loop after a decision?

Where would the team struggle if this person left?

This question exposes hidden dependencies. It should lead to recognition, knowledge sharing and succession planning, not another reason to keep the person in the same role forever.

Managers usually observe employees in a limited set of situations. A structured behavioural conversation can open a wider view of how someone approaches responsibility, pressure, collaboration and initiative.

Handwriting analysis can contribute themes for that conversation. It may prompt a manager to explore whether an employee prefers to support from behind the scenes, how they respond when authority is unclear or what happens when loyalty conflicts with a personal boundary.

Those themes are starting points. They should be checked against the employee's experience and workplace evidence. A report cannot tell you who deserves a promotion or who will act courageously in a future crisis. It can help a manager ask a question they might otherwise miss.

For example: "You often become the person others call when a project is stuck. Which part of that role uses your strengths, and which part has become an unfair burden?"

That question recognises contribution while leaving room for the employee to describe its cost.

Once a hidden contributor is recognised, companies often make a predictable mistake: they give them more rescue work.

Choose a better response.

First, name the contribution specifically. "You are a great team player" is pleasant but vague. Explain what the person did, what problem it solved and why it mattered.

Second, ask what they want. Dependability does not automatically mean a desire to manage people. They may want deeper expertise, broader authority, a different role or simply a fairer distribution of support work.

Third, reduce the dependency. Document the knowledge, pair the person with colleagues and create backup ownership. A promotion that leaves the old invisible workload attached is not genuine progress.

Fourth, connect responsibility to recognition. Review scope, title, compensation and access to development. If the business relies on work that is not in the job description, the role may need to change.

Finally, protect boundaries. Service is meaningful when it is chosen. Constant availability, emotional labour and crisis recovery should not become the price of being considered loyal.

The best lesson from the metaphor is not that every organisation needs one extraordinary rescuer. It is that strength can remain unnoticed until a difficult moment reveals it.

Create systems that notice contribution earlier. Ask peers who helps them do better work. Review invisible coordination alongside individual targets. Rotate critical responsibilities. Give managers language for discussing behaviour without confusing confidence with capability.

When dependable people are recognised, developed and supported, the company becomes less dependent on heroic effort. Their example can shape how the whole team works.