SECTION 1
Chapter 2:
Meets Expectations
3 minute read
The meeting was the following Tuesday at 10:00.
Claire's office was small and tidy, the kind of space that reflected its occupant: organized, functional, nothing on the walls that didn't need to be there. She smiled when he came in and gestured to the chair across from her desk.
"I want to start by saying, this has been a strong year for you," Claire said.
She meant it. Over the next fifteen minutes she walked through his contributions with a specificity that surprised him. She mentioned the vendor integration. She noted Priya and Tom, the two new analysts he'd brought up to speed. She talked about his institutional knowledge, the steadiness he brought to the department.
It was, Marcus thought, an exceeds-expectations kind of conversation.
Then Claire turned the printed page over and slid it across the desk.
Five goals, rated individually. Two said Exceeds Expectations. Three said Meets Expectations. At the bottom, under a thin horizontal line, was a single overall rating.
Meets Expectations.
"I'm not sure this reflects what you just described," he said.
"The system averages the goal ratings to produce the overall score," Claire said. "Two exceeds and three meets averages to meets." She paused. "I know it doesn't always feel right."
"It doesn't feel right."
"I understand." She said a few more things about his trajectory, about the conversation being more important than the number at the bottom. She wasn't wrong, exactly. But that number controlled a lot of things—his pay, his bonuses, his opportunities.
He thanked her and walked back to his desk.
***
It wasn't there.
What was there: Marcus demonstrates strong institutional knowledge. He is a dependable member of the operations team. His technical contributions support the department's ongoing objectives.
Ongoing objectives.
He closed the document and thought about his year. Systematically. From the beginning.
The vendor integration: 40% reduction in processing time, error complaints gone since October of last year. The onboarding framework for Priya and Tom: two analysts now running their own client accounts. The compliance handoff guide he'd written in a week—because someone had to—now used by three departments. The vendor negotiation he'd quietly steered Derek through, because he'd seen it going sideways.
He stopped at that last one.
He had coached Derek through a negotiation. Derek, who, he had learned late yesterday, had just been named to the Q2 team lead list.
He was trying not to feel angry about that. Jealousy’s not a good look. But he felt like a person who had just realized someone had been keeping score on a board no one else could see. Or maybe someone was making up the score, because no one was actually keeping stats in real time.
***
The problem, he understood now, was not that he hadn't done the work.
The problem was that he had no way to prove it. Claire had described it well. But she couldn’t quantify it. And what you cannot quantify, you cannot defend. The system isn’t even set up to let you.
Relevant Business Result: The bottom-line metric, connected to the organization's core mission, that your efforts influence. It's the kind of number that moves decisions about budget, headcount, and who leads the next initiative.
What would it take to walk in there next time with evidence she couldn’t dismiss as irrelevant?
He opened a browser and typed five words into the search bar: How to prove your value.
He stared at the results. Articles. Listicles. A LinkedIn post from someone he didn't know. But nothing that felt like it was written for him.
He deleted the search. He wasn't sure what he was looking for. He just knew that what he'd been doing—working hard and trusting that someone was noticing—wasn't working. And that the answer was going to require him to do something very different from the same-old-same-old.
The tools Marcus is about to discover are part of the My Value App.
© 2026 Torch Solutions Group, LLC