Accelerating the Value From a Process Framework

A process framework only delivers real business value when it’s governed, connected to performance, and made usable across the organization—APQC’s Mosaic environment is positioned as the mechanism to do that, but Mosaic’s benefits depend on how the framework is set up and adopted. The core message from the session is that organizations should not “jump in” with the tool; they should first decide how they will use a framework, who can change it, how knowledge will be stored and accessed, and how results will be measured. Done well, Mosaic helps turn process documentation, benchmarks, and lessons learned into a shared operating system for execution.

APQC frames process management around five lifecycle phases: identify and organize processes, capture and design process knowledge, perform and manage work, monitor and control performance, and then improve and integrate to close the loop. Under that lifecycle sit seven process-management tenants—such as strategy alignment, process governance, usable process models, and accessible process knowledge—that define what “well-managed” looks like. Mosaic is presented as a way to operationalize those tenants by linking the framework to roles, tools, performance measures, and best-practice research.

In APQC’s definition, a process framework is a catalog of mutually exclusive, collectively exhaustive, hierarchically decomposed processes—ranging from enterprise-level strategy down to granular activities. The “mutually exclusive” principle prevents the same work from appearing multiple times in conflicting ways, while “hierarchical decomposition” breaks large goals into manageable chunks that can be owned by departments and functions. Just as importantly, the framework becomes a bridge between what the organization does and who does it: roles and responsibilities in the org chart can be mapped to the processes they execute, and tools, data architecture, policies, standards, and constraints can be connected to the work.

Mosaic (and Mosaic Accelerator) is described as a structured environment for managing that process knowledge. Mosaic provides three linked views—Manage, Measure, and Learn. “Manage” centralizes process content such as flowcharts and lessons learned, either directly in Mosaic or via links to internal systems like SharePoint. “Measure” ties process work to benchmarks and performance metrics, including live feeds from APQC’s benchmarking portal for comparisons across industries, regions, and organization sizes. “Learn” connects users to APQC’s knowledge base research, white papers, and reports relevant to specific processes.

The session’s practical emphasis lands on governance and adoption. Mosaic Accelerator is laid out as a five-step approach: run a health/readiness check (including how many frameworks exist and how they fit together), assemble a design team, make design decisions (including access control such as read-only versus edit permissions and how changes get reviewed), implement with training and communications, and then provide ongoing support so the business uses the system correctly. A key warning appears repeatedly: without that structured setup, organizations risk clutter, inconsistent process knowledge, and even publishing the wrong version of “how we do the work.”

In the Q&A, participants described using Mosaic selectively—especially for knowledge management through communities and embedding lessons learned into workflows. APQC also shared that shared services functions (finance, human capital management, supply chain) can benefit because standardized processes can be mapped to how work connects across the enterprise. One example from APQC itself highlighted a gradual migration strategy: link existing process knowledge wherever it currently lives, then move content into Mosaic’s consistent storage over time rather than pausing all work to migrate everything at once.