Executive Summary
The Purpose Triangle is Business Training Works’ strategic framework for defining change before execution begins. It helps organizations clarify the current state, the future state, and the reason movement between them is worth the cost. Rather than treating change as a rollout problem, the model defines what must shift in the work, the process, and the experience of the people involved. This page explains how the framework works, why large organizations often need nested triangles, and what tends to go wrong when this level of definition is skipped.
What This Page Answers
- What is the Purpose Triangle?
- Why does change need strategic definition before execution planning begins?
- How does the framework define current state, future state, and the reason for change?
- Why do large organizations often need connected triangles at different levels?
- What problems show up when leaders skip this step?
How the Purpose Triangle Works
Developed by Business Training Works in 2016 and refined through a decade of client work, it is a strategic framework built on a single premise: clarity about what the change is trying to produce must come before any execution work begins. A senior leadership team can use it to govern an enterprise-wide transformation. A front-line manager can use it to explain a department-level shift to a team. Individual contributors can use it to find their footing in a new world. The same framework. The same language. No specialist required to interpret it.
And here is what makes it genuinely scalable: the triangle multiplies. An enterprise has a triangle. A division has a triangle. A department has a triangle. An individual role can have a triangle. Each one maps the current state, the future state, and the WHY that makes the distance worth traveling. Each one connects upward to the triangle above it. The language stays the same at every level. The work stays aligned across every level. Front-line employees mapping what their roles look like today versus what those roles need to look like when the change has taken hold are doing the same intellectual work as the CEO governing the enterprise transformation. That is not a small thing.
To make this concrete, one example runs through the entire section: a mid-size financial services company moving its customers from phone-based service to a self-service portal. The decision has been made. Leadership is aligned. Now the work of understanding what the change requires begins.
Purpose at the Center
The Purpose Triangle is not a triangle of equal parts. Purpose sits at the center, and everything else radiates from it. Not because it is the most interesting element, but because it is the one that makes every other element coherent.
The WHY is not a goal statement. It is not a project milestone. It is not a message crafted by a communications team and approved by legal. It is the reason this change matters, stated plainly enough that anyone in the organization could understand it, repeat it, and test decisions against it.
Organizations regularly mistake the trigger for the WHY. The trigger is what set the change in motion: a new regulation, a competitive threat, a leadership decision, a market shift. The WHY is the reason the disruption is worth it. A company implementing a new enterprise system because a competitor gained a productivity advantage has a trigger. The WHY is what the organization will be able to do, or do better, once that system is fully operational. These are different statements and they do different work.
In the portal example, the trigger is competitive pressure from digital-first competitors gaining market share. The WHY is different and more important: the company needs to reduce service costs while improving response times for routine customer requests, positioning the organization to serve customers the way customers increasingly expect to be served. That is the reason the disruption is worth it. That is what leaders at every level will test their decisions against.
When the WHY is clear, it functions as true north. Leaders navigating difficult decisions during the initiative can test their choices against it. Managers communicating the change to their teams can anchor every conversation in it. Employees trying to understand what the change asks of them can orient to it. When the WHY is vague, everything downstream becomes a judgment call with no reliable reference point.
Two things are worth saying directly about the WHY before moving on.
First, if leaders cannot state it clearly before the work begins, the work should not begin. This is not a counsel of perfectionism. It is a recognition that a change initiative without a clear WHY is an initiative that will generate its own explanation as it moves, and those explanations will be inconsistent, incomplete, and often wrong.
Second, the WHY can shift. Markets change. Circumstances evolve. New information surfaces. When the WHY changes, everything built on it changes too, and the right response is to acknowledge that openly and reorient the work. Leaders who recognize a shift in the WHY and respond to it are doing their jobs. Leaders who watch the WHY shift and keep executing against the original version are not.
The WHY also nests. The enterprise WHY sits at the top. A division’s WHY connects to it. A department’s WHY connects to the division’s. A role’s WHY connects to the department’s. When every level of the organization can state its own WHY and trace it upward to the enterprise WHY above it, the change has a coherence that no communication plan alone can produce.
Where You Are and Where You Are Going
Here is where the Purpose Triangle does something that most strategic frameworks do not.
It requires leaders to map two states, not one. The current state describes the organization as it exists today. The future state describes the organization as it needs to exist when the change has fully taken hold. The gap between those two states, mapped across all three points of the triangle, is the actual definition of the change.
This matters more than it might appear. Organizations that describe only the future state know where they want to go but have no honest picture of how far they need to travel. They underestimate the work, miscalculate the resources, and discover the real scope of the change somewhere in the middle of the initiative when the cost of the discovery is highest.
With both states mapped, the WHY becomes testable. Either the destination justifies the distance, or it does not. Either the organization has the resources to close the gap, or it does not. Either the disruption to the people involved is proportionate to what the change produces, or it is not. These are hard questions. The Purpose Triangle forces them to the surface before the work begins rather than after.
In the portal example, the current state is an organization where customers call a service line staffed by eighty representatives. Wait times average twelve minutes. Routine requests, balance inquiries, address changes, statement requests, consume the majority of call volume. The customer service team’s work is defined almost entirely by phone interaction. That is the reality today.
In the future state, the majority of routine requests are handled through the portal without human intervention. Call volume drops significantly. The customer service team handles complex interactions requiring judgment and empathy. The team is smaller. The skill requirements are higher. Response times for routine requests are measured in seconds rather than minutes.
The gap between those two states is the actual definition of the change. It is not small. And with both states mapped honestly, the WHY either holds up or it does not. In this case it does: the destination justifies the distance. But the organization now has no excuse for underestimating what the distance requires.
And because the triangle multiplies across the organization, both states get mapped at every level. The enterprise maps its current and future states. The division maps its own. The department maps its own. Each mapping is specific to that level, informed by the one above it, and honest about the distance that level needs to travel. The result is an organization that understands the change not as a single large abstraction but as a set of specific, connected pictures of where things are and where they need to go.
The Three Points of the Triangle
Each point of the triangle describes a specific dimension of organizational reality. Each must be mapped in both the current state and the future state. All three future state descriptions must connect back to the WHY or the triangle loses its integrity.
Work Product
The work product point asks a simple question: what does this organization produce?
In the current state, the answer describes the real output of the work today. Not the intended output, not the ideal output, but what comes out the other end of the organization’s effort on a typical day.
In the future state, the answer describes what that output looks like when the change has fully taken hold. What does the work produce in the new world that it did not produce in the old one? What changes about the quality, the form, the speed, or the nature of what the organization delivers? What no longer gets produced at all?
The gap between those two descriptions is the first honest measure of what the change requires. A small gap suggests a manageable transition. A large gap suggests significant work across every other dimension of the triangle.
In the portal example, the work product in the current state is a resolved customer interaction delivered by a trained representative over the phone. In the future state, the work product is a self-service resolution completed by a customer through a digital interface, with human intervention reserved for interactions the portal cannot handle. The form, the delivery mechanism, and the human involvement all change. That gap tells the organization something specific about what the training, the technology, and the communication plan will need to accomplish.
At the role level, the work product point asks the same question scaled to the individual: what does this person produce today, and what will they produce when the change has taken hold? That specificity is what makes the triangle useful to someone who is not a senior leader, not a project manager, but simply a person trying to understand what the change asks of them.
Processes
The processes point asks how work moves through the organization.
In the current state, this means understanding the real workflow. Not the documented workflow, not the intended workflow, but the way work flows today. Who initiates what? Where do handoffs happen? Where does work slow down, pile up, or disappear? Where do informal processes substitute for official ones?
In the future state, this means describing how work will move once the change is complete. What steps now exist that did not exist before? What has been eliminated? Where do handoffs now happen that used to happen somewhere else? Who initiates work that someone else used to initiate?
The gap between those two descriptions is not a process mapping exercise. It is a clear-eyed picture of how far the organization needs to travel in its day-to-day operations. Not its org chart, not its systems, not its stated policies, but the way work moves.
In the portal example, the current state process begins when a customer dials the service line. A representative answers, authenticates the customer, identifies the request, resolves it, and closes the interaction. Every step involves a human being. In the future state, the process begins when a customer logs into the portal. Authentication is automated. Routine requests are resolved without human involvement. The representative enters the process only when the portal routes an interaction that requires judgment. The handoffs are different. The initiating action is different. The role of the customer service representative is fundamentally different. That is not a small process adjustment. It is a redesign of how the work moves.
At the department level, the processes point maps the workflows specific to that team. At the role level, it maps the specific tasks, handoffs, and interactions that define how one person’s work connects to the work around them. The more granular the triangle, the more specific and useful the processes picture becomes.
People
The people point is where change initiatives most often underinvest, and where the consequences of underinvestment are most visible.
In the current state, the people point describes who does what, with whom, and to what standard. What are the existing roles? What authority structures are in place? What relationships govern how decisions get made? What does a normal day look like for the people most affected by this change?
In the future state, the people point describes all of that after the change has taken hold. What roles have shifted? Who now carries authority that was held elsewhere before? What relationships now matter that did not matter before? What does a normal day look like for the same people in the new world?
The gap here is the most personal dimension of the change, and therefore the most sensitive. Change almost always redistributes power, relationships, and identity. People who lose authority in the future state will not describe that loss neutrally. People asked to build new relationships with colleagues they have not worked closely with before will not find that transition effortless. Organizations that map the people gap honestly before the work begins can plan for these dynamics. Organizations that skip it discover them in real time, when the cost of the discovery is paid in resistance, attrition, and failed adoption.
In the portal example, the people gap is the most consequential dimension of the change. In the current state, eighty customer service representatives define their professional identity around the ability to help customers over the phone. They are good at it. Many of them have done it for years. In the future state, the team is smaller, the work is more complex, and the skills required are different from the ones that made people successful in the current state. Some people will thrive in that new world. Others will not. The organization that maps this gap honestly before the work begins can design a transition that treats people with dignity, identifies who is well positioned for the future state, and makes deliberate decisions about support, retraining, and transition assistance. The organization that skips this point discovers the human cost of the change in the form of attrition, disengagement, and resistance at the exact moment when it most needs people to be present and committed.
At the role level, the people point becomes intensely personal. It asks individuals to map what their working relationships, responsibilities, and identity look like today versus what they will look like when the change is complete. That is not always a comfortable exercise. It is almost always a useful one.
Governance of the Triangle
A Purpose Triangle without governance is a strategic document rather than a strategic tool. Someone needs to own it.
Ownership means more than having drafted it. It means having the authority and the responsibility to maintain its integrity across the life of the initiative. To call it when the WHY has shifted. To resolve conflicts when workstreams pull against each other. To test major decisions against the triangle and push back when those decisions compromise the future state.
In the portal example, ownership of the enterprise triangle sits with the Chief Operating Officer. Ownership of the customer service triangle sits with the Director of Customer Service. Ownership of the technology workstream triangle sits with the Chief Technology Officer. Each owner is accountable for the integrity of the triangle at their level and for connecting it clearly to the triangle above it.
In most organizations, the governance structure mirrors the triangle structure: nested, connected, and clear about who is responsible for what at each level. The practical questions to answer before the work begins: who owns each triangle, who has standing to challenge it, how do conflicts between levels get resolved, and what is the process for updating a triangle when circumstances change? These are not exciting questions. But the absence of clear answers to them is one of the most reliable predictors of a change initiative that loses coherence as it scales.
The Cost of Skipping This Step
The symptoms of a change initiative without a clear Purpose Triangle are recognizable, and they almost always get misread.
At the three-month mark, the symptoms look like execution problems. Communication is inconsistent. Different parts of the organization are moving in slightly different directions. Resistance is higher than expected. Leaders are making decisions that seem locally reasonable but do not add up to a coherent whole.
At the six-month mark, the symptoms look like people problems. Key contributors are disengaged. Managers are struggling to answer basic questions from their teams. The energy of the launch has dissipated and nothing has replaced it.
In both cases, the diagnosis points at execution. The actual problem is strategic. The execution is inconsistent because there is no clear picture of what the execution is trying to produce. The people are disengaged because no one has given them a clear picture of where they fit in the future state.
In the portal example, an organization that skips the Purpose Triangle might announce the change, begin the technology implementation, and start building the communication plan before anyone has honestly mapped how far the customer service team needs to travel. Three months in, the training is behind because nobody scoped it against the actual skill gap. The communication is generating anxiety because it describes the future state without acknowledging what it costs the people being asked to get there. The technology is on schedule. The change is already in trouble.
The Purpose Triangle does not guarantee a successful change initiative. Nothing does. But it does guarantee that the people leading the work are starting with a shared, honest, and specific picture of what the change is trying to produce and how far the organization needs to travel to get there.
That is the measure before the cut.
Section Takeaway
The Purpose Triangle outlines the now and later. One organization might have dozens of them, nested from the enterprise level down to the individual role, each one mapping the current state, the future state, and the WHY that makes the distance worth traveling. Strategic clarity at that level does not manage itself. It needs an execution architecture built to match it. That is what the next section provides.