Most hiring messes start before the first resume hits your inbox. Someone posts a vague job. Six people interview. Then the debrief turns into a vibe check: “I liked them.” “Felt off.” “Great energy.” That is not a hiring process. That is a group chat.
If you want a cleaner process, agree on what “good” looks like in writing before you talk to anyone. That document is a hiring scorecard. It is not fancy software. It is one page that turns opinions into evidence.
What a scorecard actually is
A scorecard lists the outcomes for the role, the skills that produce those outcomes, and a simple 1–5 rating with space for notes. Every interviewer uses the same sheet. You decide based on those ratings, not on who talks loudest in the room.
Keep it tight:
- Three to five outcomes the person must deliver in the first year
- The skills and behaviors that predict those outcomes
- Deal-breakers you will not waive
- Nice-to-haves that cannot rescue a weak must-have
If you cannot fit it on one page, you do not know the job yet. A long requirements list usually means the team has not agreed on the real work.
Write it before the job post
Most teams skip this. They write the posting first, then reverse-engineer requirements from old listings. Flip the order.
Sit with the hiring manager and one or two people who do the work. Ask what this person will own in six and twelve months, what a strong first 90 days looks like, where past hires struggled, and which skills are teachable. Translate answers into outcomes, not adjectives. “Strong communicator” is mush. “Can run a weekly pipeline review and leave the team with a clear next action” is something you can test.
Write the job post from the scorecard, not the other way around. Candidates see the actual work. You get fewer keyword-only applications.
Use it in every interview
Give every interviewer the scorecard and two or three questions tied to their section. You do not need eight people asking “Tell me about yourself.” The hiring manager probes core outcomes. A peer probes disagreement and messy handoffs.
Take notes against the criteria. Afterward, each person scores independently before the group talks. That order matters. If you debrief first, the loudest voice rewrites everyone’s memory.
Walk the scorecard line by line. Ask for evidence: what did the candidate say or do? If two interviewers scored a 2 and a 5 on the same skill, that is a process problem. Fix the questions or the definition. Do not paper over the gap with “I just had a good feeling.”
What this actually does
A scorecard will not fill an empty seat by itself. It cuts bias that hides in vague “culture fit.” It makes yes or no faster because the bar is already defined. It gives you an outline for the first 90 days. It protects the process when stakeholders disagree, because the criteria were agreed up front.
If someone wants to add “top school” or “someone I’d grab a beer with,” put it on the table early. If it is not on the scorecard, it is not a reason to hire or reject.
Start with one role this week
Pick an open job. Block 45 minutes with the hiring manager. Write the outcomes, the skills, and the deal-breakers. Share the page with anyone who will interview. Do not post or schedule until that page exists.
You will still have hard calls. People are not spreadsheets. The point is to stop hiring on charm alone and hoping it works out later. Decide what the job needs, write it down, and hold every candidate—and every interviewer—to the same bar.