OR v2

[OR] [BJB] [E2] [C2] Bank Julius Baer's Plan Phase of the Operational Resilience Planning Methodology

Written by Moh Heng Goh | Nov 16, 2026, 8:28:03 AM

Introduction

Every programme that goes wrong in its second year usually went wrong in its first month, when nobody wrote down the starting point, the target or the person accountable. The Plan phase of Bank Julius Baer's Operational Resilience Planning Methodology exists to prevent that.

It is the first of three phases and has five stages: Assess Capability and Maturity, Analyse Gap, Develop Strategy and Roadmap, Confirm Risk Appetite, and Develop and Embed Governance. Bank Julius Baer (BJB) runs its Singapore operations under a Monetary Authority of Singapore (MAS) wholesale bank licence, so each stage has to produce evidence a supervisor can read.

Public information about BJB is used as context only. Teams, systems and figures below are illustrative and need to be replaced with the bank's own.

Purpose of the Chapter

This chapter prepares you for the five-stage chapters that follow. After reading it you should understand what the Plan phase is for, what each stage produces, and how the stages depend on each other. You should be able to explain to a colleague why the bank does not begin by naming critical services, and why capability, gaps, strategy, appetite and governance come first. Think of it as agreeing the destination and the route before anyone starts the engine.

Why Plan Comes First

Preparation matters because operational resilience cuts across silos. Business continuity, technology risk, outsourcing, cyber security, compliance and the front office each hold part of the picture. The Plan phase pulls these parts together. It should reuse what already exists, such as existing business continuity plans, technology recovery arrangements and the operational risk framework, rather than start again. It also surfaces competencies the team lacks, so that people and budget are lined up before work starts.

Stage 1: Assess Capability and Maturity

The first stage measures the present. Business heads complete a scorecard across resilience parameters, and the results are plotted on a radar chart so strengths and weaknesses are visible at a glance. The OR lead then picks the parameters that need attention first.

Illustrative example: in BJB Singapore, the operations head scores third-party management as 2 out of 5 because the vendor inventory lists suppliers but not the services they support. The head of technology scores recovery testing as 4 out of 5. The contrast tells the team where to look.

Stage 2: Analyse Gap

Stage 2 compares the current state with the desired state. The team defines scope, lists applicable standards and regulations, assesses risks, performs the gap analysis and develops an action plan.

Illustrative example: the gap register records that service-level recovery targets exist for systems but not for client-facing services. The root cause is that planning was done per application, not per service. The owner is the head of operational risk and the target date is the end of the next quarter.

Stage 3: Develop Strategy and Roadmap

The roadmap is the bridge between strategy and execution. It states a vision with a date, groups actions into initiatives, and sequences them by impact and feasibility within resource limits.

Illustrative example: BJB's roadmap commits to a service inventory within six months, tolerances for each critical service within twelve months, and a first integrated test in the second year. Each initiative has a sponsor and a budget line.

Stage 4: Confirm Risk Appetite

Operational resilience widens the usual risk appetite discussion. The board states how much disruption to clients and markets it will accept, and management translates that into thresholds and indicators.

Illustrative example: the bank's appetite statement adds that disruption to client payments is a critical operational risk, with key risk indicators such as the number of failed payment cut-offs per quarter reported to the board.

Stage 5: Develop and Embed Governance

Governance defines who is accountable, how decisions are escalated and how progress is reported. It also integrates resilience into the three lines model so first and second line roles are clear.

Illustrative example: a senior executive is named owner of each critical service, the second line challenges tolerances, and a resilience forum reports to the Singapore executive committee and onward to the board [verify how Group governance applies to the branch].

Decision Rights Across the Phase

Each stage needs a named decision maker, or it drifts. A workable allocation for a Singapore bank is shown below, and BJB should confirm it against its own delegations of authority.

  • Stage 1: the OR lead designs the scorecard and each business head owns the scores for their vertical. Senior management signs off the baseline.
  • Stage 2: the head of operational risk owns the gap register. The compliance function confirms that the requirements matrix is complete.
  • Stage 3: the executive committee approves the roadmap and its funding.
  • Stage 4: the board approves the appetite statement on the recommendation of the chief risk officer.
  • Stage 5: the executive committee approves policies. The resilience forum monitors delivery.

Readiness Questions Before Starting

Before the Plan phase begins, the OR lead can ask a short set of questions to test readiness. Is there an executive sponsor who will attend the forum? Is there a budget for the first year, even if approximate? Which existing programmes, such as business continuity, technology recovery, outsourcing oversight and operational risk, will be reused, and who owns them? Does the team have the skills to run a maturity assessment and a gap analysis, or does it need help? Are the dates of regulatory submissions and Group reporting known, so the plan avoids clashes? Answering these questions in writing takes an hour and prevents months of delay.

Common Mistakes in the Plan Phase

Teams often rush to name critical services before the foundation is laid, which leaves the services without an agreed appetite or an owner. Others treat the maturity assessment as a compliance form, scoring generously to avoid awkward conversations. A third mistake is to let the roadmap grow until it contains every project in the bank with a resilience label. The remedy for each is the same: keep the Plan phase short, evidence-based and honest, and finish it before the Implement phase begins. A realistic target for a bank of BJB's size is a few months, not a year, with the roadmap itself reviewed twice a year afterwards.

Summary Table

Table 2: Bank Julius Baer's Plan Phase of the Operational Resilience Planning Methodology
Stage Question answered Output
1. Assess Capability and Maturity Where are we today? Scorecards, radar charts
2. Analyse Gap What is missing? Gap register and action plan
3. Develop Strategy and Roadmap How do we get there? Roadmap with initiatives
4. Confirm Risk Appetite How much disruption is acceptable? Board-approved statement and indicators
5. Develop and Embed Governance Who decides and who reports? Governance framework and policies

Conclusion

The Plan phase is unglamorous and decisive. A bank that completes it can say what it has, what it lacks, what it will do, how much risk it accepts and who is responsible. The next chapter starts with the first stage, the assessment of capability and maturity.

Sources

Continue reading: Chapter 3, Assessing Capability and Maturity Stage of OR Plan Phase for Bank Julius Baer, shows how to establish the baseline.

eBook 2: Implementing Operational Resilience for Bank Julius Baer
C1 C2 C8 C14

 

  "Plan" Phase of the Operational Resilience Planning Methodology
  C2 C3 C4 C5 C6 C7