.png)
You have probably heard of the People Process Technology framework.
You may have seen it on a consultant's slide deck. You may have heard a vendor reference it during a sales pitch. You may have nodded along in a meeting where someone said "we need to think about this holistically across people, process, and technology."
What you may not have noticed is that almost everyone who uses the framework gets the order of operations completely wrong.
The standard pattern in most businesses is to lead with technology. A new tool is purchased. The process gets redesigned around the tool. The people are trained on the new process. By the time the rollout is complete, the business has spent significant money, redesigned workflows to fit the tool's limitations, and asked its people to adapt to both. The results are predictably underwhelming.
The People Process Technology framework, used properly, is the most important operational thinking tool a growing business has. Used backwards, it is one of the most expensive sources of operational waste. This post is the practical guide to using it correctly.
What the framework actually is
The People Process Technology framework, often called PPT or the Golden Triangle, was introduced by business management expert Harold Leavitt in the early 1960s as part of his Diamond Model of organisational change. The core insight is simple. Organisational performance depends on three interdependent components, and changing one without addressing the others leads to suboptimal outcomes.
The three components are exactly what the name suggests.
People. The humans in your business. Their skills, their knowledge, their motivation, their relationships, their capacity to learn. This is the layer where innovation happens and where decisions get made. Without capable, engaged people, no process or technology delivers what it should.
Process. The repeatable workflows that structure how work gets done. The standard operating procedures, the decision rights, the handoffs between teams, the rhythms of the business. Process is what allows the business to function predictably at scale.
Technology. The tools, systems, and software that people use to execute processes. From your CRM to your communication tools to your financial systems. Technology amplifies what people and processes can do.
The framework's central claim is that these three components are interdependent. You cannot meaningfully improve one without considering the impact on the other two. A new process that the team is not trained for will fail. A new technology that the process does not support will be underused. A talented team running on broken processes will be frustrated and ineffective.
This sounds obvious. It is also routinely ignored in practice.
Why most businesses get the order backwards
The standard pattern in most growing businesses is to lead with technology. Someone identifies a problem. Someone else suggests a tool. The business buys the tool, implements it, and then expects the process and the people to catch up.
This pattern fails for predictable reasons.
Technology cannot fix a broken process. If your client onboarding process is fundamentally broken, putting a CRM on top of it just gives you a digitised version of a broken process. The customer experience does not improve. The bottleneck does not move. You have spent money to make the existing problem more efficient at being a problem.
Technology choice constrains process design. Once you have selected the technology, you are working within its assumptions. The process gets redesigned to fit what the tool can do, not what the business actually needs. This is fine when the tool happens to fit the need. It is expensive when it does not.
People are asked to adapt to both at once. The team is being asked to learn a new tool and a new process simultaneously, while still doing their actual job. Adoption suffers. The implementation drags. Six months later, the team is partially using the tool, partially running the old process, and entirely frustrated.
The right order is the reverse of the common practice. People first. Process second. Technology third. Let me explain why each step matters in that sequence.
The right order: people, then process, then technology
Start with people
The people layer is first because everything else depends on it. If your team is not capable, engaged, or aligned with the change you are trying to make, no process improvement or technology investment will deliver the return you expect.
Starting with people means three specific things in practice.
Assess the capability gap. What skills, knowledge, or experience does your team currently have, and what will they need to support the change you are planning? If you are about to introduce a new way of running operations, are the people who will run it equipped to do so?
Address the motivation question. Why is this change happening? What does it mean for the people affected? If the team does not understand or buy into the change, the process improvement and technology investment will hit a wall of passive resistance.
Identify the right roles and accountabilities. Who is going to own the redesigned process? Who is responsible for the technology? Who needs to be consulted, informed, or involved at each stage? If these decisions are made late, the implementation will stall when ownership becomes unclear.
This step is unglamorous and slow. It is also the difference between an implementation that sticks and one that collapses. The businesses that get the people layer right are the ones whose process and technology investments deliver. The ones that skip this step are the ones whose initiatives keep failing for reasons they cannot articulate.
Then design the process
Once the people layer is clear, the process layer comes next. Not technology. Process.
The process layer is about defining how the work should flow, who does what, where decisions are made, how handoffs work, and what good looks like. This is a design exercise that should happen with the people who will run the process, not for them.
Designing the process before selecting the technology has three specific benefits.
The process is designed around the work, not the tool. When you start with the process, you can design what genuinely needs to happen. When you start with the tool, you design what the tool allows. The first produces a better business. The second produces a business that fits the limitations of whatever you bought.
You can identify what the technology actually needs to do. Once the process is clear, the technology requirements become specific. You are not shopping for "a CRM" or "an automation tool." You are shopping for a tool that supports a specific, well-understood workflow. Your evaluation criteria become clear. Your selection becomes faster and more confident.
You can identify what does not need technology at all. A meaningful slice of process improvements do not require new technology. They require clearer decision rights, better handovers, or simpler workflows. When you start with process, you find these improvements. When you start with technology, you spend money you did not need to.
A practical example. Imagine your team's client onboarding process is broken. The standard pattern is to look for a client onboarding tool. The better pattern is to redesign what client onboarding should look like, then decide which parts of the redesigned process need technology and which can be improved through documentation, training, or workflow change alone.
Then select the technology
Only once the people layer is clear and the process layer is designed do you select the technology. By this point, the selection process is much easier.
The technology you need is the technology that supports the redesigned process with the people you have. Your selection criteria are specific. Your evaluation framework is clear. The risk of buying the wrong tool drops significantly because you know exactly what good looks like.
A few principles for the technology layer.
Fit the workflow, not the other way around. The right technology adapts to your business. The wrong technology requires your business to adapt to it. If a tool is forcing you to redesign your process to fit its assumptions, ask whether you are picking the right tool.
Buy capability, not features. Most tools have far more features than you will ever use. Pay for the capability you actually need, not the feature list that looks impressive in the demo.
Plan for the total cost. Subscription cost is the smallest part of the total. Implementation, integration, training, and ongoing maintenance are where the real spend happens. Budget for all of them, not just the headline price.
Pick tools that integrate. Your business runs on many tools. The ones that genuinely help are the ones that work with everything else you have, not the ones that create another data silo.
The technology layer matters. It is also the layer that gets the most attention and the most budget, despite being the layer where you have the least leverage if the people and process layers underneath are not solid.
What this looks like in practice
Imagine your business has a problem with cross-functional handovers between sales and operations. New clients are being onboarded inconsistently. The team is frustrated. Customer experience is suffering.
The wrong approach. Buy a workflow automation tool. Configure it to manage the handovers. Train the team on the new tool. Hope it works.
The right approach using PPT.
First, people. Who are the people involved in the handover today? What does each of them experience when it goes wrong? What capability do they need to run a better version of this workflow? Get them in a room. Hear from them directly. Identify the operational owner who will be accountable for the new way of working.
Second, process. Redesign the handover. What information needs to transfer? Who decides what? What is the trigger that initiates the handover? What is the acceptance step that confirms it happened? Build this design with the people who will use it, so they own it from the start.
Third, technology. Now, and only now, evaluate technology that could support the redesigned handover. Maybe it is a workflow automation tool. Maybe it is a CRM configuration change. Maybe it is a shared document template. Maybe a combination of all three. Whatever it is, the choice is informed by what the redesigned process actually needs, not by what the tool happens to do.
The difference between the two approaches is measurable. The first usually delivers thirty to fifty percent of the value it could. The second usually delivers ninety percent or more, because the foundation is right.
How AI changes the framework
The People Process Technology framework was developed sixty years before generative AI existed. The basic logic still holds, but the technology layer has shifted in important ways.
AI tools are different from previous workplace technology in three specific ways that affect the framework.
The capability is genuinely new, not just better. A CRM is a faster way to do something you were already doing. An AI tool can do work that humans were previously doing entirely. This means the process redesign question is bigger. It is not "how does this tool fit into the workflow?" It is "what should the workflow look like if AI is handling certain steps?"
The technology evolves faster than the process can. Previous technology shifts happened over years. AI capability changes month to month. This means the process design layer needs to be modular and adaptable, not locked into a specific tool's current capability.
The people layer is more important, not less. Because AI is doing more of the work, the human capability question becomes about supervision, judgement, and exception handling. The skills your team needs are different from the skills they needed a year ago. This is the people layer in PPT, and it has become more critical, not less, in the AI era.
The framework still applies. The application has evolved. The businesses that will succeed with AI are the ones that lead with people, redesign the process, and then select the technology, even when the technology is genuinely transformational. The ones that lead with AI tools and try to retrofit the rest will continue to fall into the same trap as every previous technology wave.
The bigger picture
The People Process Technology framework is not complicated. It is also one of the most underused operational thinking tools in business.
The reason it gets misused is not that it is difficult. It is that the technology layer is the most exciting, the most visible, and the most heavily marketed. Vendors do not sell processes. Consultants do not lead with people questions. The path of least resistance is to lead with technology and hope the rest catches up.
That path is what produces the operational underperformance most growing businesses are experiencing right now. The new CRM that nobody uses properly. The automation tool that automated a broken process. The AI pilot that stalled because the team was not ready. Every one of these is a People Process Technology failure, even when the people involved would not describe it that way.
The fix is to use the framework correctly. Lead with people. Design the process. Then select the technology. Slow at the front. Fast at the back. The investments deliver. The team comes with you. The business operates better.
This is one of the rare ideas in operations that gets more powerful the more disciplined you are about using it. The first time you apply it properly to a real change in your business, you will see the difference. After that, it becomes one of the most reliable thinking tools in your operational toolkit.
People first. Process second. Technology third. Every time.
