The problem you already have
Two teams can disagree about the same process for years and never resolve it. That is not a people problem. It is what happens when nobody has mapped the structure underneath.
The structure the business runs on, made visible, so product and process teams build against the same thing. Most organizations never have it.
For product
Your roadmap is built against today's shape of the business. When that shape changes, nothing tells you which of your shipped features now serve the wrong customer, or none at all.
For process
You ran the improvement and hit the number. Nobody re-checks it when the business itself changes shape. The gain quietly stops being a gain, and the process keeps optimizing for a business that no longer exists.
For programs
You hit every milestone on schedule. The system goes live configured around a process list nobody validated against how the business actually runs. The rework shows up after go-live, against a budget that is already closed.
For AI & automation
Ask an AI to map your process and it defaults to the reference built for standardized production. Give it the real value chain, and it stops guessing.
A real transformation
An engineer-to-order manufacturer built custom industrial equipment project by project. Each system was designed, sourced, and installed from zero for a single client. Stuck under €20M, around twenty projects running at once, because nothing was reused. Three years, two moves: product engineering left the project first, then supply chain. Three value streams became five. Same people, different architecture.
What is Business Process Architecture
Every "Level 100" and "the four-level model" on this page means this. This practice works down to Level 100. Level 1000 is Business Process Management territory. A different discipline, beyond this scope.
Strategy and structure. Kept separate from operations on purpose, so a change in strategy does not force a rewrite of how the work runs.
How the organization is built to deliver: production, engineering or project-based, or a hybrid of both. The shape of the business, before any single process is named.
Not Porter's value chain. It does not benchmark the organization against competitors — it is the organization's own structural skeleton, how work flows from market need to delivered output.
Not SCOR, either. SCOR makes the same move, but only inside Plan/Source/Make/Deliver. This generalizes it to the whole organization.
The end-to-end flows, built from APQC processes, that actually deliver. This is what the engagement maps and what BPA Navigator helps assemble.
Not classical Lean Value Stream Mapping. No cycle times, inventory buffers, or shop-floor detail — each step here is a whole process, not a task. Classical VSM zooms in on one product family; this zooms out to the process level.
Click-by-click steps, swimlanes, task-level detail. Out of scope for BPA by design.
A different discipline: process mapping, BPM, lean tooling.What we solve
Five problems. Each one starts as friction between the business and whoever is building on top of it: product, process, or program. Each is common. Each is expensive. Each has usually been tried before.
Problem 1
Two teams describe the same process and you cannot tell it is the same process. Every review reopens the naming debate.
What it costs
You cannot consolidate, compare, or benchmark. Every reorganization restarts from a blank list. Weeks per program lost to alignment.
What the engagement does
We set the structure with your team, on a proven process framework. Every process gets one name and one place. The system keeps it consistent after we leave.
Problem 2
Strategy statements sit next to click-by-click steps in the same diagram. Nobody trusts the map, so nobody maintains it.
What it costs
Process documentation that no decision is ever made from. A Visio folder that dies within a year of the consultant leaving.
What the engagement does
We map the value stream with you, at one level of detail, validated in the room. The four-level model is enforced, not suggested. The system keeps the reference and the definitions one click away.
Problem 3
An ERP rollout, a target operating model, or a transformation is stuck in "agree on the process list". Scope keeps moving.
What it costs
The program burns its first quarter on structure it should have started with. Design decisions get made in slideware, then relitigated.
What the engagement does
We deliver the architecture as the program backbone in days: value chains, value streams, and the processes under them, on a standard your vendors already recognize.engagement
Problem 4
One internal expert, or one consultant, holds the whole approach. When they are busy or gone, process work stops.
What it costs
The architecture rots. New process hires take months to become useful. The capability never scales past one desk.
What the engagement does
We run the first pass, then hand the method over. Where the team needs to own it fully, training and the book carry the transfer.engagement · then training
Problem 5
You have process documentation. You do not have owners, measures, or a cadence. Nothing about how the work runs has changed.
What it costs
Effort spent on documentation with no operational return. Accountability stays with the org chart, not the process.
What the engagement does
We install ownership, measures, and a governance cadence, so the architecture becomes how the organization is run. Training embeds it if the team is new to process-based management.engagement · then training
The engagement addresses all five. Training, the book, and BPA Navigator support it. They are not separate solutions. Each one does the same job: translate the business into what product and process teams can build against, and keep that translation current as the business changes.
The engagement
We start with what the business is accountable for: the outcomes, the value chain, whose life changes when the work goes right. We translate that into terms product and process teams can build against. Not a discovery workshop. A fixed-term contract, embedded with your people. The form is your call: employed on term, interim, or contractor. The work is the same.
We build the architecture that makes the organization visible to itself, on the APQC framework, in BPA Navigator. Value chains, value streams, and the processes under them: one shared reference, not two teams guessing at each other's version.
We hand over. The team maintains the architecture without us. That includes the product and process people who now share one picture of the business. Leaving it working is the point of the engagement. Not a side effect.
Two sizes, one method
The whole architecture: value chains, value streams, and the processes under them. Built with your people. Handed over running without us.
Days, not weeks.
The same method, run against one program or one problem. A partial map you can act on. If you want to continue, it is the natural first step into the full engagement.
The tool
APQC PCF is a marketplace of processes. Each one is filed under a process group. A real value stream does not live in one group: a VSM or a process map combines processes from several. BPA Navigator searches that marketplace and suggests which processes belong in the map you are building, as guidance. You assemble the value stream. The tool tells you what the standard has for each step and where it sits. Every step carries its own inputs, outputs, and the points where organizations actually break: not just where it sits in the taxonomy, but where two teams reach for it differently.
Describe a step, a process, or a problem in plain language. Get back the exact place it sits in the framework, with the official description.
Browse the framework category by category, down to the exact element. Every id, name, and description comes straight from the source file.
Name a Level 100 value stream, then add APQC processes from the marketplace in order. Each step is a process. Preview it as a flow.
For any process in your map, see how the five frameworks name and structure it differently.
A generic example — Hire to Retire, assembled in Build mode from the APQC marketplace. Not a client map.
The 3,142 elements recur across the five frameworks, about 10,500 entries in total. Compare shows where an industry names or structures a process differently.
BPA Navigator is not self-serve software — I run it live in engagements and training, and attendees of a paid course get personal access for the length of it. Ask to see it →
Where this starts
Training
Hands-on, two days, scoped with your organization in advance, on your real processes. For the practitioners who will own the architecture, and the analysts on ERP and digitalization programs.
Ask about training →Free workshop
45 minutes. We open with a real transformation, played live, start to finish: no jargon, no codes, just the arc. Then you name what you deliver, mapped against the business's real value stream as you submit it. We close on two or three live answers from the room. For product managers, product owners, and product analysts. Free, open to people from several companies, no commitment.
Ask about the next session →The book
Business Process Architecture by Radu Achim. The full method the engagement, the tool, and the training are built on.
Implementation partners
Running an ERP or digitalization rollout? The engagement can work with your delivery team, across your own client projects — a subcontracted architecture layer, not a separate offer to your client.
Ask about partnering →
Team
Radu Achim leads the practice. Author of Business Process Architecture, twenty years in complex industrial operations, Lean Six Sigma Master Black Belt, PMI-ACP. The practice is growing, adding senior process architects and partners as engagements need them. Direct, or through senior placement channels.
Partner
Alexandra Niculae brings process mapping expertise for the detailed process layer. Lean Six Sigma Master Black Belt, BPMN 2.0 trainer, international speaker and author, credentialed through BPMInstitute.org and ILSSI.
Get in touch