Creating a Process Map from Scratch | Process Street Creating a Process Map from Scratch – Process Street

Choose a process to be mapped

Ensure you have a whiteboard

A whiteboard is where your process map will be drawn, rubbed out, edited, scrapped and perfected. It's essential you have one big enough to draw on in a room that can hold a team of people.

A PIP process map from the British Government.

(Source)

It's best to write process components on stick notes because they can easily be moved around the board and then pen lines can be drawn (and rubbed out) between them.

If you'd prefer a digital version of the above for remote teams, you can try something like Realtime Board — a collaboration tool for teams that also includes virtual post-its.

Realtime Board's agile board example.

Ensure you have process mapping software

The best free multi-platform dedicated process mapping tool is yED. Perhaps your organization has installed something like Microsoft Visio, but if not, yED is well worth checking out, as Ian James explains.

the yED explainer video

Arrange a meeting with the team who execute the process

To map a process, you need to understand it.

Arrange a meeting with those who execute the process to be mapped, and make sure they're free either to be in the room with the whiteboard, or have accounts on a whiteboard tool's site.

Use Google Calendar to send the invite or arrange it automatically with a tool like x.ai — an AI for scheduling your meetings.

Interview the team to get a rough sketch of the process

To understand the process, you first need to understand a few things...

  • 1
    What is achieved?
  • 2
    How is it achieved?
  • 3
    When is it achieved?
  • 4
    Where is it achieved?
  • 5
    Who achieves it?

Ask these questions on the whole, and for each sequential step.

Don't worry about anything other than getting a rough draft of the map down. It's not time to refine or optimize, just sketch.

Using simple flow chart notation, sketch the process "as is" on the whiteboard.

At this point, you only really need these symbols.

It'll probably end up looking a little bit like this:

Refine the process together

Once you have a sketch, it's time to optimize the process map. What can be done differently?

Either use this separate optimization process, or follow the steps in this task.

Finalize the whiteboard draft

Make sure you have a version of the map everyone is happy with, and you have cut non-essential steps from the original, if there were any.

Create a digital version of the process map

Now you've done the collaborative task of whiteboarding the process, it's time to create a digital version.

yEd is a free and powerful alternative to some of the popular and costly solutions. Depending on your business' regulations or your preferences you may want to create the final map in compliance with BPMN, or may not.

Distribute the digital version to the executing team

When you've got the final map ready, give it to the team to use and ask them to report back any problems with its usability, or report if they find themselves skipping over sections. Is it too simple? Is it too verbose?

Take their feedback, and refine the map.