Guide to creating a process hierarchy
Most people think, “why should I care about a Process Hierarchy?” – a fair enough question. We know this guide might sound like a fast way to put yourself to sleep, but the surprising truth about the Process Hierarchy is that it can actually be an illuminating and rewarding business project. It’s a first step in shining a light on how you operate, where waste is happening, where fat can be cut, and how you can improve. This adds up to dollars and cents; a topic we all find interesting.
Whether you’re new to process hierarchies or just need a refresher, this guide will help you learn:
What is a process hierarchy?
Before we start, let’s quickly recap what a process hierarchy – or process architecture – is.
A process hierarchy visually demonstrates all of the ongoing tasks within your business.
Think of one as being a little like an architectural blueprint for a house. Except rather than beams and rafters, a process hierarchy shows the processes that keep your business upright. They are also seen as a supplement to your organisational chart. The organisational chart shows how departments and roles are related, while the process hierarchy shows how activities are related and how they deliver the outcomes that are needed to attain your organisation’s goals. They map the small stuff, like how a receptionist should take a phone call, or how to send a late payment notice, to the very big and important stuff such as hiring a new head of a department.
Below you can see a sample process hierarchy for Product Development. This is a snippet from APQC’s Process Classification Framework® (PCF) which is the most used process framework in the world:
What’s in it for our business?
There’s a difficult, hard to impress person in every bunch so we’ll give you one simple reason: knowledge is better than ignorance. Process hierarchy is about knowledge and understanding. It ensures you’re not operating in the dark.
Familiarity, to tweak an old saying, breeds ignorance. We might think we know how our business works, but do we really? A process hierarchy will show us. It will reveal what recurrent tasks we’re doing well, what could be better, where our blind spots are (the things we’re not seeing), places we could improve customer experience, where to eliminate waste, and even where economic, market and reputational risk could lie.
By recording your processes you give your employees a common language and a clear understanding of their responsibilities. They also allow you to continuously measure and incrementally improve the processes happening across your business, reducing waste and increasing effectivity. Having one really is a no-brainer.
Here Gluu’s founder, Søren Pommer, explains it in an interview:
A process hierarchy will help you answer some key questions
A well-made process hierarchy will show you how recurring tasks flow in your company. They help determine which individuals get to participate in which decision-making processes. They provide the foundation for your standard operating procedures and routines.
A process hierarchy allows you to optimise your business. By defining:
- Which processes are primary and which are supporting.
- What their intended outcomes or outputs are.
- Who they are executed by.
- How they are related to each other.
A clear understanding of how your employees are going about their tasks provides the basis for insights into how to improve. It also shows whether you’re aligned with correct procedure. For example, the EU has an upcoming law on personal data protection. With a process hierarchy, you could quickly dig down and confirm whether your company complies with such new legislation. And if you do have to make changes, it’s much easier to pivot and tweak things when you have processes already in place.
Can we build a process hierarchy by ourselves?
Absolutely, process hierarchies can be highly complex and time-consuming. However, anyone can understand the fundamentals. With a bit of planning and help from guides like this, you will be well on your way to creating a professional standard process hierarchy.
Depending on the amount of time you have, your level of enthusiasm and the complexity of your business you might take ownership of the project yourself or hire a consultant to lead the way. If you decide the latter, we advise you only use the consultant to facilitate the process. If they end up creating your process hierarchy from top to bottom then you and your team are unlikely to assume ownership. All too often this leads to stale or buried process hierarchies.
First steps to creating a process hierarchy
Now you know the basics of process hierarchies and what to include. Here are some tips for how to take the first steps:
Step 1: Start with the standards and systems you already have
If you already have a working quality management system then, as a start, simply transfer the table of contents to the process hierarchy format. There’s no point reinventing the wheel. So make life easier as much as possible, model your process hierarchy on standards and frameworks you already have. Talk to your IT guys – they might have done something similar to prepare for a systems implementation.
Step 2: Workshop critical processes with senior management
Before you make any commitment to building a process hierarchy, getting management’s buy-in is absolutely essential. Ideally, this effort is driven by management, or someone close. This is best kicked off with a workshop that focuses on how your processes connect with your strategy.
Call on your best facilitator and get your top management team together for an offsite workshop to map the high-level end-to-end flows. This is a discussion about your business model and value stream and who is overall responsible for what. It is likely to get very lively and engaging.
Step 3: Focus on critical processes, to begin with
Start off by finding the 10 to 30 processes that really matter. They’re the ones that keep the company humming. If your vision is too broad too soon, and you try to nail down every single business process, you’ll get bogged down in the details and lose sight of the essentials.
Typically have HQ functions at a group level and then operate relatively independently at regional and/or country levels. Here it makes sense to create some common processes but we also recommend allowing “local offices” the freedom to create their own processes for how they work. Gluu has a function that allows your subsidiaries to add group processes to their local accounts on an ongoing basis.
Small and Medium sized businesses
Depending on complexity they may have between 30-200 processes. Here it is best to show end-to-end business processes first since this gives people a good overview of the business model. Each function or department can then have their own categories, or process groups, and create their own processes as building blocks.
At Gluu, we start with our value chain. This contains links to all critical processes:
These are some of Gluu’s own functional groups and processes:
Step 4: Assign responsibility for each process
Assign responsibility for each of the critical processes to specific team members. Some of these people will be obvious, like department heads in a big company, but in some cases, they won’t be and you’ll need to investigate who’s who.
Step 5: Decide on your format and tools
Next, you’re going to need a way to visually map your processes. Key for success here is that whatever tool you use, it must be shareable and easy to collaborate company-wide. If it stays in one room, it will end of up dead and forgotten. This is where online platforms, such as Gluu’s, come in.
Step 6: Assign a project manager
When it’s time to take the project out to the whole company, you’ll need a project manager to lead the way. Choose someone with a broad understanding of the business, and someone who can talk to the people both in the boardroom and on the shop floor.
Step 7: Manage your process hierarchy centrally
We’re all for decentralisation and involving everyone. However, when it comes to your process hierarchy (and your roles for that matter) then agree on the few administrator positions who are allowed to change things. You want everyone participating, yes, but retain control centrally.
⇒ Process names and outcome descriptions remain consistent.
It can be very confusing if one process is “Onboard new customer” and another is “Customer management”. Stick to one semantic style (we recommend using an active form such as “Manage processes”. Yes, you should have a process for managing processes.
⇒ Processes don’t overlap (too much).
Each process should have a very clear name and outcome. This sets the scope and ensures that you minimise overlap when other people start mapping them. If this initial map of processes isn’t clear, then you’re likely to see confusion when others start mapping.
⇒ Processes become easier to link with each other.
Getting the initial overview and understanding of end-to-end flows makes it easier to link processes and show which are related. This gives understanding and insights into the process mapping exercises that come later.
Remember, this is just the first step
Creating a process hierarchy is just a first step towards success with business processes. While it is valuable on its own, the real value will come when you start mapping processes, adding work instructions and then executing and improving them.