The Hidden Economy of Recognition

There is a resource circulating through every organization that rarely appears in its metrics, dashboards or reports-yet people notice immediately when it disappears.

Organizations measure almost everything. Performance. Engagement. Absence. Turnover. Productivity. Skills. Collaboration. Leadership effectiveness.

Yet there is another organizational resource that moves quietly from person to person every day. It costs almost nothing to produce, but its absence may profoundly alter how people experience work.

Recognition.

Not recognition in the conventional HR sense of awards, bonuses, employee-of-the-month programs or corporate praise. Something much more fundamental. The experience of being noticed by another human being.

Long before employee experience became a discipline, psychiatrist Eric Berne introduced an intriguing idea through Transactional Analysis. Berne argued that human beings possess what he called recognition hunger: a need for acknowledgment from others. In his framework, social recognition is exchanged through strokes-units of interpersonal acknowledgment that can range from affection and approval to criticism and disagreement (Berne, 1961, 1964). Berne's formulation is striking because recognition does not necessarily mean praise. Even negative acknowledgment can satisfy something that complete social invisibility cannot. This produces an uncomfortable proposition for organizations.

Perhaps the opposite of recognition is not criticism. Perhaps it is invisibility.

An employee whose work is challenged is at least participating in the social reality of the organization. Someone has noticed the work. Someone has processed it. Someone has decided that it matters enough to respond.

But consider another employee.

She delivers the analysis. No reaction. She raises an idea in a meeting. The conversation moves on. She sends a recommendation. Silence.

She is rarely asked what she thinks. Her manager does not actively mistreat her. Her colleagues do not openly exclude her. Her performance evaluation may even say that she is doing perfectly fine. Nothing dramatic has happened. And that is precisely the problem.

She may be becoming organizationally invisible.

Berne's recognition hunger was developed within a psychotherapeutic framework, not as a theory of organizations. We should therefore resist pretending that Transactional Analysis directly predicts modern workplace outcomes.

But the underlying question has aged remarkably well.

What happens to people when the social environment stops acknowledging their existence and contribution?

Decades of research from other theoretical traditions make that question difficult to dismiss. Baumeister and Leary's influential review argued that forming and maintaining meaningful interpersonal bonds represents a fundamental human motivation. Their belongingness hypothesis describes a need for recurring positive interactions embedded within stable relational bonds rather than occasional superficial contact (Baumeister & Leary, 1995).

Organizational research arrives at related conclusions from different directions.

Eisenberger and colleagues introduced perceived organizational support as employees' general belief about whether the organization values their contribution and cares about their well-being (Eisenberger et al., 1986). Brun and Dugas later argued that employee recognition should be understood not merely as an HR practice but also in relation to fundamental individual needs, while emphasizing that recognition itself is considerably more complex than conventional management practice often assumes (Brun & Dugas, 2008).

Grant and Gino demonstrated something equally interesting experimentally. Expressions of gratitude increased subsequent prosocial behavior, and their work identified feelings of social worth as an important psychological mechanism through which gratitude influenced behavior (Grant & Gino, 2010).

Different theories. Different methodologies. Different constructs.

But there is a common signal underneath them. Human beings continuously infer their social value from how others respond to them.

That makes recognition more than an HR intervention. It makes recognition a form of social information. Every question communicates something. Every invitation communicates something. Every request for advice communicates something. Every acknowledgment communicates something.

And silence communicates something too.

Organizations usually become concerned when disengagement becomes visible. Performance declines. Absence increases. Complaints appear. Conflict emerges. Someone begins searching for another job.

But what if the important change happens earlier?

Imagine an employee repeatedly contributing ideas that receive little acknowledgment. After some time, the employee stops offering them. From the organization's perspective, nothing obvious has been lost because the ideas that were never expressed cannot appear in a dashboard.

This connects recognition to another major organizational phenomenon: employee voice.

