The Art of Managing Processes within Management Systems

TL;DR

Treat processes as cross-functional, measurable, and improvable units—not as isolated functional activities.

Briefing Cornell Notes

Briefing

Sustained performance in management systems depends on treating processes as cross-functional, measurable, and continuously improvable—then wiring those process improvements into business excellence objectives instead of stopping at compliance. Colin Christmas argues that many organizations build management systems that satisfy ISO-style requirements and audits, but fail to deliver the intended outcomes because process thinking stays trapped inside functional silos. The result is “uniformity of routines” rather than “uniformity of output,” where teams follow procedures yet miss strategic objectives, customer needs, or risk reduction.

Christmas frames process management through ISO definitions: processes are interrelated activities that use inputs to deliver intended outputs, and management-system processes must be identified, measured, and improved. He stresses two practical lenses—efficiency (resource use versus results achieved) and effectiveness (whether outcomes align with objectives). A management system can look compliant while still underperforming if objectives aren’t cascaded, targets aren’t realistic, and the organization isn’t measuring the right indicators. He also warns that treating all processes as equal wastes effort; organizations should prioritize “critical processes” tied to strategic drivers and must-win battles.

A central theme is the need to connect process owners across boundaries. Christmas says process owners often sit in specific functions and naturally optimize their “box,” but cross-functional processes require people who can “connect the dots.” He recommends simple, hands-on exercises to force clarity: mapping end-to-end processes with swim lanes, then using Post-it note workshops to align outputs with the inputs of the next process owner. When the receiving team says the output arrives too late, lacks granularity, or doesn’t match what they need, the organization gets “aha moments” that reveal where accountability and design break down.

For management-system managers, Christmas pushes back on a common mismatch: subject-matter expertise in quality, safety, or compliance doesn’t automatically translate into process and systems thinking. He urges systems managers to work alongside process improvers and adopt data-driven, risk-based, and PDCA (Plan-Do-Check-Act) mindsets. PDCA becomes the practical bridge between process mapping and improvement: plan with objectives and targets, do with execution constraints and input quality, check with performance measurement, and act by validating that outcomes match what customers or stakeholders actually need—not just that the product is “safe.”

He also outlines a process framework hierarchy to make mapping scalable—from strategy and policies down to process maps, procedures, and records—then adds a benchmarking step using APQC’s Process Classification Framework (PCF) to compare designed processes against reference models by industry sector. Consistency matters: organizations need shared mapping principles so one team’s “one-page” process view doesn’t become another team’s 25-process sprawl.

Finally, Christmas argues that the biggest payoff comes when business excellence and management systems stop operating as separate teams. He cites APQC case study material about Tata Projects Limited as an example of integrating process frameworks with certification standards and process improvement. The ultimate goal is an “S-curve” shift from compliance to continuous improvement that prevents serious failures—ranging from food safety recalls to safety incidents—by ensuring cross-functional accountability and measurable outcomes.

Cornell Notes

The core message is that management systems deliver lasting success only when processes are treated as cross-functional, measurable, and continuously improved—not merely when standards are met. Colin Christmas ties ISO process definitions to practical management: identify processes, measure them, and improve them using efficiency and effectiveness checks. He emphasizes that process owners must truly own their processes and that outputs must fit the needs of the next function, which can be revealed through Post-it note mapping exercises. PDCA provides the improvement engine, while APQC’s Process Classification Framework (PCF) helps benchmark process design against reference models. The payoff is stronger alignment between management-system work and business excellence objectives, producing outcomes that reduce risk and improve customer value.

Why does “compliance” often fail to produce the outcomes leaders expect from a management system?

Christmas distinguishes conformance from performance. A management system can satisfy standard requirements and pass audits while still missing objectives because processes may not be measured properly, targets may not be cascaded, and teams may focus on routines rather than end-to-end outputs. He urges checking both efficiency (results versus resource use) and effectiveness (whether desired outcomes are achieved). If objectives aren’t met, the process design and the management-system mechanism may not be robust enough to deliver the intended results.

