Value Stream Mapping a GCC Shared Services Handoff

Start with the actual handoff, not the process description

GCCs often optimize their internal workflows while ignoring the handoff between teams. You map the handoff, not the job description. Pick one recurring handoff: for example, a process mining team handing off findings to the Lean Six Sigma team for implementation. Map that specific flow from start to finish.

Define the scope with clear start and end points

Set the boundaries. Start when the upstream team submits the handoff artifact. End when the downstream team acknowledges receipt and begins work. Anything outside that range is not part of the map. This keeps the map focused and actionable.

Identify every handoff step

List each step in the handoff. Include steps like: artifact submission, quality check, assignment, clarification request, approval, and start of work. Capture each step as a separate event. Do not group steps together. Granularity reveals hidden delays.

Capture lead time and cycle time

For each step, record lead time and cycle time. Lead time is the time from when the step is triggered to when it starts. Cycle time is the time the step actually takes. Use real data from recent handoffs. Do not estimate. Real data exposes bottlenecks that estimates hide.

Mark value-added and non-value-added steps

Classify each step as value-added or non-value-added. Value-added steps directly contribute to the handoff's purpose. Non-value-added steps include waiting, rework, and unnecessary approvals. Highlight non-value-added steps clearly. This shows where time is wasted.

Identify handoff delays

delays occur when the downstream team cannot start work. Common causes include: missing artifacts, unclear requirements, and quality issues. Map each delay with its root cause. For example, a delay might occur because the upstream team did not include a data dictionary. Document the cause and frequency.

Calculate handoff efficiency

Efficiency is the ratio of value-added time to total handoff time. Low efficiency indicates high waste. Use the formula: efficiency = value-added time / total time. Target an efficiency above 70%. Below 70%, the handoff needs improvement. Track this metric over time.

Visualize the map with swimlanes

Use swimlanes to show which team owns each step. This makes handoff points obvious. For example, the process mining team might own the submission step, while the Lean Six Sigma team owns the assignment step. Visualizing ownership clarifies responsibility and reduces ambiguity.

Highlight rework loops

Rework happens when the downstream team rejects the handoff and sends it back. Map each rework loop with its trigger and resolution time. For example, a rework loop might occur because the upstream team did not include a test plan. Document the trigger and time to resolve. Rework loops are a major source of waste.

Set a target handoff time

Define a target handoff time based on current data. For example, if the current average handoff time is 5 days, set a target of 3 days. Use the map to identify which steps to improve. Focus on steps with the highest waste. Prioritize improvements that reduce non-value-added time.

Implement improvements with a pilot

Test improvements on a small scale before full rollout. For example, create a handoff checklist for the upstream team to reduce quality issues. Measure the impact on handoff time and efficiency. If the pilot works, scale it across the GCC. If it fails, adjust and retry.

Monitor and refine the map

Review the map monthly. Update data as processes change. Track efficiency and handoff time over time. Celebrate improvements. Use the map to drive continuous improvement. A GCC that maps its handoffs regularly will outperform those that do not.

Key takeaways

• Map the actual handoff, not the process description.
• Capture real lead and cycle times.
• Classify steps as value-added or non-value-added.
• Identify delays and rework loops.
• Calculate handoff efficiency and set a target.
• Use swimlanes to clarify ownership.
• Pilot improvements and monitor results.

GCCs that map their handoffs reduce waste and improve flow. Start with one handoff, map it, and improve it. Repeat. This is how GCCs scale without breaking.