Operational
Excellence

Two documentation types, often confused:

• SOPs define how work is done.
• DTPs define step-by-step execution.

Most GBS teams have documentation that is either too abstract to be useful or so detailed it is never read. The sweet spot lets someone new execute the process within a day — not a week, not a month.

In a GBS environment, knowledge is distributed across wikis, SharePoint sites, email threads, and heads. When someone leaves, their knowledge walks out with them.

• A single source of truth is not a technology problem — it is a discipline problem.
• One authoritative location per process, updated as part of the change cycle, not as an afterthought.

The biggest source of errors in GBS is not what happens inside a team — it is what happens between teams. Handoff points are where transactions stall, data gets corrupted, and accountability disappears. E2E process ownership means someone is accountable for the outcome, not just their piece of the chain.

Process maps are the common language of GBS improvement:

• Visio — the legacy standard.
• Lucidchart — the collaboration-first alternative.
• Signavio — connects process mining to documentation.

The tool matters less than the discipline: if your process maps do not match reality, they are fiction.

Service blueprinting maps the entire delivery chain — what the customer sees (front-stage) and what happens behind the scenes (back-stage). Design thinking applies human-centered problem solving to service improvement. Both are underused in GBS because most teams optimize for efficiency first and experience never.

ITIL and COBIT were built for IT service management — GBS borrowed them because the underlying logic holds.

• ITIL covers the full service lifecycle: incident management, problem management, change management, service catalog.
• COBIT adds the governance and control layer on top.
• Not every concept translates directly to GBS, but the service lifecycle thinking is universally applicable.

A service catalog lists what your GBS delivers, to whom, at what service level, and at what cost.

• Without one, your GBS is a black box — business units do not know what they are paying for, and you cannot manage demand or demonstrate value.
• Building a catalog forces uncomfortable conversations about what is in scope and what is not.

Service transition is the handover from project to BAU — where a new process or team goes live. It is where most GBS implementations stumble. The project team moves on, operations inherits undocumented exceptions, and the first month looks nothing like the business case. Structured transition management prevents this.

Two experience metrics that measure different things:

• NPS — whether internal clients would recommend your service.
• CES — how hard it was to get what they needed.

In GBS, CES is often more actionable than NPS — a process can be accurate but so painful to interact with that stakeholders route around it entirely.

Same service, two very different questions:

• SLA — what you deliver ("resolved within 24 hours").
• XLA — how it felt: did the resolution help, was communication clear, did the stakeholder have to follow up.

XLAs shift the conversation from compliance to quality.

Continuous improvement only works when it is embedded in daily operations, not run as a quarterly initiative from a PMO slide deck. Kaizen means every team member looks for small improvements every day. The team lead’s job is creating the environment where people feel safe to flag problems and empowered to fix them.

Lean identifies eight types of waste: defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra-processing.

• Waiting — approvals stuck in queues
• Defects — rework from incorrect data
• Non-utilized talent — experienced analysts doing manual copy-paste work

Visual management makes work status visible to everyone without asking. A huddle board shows daily priorities, blockers, and KPIs at a glance. Digital Kanban tools do the same for distributed teams. The point is not the board — it is the daily standup conversation that happens in front of it.

The Lean Six Sigma belt system, in plain terms:

• White — awareness.
• Yellow — participation.
• Green — part-time project leadership.
• Black — full-time improvement leadership.
• Master Black Belt — organizational capability building.

The belt itself matters less than the structured problem-solving methodology it represents.

SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers. It is a one-page scope definition that prevents improvement projects from drifting. Before you optimize anything, you need to agree on where the process starts, where it ends, and who it serves. SIPOC forces that alignment in a single workshop.

A value stream map traces a transaction from request to delivery, capturing every step, wait time, and rework loop. The current-state map usually reveals that 80% of total cycle time is waiting, not processing. The future-state map is your improvement roadmap — the gap between the two is your business case.

DMAIC is the Six Sigma project methodology:

• Define the problem.
• Measure current state.
• Analyze root causes.
• Improve with tested solutions.
• Control to sustain gains.

Every step has specific deliverables and tollgates. Skipping straight to Improve — which everyone wants to do — is how you solve the wrong problem.

The A3 format constrains your entire problem-solving narrative to one sheet of paper:

• Left side — background, current condition, root cause.
• Right side — target condition, countermeasures, implementation plan.

The constraint forces clarity. If you cannot explain the problem and solution on one page, you do not understand it well enough.

Two root-cause tools that stop you fixing symptoms:

• Five Whys — keep asking "why" until you reach the systemic cause.
• Fishbone — categorize potential causes by type.

When the same error type recurs quarterly, someone stopped at "why" number two.

Innovation and continuous improvement are different disciplines — CI optimizes what exists; innovation creates something new.

• Hackathons generate energy and ideas, but without an idea funnel to evaluate, fund, and implement, they become annual morale events with no lasting output.
• The funnel matters more than the hackathon.

Not all savings are equal — and Finance knows the difference.

• Hard savings hit the P&L: headcount reduction, vendor cost elimination, actual budget decrease.
• Soft savings are cost avoidance — you would have needed 5 more people if you had not automated.
• Finance only trusts hard savings. Your GBS credibility depends on knowing which category your improvement lands in — and being honest about it.

The difference is timing:

• Quality control — tracking errors after they happen.
• Quality management — preventing errors before they happen.

The shift from reactive to proactive requires categorizing defects by root cause, building prevention controls, and measuring defect rates over time — not just counting how many got caught in review.

The four-eyes principle means no single person can initiate and complete a transaction alone.

• In GBS, this is the foundation of internal controls: segregation of duties between who creates, who reviews, and who approves.
• It exists because the cost of catching fraud or errors after they reach the client is exponentially higher than catching them at execution.

Audit readiness is not a quarterly fire drill — it is a daily operating discipline.

• Documentation is current, controls are evidenced in real-time, exceptions are logged with explanations.
• Your team can walk an auditor through any transaction without advance preparation.
• The teams that panic before audits are the ones that treat compliance as separate from operations.

When volumes spike or SLAs breach, the first response matters more than the root cause analysis that follows. Effective escalation management means pre-defined severity levels, automatic stakeholder notification, and a triage protocol that prioritizes by business impact — not by who escalates loudest.

The Eisenhower Matrix sorts tasks by urgency and importance. In GBS, the trap is spending 80% of your day in "urgent and important" (fire-fighting) while "important but not urgent" (process improvement, career development) never gets touched. The matrix is simple. The discipline to protect quadrant two time is not.

In a GBS environment, email is both your primary communication tool and your biggest productivity drain. Zero inbox means processing every email into an action, a delegate, a file, or a delete within a defined time window. The goal is decision speed, not email bankruptcy.

Service environments interrupt constantly — queries, escalations, status updates. Time blocking reserves specific hours for focused work and communicates those blocks to the team. Without it, your day is 100% reactive and deliverables that need thinking never get done.