How can organizations make cross-functional process ownership real instead of theoretical?

He recommends practical visualization and accountability exercises. First, map end-to-end processes with swim lanes to show how work crosses functional boundaries. Then run a Post-it note workshop: list each process owner’s outputs, connect those outputs to the next process owner’s inputs, and ask whether the receiving team is satisfied with timing, granularity, and usability. When the answer is “not really,” the organization uncovers design and responsibility gaps and creates momentum to fix them.

What does “process ownership” mean in practice, and how should systems managers engage process owners?

Ownership means the process owner must understand and take responsibility for the process—not delegate it away to a quality or compliance function by default. Christmas advises systems managers to start with the process owner’s biggest headache (e.g., a procurement director’s slow supplier onboarding). Mapping that specific process and linking it to measurement, audits, and improvement helps earn buy-in; once the process owner sees results, they stop treating systems support as a burden and start calling for help.

How do process frameworks and reference models fit into linking management systems to improvement?

Christmas describes a hierarchy from strategy and policies down to process maps, procedures, and records, where macro processes come first. After mapping, teams can benchmark their process design against a reference model using APQC’s Process Classification Framework (PCF), which can be applied by industry sector or used generically. This supports re-engineering by showing where processes align well—or where they don’t.

How does PDCA connect process mapping to continuous improvement and better outcomes?

PDCA becomes the improvement workflow. In the Plan stage, teams align objectives, targets, and measurement choices. In Do, they execute while identifying constraints and whether inputs meet expectations. In Check, they evaluate performance against the plan using the right measures. In Act, they confirm whether expected outcomes are truly achieved—emphasizing that “safe” isn’t enough if customer satisfaction is the real outcome.

What’s the relationship between business excellence and management systems in Christmas’s view?

He argues that many organizations keep these functions separate, creating a disconnect between objectives and process improvement. The fix is cultural and structural: start conversations, hold lunch-and-learns, and physically reduce barriers (e.g., seating teams together to avoid “walls” between functions). He points to APQC case study material about Tata Projects Limited as an example of integrating process frameworks with certification standards and process improvement under shared accountability.

Review Questions

What evidence would show that a management system is driving effectiveness (outcomes) rather than only conformance (audit readiness)?
Describe a Post-it note exercise for aligning process outputs to the next process’s inputs. What kinds of mismatches typically surface?
How would you apply PDCA to a cross-functional objective (e.g., reducing customer complaints) using end-to-end and swim-lane process mapping?

Key Points

1
Treat processes as cross-functional, measurable, and improvable units—not as isolated functional activities.
2
Use ISO-aligned process thinking: identify processes, measure them, and improve them based on intended outputs.
3
Evaluate management-system performance through both efficiency (resources used) and effectiveness (objective/outcome achievement).
4
Prioritize critical processes linked to strategic drivers; avoid spreading effort across everything equally.
5
Make process ownership real by mapping outputs to the next process’s inputs and resolving mismatches revealed by Post-it note exercises.
6
Embed continuous improvement with PDCA, ensuring “Check” uses the right measures and “Act” confirms expected outcomes (not just compliance).
7
Reduce the gap between management systems and business excellence by building shared accountability and working relationships across teams.

Highlights

A management system can be audit-ready yet still fail if it delivers routines instead of end-to-end outputs aligned to objectives.

Swim lanes and Post-it note output/input mapping are simple ways to expose where functional silos break process flow.

PDCA is the practical bridge from process maps to improvement—especially when “safe” outcomes don’t equal the real customer or stakeholder outcome.

APQC’s Process Classification Framework (PCF) helps benchmark process design against reference models to guide re-engineering.

Cross-functional accountability is essential to prevent serious system failures, from safety incidents to food safety recalls.

Topics

Process Management
Management Systems
ISO Process Approach
PDCA
APQC Process Classification Framework

Mentioned

APQC
Ego Certification Group
Eagle's International
Nestle
Tata Projects Limited
Colin Christmas
ISO
TQM
PCF
PDCA
MSS