Skip to content
Interface language: English
Imperium / Signal

Who received the thanks? Recognising work behind the scenes

Name the real contributions behind a shared result, from analysis and preparation to checking and presenting, without turning recognition into rankings or bonuses.

Article language: English

Fine white strands cross a wooden piece with gold-coloured teeth on a workbench.
In this article

The presentation went well. The client thanked the person who led it, the manager repeated the thanks at a team meeting, and the slides went into a shared folder. A small part of the story disappeared: who noticed that the data covered two different editions of the event, who found the right figures, and who rewrote the conclusions after the correction. The result had one visible host and several invisible contributors.

Imagine a company analysing registrations for a festival organiser. The presenter explains the result well. An analyst checked the data, a coordinator obtained the missing export, and an editor removed an unsupported comparison from the text. Their contributions differ. Saying “everyone did great” is kind, but it does not explain what made the result useful.

Recognition need not start with a prize. It can begin with an accurate sentence about the work done. Such a description also matters for the next assignment: it shows which activities and skills the company really needed. Without it, a manager may conclude that one person can prepare the next analysis, because that was the person visible on screen last time.

Say what someone did and what it made possible

“Thank you for your commitment” is neither a linguistic mistake nor a forbidden gesture. It is broad, though. In our example one might say: “After the editor's question, the analyst checked the event editions; that check let us correct the conclusion about changing interest before the presentation.” We can see what work was noticed and how it related to the result.

There is no need to claim that the whole project would certainly have failed without one person. That is a separate, often untestable story. Describe the observed contribution and its actual effect. Credit for heroically saving a project can obscure ordinary, systematic work that should have time allocated in every future assignment.

A contribution may involve preparation, checking, coordinating dependencies or explaining a result. Not all leave an output as visible as a finished slide. The coordinator who obtained the right export did not create the final analysis, but secured the material needed to do it. Naming that does not diminish the analyst's or presenter's role.

The U.S. Office of Personnel Management's account of recognition includes individual and group contributions and ordinary thanks for specific work. It concerns U.S. federal administration. We use the distinction between forms of recognition without importing its formal award rules into a Polish company.

The practical decision is therefore to establish what you are thanking someone for. Do not turn this into an investigation required before every kind remark. For a shared result, though, it is worth asking the presenter who helped prepare it and what they contributed. One question can complete a picture formed only from who was present at the presentation.

Visibility does not measure all the work

The meeting leader may be remembered most because that is when the audience encounters the result. Their contribution is real: they guide the conversation, answer questions and explain limitations. The problem starts when an organisation infers complete authorship from that visibility. Presenting and preparing are connected, but they are not the same work.

In a hybrid meeting (in Polish), some contributions may appear in a document, chat or response sent before the discussion. A manager in the room should not build the whole picture solely from the person they heard longest. Look at where the arguments, corrections and decisions later used by the team actually arose.

That does not mean counting every contribution. A short comment may change the basis of a conclusion. Another person may perform many essential checks that yield no dramatic discovery. An activity counter cannot explain those differences. A similar issue appears with work measures that encourage unwanted behaviour (in Polish): an easy measure can direct attention to the wrong goal.

In the fictional report, there is no need to assign everyone a percentage of credit. A simple distinction can be kept: who was responsible for analysis, who prepared the right data, who checked the text and who led the discussion. If several people solved the issue together, the description should show that. Artificial precision can be worse than an honest sentence about collaboration.

Recognition also reveals the work behind a result

Follow one correction in our example. The editor noticed a sentence about “growing interest” but did not remove it on a hunch. She asked the analyst about the scope of the comparison. The analyst checked the event editions, and the coordinator found an explanation of the files' origin. Only together did they establish what could be said. One name beside the correction would not capture the whole sequence.

A manager can ask what material clarified the issue and who was needed to obtain an answer. This reveals a dependency worth including in the next plan. Thanks do not replace organisational improvement. If an important check happened after hours because the deadline was poorly planned, public recognition alone will not provide time next time.

Do not reward only visible firefighting. A person who prepares correct sources from the outset may have no dramatic rescue story. Their contribution can be described through the checks made and material correctly prepared even when nothing needed fixing. Examine normal work, rather than noticing the background only when everyone must rescue a deadline.

