How to Start Your First Process Framework Programme
For First-time process leads at growing organisations · Based on APQC Process Framework Implementation Method
// TL;DR
First-time process leads starting a process improvement programme should resist the urge to map everything. Apply the APQC Process Framework Implementation Method: select a framework using the three selection questions, choose a management tool matched to your (likely lower) maturity — usually Microsoft Office to start — and filter processes through the Relevance Over Completeness lens (risk, day-to-day operations, mission-critical). Use the framework's ready-made library to identify relevant categories fast rather than inventing processes from scratch. Run a current state assessment using a survey-plus-workshop combination to baseline performance and get employees thinking in process terms before defining the to-be state.
Where do I even start with my first process framework?
Start by selecting the right framework, not by mapping processes. Use the three selection questions: Does the framework have the level of detail you need? Does it include the additional information you need for your process work? Does it cover the functional and industry-related processes you're focused on? Check whether an industry-specific variant exists — for example, APQC publishes industry-specific PCFs — and assess how well the framework aligns with the software you already use, since alignment is now a top-five selection factor.
The framework gives you a ready-made library of process categories and definitions. Treat it like a list of ingredients: you select what's relevant and assemble the meal. This turbocharges discovery because you're not inventing processes from thin air.
What tool should I use as a beginner?
Match the tool to your maturity. As a first-time process lead, you're almost certainly at lower maturity, and the most common approach is to start with Microsoft Office products or documents. Don't over-engineer. ERP platforms for framework management are for the most mature organisations (~40% of them), not for a programme finding its feet. Over-engineering tooling before you're ready wastes budget and stalls adoption.
How do I decide which processes to map?
This is where new leads most often go wrong: they try to map everything. Apply the Relevance Over Completeness principle instead. Only map a process if it meets at least one of three criteria:
- Does it involve risk?
- Does it affect day-to-day operations?
- Does it include mission-critical tasks?
Use the framework's library to spot relevant categories quickly. Everything else can wait. Focusing on relevance keeps your first programme manageable and demonstrably valuable.
How do I baseline what's actually happening?
Run a current state assessment before you define any to-be state. Its purpose is to understand what's truly happening today, establish a performance baseline, surface non-value-added tasks, and get employees thinking in process terms.
Choose your method based on available information, BPM maturity, and how much engagement you need — but don't rely on just one. Surveys are fast and broad; interviews are deep and individual; workshops are collaborative and cross-functional. A survey-plus-workshop combination is a strong default: the survey gathers wide input and the workshop aligns stakeholders. Only after this baseline exists can you identify the to-be state and prioritise improvements.
What sequence should my implementation follow?
Document and standardise first, then improve. Use the framework's common language so every part of the organisation describes work the same way. Maps and documentation tangibly show how processes occur and where waste is happening. Only after a documented baseline exists can improvement be meaningful and sustainable — otherwise you risk fragmented or random acts of improvement that look good initially but don't last and can damage connected processes.
How do I make sure it sticks?
Even a first programme needs change management. Communicate what's changing, when, and how you'll support people. Use varied incentives — monetary and non-monetary — and embed process behaviours into performance reviews. Track benefits year-over-year: transparency, clarified communications, buy-in, reduced silos, and reduced redundancy. Value compounds over years, so plan for sustained commitment, not a quick win.
Next step
Pick your framework using the three selection questions this week, then run a lightweight survey-plus-workshop current state assessment on your three most relevant processes — the ones with risk, daily impact, or mission-critical tasks. Document and standardise those first before touching improvement.
// FREQUENTLY ASKED QUESTIONS
What's the biggest mistake first-time process leads make?
Trying to map every process instead of applying the relevance filter. Only map processes that involve risk, affect day-to-day operations, or include mission-critical tasks. Use the framework's ready-made library to identify relevant categories quickly. Mapping everything wastes effort, overwhelms your team, and dilutes the value of your first programme.
Do I need expensive software to start a process framework?
No. Match the tool to your maturity level. As a beginner at lower maturity, start with Microsoft Office products or documents — the most common approach. ERP platforms for framework management suit only the most mature organisations. Over-engineering tooling before you're ready wastes budget and stalls adoption.
Should I improve processes right away or document them first?
Document and standardise first using the framework's common language, then improve. Only after a documented baseline exists — established through a current state assessment — can improvement be meaningful and sustainable. Improving before documenting leads to fragmented, random acts that may look good initially but are unsustainable and can damage upstream and downstream processes.