Acknowledgement: Many thanks to my friend and partner in business, Pierre Hervouet, who introduced me to Hum Hum.

Imagine you are paid to solve a dull task: you get a sheet of random letters and must circle specific pairs, then hand the sheet to an experimenter. The pay decreases with each sheet you complete, so each new sheet is a slightly worse deal.

Now change only one thing: how the experimenter treats your work.

• In condition 1 – Hum! Hum! – the experimenter takes your sheet, looks at it briefly, mutters a neutral “hum hum,” and places it on a pile.
• In condition 2 – Indifference – the experimenter takes the sheet without looking at it and silently places it face down on a pile.
• In condition 3 – Shredder – the experimenter takes the sheet and feeds it directly into a shredder without looking at it at all.

Nothing else changes: same task, same pay schedule, same room.

What happens?

• In the Hum! Hum! condition, participants on average complete more sheets than in the other two conditions and accept lower pay before they stop.
• In the Indifference condition, people give up earlier: if nobody even glances at the work, its meaning collapses.
• In the Shredder condition, motivation drops dramatically: watching your work destroyed in front of you is a powerful signal that it doesn’t matter.

The “Hum! Hum!” – no praise, no speech, just a brief acknowledgment – is enough to change behavior and perceived value of the work.

This logic is directly inspired by Dan Ariely’s studies on acknowledgment and meaning at work, in which he showed that the presence or absence of minimal recognition can strongly affect how much effort people invest, even when financial incentives are fixed.

---

The invisible employee: recognition as a human need

The lesson from these experiments is simple and uncomfortable: people do not work only for money or rational trade‑offs. They also work for something far more fragile: the feeling that their effort is seen and that it counts for someone.

This need for recognition is not a soft “nice to have”; it is a core human and social need:

• Contemporary leadership and motivation research shows that recognition sits alongside inclusion, fairness, and caring as a fundamental psychological need in organizational life.
• Large‑scale engagement studies repeatedly find that employees who feel appropriately recognized show higher productivity, profitability, and lower absenteeism and turnover.
• Leaders rated highly on recognizing others are consistently evaluated as more effective overall, and their teams are more engaged and committed.

In my own slide deck on recognition, I summarize some of this evidence: engaged employees contribute to 20% higher productivity and 20% higher profitability, alongside significant reductions in absenteeism and turnover. Companies that systematically recognize people report up to a 3x higher return on equity compared to those that do not.

And yet: a survey snippet in the same deck shows that around 75% of managers do not systematically apply acknowledgment practices, despite this clear value.

That gap between “we know it matters” and “we don’t do it” is where the human paradox emerges.

---

Why being acknowledged feels both good and… threatening

When I run the “Hum! Hum!” exercise and follow‑up practices, I ask participants:

“What emotions do you associate with being acknowledged?”

The answers cluster around two poles:

• Positive: happy, proud, inspired, moved, valued, touched.
• Uncomfortable: embarrassed, awkward, self‑conscious, suspicious, shame, fear of appearing cocky, fear of jealousy.

In other words, people:

• Deeply enjoy and need acknowledgment – they feel more valued and connected when they receive it.
• Simultaneously feel exposed, vulnerable, and socially at risk in the moment they are seen.

Social psychology and leadership research help explain this tension:

• Recognition satisfies esteem and belonging needs, but it also increases visibility and potential judgment, which can threaten perceived psychological safety.
• Many professionals have internalized rules like “don’t brag,” “don’t stand out,” or “don’t make others jealous,” which create an internal “little voice” that polices their desire to be seen.
• In cultures where recognition is scarce or politicized, people learn that visibility is dangerous: attracting envy, scrutiny, or extra expectations, so they prefer to keep their heads down, even while craving acknowledgment.

This is the paradox:

“I want to be recognized – but I also want to be safe.”

So people adopt subtle hiding strategies: they downplay their contribution, deflect praise, or prefer to be invisible rather than risk awkwardness, jealousy, or accusations of being “cocky.”

---

Recognition, hiding, and organizational systems

Look at the three experimental conditions not just as lab tricks but as metaphors for real organizational patterns:

• Hum! Hum! organizations
  Work is seen, even briefly. Deliverables are acknowledged. People’s names are attached to contributions. Regular rituals (reviews, retrospectives, kudos boards) make contributions visible. In such systems, people are more willing to invest discretionary effort and even accept short‑term trade‑offs because their work carries meaning beyond the paycheck.
• Indifference organizations
  Work is technically accepted but rarely acknowledged. Reports disappear into email black holes. Stakeholders barely look at deliverables. Performance reviews focus mainly on gaps. People feel like “invisible employees.” The system doesn’t shred their work, but it quietly erases the emotional value of their effort through silence and neglect.
• Shredder organizations
  Work is openly invalidated, discarded, or undone without explanation. Decisions shift abruptly, projects are canceled without acknowledgment of the effort invested, and leadership re‑writes history without crediting those who tried. Here, the message is clear: “Nothing you do here matters for long,” and motivation collapses.

In my deck, I explicitly connect recognition to Agile practices and culture:

• Agile is described as alignment, focus, value, feedback, collaboration, communication, frequent delivery, and visibility.
• Rituals such as review meetings, retrospectives, kudos systems (e.g., KudoBox), and celebration practices are presented as structural supports for acknowledgment.

These are not “soft” add‑ons. They are the systemic equivalent of the “Hum! Hum!” condition: repeating patterns where the organization briefly but clearly says, “We see this. It matters.”

