Business Process Mapping Before Software Changes

Vea un ejemplo real.

Seguir una solicitud representativa de principio a fin con las personas que la manejan. Registre las decisiones, los traspasos y la información utilizada en cada punto. Incluir pasos informales que pueden no aparecer en el procedimiento escrito. A menudo explican por qué un cambio propuesto necesita más que una nueva interfaz.

Separe los síntomas de las causas.

Pregunte por qué se produce un retraso o una acción repetida. Puede implicar información faltante, propiedad poco clara o una aprobación requerida. Distinga estas condiciones de una limitación de la herramienta antes de decidir qué cambiar. De lo contrario, el nuevo sistema puede reproducir el mismo problema con una pantalla diferente.

Defina una primera mejora acotada.

Elija una parte del flujo de trabajo con un propietario claro y un resultado observable. Acuerde cómo se revisará con el proceso actual. Registre lo que queda fuera de la primera fase para que las partes interesadas comprendan el límite y puedan planificar las dependencias en torno a él.

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