Business Process Mapping Before Software Changes

Gehen Sie ein tatsächliches Beispiel durch.

Befolgen Sie eine repräsentative Anfrage von Anfang bis Ende mit den Personen, die sie bearbeiten. Zeichnen Sie Entscheidungen, Übergaben und die an jedem Punkt verwendeten Informationen auf. Fügen Sie informelle Schritte hinzu, die möglicherweise nicht im schriftlichen Verfahren enthalten sind. Sie erklären oft, warum eine vorgeschlagene Änderung mehr als nur eine neue Schnittstelle erfordert.

Trennen Sie Symptome von Ursachen.

Fragen Sie, warum es zu einer Verzögerung oder wiederholten Aktion kommt. Dabei kann es sich um fehlende Informationen, unklare Eigentumsverhältnisse oder eine erforderliche Genehmigung handeln. Unterscheiden Sie diese Bedingungen von einer Werkzeugbeschränkung, bevor Sie entscheiden, was geändert werden soll. Andernfalls kann das neue System das gleiche Problem mit einem anderen Bildschirm reproduzieren.

Definieren Sie eine begrenzte erste Verbesserung.

Wählen Sie einen Teil des Workflows mit einem klaren Eigentümer und einem beobachtbaren Ergebnis. Vereinbaren Sie, wie es im Vergleich zum aktuellen Prozess überprüft wird. Zeichnen Sie auf, was außerhalb der ersten Phase bleibt, damit die Beteiligten die Grenze verstehen und die Abhängigkeiten darum herum planen können.

Build and verify the current-state map

Define the start and finish of the process, then ask people doing the work to walk through a representative case. Record actions, decisions, handoffs and the information needed at each stage. Include the systems involved and places where staff maintain a separate spreadsheet or message thread.

Walk through exceptions such as incomplete information, rejection, delay and an absent approver. Mark uncertain steps rather than filling gaps with an idealized sequence. Ask participants to verify the map and note differences between teams or locations. Only then sketch a proposed change. Keep the current and proposed versions separate so reviewers can see which rules are being preserved, removed or introduced.

A process-mapping worksheet

A simple table can be enough before creating a diagram. Use the diagram to communicate the verified sequence, not to hide unresolved decisions.

• Boundary: triggering event, completed outcome and process owner.
• Step: action, responsible role and the information received or produced.
• Decision: rule used, authority to decide and possible next paths.
• Handoff: receiving role or system and how acceptance is confirmed.
• Exception: missing information, delay, rejection or another route requiring attention.
• Improvement note: observed difficulty, evidence and whether it needs policy or technical action.

Do not draw only the official procedure

The written process and everyday practice can differ. Record both and ask why workarounds exist before proposing their removal. A workaround may compensate for missing access, an unclear rule or a system limitation.

Avoid treating every observed delay as a software defect. Some decisions depend on authority, policy or external information. Assign the right owner to investigate. Keep proposed changes distinct from current facts so a new diagram is not mistaken for an already agreed operating procedure.

How detailed should the process map be?

Include enough detail to understand the problem and its dependencies. Start with the end-to-end sequence, then expand the steps connected to the proposed change. Excessive detail can obscure decisions, while a map containing only department names may hide the handoffs that matter.

ILLUSTRATIVE PLANNING EXAMPLE

Example: mapping an expense claim

Follow a claim from submission through approval and reimbursement. Include a missing receipt, a rejected claim and an absent approver. Ask people doing the work to verify the sequence and identify where information is copied between systems. Mark uncertain steps for investigation rather than drawing an idealized process.

Use the verified map to define a focused improvement. Preserve the distinction between a policy decision and a software feature needed to support it.

FURTHER READING

Official resources to explore

Explore the related official guidance below. The templates and examples are practical starting points to adapt to your own project.

• GOV.UK Service Manual: how discovery works