---

The traps of acknowledgment: flattery, formulas, and the T2P2S recipe

Because recognition is so powerful, it can also go wrong very quickly.

In the slides, I name several traps:

• Flattery – empty, generalized praise (“You’re amazing!”) that feels manipulative rather than genuine.
• The sandwich – “good–bad–good” feedback that people recognize as a technique, not a real acknowledgment.
• Generic thanks – over‑used phrases (“Great job, team!”) with no connection to the person or the actual effort.

To counter these, I propose a simple recipe, borrowing the metaphor of a taco casserole:

T2P2S – Timely, Personal, Proportional, Sincere, Specific

Well‑crafted acknowledgment:

• Is Timely – close to the event, when the effort is still fresh.
• Is Personal – addresses the person, not an anonymous group.
• Is Proportional – neither over‑nor under‑done compared to the effort and impact.
• Is Sincere – aligned with what you truly think and feel, not just a technique.
• Is Specific – naming the concrete behavior or contribution that mattered.

This recipe helps leaders avoid performative praise and instead deliver acknowledgment that truly feeds the human need for recognition without triggering as much suspicion or discomfort.

---

From experiment to practice: design choices for leaders

So what can leaders, coaches, and organizations do with all this?

1. Recognize the need behind performance
   Stop treating recognition as a bonus after “real work” and start seeing it as a non‑negotiable nutrient for effort, learning, and resilience.
2. Design Hum! Hum! moments into the system
   • Short, regular review rituals where work is explicitly seen.
   • Recognition “grooming” sessions where leaders and peers intentionally look for contributions to acknowledge (not just problems).
   • Simple tools like Kudo cards or digital kudos walls embedded into normal workflows.
3. Respect the ambivalence
   When people feel uncomfortable receiving acknowledgment, don’t pathologize it. It reveals the double bind between craving recognition and wanting safety. Offer different channels: public, small group, one‑to‑one, written – so individuals can choose what feels safe enough.
4. Model healthy vulnerability as a leader
   Leaders can normalize both sides of the paradox by:
   • Openly acknowledging others and explaining why it matters.
   • Allowing themselves to be acknowledged without deflecting or turning it into a joke – simply saying “Thank you, it means a lot” already changes the norm.
5. Audit where you are: Hum! Hum!, Indifference, or Shredder?
   Use Ariely’s logic as a diagnostic lens:
   • Where in our organization do people feel acknowledged (Hum! Hum!)?
   • Where do we practice silent indifference?
   • Where do we shred people’s work – cancel projects, reverse decisions, ignore efforts – without any acknowledgment of what was invested?

The answers will often explain more about engagement, turnover, and “quiet quitting” than any formal strategy document.

---

Why this matters now

In a world of constant transformation, agile initiatives, and pressure for performance, the temptation is to optimize everything except the human experience of being seen. Yet the “Hum! Hum!” experiments remind us that people’s willingness to go the extra mile – to learn, to adapt, to stay – depends profoundly on whether someone, somewhere, genuinely recognizes their effort.

At the same time, the emotional data from acknowledgment exercises shows that recognition is not frictionless: it touches shame, jealousy, fear of exposure, and complex histories around value and worth.

If we want agile, adaptive, and humane organizations, we must learn to hold this paradox:

• Designing systems that generously acknowledge contribution.
• Creating cultures where it also feels safe to be seen.

Because in the end, what keeps people engaged is rarely the salary band alone. It is the quiet, repeated message:

“I see you. What you do matters here.”

That is the true power – and responsibility – of acknowledgment.

---

Selected references

• Ariely, D. (2012). The (honest) truth about dishonesty: How we lie to everyone—especially ourselves. (Chapter on meaning and acknowledgment in work; experimental evidence on the impact of recognition on motivation).
• Ariely, D., Kamenica, E., & Prelec, D. (2008). “Man’s search for meaning: The case of Legos.” Journal of Economic Behavior & Organization. (Foundational experimental work on acknowledgment and meaning at work).
• Gostick, A., & Elton, C. (2007). The Carrot Principle: How the best managers use recognition to engage their people, retain talent, and accelerate performance. (Global studies on recognition, engagement, and performance; cited as “The Carrot Principle” in the slide deck).
• Gostick, A., & Elton, C. (2010). The Orange Revolution: How one great team can transform an entire organization. (Team‑level impact of recognition and positive culture).
• Littlefield, C. – AcknowledgementWorks. (Contributions to acknowledgment practices, exercises, and emotional mapping around being acknowledged; credited in the slide deck).
• “Recognition (Acknowledgement) – The Neuroscience of Recognition.” The Happiness Index (2024). Overview of how acknowledgment affects wellbeing, engagement, and business outcomes.
• “The Power of Personalized Leadership: Addressing Team Members’ Unique Psychological Needs.” BrainFirst Institute (2025). Links between recognition, psychological needs, and leadership behavior.
• “Leadership as a determinant of need fulfillment.” Frontiers in Psychology (2024). Discusses how leadership behaviors satisfy core psychological needs such as relatedness, competence, and autonomy.
• “Psychology of Employee Recognition.” Team Brandscape (2025). Summarizes research on how and why recognition practices influence engagement and retention.

(Experimental and practice‑oriented content, figures, and exercises referenced in this article are drawn from the slide deck “Recognition – The philosopher’s stone of every improvement in the Agile team and beyond.”)