Decision for simple Process Map example

Guide to simple process mapping

Gluu’s Guides

Show a complex process map to your colleagues and chances are their eyes will roll and they’ll abruptly excuse themselves. The good news is it doesn’t have to be this way. This guide will show you how to create simple process maps using just four shapes.

The oft-used saying “less is more” is also applicable to process mapping. As so often with the best design, it’s about elegant simplicity – using the bare minimum to achieve a balance of functionality and clarity. If you use simple process maps then people don’t need special training to decipher them because they are instantly self-explanatory. Knowing how to create these will help you get everyone in your team on the same page.

What is process mapping?

A process map is a visual diagram that explains how a single recurring work activity is done and by whom. Ordering new stock, handling a customer complaint, sending a late payment notice, or hiring a new department head are all examples of jobs you can create process maps for. They are a bit like an electric circuit diagram, but rather than the flow of current, they show the flow of work and responsibility for completing a recurrent job.

 

ISO defines a process as “a set of interrelated or interacting activities that use inputs to deliver an intended result.”

A new concept to you?

Don’t worry. Let us give you some context. Process maps are often, but not always, subparts of a process hierarchy. A process hierarchy is the big picture that shows all the work processes going on in an organisation or business that help fulfil its purpose, and how those processes relate to one another. (For more on this have a look at our guide to creating a process hierarchy.)

Process maps illustrate how one particular piece of work is conducted and, potentially, improved upon. They are conceptual tools used to gain better understanding and cooperation. So if the process hierarchy is the blueprint for your organisation’s regular work, then the processes are its building blocks.

What are the benefits of mapping our processes?

Process maps offer a number of benefits:

  • They help you to see where improvements can be made, in terms of customer experience, cost saving or time efficiency.
  • They also ensure that everyone involved in a particular recurrent work function clearly understands how things are done and his or her own responsibilities.
  • Importantly, they also ensure knowledge stays in your company. If your key HR person leaves, for example, his or her replacement will be able to refer to the process hierarchy quickly to understand how things are done. This saves time and avoids mistakes.
  • They lay the foundation for automation, ISO (and other) certifications and the introduction of new business systems.

Read more about the requirement for a process approach in ISO 9001:2015 in this ISO reference document (PDF).

Why simple process mapping?

The world of process mapping is large and diverse. Like languages, process maps can be highly complex, like Russian or Japanese, with upward of 50 shapes to create them with. They can look highly sophisticated, and may even win a few wows from your colleagues. However, more often than not they bewilder people. Instead of being instantly graspable, some of the more complex process mapping techniques require employees to attend workshops just to understand them. You need a process to understand the process. This is often unnecessary. Less, as the saying goes, is more.

The alternative to simple process mapping is the Business Process Model Notation framework. This uses 55 shapes and is useful for detailed mapping to support ERP implementations.

Process map from BPMN a highly complex and unintuitive design.
(image credit: BPMN)

From BPMN’s 50+ shapes we have used the four basic shapes that ISO also uses. With no special artistic ability or insider knowledge, these four are all you need to create simple process maps that will galvanise your team and show you where improvements can be made.

How are they drawn?

They are made with simple swimlane diagrams. These are diagrams divided into long rectangular boxes, like a lane in a swimming pool. These rectangular shapes are the foundation of your diagram. Each swimlane represents a particular role, for example your sales assistant or your shop manager. They clearly illustrate who is responsible for what. This is what people really care about. It keeps things simple. If you don’t reduce the scope of your process map in this way, then you run the risk of making convoluted processes for the sake of sophistication rather than usability.

Focusing on “who does what” is also an approach supported by research. Dewey showed that processes rarely fail due to individuals not doing their job. Processes fail because handoffs and knowledge transfers between people go wrong. One person thinks his or her job is done and the next one doesn’t know the baton has been passed to him or her. This uncertainty interferes with the process. A swimlane diagram helps to recognise these points. They show exactly which role that is responsible for which activity. When you connect people with roles then it starts to make sense for everybody.
Two swimlanes for a process that involves two roles:

Simple Process Mapping Example for a Swimlane

The basic shapes for drawing

We just explained the first, foundational shape: the swimlane. The remaining three are:

The event circle

The purpose of these is to show when an event activates or ends a process, or in some way changes its direction. An event could be a reminder notification that a certain customer is late paying an invoice, which then sets the process in motion of sending a late payment notice.

Simple Process Mapping example: A red event circle placed on a swimlane.

The activity box

These represent the different activities that must be done in order to complete or hand over a particular process. A good process map has between two or 10 activities. It has less than two, it’s an activity, not a process. And if it has more than 10 it should be broken up into multiple processes.

Simple process mapping example blue activity box leading from the original red event circle.

The decision diamond

Notice the white diamond shape in the illustration? These indicate when in a process a decision of some kind must be made. For example, if a customer wants his or her money back a customer service rep might have to decide if the amount of money involved requires approval from management. These decisions are often posed as questions.

Simple process mapping example white decision diamond giving two different directions for your process map.

These are the four basic shapes.

Let’s start!

