Bad processes drain an estimated 30% of annual revenue from organisations that never bother to count the cost. That figure rarely changes a COO's behaviour—the list of broken processes is too long, the quarter is too short, and every department head has a compelling reason why their process needs to move first.
The answer is not more resource or a bigger programme. It is sequencing. COOs who build lasting improvement programmes do not fix everything simultaneously. They choose exactly 3 processes for the first quarter, sequence them by the type of cost they produce, and complete all three before touching anything else. The first improvement pick determines whether the programme gains enough internal credibility to survive into the second quarter.
This post is written for the transformation leads, operations managers, and chiefs-of-staff who build the recommendation their COO signs off on. It gives you a 3-tier vetting heuristic and a selection rule for breaking ties. The execution path uses ESSAM's 7-step improvement cycle and single-session process mapping.
The hidden cost of picking the wrong process first
COOs are rarely held accountable for which processes they chose to improve. Post-mortems blame resources, culture, and tools. They almost never ask: did we start with the right 3?
The hidden cost of a poor first selection is sequence failure. A back-office process that takes five months to map, approve, test, and deploy consumes the improvement team's capacity for the entire quarter. Meanwhile, the loan origination process generating a 14-day cycle time continues producing customer complaints and lost win rates. By the time the back-office fix ships, internal confidence in the programme has dropped, and the COO's mandate for a second quarter of improvements is weaker than it was at the start.
The selection problem is asymmetric. Choosing a high-visibility, high-handoff process first creates momentum: the team learns the method, staff experience the improvement, and results surface quickly. Choosing a low-visibility, high-complexity process first teaches the team how to navigate internal politics—which is valuable, but not what builds a programme.
Abdulla Al-Awadi, who founded ESSAM after serving as Chief Strategy Officer at a major Kuwait bank, observed this pattern across improvement engagements: teams that picked their first process based on visibility and handoff count produced sustainable programmes; teams that picked based on seniority of the department head requesting help produced one-time projects.
The 3-tier heuristic below gives you a systematic way to make the selection defensible.
The 3-tier vetting heuristic
Every process in a bank produces one of three types of visible cost: it costs the customer experience, it costs the balance sheet directly, or it costs the bank's risk and regulatory standing. Each type maps to a tier. Your first-quarter agenda picks one candidate from each.
Tier 1: Customer-visible processes
Customer-visible processes are those the customer experiences directly or measures in their own time. Loan origination, account onboarding, account opening, service request handling, and corporate client onboarding all belong here. Their cycle time, error rate, and handoff count are visible outside the bank.
These processes are the right anchor for the first quarter. Improvements here produce outcomes the whole organisation can see—falling complaint rates, faster approval times, higher NPS scores from frontline staff. That visibility builds the credibility the programme needs to survive into quarter two.
When selecting a Tier-1 candidate, prioritise the process with the highest ratio of wait time to total cycle time. A 14-day loan process where the credit decision takes less than a day is almost entirely composed of wait—routing, document chasing, verification queues, and escalation loops. That ratio is where E-S-S-A-M's Eliminate phase produces the sharpest reductions.
Tier 2: Cost-visible processes
Cost-visible processes are back-office and closing workflows whose inefficiency shows on internal reports. Month-end reconciliation, GL reconciliation, inter-department handoffs, interbank settlement, and payroll processing belong here. Customers do not see these processes directly, but finance does.
A cost-visible process is the right second choice. Improvement here generates internal ROI data—overtime hours avoided, error-correction loops retired, downstream reports released earlier. That data justifies the programme budget and earns the CFO's endorsement for the next cycle.
When selecting a Tier-2 candidate, look for the process where the same rework loop appears every cycle. Reconciliation processes that re-create the same exception list every month have chronic process debt, not a one-time data problem. Eliminating that loop produces compounding savings: every month the fix holds, the savings accumulate.
Tier 3: Risk-visible processes
Risk-visible processes are compliance and control workflows whose cost is quiet until an external event makes it loud. Regulatory reporting, alert triage, exception handling, KYC review cycles, and audit trail maintenance belong here. Under normal conditions, these processes are invisible. Under a MAS or BNM examination, they surface quickly.
A risk-visible process is the right third choice. Improvement here signals governance seriousness to regulators and reduces the probability that an external review finds gaps an internal one should have caught. For SG and MY banks operating under increasing regulatory expectations in 2026, this third pick matters beyond internal ROI.
When selecting a Tier-3 candidate, choose the process with the most unowned steps—where nobody can clearly state who is responsible for an exception if it surfaces between two teams. Ownership gaps are where regulatory risk concentrates.
The tie-breaking selection rule
If two candidates compete within the same tier, choose the one with the higher handoff count. Handoffs are where cycle-time variance, wait time, and error accumulation concentrate. A process with 9 handoffs where 3 are purely administrative—no decision, no control, no value—will produce a faster, larger improvement than a process with 4 handoffs and a genuine bottleneck at each one. Count handoffs before scoring anything else.
From selection to execution: the ESSAM 7-step cycle
The 3-tier heuristic tells you which processes to pick. The ESSAM 7-step improvement cycle tells you how to fix them within a single quarter.
The cycle runs: Baseline → Analyze → Optimize → Document → Deploy → Feedback → Repeat. For a first-quarter programme, each of the 3 selected processes runs through steps 1–6 before the quarter closes. Step 7 (Repeat) begins the next cycle.
What makes this feasible within a quarter is ESSAM's conversational capture. The Baseline step requires no flowchart software, no IT engagement, and no specialist process documentation. The process owner and one or two practitioners describe the process in natural language—where it starts, where it ends, and where days disappear. ESSAM generates the baseline map from that conversation in a single session.
Most process mapping programmes stall at Baseline because they require pre-work: process documentation, system access for mining tools, or consultant-led workshops that take weeks. Single-session conversational capture removes that stall. The Analyze and Optimize steps can begin in the same week as the Baseline.
For the Optimize step, the E-S-S-A-M framework (Eliminate, Simplify & Standardize, Automate, Migrate) provides the decision logic. Eliminate targets steps with no decision, control, or value content—administrative routing, duplicated checks, approval escalations for low-risk items. Simplify & Standardize targets format inconsistencies and exception paths that exist only because nobody agreed on a standard. Automate targets repetitive checks with rule-based logic. Migrate targets low-value tasks that belong closer to the front line, not in a specialist queue.
The Document step produces the approved SOP from the optimised design. It is not a process narrative or a slide deck—it is a structured, deployable document.
The Deploy step puts the new SOP in front of the staff who run the process. ESSAM deploys via WhatsApp. In Singapore, WhatsApp penetration is 88%; in Malaysia, it is 92% (industry data). Staff receive the updated process through a channel they use daily. No app installation, no e-learning module, no classroom session required. The SOP reaches the team within hours of approval, not weeks.
The Feedback step collects variance—where staff find the new SOP unclear, where exceptions surface that the design did not anticipate, and where the next optimisation opportunity lives. That input feeds the next cycle's Baseline.
What the Kuwait proof says about Tier-1 selection
The sequencing principle is not theoretical. At a Kuwait bank, a high-visibility procurement process—one with broad operational and supplier impact, making it a Tier-1 analogue—was mapped, redesigned, and deployed using ESSAM. The result was a reduction from 139 days to 57 days: 59% cycle-time compression, 82 days of waste retired permanently. That is a documented, real outcome from a verified engagement.
What the Kuwait case confirms about first-quarter sequencing: a Tier-1 process with high visibility and a high handoff count produced a result the wider organisation could see and measure. The programme gained credibility before the second cycle began. The improvement sustained because the ESSAM cycle built ownership and a feedback mechanism—not a deck that the team filed after the consultant left.
Consider, hypothetically, a retail lending bank applying the same Tier-1 selection logic to its loan origination process. The 14-day average cycle time is almost entirely composed of wait at handoffs—routing, document collection, verification queues, approval escalations. A single ESSAM mapping session with the origination team surfaces 9 handoffs, 3 of which add no decision or control value. The E-S-S-A-M Eliminate phase removes them. The redesigned SOP deploys to processing staff in Singapore and Malaysia via WhatsApp the same week the new design is approved. Cycle time drops. Complaint volume falls. The COO's first-quarter report has a number. This is an illustrative walkthrough of the method—the sequencing logic, not a specific client outcome.
That number—whatever it is for your bank's first process—is what earns the mandate for quarters two and three.
How to build the first-quarter recommendation
If you are preparing the process agenda for your COO, the following sequence produces a defensible recommendation.
Start by inventorying visible symptoms. Pull complaint escalation logs for Tier-1 candidates, overtime and error-correction reports for Tier-2, and any audit findings or near-miss records for Tier-3. Each symptom maps to a tier. Your candidates should surface from data, not from department heads lobbying for priority.
Run a single-session mapping conversation per candidate. Bring the process owner and one or two practitioners. ESSAM's conversational capture requires no prior documentation. Describe the process—start, end, and where time disappears. The session produces a baseline map and a waste analysis for each candidate. Run all three sessions before scoring anything.
Score each candidate on 7-step cycle readiness. The question is not which process is most broken—it is which process can complete steps 1–6 within the quarter. Processes requiring regulatory sign-off, system integration, or third-party coordination before any change can be tested belong in quarter two or three. Readiness, not severity, governs first-quarter selection.
Present one candidate per tier with a clear rationale. The recommendation to your COO is not a ranked list of 10 processes. It is 3 processes—one from each tier—with the handoff count, estimated cycle time saved, and deployment path for each. That framing makes the selection decision fast and the accountability clear.
Lock the list once approved and begin. Re-ranking when new symptoms surface mid-quarter is the fastest way to finish the quarter with no completed improvements. The 3 selected processes are the programme for the quarter. New candidates enter the next cycle's selection process.
Where this heuristic does not apply
The 3-tier model assumes each process can be mapped, optimised, and deployed within a single quarter. Two conditions break that assumption.
First: processes requiring regulatory pre-approval for any operational change. In MAS and BNM-regulated environments, certain compliance process changes require examiner notification or approval before implementation. These processes are not first-quarter candidates regardless of tier or handoff count. They are valid programme targets but need a longer runway.
Second: processes dependent on system integration that does not yet exist. If the optimised design requires a data feed or API connection that the bank's IT team needs months to build, the deployment step cannot complete in the quarter. The mapping and design work remains valuable—it goes into the queue—but the process should not occupy a first-quarter slot.
When in doubt, apply the readiness test before committing the slot: can steps 1–6 of the ESSAM cycle complete before the quarter closes, using only the tools and channels available today? If the answer is no, swap in the next candidate from that tier.
Start with one process
Tell ESSAM which process you want to examine first. Describe it in plain language—where it starts, where it ends, and where your team loses the most days. ESSAM returns a baseline map, a waste analysis using the E-S-S-A-M framework, and a redesigned SOP ready for staff deployment. No specialist required. No flowchart software. One conversation produces a working draft.
Share the process at https://apac.essam.ai/contact and ESSAM will return the analysis.
Frequently asked questions
Why pick exactly 3 processes for the first quarter instead of more?
Three processes is the number that a standard improvement team can baseline, optimize, document, deploy, and begin collecting feedback on within a single quarter—without parallel-running multiple changes and losing the signal on what worked. Fewer than 3 underuses the team's capacity. More than 3 produces half-finished improvements that erode programme credibility. The constraint is intentional.
How does the 3-tier heuristic differ from a standard priority matrix?
A standard priority matrix scores processes on impact and effort. The 3-tier heuristic scores them on the type of cost they produce—customer-visible, cost-visible, or risk-visible—and selects one from each type. The goal is a balanced first-quarter agenda that produces a visible win (Tier 1), an internal ROI result (Tier 2), and a governance signal (Tier 3), not the single highest-scoring process on a two-variable grid.
What is the E-S-S-A-M framework and how does it apply to process optimisation?
E-S-S-A-M stands for Eliminate, Simplify & Standardize, Automate, Migrate. It is ESSAM's proprietary optimisation method, applied after the baseline map is complete. Eliminate removes steps with no decision, control, or value content. Simplify & Standardize consolidates variant paths and removes format inconsistencies. Automate applies to repetitive, rule-based checks. Migrate reassigns low-value steps from specialist queues to front-line staff. Each phase produces a measurable reduction in cycle time, error rate, or handoff count.
How are redesigned SOPs deployed to staff in Singapore and Malaysia?
ESSAM generates the approved SOP as structured text and deploys it via WhatsApp. WhatsApp penetration is 88% in Singapore and 92% in Malaysia (industry data). Staff receive the updated process through a channel they already use daily—no app installation, no e-learning module, no classroom session. The SOP reaches the team within hours of the design being approved, not weeks.
What does the Kuwait bank case tell us about sequencing the first improvement?
At a Kuwait bank, a procurement process—high in operational and supplier visibility, making it a Tier-1 analogue—was mapped, redesigned, and deployed using ESSAM. Cycle time fell from 139 days to 57 days: 59% compression, 82 days of waste permanently retired. That is a documented, real outcome. Starting with a high-visibility, high-handoff process generated results the wider organisation could see before the second improvement cycle began—which is exactly what a first-quarter selection should do.
Related reading: