Read a sample: 1. Credit Is a Leadership Practice
The project update is almost over when the executive asks, “How did you get the launch back on track?”
You were the manager in the room. You helped set priorities, secured a decision, and kept the work moving. You also know that Elena found the problem in the handoff process, Marcus rebuilt the testing schedule, and Priya coordinated the customer-facing changes. You could say, “I brought the teams together and fixed the launch plan.” Nobody in the meeting might challenge you.
Or you could say, “Elena identified where the handoff was failing. Marcus revised the testing schedule, and Priya coordinated the customer-facing changes. I helped remove a decision bottleneck so they could move forward.”
Both answers are brief. The difference is what the audience learns.
In the first, the manager becomes the story. In the second, the manager still has a role, but the account reflects more of the work that produced the result. People who were not present become visible, and the executive gains a more useful understanding of how the problem was solved.
That choice is a leadership practice. It happens in project updates, performance conversations, emails, presentations, and informal discussions about who might be ready for a new opportunity. It is not limited to award ceremonies or moments when someone has done something extraordinary. Every time you describe a result, you make choices about which actions to mention, whose names to include, and how much confidence to place in your account.
Those choices do not need to be perfect. They do need attention.
Praise expresses approval. Credit attributes a contribution.
“Great work on the launch” may be sincere and encouraging. It tells the team that you value the outcome. It does not explain what anyone did. “Priya coordinated the customer-facing changes so the support team had consistent information before launch” gives listeners a clearer account of her contribution.
Recognition can include both. A manager might say, “Priya, thank you for coordinating the customer-facing changes. Your work helped the support team prepare for the launch.” The appreciation matters, and so does the description.
This distinction is useful because generous praise can coexist with poor attribution. A manager may frequently thank “the whole team” while repeatedly naming the same visible employees when discussing expertise or readiness for advancement. The team hears appreciation, but decision-makers receive a narrower picture of who contributed.
The opposite can also happen. A technically accurate list of names and tasks can sound transactional if it never conveys appreciation. Credit is not a replacement for thanks. It is the part of recognition that helps others understand the work.
A useful attribution usually answers three questions:
- Who contributed? Name a person or describe the group when doing so is appropriate.
- What did they do? Identify an action, decision, or piece of work rather than relying on a broad adjective.
- What did it make possible? Connect the contribution to its context or effect without claiming more than the evidence supports.
The final question requires care. “Marcus’s revised schedule gave the team a workable sequence for completing the remaining tests” is different from “Marcus saved the launch.” The first describes a plausible contribution. The second assigns him the whole outcome and may erase the people who performed the tests, resolved defects, or made the launch decision.
Accuracy is not a matter of making every sentence longer. It is a matter of selecting details that give a fair account.
Managers often occupy positions where information converges. You may receive updates from several people, summarize work for your own manager, and represent your team in meetings that contributors do not attend. That role gives you influence over the story others hear.
Some of that influence is explicit. You decide who presents a project, whose name appears in a report, and which examples you bring to a performance discussion. Other choices feel incidental: whose comment you repeat, whose work you describe as strategic, and whether you say “I,” “we,” or someone’s name.
None of these choices is inherently wrong. “I” can accurately describe a decision you made. “We” can accurately describe collective effort. Problems arise when familiar wording repeatedly conceals how the work was divided.
Imagine that your team resolves a recurring customer issue. You tell another leader, “We redesigned the process.” That may be a fair summary in a quick hallway conversation. If the discussion turns to who developed the solution, however, you can add detail: “The redesign was a team effort. Aisha analyzed the recurring cases, Ben proposed the new routing approach, and the support leads tested it with their teams.”
You do not have to turn every casual exchange into a complete project history. You do have to notice when a summary has become the only account people ever hear.
Your role also affects what you can see. A manager may observe the final presentation but not the early investigation that made it possible. You may know who gave the persuasive recommendation but not who assembled the information behind it. You may hear from confident employees more often than from colleagues whose work is less visible or whose roles keep them away from meetings.
This is not necessarily a character flaw. It is an information problem—and, if left unaddressed, a leadership problem. Good intentions cannot fill gaps in your knowledge. You need ways to notice the gaps before turning a partial view into a confident story.