When describing the result, separate an agreed role from additional help. The editor may have performed her regular checking task, while the coordinator took over a missing clarification once. Both can be named. The difference helps assess whether the division of work still reflects reality or the team regularly relies on another person's effort without planning for it.

Aeneia conceptual photography

What an experiment with public recognition shows

Bradler, Dur, Neckermann and Non described a field experiment on public recognition in which 363 people, mainly students, individually performed a one-off, paid three-hour data-entry task. After two hours, thank-you cards were unexpectedly given in randomly selected groups: depending on the condition, to everyone or to the top one or three performers. Compared with groups that received no recognition, the researchers observed improved subsequent performance under the conditions of the experiment.

This does not mean every company should choose a winner every two hours. A short task, a surprise distinction and ongoing expert collaboration are different situations. Our question is accurate recognition of contribution to a particular result. One study is not enough to design a competition, bonus or employee assessment system.

Before choosing public thanks, consider the recipient. Not everyone wants to discuss the details of their work in public or be presented as the person who fixed someone else's mistake. Agree on the scope and form in advance if appropriate. Recognition does not require revealing a client's confidential context or turning an internal explanation into a company anecdote.

In our example a manager can thank the whole team and name roles specifically without saying who first mixed up the files. If the cause needs discussion, that should happen in the appropriate setting. Thanks and analysis of an error serve different purposes. Combining them in a public scene can make both harder.

Correct an omission without a new exaggeration

Suppose the manager has already credited the entire result to the presenter. After a conversation, they learn of the others' work. They can return to the team with a specific correction: “Yesterday I mentioned only leading the presentation. Marta also checked the analysis, Jan supplemented the data, and Lena prepared the corrected text.” This corrects the record rather than dissolving the omission into a general “of course, thanks to everyone”.

The presenter can also complete the account of their own work. They need not disappear from the thanks or pretend they contributed nothing. They can say what they used and who prepared each part. For a shared result, this helps the audience identify the right people for further questions. Fair attribution remains useful after the meeting.

If the team disagrees about who performed an activity, do not settle it solely by confidence of delivery. Check the materials and ask about the particular part of the work. Sometimes two people refer to different stages. Sometimes someone helped with the reasoning without writing the final sentence. This calls for clarification, not automatically dividing credit in half.

Internal recognition is not consent to publish someone's name or a client's story. A B2B website case study (in Polish) requires a separate decision on the material's scope and approval. It cannot be inferred from someone being named in a team meeting. Audience, purpose and access to information differ.

Thanks do not assign the next duty

Suppose the coordinator helped obtain data because he knew the context of an earlier assignment. After the thanks, others start sending him every export problem. The company has just changed his work without discussing scope or availability. Accurately describing one act of help does not mean that person now owns the entire area.

The manager should separate recognition from such an assignment. They can say how the coordinator helped this analysis and separately establish who should handle similar needs later. If the company wants to use his experience more widely, it needs a real decision about the task and time. “You're the best at this” organises neither.

Likewise, an editor who found one discrepancy does not automatically become the person confirming every analysis. Keep the boundary of her contribution in the thanks, then deliberately plan how future results will be checked. Recognition will not become an unlimited queue of requests for the most helpful person.

An AI result also rests on people's work

In the festival report a tool may draft a description of the data. A person chooses the right source, checks its scope, removes an unsupported conclusion and decides whether to use the result. If the summary says only “AI wrote the report”, some of the work required to prepare it disappears. The company can no longer accurately assess the effort or skills needed for the next assignment.

For evidence behind claims in a B2B offer (in Polish), this gap can have a further effect. A company starts promising a fast result by counting generation time alone. Recognising checking work helps retain a connection between the claim and actual delivery. There is no need to portray every check as extraordinary heroism; it needs to be included in the task description.

When an expert becomes a leader (in Polish), their own visible output may cease to be the main result of their work. They help others recognise a problem, coordinate a dependency or secure an assessment. Such contributions also deserve specific description. A job title alone does not explain what the person actually did for the team.

Aeneia Audit can trace the respective roles of a tool and people in a particular AI use: preparing sources, verification and approval. Such material helps reveal work hidden behind the finished result. Decisions about how to thank people and organise the team remain with the company.

At the next review, begin with a short question about what supported the result. Perhaps the presenter really did most of the work. Perhaps you will learn about a contribution you had not seen. Either way, the thanks will rest on better evidence than memory of who held the slide remote.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear