Frequently Asked Questions About APQC Process Framework Implementation Method
21 answers covering everything from basics to advanced usage.
// Basics
What is APQC's Process Classification Framework (PCF)?
The PCF is APQC's taxonomy-based framework that lists what work gets done across an organisation. It provides a ready-made library of process categories and definitions used as the starting point for process discovery, standardisation, and improvement. Industry-specific variants exist. It is not a procedure — it does not describe how work is done, only what work is done.
What does 'framework lists WHAT, not HOW' actually mean?
A framework catalogues the categories of work an organisation performs — like 'manage accounts payable' or 'develop products' — without prescribing the detailed execution steps. The HOW lives in procedures, work instructions, and process maps. Keeping these artefacts distinct prevents confusion: the framework is your authoritative list of process categories, while maps document the actual flow of a specific process.
What inputs do I need to start applying this method?
Three are required: your organisation context (industry, size, functions in scope), your current process management maturity level (lowest, developing, or most mature), and your primary use case (discovery, performance improvement, technology implementation, audit, or benchmarking). Optionally, define your adoption scope target and list any existing frameworks or tools the new framework must align with.
// How To
How do I decide my process management maturity level?
Self-assess on a scale of lowest, developing, or most mature based on how sophisticated and embedded your process management programme is. Maturity influences recommended tooling — Office documents at low maturity, ERP platforms at high maturity — and adoption scope, since organisation-wide adoption is more prevalent at higher maturity. Be honest; over-stating maturity leads to over-engineered tooling you won't use.
How do I apply a framework to an ERP implementation?
Before configuration begins, use the framework to document and standardise current processes, build a process library, and take inventory of current IT applications. This gives you leverage to configure the ERP to your architecture rather than inheriting the vendor's defaults. Use value stream mapping to capture end-to-end flow and expose waste before it gets hardwired into the new system.
How do I build a business case for expanding from siloed to organisation-wide adoption?
Reference the effectiveness gap: 46% of siloed adopters rate their process efforts effective versus 61% for business-unit and 80% for organisation-wide adoption. Frame siloed adoption as a transitional state, not a destination. Then execute the four-stage change management process, break down language silos with shared glossaries, and establish cross-company goals so all units work toward the same priorities.
How do I run a current state assessment effectively?
Combine methods rather than relying on one. Surveys are fast and broad; interviews are deep and individual; workshops are collaborative and cross-functional. Choose your mix based on available information, BPM maturity, and required employee engagement. The goal is to understand what's actually happening, establish a baseline, surface non-value-added tasks, and get employees thinking in process terms before defining the to-be state.
Do I have to document processes before I can improve them?
Yes. Step one is always to document and standardise using the framework's common language and definitions so all parts of the organisation describe work the same way. Only after a documented baseline exists can improvement be meaningful and sustainable. Maps and process documentation tangibly show how processes occur and where non-value-added tasks happen, giving improvement a target.
// Troubleshooting
My improvement efforts look good short-term but keep falling apart. What's wrong?
You're likely making fragmented or random acts of improvement without a structured framework-based approach. These may show early wins but are unsustainable and can damage upstream and downstream processes. Adopt a framework to establish common language and definitions, document and standardise first, and only then improve — so gains hold across connected processes.
We adopted the framework but nobody's using it. How do I fix engagement?
Address the Buy-in & Engagement challenge. Communicate the framework's value clearly and use a range of incentives — both monetary (pay, bonuses) and non-monetary (recognition, thanks). Critically, embed desired behaviours into performance reviews so adoption signals as a required function of the job, not optional. Relying on a single incentive type fails because different people respond to different motivators.
Our ERP vendor already configured our processes their way. Can we still apply this method?
Yes, but you're now managing costly rework rather than avoiding it. Document your actual processes using the framework, identify where the vendor architecture misaligns with your operations, and prioritise reconfiguration for high-risk, day-to-day, and mission-critical processes. Going forward, apply Governance Before Technology so future implementations don't repeat the mistake.
We've been using a framework for six months and see little improvement. Should we abandon it?
No — you're measuring success prematurely. Value compounds over years, not months. About two-thirds of organisations using the PCF under a year strongly agree it improved processes, rising to 96% at 10+ years. Check you've documented and standardised before trying to improve, and that you're tracking the right benefits like transparency and reduced silos.
// Comparisons
How does a process framework compare to building processes from scratch?
A framework provides a ready-made library of processes and definitions, turbocharging discovery and standardisation. Building from scratch means inventing processes out of thin air — slower, inconsistent, and lacking common language across the organisation. Treat the framework like a list of ingredients: you select what's relevant and assemble the meal, rather than reinventing every recipe.
How does the APQC method compare to generic BPM approaches?
Generic BPM often jumps straight to mapping and improving processes. The APQC method insists you document and standardise using common language first, apply a relevance filter instead of mapping everything, match tooling to maturity, and treat organisation-wide adoption as the effectiveness driver. It also builds in structured change management and long-term benefit tracking, recognising that value compounds over years.
What's the difference between siloed, business-unit, and organisation-wide adoption?
Siloed adoption is deployment within isolated functions; business-unit adoption covers one or more units; organisation-wide spans the entire enterprise. Effectiveness rises with scope: 46% siloed, 61% business-unit, 80% organisation-wide. Siloed and business-unit adoption should be transitional stages with an explicit roadmap to organisation-wide, which is the strongest predictor of process management effectiveness.
Should I use a survey, interview, or workshop for current state assessment?
Use them in combination for best results. Surveys reach broad audiences fast; interviews probe deep with individuals; workshops enable cross-functional collaboration. A survey-plus-workshop combination is common — the survey gathers wide input and the workshop aligns cross-functional stakeholders. Choose your mix based on available information, BPM maturity, and how much employee engagement you need.
// Advanced
How do I use value stream mapping to break down organisational silos?
Use value stream mapping to document high-level, end-to-end process steps, capturing the flow of information and materials while driving out waste. Because it spans functions, it forces cross-functional collaboration and reveals the full process picture. Pair it with shared glossaries that define or eliminate jargon, cross-company goals, shared improvement efforts, and process improvement walks organised by work cells.
What is the four-stage change management process and why does the final stage matter most?
The stages are Plan, Design, Implement, and Sustain. At each, communicate what's changing, when, and how staff will be supported, using a phased plan with emails, town halls, forums, videos, and social media. The Sustain stage — shifting the culture — is what makes change permanent. Without it, implementation gains erode and the effort won't hold.
Why is framework alignment with existing software now a top-five selection factor?
AI and emerging tools have made integration critical. If your framework doesn't align with the processes and business software already in use, you create friction, duplicate definitions, and undermine the common language the framework is meant to provide. When selecting a framework, explicitly assess how well it maps to your current systems and toolchain, not just its process coverage.
What are the two evergreen adoption challenges and how do I address them?
Buy-in & Engagement and Alignment & Purpose. For Buy-in, overcome resistance with clear value communication, varied monetary and non-monetary incentives, and behaviours embedded in performance reviews. For Alignment, collaborate cross-functionally to define which processes are prioritised and how process efforts support organisational goals, ensuring efforts reflect the full picture rather than staying confined within silos.
How do I measure and sustain the value of a process framework over time?
Track the top five benefits year-over-year: transparency, clarified communications, established buy-in, reduced operational silos, and reduced redundant processes. Because value compounds — 96% satisfaction at 10+ years versus roughly two-thirds in year one — sustained commitment is the strategy. Use these metrics to justify continued investment and resist the temptation to declare success or failure prematurely.