When the CEO of the food company where I worked asked for a way to evaluate our salespeople, I ended up leading the project. What we built was a one-page weekly scorecard for every sales rep, combining hard numbers with the judgment of the people who worked alongside them. This is how it was put together, what it was used for, and what I'd keep in mind if you're building something similar.
Where did the sales evaluation system come from?
It started with an instruction from the CEO. The assignment landed on me as someone who already worked on sales planning and sales management, and I took the lead on developing it.
I'd already spent years in the part of Korean sales that isn't selling: the planning, the reporting, the numbers behind the people in the field. Evaluating salespeople fits right into that territory, and it's harder than it looks, because a sales rep's results depend on things the rep doesn't control, like territory, customers and timing.
What did the scorecard measure?
We set it up around KPIs tracked on two clocks, weekly and monthly. The weekly view kept a rep's recent activity in front of them and their manager. The monthly view gave the bigger picture.
The scorecard didn't stop at numbers. It combined two kinds of evaluation:
- Quantitative: the KPIs themselves.
- Qualitative: assessments from the rep's team leader and from colleagues.
The quantitative part ran weekly and monthly. Peer assessments were collected quarterly, since asking colleagues to evaluate each other every week would turn it into a chore.
Why combine numbers with peer and manager reviews?
Here is the general case for it, separate from our particular system. A number can tell you what happened, but it rarely tells you why. Someone can hit a target by borrowing from next quarter, or miss one while building a customer relationship that pays off later. A team leader and teammates see how a person works, and that context helps explain the figures. The risk of relying on judgment alone is bias and favoritism, which is why you want the numbers next to it, not instead of it.
Why one page per salesperson?
Each rep got a one-page report every week. One page is a deliberate limit. A report that runs to ten pages gets skimmed, and a rep can't act on ten pages of data. One page forces a decision about which numbers actually matter, and it gives the rep and the manager a single shared sheet to talk from.
What was the evaluation used for?
The purpose was practical on both ends. Top performers were recognized and rewarded. Those at the bottom were coached. I think that second half is the part people skip when they build these systems. A scorecard that only ranks people feels like a verdict. One that leads to coaching gives the ranking a reason to exist.
What tools did we use to build it?
It began in Excel and Python. From there it moved to Power BI, and by the time I left the company, the Power BI version was actually in operation. A web-based version was also planned, but that part stayed a plan.
If you're starting from nothing, I'd say the order matters less than people think. Get the logic right in a spreadsheet first. Moving it to a dashboard tool is the easy step once everyone agrees on what the numbers mean.
What to check before you build a sales scorecard
- Can you explain every KPI on it in one sentence, and does the rep agree it reflects their work?
- Does the report fit on a single page that a busy person will actually read?
- Do the qualitative reviews run on a slower cycle than the numbers, so they don't become a weekly burden?
- Is there a clear next step for the best performers and for the weakest ones?
If I had to boil the whole project down to one idea, it's that an evaluation is only worth building if the person being evaluated gets something back from it.
Comments
Post a Comment