Gluu

Gluu Academy

Designing process architectures

Process architecture fundamentals

In this Gluu Academy lesson, you’ll learn how to design a process architecture that connects strategy to execution — turning big goals into everyday actions. Through the example “Supplier Selection”, we’ll show how architecture links value chains, ownership, systems, and improvement loops into one connected framework.

Lesson resources

Key learnings

  • Architecture links strategy → execution
  • Eight parts in a process architecture: Landscape, Hierarchy, Ownership, Interfaces, Standards, Measures, Tech/Data, Improve
  • Parts interlock: top anchors, bottom standardizes, feedback sustains
  • Start small with one example: Landscape → L3 owners → L4 map → L5 how-to → KPIs/controls → Pilot → Improve.

Video transcript

By the end of this lesson, you’ll understand how a process architecture connects strategy to daily work. You’ll learn the core parts, how they fit together, the order to tackle them

I will use the process Supplier selection as our running example for explaining the basics of process architecture. Our own BPM tool will serve as the basis for the illustration.

Architecture is your map of flow and value. It shows what exists, who owns what, and how standard work is done.

Without it, we get silo fixes, duplicated projects, and ‘automation without clarity.’

With it, we focus investments, align teams, and make good practices repeatable.

A process architecture normally has eight basic parts:

  1. Landscape
  2. Hierarchy
  3. Ownership
  4. Interfaces
  5. Standards
  6. Measures
  7. Tech & Data
  8. Improvement

These eight parts interlock. I’ll explain each briefly, show how it relates to the others, give the ‘Supplier selection’ example, and mention common frameworks or tools.

The process landscape often starts with a value chain that is a one-page helicopter view of how the business delivers value end-to-end. It anchors strategy and shows where to invest.

For example: ‘Select supplier’ lives under Procure products & services

The hierarchy is a shared scale—from big categories down to tasks—so everyone speaks the same language.

Now let me show you some example levels:

L1 Operate the business → L2 Procure products & services → L3 Select supplier → L4 activities (e.g., Evaluate suppliers, Register supplier in ERP, etc. → L5 work instructions and tasks: Register supplier

Frameworks: APQC levels for naming; BPMN for L3; works instructions managed at L4 and L5.

Clear ownership helps keep processes updated and alive after launch.

Example: Process owner = Head of Procurement; editors = Category Manager and Legal/Quality; executors = Buyers. This can all be detailed as a RACI matrix.

Tools: RACI template, owner network, lightweight change log.

Interfaces make boundaries explicit so work flows more smoothly.

Example: Inputs from Select supplier; outputs to Register supplier in ERP. Triggers like ‘new category need’ start the flow.

Tools: SIPOC for quick scoping; BPMN message flows; a simple interface catalog.

Standards turn maps into standard work.

Example: Activity ‘Register supplier in ERP’ has a 10-step instruction that helps to ensure data quality.

Tools: SOP/checklist template; short screen captures; document control.

Measures show value; controls manage risk.

Example KPIs: lead time to approve a supplier; first-time-right documentation; % suppliers meeting ESG/quality thresholds.

Example controls: 4-eyes approval; due-diligence checklist; conflict-of-interest declaration.

Tools: simple KPI dashboard; compliance tags aligned to ISO/COSO.

Make it clear which systems and data objects enable each activity.

Example systems: ERP’s supplier module, contract repository, risk screening tool.

Data objects: vendor master record, due-diligence file, contract.

Tools: application map/CMDB; lightweight data glossary; integration list (APIs/files).

Keep a living backlog so improvements don’t depend on big projects.

Example: Log issues and comments from business users and take them through a clear decision process.

Tools: Kanban/backlog (Jira/Planner); incident forms routed by process; versioned change log.

The landscape – or value chain – anchors the hierarchy.

Owners govern at L3; L4 activities carry instructions, measures, controls, systems and data tags.

Interfaces connect processes so handoffs are clean.

The improvement pipeline feeds changes back into owners.

It’s one connected system—strategy at the top, standard work at the bottom, feedback closing the loop.

So to summarize you can start with process architecture in the sequence I have explained: Create your one-page value chain. Assign L3 owners. Pick a process as your pilot, map it, attach the first instructions, KPIs, controls, and system/data tags. Publish it, run it, and improve it. That’s strategy operationalized.