_(1).svg?revision=1)
Value Map Framework
Telling Value Stories
Service organizations have always been metric and data driven. In the never-ending pursuit of operational efficiency and control, organizations and vendors have built elaborate dashboards tracking anything and everything that can be counted. Services is always trying to find that number to tell us what is happening. This does not lead to success though or create value.
For years, the Consortium has been working with Members on maturing measures as the methods of delivering services has evolved. The journey started with model specific measures and triangulation for KCS and Intelligent Swarming. As self-service delivery became the main mode of operation, measuring self-service success became the focus which then evolved into understanding success by channel with the expansion of customer touch points.
This work is still valid but there is a missing component in how we take all these measures and turn them into a value story. Today the focus is on informing. This needs to shift to telling a story that is relevant to the audience we are communicating to. A story changes how an audience sees the situation and, often, what they decide to do about it.
For support and service organizations, storytelling isn’t just a communication style, it's a strategic necessity. The data these organizations generate is rich, continuous, and uniquely positioned to intersect customer reality and business performance. But data without narrative is just noise that is easy to ignore. The difference between a team that is seen as a cost center and one that is recognized as a strategic asset almost never comes down to what is being delivered. It comes down to whether they’ve learned to tell the story of what they deliver in language that moves the people who need to hear it. Success metrics tell us what happened. Value stories tell us why it matters to the customer, to the business, and to every stakeholder who needs to understand what service is actually delivering.
The Consortium working group Measuring and Communicating Value, collaborating across 30 companies, has developed the Value Map Framework giving services teams a flexible, structured, repeatable approach for telling value stories that adapt to changing conversations, shifting audiences, and evolving organizational priorities.
The Value Map: A Five-Layer Framework
The Value Map is built as a pyramid, each layer depending on the one beneath it, and each one bringing you closer to a story that’s both credible and compelling. What makes it powerful isn’t any single layer in isolation. Each layer interacts with the building from the ground up or the top down.
Layer 1 — Data
"What trusted sources have our data, and what do we need to understand about them?"
Everything starts with data, but not just any data. The foundation of a credible value story is understanding where your data comes from, who owns it, and what it can and can’t tell you. Before you can measure anything meaningful, you need to know which sources are trusted, how they’re maintained, and what assumptions are baked in.
This layer is about building the raw material for your story. Skipping it, taking data sources for granted, is one of the most common reasons value stories fall apart under scrutiny.
Key considerations:
- Identify and document your trusted data sources across the organization
- Understand the limitations and context of each data source
- Establish consistency so that data is repeatable and defensible over time
- Build relationships with the people who own and manage those systems
Layer 2 — Signals and Measures
"What tangible, repeatable evidence can we produce from our data?"
Data becomes useful when you can turn it into signals that are specific, repeatable indicators that something meaningful is happening. This is the measurement layer where you are defining the metrics and patterns that serve as reliable evidence of performance and impact.
The emphasis here is on tangibility and repeatability. The goal is to establish measures that can be tracked over time, compared across contexts, and trusted by people who weren’t in the room when you built them. This is very much where traditional services dashboards and reports live.
Key considerations:
- Define metrics that connect operational activity to business outcomes
- Prioritize measures that are repeatable and auditable
- Focus on metrics that can inform decisions
- Align signal definitions across teams so comparisons are valid
Layer 3 — Results, Insights, and Recommendations
“What impact are we seeing? What do the signals tell us? What should we do about it?”
This is where intelligence for the business grows incrementally moving beyond reporting to answering what the signals and measures mean. Results describe what happened. Insights explain why. Recommendations tell what to do next.
This three-part structure is what separates a dashboard from a value story. Anyone can pull a report and make a graph. The skill and the strategic value is in the synthesis connecting the dots, surfacing patterns, and giving decision makers something they can act on.
Key considerations:
- Move beyond dashboards and vanity metrics toward insight and recommendation
- Frame insights in terms your audience cares about (cost, risk, growth, retention)
- Be honest about what the data is showing and what is doesn't show
- Recommendations should be specific, actionable, and tied to a clear owner
Layer 4 — Delivery Approach
"How do we make this easy to understand and hard to ignore?"
You can have perfect data, airtight signals, and develop brilliant insights yet still lose your audience if the delivery doesn't land. The format, the framing, the medium, and the narrative arc is what makes your value visible and memorable.
The same insights or recommendations needs to be packaged differently for a CFO, a product manager, or a front-line team leader. Delivery is a strategic decision and is the difference between a value story that can’t be ignored and changes minds versus a flashy dashboard that is ignored.
Key considerations:
- Match the delivery format to the audience
- Make it easy, don't make your audience work to find the point
- Use concrete examples and real numbers with a narrative arc
- Test, repeat, and refine the story
Layer 5 — Audience and Context
"Who needs to understand the value? What is their role or focus? What biases exist?"
The top of the pyramid, and in many ways the most important layer, is context and audience. Context shapes everything. What counts as compelling evidence, what language resonates, what skepticism you need to overcome, and what success looks like from that person’s perspective must all be accounted for.
This layer asks you to shift your perspective to that of the audience. It is more than thinking about what you want the audience to know. What do they already believe? What pre-conceived bias do they hold? What are they held accountable for? Where does service fit in their mental model of the business?
Getting this right turns a good value story into one that changes minds and impacts the wider business.
Key considerations:
- Map your stakeholders and understand their specific priorities and pressures
- Anticipate biases and objections before they surface in the room
- Tailor language to what your audience values
- Revisit audience context regularly, as roles and priorities shift
The Thread That Holds It Together: Trust
Trust is a variable that cannot be ignored but is one often lost in measure discussions. Without trust, even the most well-constructed value story will be dismissed. Building it is not a single action. It’s an ongoing investment in relationships, transparency, and consistent delivery over time.
Trust operates across three dimensions:
- Trust in People: Does your audience believe in you and your team as credible sources?
- Trust in the Organization: Does the broader company trust that service organizations are a strategic contributor?
- Trust in Systems: Does your audience believe the data and tools you're drawing from are reliable?
What Comes Next
The Value Map Framework isn’t a one-time exercise, but a living framework designed to evolve alongside your company’s conversations and priorities. The Consortium’s Measuring and Communicating Value work leverages this framework offering practical measurement templates ready to use, guidance for influencing and acting on data results, recommendations for delivering value stories to different audiences, real-world examples from member companies, and AI use cases and considerations for modern support environments.
Service organizations have never been short on data. What’s been missing is the discipline to turn that data into stories that are crafted, credible, relevant, and impossible to ignore. The Value Map Framework provides that structure.
We measure success. We tell stories about value. We own our story.
The work is still evolving through collaboration among ~30 participants across 19 companies. Additional templates, examples, AI considerations, and practical guidance will be shared at the September 30 virtual event - Support as the Company Value Engine: Measuring What Matters.
