Process Design.

End-to-end process mapping and redesign. Following the work, not the org chart. Eliminating the handoffs that accumulate over time.

Full practitioner methodology in the CN Portal Log in →

The key principles

How CN approaches this work.

Start with outcomes, not activities

Map the process from the desired outcome backwards. What does success look like for the person receiving the output? Every step that does not contribute to that outcome is a candidate for removal.

Follow the work, not the org chart

Real processes cut across functional boundaries. Map them that way. The handoffs between functions are where the most waste and the most failure risk accumulates.

Challenge every handoff

Every transfer of responsibility is a potential failure point. Ask: is this handoff necessary? Who created it and why? What happens when it breaks? The goal is not to eliminate all handoffs — it is to ensure every one that remains is designed rather than inherited.

Design with the people who do the work

Process maps created in isolation and handed to the workforce are rarely followed. The people who do the work know the exceptions, the workarounds, the reasons the current process evolved the way it did. Their involvement is not consultation — it is a design requirement.

Connect process to technology before selecting systems

The process must be designed before the technology that supports it. System configuration should reflect the designed process — not the legacy process it replaces.

What good looks like

✓Processes designed around outcomes, not organisational convenience
✓Every handoff justified and owned by a named role
✓SOPs written by and for the people who do the work
✓Exceptions handled by design, not improvisation
✓Process ownership clear — someone accountable for each end-to-end process
✓Technology configured to support the designed process

Warning signs

✗Process mapped on a slide but never tested in reality
✗Redesign done by consultants, handed to workforce to follow
✗Technology selected before process is redesigned
✗No process ownership — everyone assumes someone else manages it
✗Exceptions handled by workaround, creating shadow processes
✗SOPs written at a level of abstraction that provides no practical guidance

Diagnostic questions

Use these in client conversations or team reviews to quickly surface where the real issues are.

QCan you trace a single transaction from trigger to outcome across every team it touches?

QWho owns each end-to-end process — not just a step within it?

QHow many formal handoffs does the most common transaction involve? How many are necessary?

Full Practitioner Guide

The complete methodology is in the CN Portal.

The full guide covers: current-state mapping methodology, value stream analysis, handoff challenge framework, SOP design principles, process governance, and the integration checklist for connecting process redesign to the people and technology layers.

Access Portal Join the network