PCF Case Studies: How Organizations Use the Process Classification Framework

Organizations use the Process Classification Framework (PCF) less as a static taxonomy and more as a practical engine for transformation: it helps teams assess where processes stand, align work across functions, and then turn that shared understanding into measurable roadmaps.

A standout case is Elevations Credit Union, where a new CEO in 2008 pushed for a more efficient organization and a path toward adopting the Baldrige criteria and winning the Malcolm Baldrige award. The process improvement team started with a “current state” assessment using the banking PCF. They converted PCF sections into a survey, drilled down to level-three processes, and asked finance, sales, and other functions to rate each process on a one-to-five scale—ranging from “we don’t really have anything documented” to a “nirvana” end state where work is documented, consistently followed, and tied to measures. Those ratings revealed gaps and strengths.

Next came an internal framework-building phase. The team took the banking PCF and ran large workshops with the right people, using color-coded post-it notes to mark gaps across PCF sections. Through structured conversations, participants decided which gaps were real needs versus unnecessary complexity, and the organization assembled an “as-is” map. That engagement mattered: people could see how their work affected the business and how it connected to other teams, which accelerated the transformation.

With the “as-is” picture in place, Elevations moved to a “to-be” state and then structured a BPM tracking tool. The adapted PCF fed directly into scorecards that tracked project status, process owners, and supporting resources like measures. The result was an end-to-end approach—from assessment to execution—over roughly 2,000 days, culminating in winning the Malcolm Baldrige award by 2014.

Other organizations used the PCF to sharpen improvement prioritization. Sword’ group treated PCF level-one categories as a backbone for process improvement: interviews produced ratings that fed a maturity assessment scorecard built around five categories—process maturity (documentation and compliance), business contribution (impact on organizational goals), business alignment (fit between importance and capability), accountability (governance, roles, process ownership), and performance measurements (KPIs and results). Those inputs were then plotted on a two-by-two to weigh potential value against feasibility, helping teams select the best improvement targets.

HP used the PCF as a taxonomy for process improvement requests, flagging initiatives against PCF categories to reduce redundancy and manage scope across the organization.

For technology adoption—especially ERP—Pearson’s case highlighted how PCF can reduce resistance by using an objective third-party reference. Multiple regions had run separate ERP implementations with different consultants, creating wasted effort and undermining standardization goals. Workshops used PCF process areas (record-to-report, procure-to-pay, and order-to-cash) to compare current practices, identify redundancies and gaps, and consolidate finance processes. The effort reduced the number of processes from 27 to 21.

University of North Texas system used the PCF as a foundation for a SOP taxonomy and document repository, enabling teams to drill down from high-level process groups to specific process pages and related content. CMI combined PCF-based mapping with annual reassessment to prioritize common end-to-end processes, using PCF’s embedded KPI associations as a benchmarking aid.

Across these examples, the common thread is that digital transformation often stalls without a process foundation. By standardizing and documenting processes through the PCF, organizations can better automate work—particularly transactional, non-differentiating processes—using tools like robotic process automation without getting stuck in endless rework over “what the process really is.”