Morrison defines upward voice around employees voluntarily communicating suggestions, concerns, information about problems and work-related opinions to people higher in the organizational hierarchy. Silence, conversely, deprives organizations of potentially useful information (Morrison, 2014).

Amy Edmondson's research on psychological safety similarly showed that teams differ in whether members believe interpersonal risk-taking is safe, with psychological safety associated with team learning behavior (Edmondson, 1999).

This suggests a provocative possibility.

Before employees become silent, they may first learn that speaking produces no meaningful social response.

Not punishment. Not rejection.

Nothing.

And nothing can be extraordinarily informative. An organization does not have to tell someone, Your opinion does not matter.

It can teach the same lesson simply by repeatedly failing to respond.

Most organizations conceptualize recognition vertically.

Manager → Employee.

That assumption is understandable, but socially incomplete. Employees do not experience organizations exclusively through their managers. They exist inside networks of colleagues, experts, friends, informal leaders, project partners, mentors, brokers and communities.

Recognition therefore does not merely move down the hierarchy. It moves through the network. And once we make that conceptual shift, a different analytical possibility emerges. Instead of asking only whether employees receive enough recognition, we could ask:

How is recognition distributed across the organization?

That is a network question.

Organizational Network Analysis already demonstrates that an employee's position within informal relationships can contain information that formal organizational charts cannot provide. Sparrowe and colleagues, for example, found individual job performance positively related to centrality in advice networks in their field study of 190 employees across 38 work groups (Sparrowe et al., 2001). Burt's work on structural holes showed how brokerage positions connecting otherwise separated groups can provide access to diverse information and opportunities, with brokers in his study more likely to have ideas recognized as valuable (Burt, 2004).

Now imagine applying network thinking not only to advice, collaboration, knowledge or innovation, but to recognition itself. An organization might discover employees who receive acknowledgment from many different parts of the network. Others may constantly provide recognition while receiving very little themselves. Some managers may distribute acknowledgment broadly across their teams, while others unconsciously concentrate it around two or three trusted employees. Some departments may be internally rich in recognition but almost invisible to the rest of the organization.

And some employees may occupy a particularly dangerous position:

high contribution, low recognition.

Their work matters. Their expertise matters. Perhaps many processes depend on them. But the social network around them does not consistently communicate that they matter. Traditional HR metrics may never reveal this discrepancy.

A network might.

This leads to a concept worth investigating empirically: recognition inequality.

Two employees can work for the same company, report to the same manager, receive comparable salaries and operate under identical HR policies while inhabiting radically different social organizations.

One employee is regularly consulted. Her ideas generate discussion. Colleagues ask for her judgment. Leaders mention her contributions. People respond when she speaks.

The other employee receives dramatically less social acknowledgment. On the organizational chart they occupy comparable positions. Inside the informal organization, they may live in different worlds. This matters because network research repeatedly demonstrates that relationships and structural position are not distributed equally. Access to advice, information and brokerage opportunities differs across individuals, and those differences can be associated with meaningful organizational outcomes.

Why should we assume recognition is distributed equally?

There is little reason to. In fact, recognition may follow the same cumulative logic that governs other social resources. People who are already visible may attract more interaction. More interaction creates more opportunities to demonstrate competence. Demonstrated competence attracts more requests for advice. Requests create further visibility. Visibility generates additional recognition.

Meanwhile, peripheral employees may experience the reverse process. Less interaction. Less opportunity to contribute. Less acknowledgment. Less visibility. Eventually, the organization may conclude that they contribute less.

The disturbing possibility is obvious:

What if organizational visibility partly creates the performance perceptions that we later treat as objective evidence of talent?

This is why I believe recognition should eventually become a serious subject for People Analytics and Organizational Network Analysis.

Not because organizations need another engagement question. But because recognition may have an architecture. It may have hubs. It may have brokers. It may have isolated nodes. It may have departmental boundaries. It may have reciprocity. It may have asymmetry. And it may have concentration.

