APQC Process Maturity Model: Seven Tenets and PCF Levels

The APQC process maturity model is APQC's Seven Tenets of Process Management, a framework of seven areas that together describe how mature an organization's process management practice is, with a five-point scale applied to each tenet. The seven tenets are strategic alignment, governance, process models, change management, performance and maturity, process improvement, and tools and technology. It is a separate thing from APQC's Process Classification Framework, the PCF, which is a taxonomy of business processes arranged in five levels under thirteen top-level categories. Those two get confused constantly, including in vendor marketing, so this piece separates them before doing anything else.

What is APQC?

APQC stands for the American Productivity and Quality Center. It is a member-based nonprofit headquartered in Houston, and its work is benchmarking and best-practice research: it collects process performance data from member organizations and publishes the frameworks, definitions, and measures that let one company compare its processes with another's on a common basis. APQC describes itself as working with more than 500 organizations worldwide across all industries.

That origin explains the shape of everything APQC publishes. The frameworks exist to make comparison possible. If your finance close process is called something different from everyone else's, benchmarking it is meaningless, so APQC's first contribution was a shared vocabulary and its second was the maturity thinking layered on top.

The seven tenets of process management

APQC's own paper on the subject states the position directly: years of process-based research uncovered seven essential tenets on which to establish a strong process capability. These are what the APQC maturity model actually measures. The descriptions below follow APQC's published definitions.

APQC publishes a five-point maturity scale for each tenet, along with practices for moving up it. The scale itself sits inside APQC's member library rather than on the open web, so this article does not reproduce level names it cannot verify at source. What you can do without membership is use the seven tenets as the assessment structure, which is most of the value: the diagnostic question is which of the seven is weakest, and that is answerable with your own evidence.

APQC process maturity model vs the Process Classification Framework

This is the distinction that trips people up, and APQC's own paper draws it cleanly. A process framework illustrates a hierarchy or decomposition of processes. A process model shows how those processes are managed across the organization. The PCF is the framework. The Seven Tenets are the model of the management practice around it.

In plain terms: the PCF tells you what your processes are and gives them standard names and numbers. The Seven Tenets tell you whether you run them like a mature organization. You can adopt the PCF as a taxonomy and still score badly on every tenet, and plenty of organizations do exactly that, which is how a company ends up with a beautifully mapped process library that nobody owns and nobody measures.

APQC PCF levels: how the framework is structured

The PCF is hierarchical. It opens with thirteen Level 1 categories, which are the broadest groupings, and each of those decomposes through four further levels.

The thirteen Level 1 categories in the cross-industry PCF are: develop vision and strategy; develop and manage products and services; market and sell products and services; deliver physical products; deliver services; manage customer service; develop and manage human capital; manage information technology; manage financial resources; acquire, construct, and manage assets; manage enterprise risk, compliance, remediation, and resiliency; manage external relationships; and develop and manage business capabilities.

One structural detail matters when you start using it. In the PCF, each element is defined by its children. A process group is defined by the processes underneath it, a process by the activities underneath it, and so on. That is why you cannot meaningfully adopt the top two levels and stop: the definitions live further down. APQC also publishes industry-specific versions of the PCF alongside the cross-industry one, so a bank and a utility are not forced into the same vocabulary for work that genuinely differs.

How to run an APQC-style process maturity assessment

You do not need APQC membership to assess yourself against the seven tenets, and the discipline of doing it honestly matters more than the instrument. A workable sequence:

1. Pick the scope before the framework. Assessing "our processes" across a whole enterprise produces an average that describes nothing. Choose either one PCF category, for example manage financial resources, or one business unit, and assess that.
2. Score each of the seven tenets separately. Resist the urge to produce one overall maturity number first. The finding you want is which tenet is weakest, because process capability behaves like a weakest-link system rather than an average.
3. Gather evidence, not opinions, for governance in particular. Ask who the named owner of a specific process is, then ask that person whether they know they own it. Governance is the tenet where self-assessment is most flattering and the evidence test is easiest.
4. Ask the people executing the process, not only the process office. Maturity scores collected exclusively from the team that runs the process program are reliably high. The useful reading comes from the operators who live with the handoffs.
5. Re-score on a fixed interval. A single maturity reading is a snapshot with no trend, and process maturity moves over years. Annual is the usual cadence, and the value only appears at the second reading.

APQC vs CMMI vs the other process maturity models

APQC is one of several answers to the same question, and they are not interchangeable. This is the shortlist most process teams end up comparing.

Two honest notes on that table. APQC's framework is free to structure your thinking around and its deeper resource library is a membership product, so the cost depends entirely on how far in you go. And our own process maturity assessment is not an APQC instrument, is not endorsed by APQC, and awards no APQC or CMMI rating. It scores the conditions that produce process maturity and benchmarks them, which is a smaller claim than an appraisal. If a formal appraised level is what you need, our explainer on the CMMI maturity model covers what that process actually involves.

Where process maturity assessments usually go wrong

• Mapping instead of managing. The most common failure is treating PCF adoption as the project. A complete process map with no owner, no measure, and no improvement cadence scores badly on five of the seven tenets while looking like progress.
• Assessing the process office instead of the organization. If the people who built the process program are the only ones scoring it, the result is a self-report on their own work.
• Documentation nobody can find. The process models tenet is about captured knowledge, and captured is not the same as findable. Plenty of organizations have the documentation and still work from memory because it is buried across a wiki, a shared drive, and three people's inboxes. When the complaint is "I did not know that was documented", the gap is retrieval rather than authorship, and making every answer at work searchable in one place closes it faster than another mapping exercise will.
• One number instead of seven. Rolling the tenets into a single maturity score destroys the only actionable finding, which is which tenet is holding the rest back.
• Confusing process maturity with digital maturity. Automating a badly governed process makes it faster and no more mature. The tools and technology tenet sits last in APQC's list for a reason.
• No second reading. Maturity assessment produces value as a trend. A one-time exercise filed as a report is a cost, not a diagnostic.

What is process maturity, in one paragraph?

Process maturity is how consistently and deliberately an organization runs its processes: whether they are defined, owned, measured, and improved on purpose, or whether they work because experienced people remember how. A mature process survives the departure of the person who invented it. An immature one does not, which is why maturity is the thing that predicts whether performance holds when the team changes.

Is the APQC framework free to use?

APQC publishes the Process Classification Framework on its own site, and the frameworks and a portion of the resource library are openly available, with much of the deeper research and the detailed maturity content restricted to members. In practice this means you can adopt the PCF taxonomy and the seven tenets as a structure without paying anything, and you pay if you want APQC's benchmark data, the detailed maturity scales, or its assessment services. Confirm current access terms on APQC's own site before planning around them, since membership models change.

The short version

Use the PCF when the problem is that nobody agrees what the processes are called. Use the seven tenets when the problem is that the processes exist and still do not improve. Score the tenets separately, get your evidence from the people executing the work rather than the people running the program, and re-score on a fixed cadence, because the second reading is where the information is. If you want process maturity scored against an industry median alongside the four other dimensions that determine whether process work sticks, a process maturity assessment returns all five in one report, and the organizational maturity model page covers how process maturity fits the wider capability ladder.