SECTION 1

Chapter 7:

The Conversation

5 minute read

He sat with the assessment for the next couple of weeks. Not because he was uncertain about what it told him—he'd scored the cell honestly and he trusted the diagnosis. He needed time to think about how to use it. Then he requested a meeting with Claire. He’d written the request three times before sending it. The third version said: “I've been doing some thinking about my work this year and where I want to go next. I'd like twenty minutes if you can schedule a time.”

Claire replied the same afternoon. “Monday at two.”

He spent the weekend on a one-page summary of his value. Not a complaint. Not a case for a promotion. Just a record: the Relevant Business Results his work influenced, the Value-Added Outputs connected to them, and a single paragraph about where he wanted to aim next. He'd included the Henderson rollout by name. He'd included a line about the skill he'd been developing without anyone asking: the ability to translate between systems and the people who used them, and to document that translation in a way that lasted—the process guides.

He printed his summary Sunday evening and read it over once. It was, he thought, the first time he'd ever put something on paper that actually reflected what he'd been doing for the last eleven years.

He folded it in half and put it in his bag.

***

Claire's office was the same as it always was. The neatly organized desk. The chair across from it that Marcus had sat in a little over a month ago, when he was handed a piece of paper that said Meets Expectations.

He sat down. He took the summary out of his bag and slid it across the desk.

"I thought it might be easier to start with this," he said.

Claire picked it up and read it the way she read everything—methodically, all the way through before responding.

She set it down.

"I didn't know you’d done all of this," she said.

"I know," Marcus said. "That's partly on me."

"The vendor integration—I knew about that. But the compliance guide being used by three departments, the onboarding framework for Priya and Tom—" She paused. "I knew those things happened. I didn't know to connect them to you."

"I didn't make it easy to connect them," Marcus said. "I finished things and moved on."

She leaned back slightly. "But now you're showing them to me," a question implied.

"I realized,” Marcus explained, “I'd been assuming the work would speak for itself. And it doesn't. Not because the work wasn't real, but because no one was watching the right things at the right time. Including me."

Claire nodded slowly.

***

They talked for thirty-five minutes, which was fifteen more than he'd asked for.

She asked how he'd measured the adoption rate on the process guides. She asked about previous projects he had worked on that were similar to the vendor integrations project and what he thought was holding the Henderson rollout back. She asked, toward the end, what he wanted the next year to look like.

He'd thought about this carefully: he wanted to contribute to something the organization currently needed, not something it had needed six months ago. He wanted his outputs to be visible while he was creating them, not just after.

She listened to all of it.

Then she said, "I've been building a case for a new initiative tied to the vendor compliance framework—the one that's been sitting in planning for three months. I haven't been able to move it, because I can't demonstrate projected impact to the executives. I need someone who understands both the systems and the outcomes well enough to build the evidence case."

Marcus looked at her.

"That's what this summary is," he said.

"I know," Claire said. "That's why I'm telling you."

Before he stood up, Marcus said, "I'd like to keep sharing this kind of summary with you. Updated. As things change."

Claire set the paper down. "I'd like that. I want to know what you're working on before it's done—not just after." She paused. "And now I know what to look for."

That was new. Not a review. Not a rating. A shared definition of what his work was worth and where it was pointed—in a language they'd both agreed to use. They were looking at the same scoreboard now, and both of them knew how to read it.

***

He walked back to his desk a different way than he usually did—down the long corridor past the fourth-floor windows, the ones that looked out over the parking lot where he'd sat in his car in February and felt the quiet, clarifying recognition that the rules he'd been playing by weren't the rules anyone else was using.

He stopped at the windows for a moment.

He hadn't gotten a promotion. Not yet. He didn't have a new title or a firm commitment about what came next. What he had was a real conversation with his manager—probably their first. He had a role in building something that mattered. And he had the beginning of a case that could be made, because he'd built the evidence to make it.

In CorporateBall, that was how it started. Not with a decision from above, but with a conversation between two people who finally had the same information of what value looked like, and how to measure it.

He walked back to his desk and opened the app.

He had some things to update.

Marcus built his scoreboard with the My Value App. You can too.—Learn more

Torch Solutions Group Logo

© 2026 Torch Solutions Group, LLC