Get AI summaries of any video or article — Sign up free
How to Leverage Process Frameworks | APQC Webinar thumbnail

How to Leverage Process Frameworks | APQC Webinar

APQC·
5 min read

Based on APQC's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

About three in four organizations use a process framework; APQC’s PCF leads, followed by ITIL and SCORE.

Briefing

Process frameworks are most valuable when they’re chosen with clear criteria—especially around KPI/measure needs, industry alignment, and whether a “starter kit” exists—and then used to turn standardization into measurable performance gains. APQC’s 2023 survey results show that roughly three out of four organizations use a process framework, with APQC’s Process Classification Framework (PCF) leading, followed by ITIL and SCORE. The selection priorities have shifted since earlier survey waves: “depth” has dropped, while “breadth” no longer sits at the very top. Instead, many organizations now focus on three practical questions: whether the framework includes the KPIs/measures needed for apples-to-apples comparisons, how well it aligns to their industry, and whether it provides a starter kit so teams don’t have to build from scratch.

Once a framework is in place, organizations tend to apply it first to process discovery and performance improvement. In a live poll, about 63% of participants said they use frameworks for process discovery and standardization, with performance improvement next; roughly one-third reported they don’t use a framework yet. The survey trend reinforces that emphasis: process discovery fell from 91% of organizations in 2019 to 69% in 2023, while performance improvement has risen to nearly match it. For discovery work, frameworks help teams build process maps or models, define current processes, and document business capabilities—largely because frameworks provide a ready-made library rather than forcing teams to reinvent structure.

Performance improvement is where frameworks are meant to prevent “random acts of improvement” that can create ripple effects. APQC highlighted four common uses: (1) moving from standardization to improvement, (2) measuring whether improvements worked, (3) prioritizing improvement opportunities under resource constraints, and (4) governing process variations. The path is KPI-driven: once measures are selected, organizations can identify performance gaps and then target improvements. Success metrics should be measurable and aligned to what business leaders care about—productivity, time savings, and reduced costs—while staying objective and minimizing human bias. Prioritization also requires balancing effort and reward and accounting for upstream/downstream impacts.

Implementation differs from application. Applying a framework describes how teams use it; implementing it means embedding it into day-to-day operations. Survey results show the most common implementation steps are documenting and standardizing processes, followed by improving processes. Mapping is central to this work: frameworks define what work gets done, while process maps illustrate how it happens. Teams are advised to map only relevant processes—often starting around level three in the framework—so they don’t spend time mapping everything that won’t reveal actionable handoffs or variation.

Challenges and benefits track closely with change management. Top implementation obstacles include engagement, alignment, and purpose, plus limitations of the framework itself. APQC ties these to common change failures: insufficient communication, operational silos caused by jargon or mismatched definitions, and—most critically—lack of sustainability after rollout. Benefits reported from framework use include transparency that clarifies communication, reduced redundancy, fewer operational silos, and time savings.

The Q&A underscored practical guidance: end-to-end processes (e.g., procure-to-pay) can be incorporated via overlay, integration, or alignment depending on the goal; process relevance for mapping can be prioritized using criteria like risk, multi-department impact, and handoffs; and governance typically relies on process owners, stewards, and steering committees to enforce consistent use. Overall, the throughline is clear: frameworks deliver value when they’re selected for measurable outcomes and then embedded with governance, communication, and ongoing reinforcement.

Cornell Notes

APQC’s 2023 survey finds that about three in four organizations use a process framework, most often APQC’s PCF, followed by ITIL and SCORE. Framework selection increasingly hinges on three questions: whether the framework includes the KPIs/measures needed for comparisons, how well it aligns to the organization’s industry, and whether it offers a starter kit to avoid starting from zero. In practice, teams use frameworks mainly for process discovery and performance improvement, with performance improvement rising as a priority. Frameworks support improvement by linking standardization to measurable performance gaps, enabling objective success metrics, and providing governance for justified process variations. Lasting results depend on change management—especially communication, alignment across silos, and sustainability after rollout.