One could imagine constructing a recognition network from carefully designed relational questions and examining who receives acknowledgment, who provides it, where recognition becomes trapped inside silos and which employees remain structurally invisible.

The analytical possibilities become even more interesting when recognition is combined with other networks. An employee could be highly central in the knowledge network yet peripheral in the recognition network. Another could receive enormous recognition despite relatively low centrality in actual workflow. A manager might be central in formal communication but almost absent as a source of recognition. A broker connecting departments could carry enormous relational value while receiving little acknowledgment from either side.

These are not merely interesting network patterns. They are organizational hypotheses. And they are testable.

Workplace ostracism research provides a particularly important warning.

Ostracism is typically conceptualized as being ignored or excluded by others. A 2021 meta-analysis covering 95 independent samples and 26,767 participants found workplace ostracism significantly related to a broad range of employee attitudes, well-being indicators and behaviors. The analysis also found evidence for organization-based self-esteem as a mechanism connecting ostracism with outcomes including commitment, job satisfaction and performance (Li, Xu, & Kwan, 2021).

Recognition deprivation and ostracism should not be treated as identical constructs. But placing them beside each other reveals something important. Organizations tend to search for negative events.

Harassment. Conflict. Toxic leadership. Incivility. Bullying.

Perhaps we should also investigate the systematic absence of positive social signals. Because organizational damage may occur without anyone doing anything obviously wrong.

Nobody attacks the employee. Nobody humiliates them. Nobody excludes them from the payroll. Nobody writes a hostile email. They simply become less and less present in the attention of others. And eventually they may reciprocate.

They stop asking. Stop suggesting. Stop challenging. Stop volunteering. Stop connecting.

Perhaps, finally, they leave. The resignation is recorded. The network process that preceded it is not.

HR frequently asks employees:

Do you feel recognized for your work?

It is a useful question. But it compresses an inherently relational phenomenon into an individual score.

Perhaps the more interesting questions are:

Recognized by whom? How frequently? For what? And who receives almost none?

The difference is fundamental. The first question produces a percentage. The second set of questions begins to reveal a social system.

And that may be where the next generation of People Analytics needs to go. From measuring isolated employees to understanding relational environments. From asking whether recognition exists to mapping where it flows. From recognition programs to recognition networks. From employee engagement scores to the architecture through which people continuously learn whether their presence matters.

Berne gave this human need a name more than sixty years ago. Modern organizational science has given us sophisticated constructs around belonging, support, psychological safety, voice, social worth, ostracism and social networks. The opportunity now is not to choose among them. It is to connect them.

Because somewhere inside every organizational network there may be an employee who is competent, productive and formally included-yet gradually disappearing from the social reality of the organization.

Disengagement may therefore be only the visible end of a much quieter social process. Long before an employee withdraws from the organization, recognition may already have begun to disappear from the employee’s everyday experience of work.

People Analytics captures the outcome. A recognition network might reveal the process.

An employee does not become invisible on the day they leave. In some organizations, invisibility may be what happens first.

Baumeister, R. F., & Leary, M. R. (1995). The need to belong: Desire for interpersonal attachments as a fundamental human motivation. Psychological Bulletin, 117(3), 497–529. Berne, E. (1961). Transactional Analysis in Psychotherapy. Grove Press.

Berne, E. (1964). Games People Play: The Psychology of Human Relationships. Grove Press.

Brun, J.-P., & Dugas, N. (2008). An analysis of employee recognition: Perspectives on human resources practices. The International Journal of Human Resource Management, 19(4), 716–730.

Burt, R. S. (2004). Structural holes and good ideas. American Journal of Sociology, 110(2), 349–399.

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

Eisenberger, R., Huntington, R., Hutchison, S., & Sowa, D. (1986). Perceived organizational support. Journal of Applied Psychology, 71(3), 500–507.