Where do you start with process management?

More in control, step by step

Many organizations that want to start with process management quickly run into the same question. Where do you begin, without it becoming an abstract undertaking or getting bogged down in good intentions? That doubt is understandable. Process management can yield a lot, but only if the start is right.

In the first blog of this series we went deeper into what process management is. Then we looked at the 5 biggest misunderstandings that hinder good process management. In this blog, we look at how to successfully start with process management.

In practice, it often starts too quickly with solutions like drawing processes or setting formats. Or making agreements that don't really stick anywhere. That feels like progress, but the real foundation remains undiscussed. And it is precisely that foundation that determines whether process management will help in daily work, or slowly fade into the background.

If you want to implement process management sustainably and successfully, you don't start with the process. You start with the work itself.

See what you want to achieve

Organizations often start with process management due to a specific reason. Think of stricter laws and regulations, recurring errors, an audit that takes a lot of time, or a change that just doesn't get off the ground.

What the reasons have in common is that they ask for control. Control over how the work is progressing, where the risks lie, and who is responsible for what. Process management is then not a goal in itself, but a means to achieve that insight.

In practice, organizations aim to achieve the following goals with process management:

• Manage risks
• Making changes manageable
• Successfully implement improvements
• Demonstrably comply with laws and regulations
• Getting clarity on responsibilities

That broader goal determines where you start and how you take the first steps. In practice, this means you start with one concrete piece of work that plays an important role in this.

First, choose one process with impact

Another pitfall is that organizations often want to start too big. Modeling multiple processes at once. Or immediately wanting to create a complete overview of the organization. This demands a lot of time and, especially at the beginning, offers little grip.

It is better to start small and concrete. And to achieve quick wins with it. Start with one process that is recognizable, affects multiple people, and is visibly problematic. This could be a process where errors occur, where a lot of coordination is needed, or where compliance requirements converge.

Exactly these kinds of processes quickly reveal bottlenecks and where process management adds value. Such a process also often clearly demonstrates to the rest of the organization what process management concretely delivers, rather than what it costs.

Tip: Use the AI function of Sensus BPM Online to quickly develop an initial process. You describe how the work flows, and AI immediately creates a proposal that you can adjust and refine.

What a process really is

A process is nothing more than the route work takes from beginning to end. It describes how a request arises, how it is picked up, which steps follow, and when the work is finished.

In many organizations, that process is largely implicit. It's embedded in experience, routines, and unspoken assumptions. People know what to do, until a situation is just a little different. Then it becomes clear how vulnerable those invisible agreements are.

As long as processes are not explicit within an organization, they remain difficult to discuss. And what you cannot discuss, you cannot effectively improve.

Case study
A public sector organization began the process surrounding resident reports. It seemed simple, but in practice, information was found in different places and agreements were mostly implicit. By making this one process visible together, not only did an overview emerge, but also a conversation about responsibilities and collaboration. That conversation turned out to be even more valuable than the schedule itself.

This is how you develop an initial process

When you start working with a first process, it helps to approach it in a structured way. You don't start from theory, but from practice. Sensus BPM Online helps you tackle this step by step.

The steps below provide guidance in developing an initial process. One that is actually used.

1. Map the process from start to finish
Start from the trigger for the work and end at the moment the process is complete. So, not from functions or teams, but from the journey the work takes.

2. Clarify who has which role
Define roles, decision-makers, and those responsible for follow-up. This prevents unclear responsibilities.

3. Name transfers and decision points
It is precisely in these moments that errors and delays occur. By making them explicit, it becomes visible where the risks lie.

4. Link agreements to daily practice
Ensure the process aligns with how people actually work. Therefore, do not describe an ideal situation, but take reality as a starting point.

5. Use the process to start a conversation
The goal isn't the plan itself, but the conversation it sparks. What problems are we encountering? What can be simplified? What needs clarification?

Case study
A university of applied sciences applied this step-by-step plan to the process of developing and approving new educational components. In practice, decision-making often stalled between the program coordinator, the examination board, and program management. It was unclear who needed to be involved when and who made the decision. By detailing the process, handoffs and decision points became clear. After this, the work proceeded much more smoothly. And with new national accreditation requirements, the university of applied sciences could easily adapt the process again.

See process management as a development

Process management is not a one-time project. It evolves with the organization's needs. Initially, it often focuses on overview and basic agreements. Later, the attention shifts to improvement, adjustment, and learning from what happens.

That's why it helps to always ask the same simple question: what needs to go better tomorrow than today? That question keeps process management concrete and prevents it from becoming a standalone initiative.

In practice, process management primarily helps organizations to:

• To better understand how the work proceeds from beginning to end
• Making vulnerabilities and dependencies visible
• To keep appointments negotiable and adaptable
• Guiding changes better

Not everything at once, but step by step.

A good start prevents later recovery work.

Process management doesn't start with drawings, systems, or diagrams. It starts with paying attention to how work actually happens. By first understanding where the friction points are, making conscious choices, and starting small, a solid foundation is built.

This foundation ensures peace. Fewer misunderstandings. Less reliance on chance. And more room for focused improvement, without having to start over each time.

Curious whether this way of working

is right for your organization?

See how processes become part of everyday work

Want to see how Sensus BPM Online makes process management part of the way people actually work? Try it for yourself and see whether it fits your organization.

Try it free for 30 days, with no commitment. You can get started right away.