You have your swimlanes, and know the three other shapes – you are ready to start depicting how a process is conducted and by who. Here are three steps to creating a usable map.

Step one: Setting it up

Before you start getting creative with the shapes, there’s a few things you need to do first.

One: Select and define a process to map

You can start with your company’s business model, value chain or current process hierarchy. This first step is a natural top management activity – later steps should involve the people that will do the work.

Alternatively, you can start with the process that has the most impact on your customer experience – or where you have the biggest opportunity to improve.

Complaint handling is important to do well, so we’ll use that as an example. To name it, it’s best to write it as an imperative – “Handle customer complaint”. This makes it personal and actionable. “Complaint management” sounds more like a department name. Avoid lingo.

Screenshot of a software value chain

Two: Define its outcome

When you have selected and named your process then you need to set the boundaries for it. What is its outcome? What starts it? And what ends it?

Start with the outcome of the process. Complaint handling is essentially about turning angry customers into happy ones – while not spending too much money doing this. So the main output is, “satisfied customer.”

Outputs

An “output” is the outcome or deliverable that the process or activity should result in.

Three: Select a process owner

Now that your process is named and defined it is time to identify the natural process owner. For our example, who handles a customer complaint depends on your business. If you have been personally involved if a substantial part of the business is at risk. On the other hand, if you have lots of customers then the process owner may be your customer service director. Decide on the process owner based on:

  • Who has the most at stake?
  • Who has the authority to really change the process?
  • Who has the best understanding of the end to end flow?
  • In this case, let’s say the customer service director is the owner. It’s an important decision since we’re giving this role the authority to improve the process going forward.

You can read more about the process owner role here.

Step two: Start drawing your swimlane map – the “who does what”

Now you are ready to start adding the three shapes into your swimlane diagram. We will continue using the example of handling a customer complaint for our discussion here.

Defining the roles

We start by defining the organisational roles involved. For our example process, we have a customer, a customer service representative and a technician involved. Each role has a swimlane showing which activities he or she will act out.

The kickoff

To kick things off, the customer submits a complaint. This is the event that starts the process. An event is an occurrence that starts (or happens during) a process flow. As discussed, these are shown in your diagram with a circle shape. Once this event happens, the work starts.

The work activities

The different types of work required to complete a job are called activities. For example, recording or taking the details of a customer complaint is an activity the customer service representative is responsible for. Activities are illustrated in your diagram with square boxes. An activity box shows what outcome a role is responsible for achieving to allow a process to proceed towards completion.

In the case of handling a customer complaint, the first activity is carried out by the customer service rep who receives the complaint. He or she needs to complete the tasks of interviewing the customer, filling in a complaint form and submitting it. In this case, the activity might be “receive complaint” and the output is the case is recorded in the system.

You might be wondering how much of the work your company does can be defined as an activity. Good question. Our advice is to keep it simple at first. An activity can include many tasks and take minutes or even days to complete.

The next activity is to resolve the customer’s issue. We’ll say the customer service rep is responsible for this, since he or she may be able to resolve it immediately, on the first contact with the customer. This gives the best customer experience.

Decisions, decisions!

Deciding whether or not this is possible is what is called “a decision point”. These are shown in swimlane diagrams with diamond shapes. They can illustrate simple yes or no decisions or more complex decision, perhaps with more than two or three answers. Decision diamonds help us to see the points at which the work process may change hands. In our example, the service rep must decide whether he or she can resolve the complaint immediately or whether he or she will refer it to a technician or perhaps a team leader.

We’ll keep this process simple for now and just add a final activity. Say the technician resolves the complaint and the service rep gets confirmation the customer has gone away satisfied. Here we can add an event circle to close the process – or, in the case of something else, indicate which process naturally follows on (then you’re starting to show the relationships between your processes – a future topic).

Decision for simple Process Map example

Once you have created multiple processes then you can view them as building blocks for other processes. The white shape in the diagram illustrates another process.

This is a swimlane and how you create it. We now have a simple process map. That’s the easy part. The hard part is to turn it into action. This inevitably means it will have to adapt and evolve.

Step three: Keep it alive!

Where do you draw your process map? Some use Post-it notes. Other draw them up on a whiteboard. Some use paper so they can bring it along with them wherever they go.

But what do you do when you want to share and change it perhaps over the following week or month or even year? This is an important question. For process maps to be meaningful, for them to stay alive and be of lasting value, they need to be shareable and accessible to more than one or two people.

To achieve this some go back and redraw the whole thing in Visio. This takes a lot of time and it makes it “your process” which is good if you will be executing it, but less helpful if others are involved. If you subconsciously see it as your creation then you may defend it passionately. You may have good arguments. If nothing else, then you risk defending it because you’ll be the one who will have to go back into Visio every time someone spots a necessary change. And believe us, they will love spotting those.

So, we suggest picking a tool, such as Gluu, that:

  • is collaborative.
  • allows you to delegate ownership.
    involves people.
  • makes it easy to communicate around changes.
  • automatically tracks changes.

Where do I go from here?

If you want to try creating a process, then we have a built-in guide in the Gluu platform. Why not sign up for a free trial account and start practising?