How to recognise who contributed what, without rankings

To recognise contribution fairly, describe what each person did instead of deciding who did best. Agree a short list of contribution roles at the start, record who played which role as the work happens, and make that record visible to the people whose opinion matters to the contributor. Recognition then rests on facts people can check, not on who presented at the final meeting.

Why rankings backfire in innovation work

Leaderboards, points and "innovator of the month" feel motivating at launch. In innovation work they cause three predictable problems.

First, they reward the visible parts of the work. The person who presents the prototype gets the credit; the person who ran fifteen interviews to find the real problem does not. Second, they punish good judgement. The colleague who argued, with evidence, that a project should stop has saved the organisation money, but has "lost" in any ranking that counts launches. Third, they turn collaborators into competitors. When there is a top spot, people start guarding ideas and avoiding risky assignments.

Innovation depends on people sharing half-formed ideas and doing unglamorous research. Anything that makes them compete for a single ranking works against both.

The steps

1. Agree what counts as a contribution

Before the work starts, write down the kinds of contribution the work needs. Keep it to eight to twelve roles, in plain words. For a typical innovation project:

• Framed the problem
• Ran research (interviews, observation)
• Synthesised findings
• Generated or developed ideas
• Built a prototype or test
• Ran the test and read the results
• Brought in people, data or access
• Facilitated sessions
• Made or secured a decision
• Led the handover into operations
• Challenged an assumption that changed the direction

The last one matters. Naming "challenged an assumption" as a contribution makes dissent visible and valued.

There is a precedent for this. Academic publishing, where author order used to imply a ranking, now often uses the CRediT taxonomy (ANSI/NISO Z39.104-2022): fourteen named contributor roles, such as "investigation" and "methodology", so each author's part is described rather than ordered. You do not need its exact list, but the principle transfers.

2. Separate roles from responsibility

A RACI tells you who is accountable and who is responsible for a task in advance. A contribution record tells you who actually did what, afterwards. Keep both. Comparing them is often revealing: the person accountable on paper may not be the person who carried the work.

3. Record as you go, not at the end

Memory at the end of a project is unreliable and favours whoever is most recent or most senior. Instead, at the close of each session or stage, spend two minutes noting who did what against the agreed roles. Let people add their own entries and confirm others'. If an entry is disputed, resolve it then, while everyone remembers.

4. Make the record visible to the right people

Recognition only works if someone who matters sees it. Decide who that is: the contributor's line manager, the sponsor, a promotion panel. Share the record with them at natural points, such as the end of a stage or a quarterly review. A stakeholder communication plan is a simple way to make sure this happens rather than being forgotten.

5. Use the record in retrospectives

During each retrospective, look at the record together. Ask: whose contribution was essential and easy to miss? Which roles were empty? Empty roles tell you about capability gaps; if nobody ever "synthesised findings", the team is collecting research and not using it.

6. Say thank you specifically

General praise ("great work, team") is pleasant and quickly forgotten. Specific acknowledgement lands: "Noura's interviews with night-shift staff are why we changed the problem statement." Leaders should do this in front of the people whose regard the contributor values. It costs nothing and is remembered for years.

7. Connect the record to how people grow

Over time, each person accumulates a record across several projects. That record is useful in development conversations: it shows what someone has practised, what they have not tried yet, and what they might guide others in. Use it to plan the next assignment, not to sort people into tiers. The career angle is covered in a career path for innovators inside the organisation.

Illustrative example: a hospital trust's discharge project

Illustrative. The organisation is invented.

A hospital in Manchester ran a twelve-week project to reduce delays when patients were ready to leave. Seven people took part: two nurses, a pharmacist, a porter supervisor, an IT analyst, a patient representative and a project lead.

At the first session, the team agreed nine contribution roles, including "challenged an assumption". After each weekly session the project lead spent two minutes on the record. By week four, a pattern was visible: the pharmacist had been recorded under "ran research" and "challenged an assumption" three times. Her observation that discharge medicines were batched only twice a day was what moved the team away from its original idea of a new discharge checklist.

At the final review, the sponsor did not announce a "star of the project". She read out three specific contributions, including the pharmacist's, and the record went to each person's line manager. Two months later the pharmacist was asked to guide a similar project in another ward, based on what the record showed she was good at.

Do's and don'ts

Do

• Agree contribution roles before the work starts.
• Include roles for research, challenge and handover, not only ideas.
• Record in short bursts during the work.
• Let people confirm or correct their own entries.
• Share the record with managers and sponsors at set points.
• Thank people for something specific.

Don't

• Publish leaderboards, points tables or "top innovator" lists.
• Count the number of ideas someone submitted as their contribution.
• Give all the credit to whoever presents at the end.
• Wait until the project closes to reconstruct who did what.
• Turn the record into a score or a rating.
• Treat an empty role as someone's failure; treat it as a gap to fill.

When people ask for a competition anyway

Sometimes a sponsor wants an award. You can keep that without ranking people. Recognise pieces of work, not individuals, and describe them by what they achieved: "the test that saved us building the wrong thing". Or recognise categories of contribution: "best piece of research this year". Make sure the evidence for any award comes from the contribution record, so the choice is grounded in what happened. Hackathons have their own rules for judging entries; see judging criteria that pick the right winner. The point here is about colleagues, not competition entries.

Questions people ask

How do you recognise team members fairly when everyone contributed? Describe what each person did rather than who did most. A short agreed list of contribution roles, recorded during the work, lets everyone's part be named. People rarely object to a fair description; they object to being placed below someone else.

Are leaderboards good for employee engagement in innovation programmes? They can raise activity briefly, but they reward visible, countable actions such as submitting ideas, and discourage the research, challenge and follow-through that make innovation work. A visible record of contributions keeps people engaged without setting colleagues against each other.

How do you give credit to people who stopped a bad project? Name it as a contribution in advance: "challenged an assumption" or "read the test results". When the record shows that someone's evidence led to stopping work, thank them for it specifically and in front of the sponsor. Stopping early is one of the most valuable things a team can do.

Methods and further reading

A RACI sets expectations, a retrospective is where the record gets used, a feedback capture grid helps structure what colleagues say about each other's work, and a stakeholder communication plan makes sure the right people see it. For the wider picture, read how to build innovation capability in your team and why innovation champion networks fizzle out.