Talent audits for small businesses

A talent audit is the twice-a-year sit-down where you decide, role by role, who is ready for more, who needs support, where the team is too thin, and what you are going to do about it. In a company of ten to a hundred and fifty people it is usually done once, badly, right before a hire or right after someone resigns.

It does not need a framework or a consultant. It needs the role written down, the evidence from the last months, and a record of what you decided.

When a small business actually needs one

• Before a hire, to see whether the gap is really a missing person or an unclear role.
• When the founder is still doing work that belongs to someone else, and nobody has noticed the overlap.
• After a resignation, to work out which parts of the role move where.
• Before a board update or a funding round, when people decisions have to be explained rather than described.
• When two people are doing the same job, and that only becomes obvious at review time.

Why audits break between ten and a hundred and fifty people

Up to about ten people you can hold the whole picture in your head: who delivers, who is overloaded, who is ready for more. After the first managers join it splits. Each manager remembers a different part, job descriptions list tasks instead of ownership, and nobody agrees what the role asks for. By the time you sit down you are comparing memories instead of work — so the audit turns into an argument about perception and the decision gets postponed again. The cause is rarely a lack of goodwill. It is the missing record.

The four steps that turn it into a decision

01 — Write the role down before you judge the person. An audit is only fair if the role was clear first. Write down what the role owns, where its boundaries are and what success looks like over the next two quarters, and do it with the person, not about them. This is the conversation where the overlap with your own work as founder usually becomes visible.

02 — Collect evidence as it happens, not the week before. Impressions from the last three weeks crowd out nine months of real work, so the person who carried the quarter gets judged on their quietest month. A short note after a project or a one-to-one is enough. What matters is that the record exists before the audit starts.

03 — Prepare the comparison, then let the manager decide. Bring the role definition, the evidence and a view of the peers into the room. A prepared recommendation makes the conversation faster and more honest, but the manager still makes the call. That is the difference between a decision you can defend and a score handed down by a tool.

04 — Write the outcome down, with a date. Whatever you decide — a new responsibility, a raise, more support, a different role — record it on the day. The next audit then starts from the last agreement instead of from memory, and the founder and the manager tell the same story.

What to do with the outcome

An audit that ends in a rating and no change teaches your team that the process is theatre. Every conversation should leave one of four things behind: a clearer role, more support, a different scope, or an honest conversation about fit. Write down which one it was, date it, and keep it on the person. After two or three cycles that record answers the question you get asked most — what happened last time — and it shows how someone grew, what you promised, and what you actually delivered.

What a good audit leaves behind

• A clearer role, or more support, or a different scope, or an honest conversation about fit — one of the four, named.
• A written decision on the person's record, dated, so the founder and the manager tell the same story.
• A view of the pipeline: who is ready for more, and which role is thin — before it becomes a resignation.

The short version of the method fits on one page, and that is the point: role first, evidence while it happens, the manager decides, the outcome is written down.