liveBook · Manning

Public recognition

As explained in Think Like a Software Engineering Manager

Public recognition is acknowledgment of an individual’s contributions or achievements in a setting visible to other people.

Public recognition acknowledges an individual’s contribution where other people can see it. Unlike private recognition, it increases visibility, shows what excellent work looks like, and can connect the contributor with collaborators. section 6.2.4 section 6.3.2

Use public recognition to:

  • Explain the problem, challenges, actions, and impact rather than offering vague praise. section 6.2.4
  • Set a visible benchmark that helps teammates understand and repeat valuable behaviors. section 6.2.4
  • Choose an audience and channel, such as Slack, an all-hands meeting, a retrospective, or a formal recognition platform. section 6.3.2
  • Ask about individual preferences first, since some employees prefer private recognition or a combination of private and public acknowledgment. section 6.3.2

Making technical work visible

An engineer publicized a successful testing infrastructure. Multiple teams then requested collaboration, creating mutually beneficial opportunities. A manager can strengthen the message by describing the technical problem, the engineer’s approach, and the resulting effect. section 6.3.2 section 6.1.1

Public praise is not automatically the best choice. Match visibility to the person’s preferences, keep recognition specific and fair, and preserve recognized achievements for later performance reviews. section 6.3.2 section 6.5

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains purposes, channels, audience tailoring, preference checks, and trade-offs with private recognition.
Examples
Uses manager praise for a technical solution, a publicized testing infrastructure, Slack shout-outs, all-hands meetings, and recognition platforms.
What it assumes
Assumes responsibility for individual feedback and recognition while teaching managers to account for differing validation preferences.
What you can do after
Apply it via Slack, all-hands meetings, retrospectives, or formal recognition tools while tailoring visibility to the recipient.
How it connects
Connects public recognition with private recognition, feedback, collaboration, performance reviews, and rewards and recognition.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.