
SECTION 1
3 minute read
Three weeks later, Marcus had a new Relevant Business Result in the app—the vendor compliance framework metric, with a baseline and a number to move. He had a new Value-Added Output event: process documentation for the Meridian onboarding workflow, quantity measured, quality criterion set, connected to the RBR above it.
It took four minutes. He'd gotten faster at it—not because the thinking was easier, but because he'd done the foundational work.
He sent the updated report to Claire that same afternoon. She replied within the hour—two sentences acknowledging the Meridian connection and a question about the compliance metric baseline. Not a performance conversation. A working one.
That was what it looked like when two people had the same information. His record, kept current. Her context, applied to it. No lag. No guesswork about what he'd been doing or whether it mattered.
The vendor compliance framework had a name now: Project Meridian. Claire had presented the preliminary case to the GM two weeks ago. The GM had asked three questions, all of which Marcus had anticipated, and Claire had answered them using language and numbers Marcus had helped build.
The project wasn't approved yet. It was in the queue, which in this organization meant it existed—which was more than it had meant a month ago.
Marcus was on the working team.
***
He thought about the scoreboard.
In every stadium, in every league, it hung visible and indifferent—reporting what happened, not what anyone felt about what happened. It didn't care about effort or intention or the number of hours logged in an empty building on a Thursday night.
For a long time, Marcus had assumed that someone else was keeping his score. He understood now that no one was. Not because the people around him were negligent, but because, in CorporateBall, the scoreboard didn't exist until someone built it. And the only person with the full picture—what Marcus Reyes produced, what changed because of it, what it was worth—was Marcus Reyes.
That was the job. Not just doing the work, but building the record of the work. Making sure that when the question was asked—what value does this player actually produce?—there was an answer that didn't depend on who happened to be watching.
***
Marcus picked up his phone and typed a message to Diane. “Coffee next week? I want to show you something.”
She replied in the time it took him to set the phone down. “Already?”
He smiled at that. “I've been keeping track.”
Her response was a single word, which was not how Diane usually communicated, which meant she was pleased. “Thursday.”
***
He looked out the window. The building hadn't changed. His job title hadn't changed. His manager, his department—all of it was the same.
He was not the same.
He had a record now. A real one. Not a memory of having worked hard—a record with numbers and dates and outputs and connections. A thing he could hand to someone and say: here is what I produced; here is what changed because of it; here is what it was worth.
He'd needed a framework: a way to measure value, and a place to put the work he was already doing.
He had that now.
In CorporateBall, the players who thrive are the ones who kn0w their stats.
Marcus closed the app and got back to work.
The scoreboard Marcus built is available to every subscriber. Learn more