Role Scorecard Design for a Small Shop

Why this matters

Most small-shop job descriptions are useless: a wall of tasks nobody reads after the first week, with no way to tell if the person is actually winning at the role. A scorecard fixes that. It is a one-page definition of a role built around outcomes, not chores - what this person is responsible for producing, and the few numbers that prove they are producing it. Get this right and three things get easier at once: hiring the right person, knowing if a current person is succeeding, and the eventual handoff of work off your own plate. Without it, "good job" and "this isn't working" are both just gut feelings you cannot defend.

Step 1: Name the mission of the role in one sentence

Start with why the role exists, in plain language. Not the title, the point.

• Dispatcher: "Keep every tech full, on time, and sent to the right job with what they need."
• Office lead: "Make sure every job gets quoted, scheduled, invoiced, and paid without falling through a crack."
• Service tech: "Fix it right the first time and leave the customer wanting us back."

If you cannot write the mission in a sentence, you do not yet know what you are hiring or holding someone to. The mission is the north star the rest of the scorecard hangs on.

Step 2: List the outcomes, not the tasks

This is the heart of it. An outcome is a result the person owns; a task is an activity. "Answer the phone" is a task. "No lead goes uncontacted past same-day" is an outcome. Write three to six outcomes per role, each a result you could verify.

• Outcomes are stated as a finished state, not an action: "Trucks are stocked for tomorrow's jobs by end of day," not "stock the trucks."
• They are the things that, if all true, mean the role is being done well.
• Tasks still exist, but they live in a checklist or SOP, not the scorecard. The scorecard is about results; the SOP is about how.

Keep it to a handful. A scorecard with twenty outcomes is a task list wearing a costume, and nobody can be held to twenty things at once.

Step 3: Attach a measure to each outcome

For each outcome, name how you would know it is happening - the simplest signal that works. Some are hard numbers, some are yes/no checks, some are reviewed by eye.

• "Trucks stocked by end of day" - check: any morning a tech is missing a stocked item? Aim for near-zero.
• "Leads contacted same-day" - measure: percent of leads first-contacted within the day.
• "Callbacks low" - measure: callback rate over the month.

Pick the fewest measures that genuinely tell the story. The wrong move is a dashboard of fifteen metrics; the right move is three or four the person can actually move and you can actually watch. If a measure cannot be influenced by the person, it does not belong on their scorecard.

Step 4: Set the standard - what good looks like

A measure with no target is just trivia. For each one, state the bar: the level that counts as winning. Make it realistic from where the shop actually is, not a fantasy.

• Set targets you would genuinely be happy with, not perfection. A standard nobody can hit teaches people to ignore the scorecard.
• Where you do not have history, set a starting bar and adjust after a month of real data.
• Distinguish "meets" from "exceptional" so a strong performer has somewhere to aim.

The standard is what turns "I think you're doing fine" into "you hit the bar on three of four, let's work the fourth." That is a conversation both sides can have honestly.

Step 5: Fit the role to the person (and spot mismatches)

Once outcomes and standards exist, you can ask the real question about a current team member: are they hitting the scorecard? This separates two very different problems that owners constantly confuse.

• Right person, wrong seat: good employee, but the role's outcomes do not fit their strengths. The fix is to reshape the role or move them, not to coach harder.
• Wrong fit for the seat: the outcomes are reasonable and the person cannot consistently hit them even with support. That is a clear, defensible signal, not a vibe.

A scorecard makes a hard people-decision a calm one, because it points at results instead of personality. It also makes the hiring conversation concrete: you are recruiting for someone who can produce these outcomes, and you can interview against them.

Step 6: Review it on the rhythm and keep it alive

A scorecard in a drawer is worthless. Tie it to your operating rhythm: glance at the measures weekly, sit down on the role monthly or quarterly. Update outcomes when the role changes - as the shop grows, the dispatcher's job in year two is not the job in year one, and the scorecard should follow.

Keep it to one page, forever. The day it becomes three pages it stops being read, and an unread scorecard is the same as no scorecard.

References

• See related: Cross-Training vs Specialization Decision Matrix
• See related: When to Add an Office Role vs Stay Lean Decision Tree
• Outcome-based role definition, standard small-business management practice
• U.S. Small Business Administration guidance on roles, hiring, and performance management