SECTION 2
Chapter 8:
The Manager's Own Scoreboard
4 minute read
Dani’s last day was the next day, Friday. The team gathered around her desk at four o’clock—the kind of goodbye people who actually like each other prefer over a catered event in a conference room. Someone had brought a cake, and they’d passed around a card they’d all signed. Reid hadn’t even assigned those things. People who cared about each other just did them.
Reid updated Dani about the requisition for her replacement before the cake was cut. About the role profile built from her worksheets. That the best parts of what she’d built here wouldn’t leave when she did.
Dani was quiet for a moment. “So I helped hire my own replacement.”
“You did,” Reid said.
She looked at him. “Do better with the next one.”
***
That weekend, Reid opened the app for himself.
Not for his team—his own account, his own outputs. Ray’s question, weeks old now, turned back on its asker: What measurable value do you produce that impacts the organization, and how would we know?
He sat with it for a long time.
Then it clicked. The Relevant Business Results of his team were either the same as his or they fed his. The same for Sandra. The chain was now easy to follow, and his link was clear.
But that didn’t feel like it was enough. Leading people had to have a result of its own, one focused on the people themselves. He went looking for it in the place he stared at every month without ever really seeing it: the budget. And there it was, a line he’d only ever treated as an expense. Cost of labor. Recruiting, ramp-up, vacancies, backfills. It didn’t belong to anyone on his team. It belonged to the role that hired, developed, and kept people—his. The question was how he influenced it.
He went back six years—not to performance reviews, to the people themselves. Every team member who’d moved on: where had they gone, and what had happened after?
Two years in, three people had left the team—one promoted quickly, two not, and looking back he understood why: he’d still been learning what to ask of his team. In the four years since, twelve had moved on. Ten of those had stepped into more complex roles—within two years, it appeared. And eight of those ten were still thriving there to date. He’d need to consider an amount of time that would refine his criteria; he could call it ninety days or longer in their new role.
Ten people who hadn’t needed to be replaced from outside. Ten searches the company never had to fund, ten ramp-ups it never had to absorb. He hadn’t tracked it or named it as something he made, but six years of history said it wasn’t luck. It was a skill, and it was moving the very line he’d only ever read as an expense: cost of labor.
He opened the app. He put in “cost of labor” as a Relevant Business Result. And he named a Value-Added Output: “A promotable employee.” He added the criteria:
Advances to a role of greater complexity within two years.
Still performing in that role ninety days after advance.
And stayed in the company—you always want to keep your own.
“I produce promotable employees,” he could finally say. “Fifteen of them in six years. Ten I can name from the last four alone, with the roles they moved into and the proof they were still there. That’s what this team loses if the role goes away.”
He entered it all—names, transitions, the one-on-ones where he’d done the job right. Then he sat back and looked at what he’d built.
It was the most honest document he’d ever made about himself. Not a resume: evidence of value. Not a self-assessment: an agreement with the company—assuming he took the step of negotiating that with his own manager. But this is what he produced, what it moved, what it was worth, in terms the company already measured.
The scoreboard Reid built for himself is available to every subscriber.
Six years managing. Six years producing promotable employees. He was better at it now than when he’d started, with the numbers to prove the trend. He’d just figured out, on a Saturday over a second cup of coffee, that producing promotable employees proved his value as a manager.
***
To win in CorporateBall, a franchise needs more than talented players. It needs a scoreboard in plain sight. So every player knows their own statistics—goals, saves, assists, batting average—and knows exactly what those numbers add to the franchise. Nobody waits for a season-end review to find out how they played; the numbers are up on the board where both manager and player can see them, all game long.
***
Reid closed the app.
Outside, the city went on with its Saturday, indifferent to whatever anyone inside was figuring out. Reid sat in the quiet, the scoreboard finally visible, the numbers finally his.
He felt like a manager who’d finally learned to keep his own score.
© 2026 Torch Solutions Group, LLC