Tips & Tutorials

6 Tips for a Good Process Description

“Ariadne alone is enough to bring a management system to life.” - We encounter this assumption time and again in our consultancy work. But alongside the right software, another factor is crucial to whether you embrace a management system, use it actively and engage with it: the quality of its content. Without high-quality process descriptions, even the best software is useless.

So what makes a good process description? There is no single answer. Over the years, however, we have gained plenty of practical experience that can help you document your workflows effectively.

‍

Define your goal before you write

First, ask yourself what you want your process description to achieve and who it is for:

  • Is it for employees unfamiliar with the subject, or for experts?
  • Does it cover a particularly complex process, or are the individual steps self-explanatory?
  • Do you simply want to achieve certification with a centrally maintained management system? Or do you want to create a knowledge portal organised around your processes that benefits every employee?

These questions help determine the right level of detail. After all, useful practical knowledge should not get buried ininformation that is already obvious. The general rule is therefore: as much detail as necessary, as little as possible.

If a process already runs smoothly, a brief description is enough. If it often leads to errors or confusion, more detail is needed. Our guiding principle is that documentation must help people in their everyday work. It should not exist solely to satisfy external requirements.

With that in mind, we assume your aim is to create a knowledge portal organised around your processes, using Ariadne or similar software. This generally requires more detail than documentation kept purely for certification. As well as answering “What needs to be done?”, you need to explain “How should it be done?”

Describe the individual steps as you would in a recipe, and link them to templates, other systems and work instructions. Employees can add important information and new insights themselves, shaping the documentation to support their everyday work. Rigid documentation with a fixed level of detail becomes a living knowledge platform that you can adapt to changing needs.

As for “Why does this need to be done?”, you can generally leave this out of the process description: it only needs to be covered once, when new employees are learning the job.

‍

Make your processes easy to follow

How can you keep a detailed process description clear and concise? Detailed content and concise documentation can go hand in hand:

1.    Use bullet points instead of paragraphs

Bullet points convey relevant information without complicated sentences, making each point easier to understand. They are also much quicker to update and expand than paragraphs of text. Keeping information easy to update is one of the foundations of a management system that people actively use and improve.

2.    Use verbs to describe actions

Write “Train employees” rather than “Employee training”. This makes the purpose of each process step clear and helps prevent misunderstandings.

3.    Document routine cases not exceptions

Documenting every possible exception makes a process description difficult to follow. Focus on how the process usually works. Consistently improving routine work and saving a minute each time has a much greater impact than saving an hour in a rare exception.

4.    Structure steps chronologically

Always explain who needs to do what and when, in the order the steps occur. Attach relevant documents directly to the process they relate to, so that no one has to spend time searching for them. A table helps to organise the information: clearly assigning responsibility makes handovers between departments easier to see, for example.

5.    Limit each process to 15 steps

Our experience shows that more than 15 process steps can overwhelm many users. Split longer processes into smaller ones.

Individual steps also need clear boundaries. A simple rule of thumb is to start a new step when responsibility changes, for example from one department to another, or when consecutive activities can be scheduled independently. This ensures reliable handovers without information loss and keeps the timing clear.

If a step needs a lengthy explanation, put the detail in a separate work instruction and link to it from the process.

6.    Link related processes and resources

Use your process management software to link to upstream and downstream processes, work instructions, documents and other operational systems. These links provide an overview of processes across the organisation and show how parallel processes, subprocesses and process variants relate to one another. Your management system becomes a comprehensive navigation platform where people can find every piece of information and every document in the right place.

‍

‍

Why good process descriptions matter

Good process descriptions make your management system:

  • More useful in your colleagues’ everyday work.
  • Easier to keep up to date.

Both encourage employees to contribute actively to the documentation and make it even more useful.

Think of a campfire: when everyone brings a log, everyone shares the warmth. Your knowledge portal works in the same way: everyone contributes their process knowledge, and everyone benefits as it grows.

Certification becomes an added benefit of a management system that people actively use and improve. It is no longer the sole reason for maintaining documentation centrally.

‍

‍