SECTION 1
Chapter 5:
The Value Trail
5 minute read
Marcus took a week just to think. He'd sit with a question on the drive home, turn it over at lunch, come back to it in the middle of something else. By the time the next weekend arrived, he was ready to build. He had his three Relevant Business Results. Now he needed the other side of the equation.
What value do I actually produce that influences these results?
Not what he did. Not his responsibilities or the general shape of his contribution. Value: specific things that existed in the world after he made them, things that moved the numbers on his results list.
He sat at his kitchen table on Saturday morning and navigated to the next tool in the app.
The video made a distinction he hadn't considered before. Most people spend their careers producing things—documents, meetings, reports. That's not the same as producing value. Value is what happens when an output actually changes something that matters. A process guide that sits unread in a shared drive is not value. The same guide, adopted by three departments, connected to a measurable improvement in compliance turnaround—that's value.
Value-Added Output: Something you produce—a service, physical product, event, document, or other countable output—that is proven to influence Relevant Business Results.
The question wasn't what do you produce? It was what value do you produce; that means it influences the results that matter?
He looked back through his year for things he'd produced that had actually changed something.
The vendor integration had moved processing time by 40%. But the integration itself was a project—something he’d done once and finished. He tried to picture counting it the way the app wanted him to count things, and the closest he came was “a performance improvement project.” Too broad to measure cleanly. Maybe later.
The onboarding framework had the same problem. It had put two analysts into independent client work in half the usual time—real value, built once. If he ran onboarding every time someone new joined, each onboarded employee might count as its own event. He didn’t. Not yet, anyway. Though it might be another performance improvement project.
A client report he’d rebuilt in July had reduced the report’s complexity. One-off too.
Then he got back to April: the compliance handoff guide. He'd written it in a week, handed it to the compliance team, and moved on. He hadn't thought about it since.
But now that he did think about it, three departments were using it. He knew that because people cited it in meetings—the way people cite things that have become part of how work gets done. Just a standard part of the process.
He sent a quick message to a contact in Finance, a department he hadn't known was using it, to ask them. Got a reply inside twenty minutes. Finance was often working weekends during Q1 every year.
“Yes, we use it. Saved us from building something from scratch. Really well organized.”
Marcus read that message twice, and gave himself a mental pat on the back.
Then he started thinking.
He'd written the compliance guide. He'd also written a process guide for the vendor onboarding workflow last August. One the previous spring for the regional account transition. One the year before that, for a system migration nobody had documented properly—until he did.
He had been writing process guides for four years. People asked for him by name to write them. He had never once thought to count them as value.
He picked up his phone and called Diane.
"I found something," he said.
"Tell me."
"Process guides. I've been writing them, and people use them. I just never thought to track them."
"You’re right. They're not just tasks," Diane said. "They're Value-Added Outputs. They exist after you make them. They do work you're not in the room for." A pause. "How many have you written?"
"Five, maybe six. I'd have to look back."
"And how many places are using them?"
He thought about it. "I’ll have to document this, but more than I’d thought," he said.
***
He spent Sunday afternoon building out the measurement.
Quantity was straightforward—how many guides produced. But the app pushed him further: what did success actually look like? Not whether he'd produced the guide, but whether producing it had moved the needle, had meant something.
He thought about what made his guides work. People didn't just read them; they kept using them. Though, not always. The compliance guide had become the foundation for another team's adaptation. Finance had called it well organized. And the onboarding framework was still being referenced by analysts who'd joined months after Priya and Tom. Then there was one built for marketing and another for the training group. Those never got used before they became outdated.
So the difference was adoption. Whether the team had actually changed the way they worked because of it.
He typed his criterion: “Fully adopted within 3 months of delivery.”
It took longer to define than he expected. He'd never had to describe his own unit of measure before.
By the time he closed the laptop, he had six process guides documented, four confirmed multi-team adoptions, and three follow-up conversations to schedule for Monday. He had stats on a scoreboard. Real ones. Built around the specific value he produced that no one had been counting—including him.
He had one last prompt: which Relevant Business Result did this move? It was a Relevant Business Result he hadn’t considered, compliance issues. He now had not just a measured output, but the story of how he moved that result.
He sat back and thought about those four years. Every time someone had emailed asking if he could put together a guide. Every time a team lead had said his name when the question was, “Who understands this well enough to document it?”
The organization had been telling him something. Over and over, in the only language organizations use—asking for the thing they needed.
He just hadn't known to hear it as signal.
He looked at what he'd built on the screen: One Value-Added Output, with six outputs, and four confirmed adoptions. Connected to aa Relevant Business Result. And he had a criterion he could apply to every guide going forward.
Two things were true at once, and both of them were new.
The first: he had evidence. Not effort, not reputation—a specific, measured account of value the organization was still using. Claire's quarterly review had always been a top-down read: what she observed, what she perceived, what impression Marcus had made in the months leading up to it. He'd never had a way to influence that. Now he did. The second: he had a system. The next process guide he wrote would go on the record the week it was delivered—not several years later, when someone finally thought to look back. The work he did from here forward would accumulate into something he could point to any time someone asked.
And it was possible that instead of getting recognized for one project at a time, he might be able to show a trend of successful projects. He’d work that out someday. These were only the most recent projects he contributed to.
He closed the app and sat back.
He'd been scoring with no one keeping score. Now he was making the scoreboard visible—and the next season hadn't even started yet.
© 2026 Torch Solutions Group, LLC