Business Operations
Map a business process before you outsource it
Capture inputs, decisions, exceptions and ownership before writing a statement of work.
IGS Editorial · 3 min read · Updated 17 November 2026

A process map is a shared explanation of how work moves. Before outsourcing a task, it helps reveal assumptions that experienced employees carry in their heads. Those assumptions become operational gaps when a new team starts handling the work.
Begin with one defined process rather than trying to map an entire department. Choose a recognisable trigger and an observable end state. “Manage orders” is broad; “check a submitted order and release it for fulfilment” gives the exercise clearer boundaries.
Follow a real example
Walk through a recent ordinary case with the people who performed it. Record where the request arrived, what information was checked and which system held the authoritative record. Ask what happened next instead of accepting a summary such as “then operations handles it”.
Repeat the walk-through with an exception. Missing fields, duplicate requests and approval delays often reveal more about the process than the ideal route. Preserve differences between the documented procedure and actual practice for discussion.
Mark every decision
A decision point needs a rule, an information source and an authorised owner. If a colleague says they use judgement, explore the factors they consider. Some judgement can be documented; some may need to remain with an experienced internal decision-maker.
For example, a purchase request may pass an automated completeness check but still require budget approval. The map should not merge those steps. Completeness can be checked by one role while financial authority stays elsewhere.
Make queues visible
Work often spends more time waiting than being handled. Show inboxes, approval queues and handoff points, including who monitors them. A box labelled “pending” is incomplete unless someone can explain what ends the wait.
Record the information that must travel with each handoff. A receiving team needs enough context to act without reconstructing the whole request. Identify where the same information is entered twice and why.
Define the proposed boundary
Mark which steps are in scope for the external team and which remain internal. Include access limits, permitted changes and exception routes. The boundary should be understandable to someone who was not present during discovery.
Do not assume a task is suitable merely because it is repetitive. Review its data sensitivity, decision authority, system constraints and dependency on undocumented knowledge. A smaller initial scope may be more workable while those questions are resolved.
Validate the map before contracting
Ask sending and receiving teams to review the same examples against the proposed map. Resolve contradictions and record remaining assumptions. Translate the agreed steps into work instructions, acceptance criteria and reporting requirements.
Keep the map under change control after transition. When a system or policy changes, use it to identify affected tasks and owners. The value is not the diagram itself; it is a common understanding of where work enters, how decisions are made and who ensures the process reaches its intended end.
Resolve a hidden decision before transition
During mapping, a colleague may say that they occasionally adjust a request because they know what the manager intended. Ask for a representative example and identify the evidence used. The adjustment might be a documented convention, a legitimate delegated decision or an unsupported workaround.
Do not automatically transfer that practice to a new team. Have the process owner decide whether to formalise the rule, retain the decision internally or redesign the input so interpretation is unnecessary. Record the approved route in the map and instructions.
Validate the revised route with an ordinary case and a case where the intention is unclear. Check that the operator can identify the difference without personal knowledge of the requester. A process becomes more transferable when its important decisions are explicit. The mapping exercise should therefore produce a list of resolved rules and outstanding decisions, not only a diagram. Keep unresolved items attached to owners so they cannot disappear when the transition plan moves to the next stage.