What criteria are organizations using to choose a process framework in 2023, and how has that changed since earlier survey waves?

Organizations increasingly select frameworks based on three practical needs: (1) whether the framework includes the KPIs/measures required for apples-to-apples performance comparisons, (2) how closely the framework aligns to their industry (cross-industry content can help but may not fit every nuance), and (3) whether a starter kit is included so teams don’t have to start from scratch. Earlier surveys emphasized “breadth” and “depth,” but in 2023 “depth” has fallen off the top criteria and “breadth” has moved down to around the middle of the ranking.

How do organizations typically apply frameworks, and what trend stands out between 2019 and 2023?

Most organizations apply frameworks to process discovery and performance improvement. For discovery, frameworks help build process maps/models, document current processes, and support business capability documentation—because they provide a ready-made library. A key trend: process discovery dropped from 91% of organizations applying it in 2019 to 69% in 2023, while performance improvement rose to nearly tie for second priority.

What does “standardization to improvement” look like in practice?

Frameworks support improvement by making measures central. Once KPIs/measures are chosen, organizations assess process performance against those measures, identify performance gaps, and then prioritize improvement work. Standardization also contributes directly by removing redundancy and non-value-added variations, making improvements more sustainable across the enterprise.

What makes success metrics for process improvements credible and useful?

Success measures should be measurable and aligned to what business leaders care about—examples given include increased productivity, time savings, and reduced costs. When technology and data are involved, measures should remain objective and as free from human bias as possible. Teams are also encouraged to keep an open mind about outcomes; setting one expected result and forcing everything toward it can backfire if the real end state differs.

How should organizations handle process variations without losing control of consistency?

Variations are expected, but governance is required to decide whether they’re justified case-by-case. At a higher level, organizations can standardize the process using the framework as a guide, then document variations at lower levels with clear rationale and ownership.

What are the most common implementation steps, and why does mapping depth matter?

The top implementation steps reported are documenting and standardizing processes, followed by improving processes. Mapping is used to illustrate how work happens: frameworks define what work gets done, while maps show how it flows. Depth depends on mapping purpose and risk—organizations often start around level three, where handoffs become visible; mapping too shallow can miss critical handoffs, while mapping everything can waste time and resources.

Review Questions

  1. Which three questions should guide framework selection, and why does each one matter for measurable outcomes?
  2. Describe the difference between applying a framework and implementing one. What implementation steps were most common in the survey?
  3. Give two reasons why mapping only relevant processes (and choosing an appropriate level) can outperform mapping everything at maximum detail.

Key Points

  1. 1

    About three in four organizations use a process framework; APQC’s PCF leads, followed by ITIL and SCORE.

  2. 2

    Framework selection in 2023 centers on KPI/measures availability, industry alignment, and whether a starter kit reduces build-from-scratch effort.

  3. 3

    Process discovery remains a top use case, but performance improvement has risen and nearly ties it in priority.

  4. 4

    Framework-driven improvement relies on KPI-based performance gaps, objective success metrics, and prioritization that accounts for ripple effects.

  5. 5

    Process maps complement frameworks: frameworks define what work categories exist; maps show how work flows and where handoffs occur.

  6. 6

    Implementation success depends on change management—especially engagement, alignment across silos, effective communication, and sustainability after rollout.

  7. 7

    Governance for process variations is essential: standardize at higher levels, justify variations case-by-case, and document them at lower levels with clear ownership.

Highlights

Depth has lost ground as a top framework-selection criterion; KPI/measures, industry fit, and starter-kit usefulness now drive more decisions.
Process discovery application fell from 91% (2019) to 69% (2023), while performance improvement rose to nearly match it.
Frameworks are meant to prevent “random acts of improvement” by linking standardization to measurable performance gaps.
Mapping depth should match risk and handoff complexity; many organizations start around level three to reveal actionable handoffs.
Sustainability is the recurring failure point—frameworks can be implemented and then “go stale” without ongoing reinforcement and governance.

Topics

Mentioned

  • Kelly South
  • Madison Lundquist
  • PCF
  • ITIL
  • SCORE