Improving Lessons Learned
(Stage of the “Implement” Phase – Operational Resilience Planning Methodology for Metrobank)
Introduction
As one of the Philippines’ leading universal banks, Metropolitan Bank & Trust Company (Metrobank) is dedicated to maintaining operational resilience in the face of evolving financial, technological, and geopolitical risks.
In the “Implement” phase of its Operational Resilience Planning Methodology, the Improving Lessons Learned stage serves as the cornerstone for continuous enhancement — ensuring that every incident, scenario test, or disruption becomes an opportunity for learning and improvement.
This stage transforms past challenges into future strengths. By systematically capturing, analysing, and integrating lessons learned, Metrobank can refine its response mechanisms, enhance service continuity, and strengthen governance across all Critical Business Services (CBS), including Payments and Fund Transfers, Deposit and Withdrawal Services, and ATM Operations.
In alignment with the Bangko Sentral ng Pilipinas (BSP)’s Operational Resilience Guidelines (issued under BSP Memorandum M-2022-043 and related circulars), Metrobank is expected to institutionalise feedback loops to evaluate and update resilience practices.
These guidelines emphasise proactive risk management, adaptability, and an evidence-based culture of improvement to support overall financial stability in the Philippines.
Purpose of the Improving Lessons Learned Stage
The objective of this stage is to ensure that every operational incident, test, or resilience exercise generates actionable insights that strengthen Metrobank’s operational resilience framework.
Lessons learned must lead to measurable improvements — whether in control design, response coordination, communication effectiveness, or system recovery time.
This process contributes to Metrobank’s long-term resilience maturity by:
- Identifying systemic weaknesses before they escalate into critical disruptions.
- Enhancing response and recovery procedures for critical business services.
- Reinforcing a culture of accountability and continuous improvement.
- Ensuring compliance with BSP operational resilience expectations.
Implementation Steps
Step 1: Collect and Document Lessons Learned
After each scenario test, incident, or business disruption, Metrobank teams must systematically collect data and observations from all relevant stakeholders, including the Business Continuity, Risk, Operations, and IT departments.
Key actions:
- Conduct structured post-incident or post-exercise debriefs (“After-Action Reviews”).
- Capture observations, gaps, and successes in the Lessons Learned Log.
- Record metrics such as Recovery Time Actual (RTA) vs Recovery Time Objective (RTO).
Example:
During a power outage simulation at the Metrobank Head Office, IT teams observed a 15-minute delay in activating the backup data centre due to communication gaps.
This observation was recorded and classified as a “procedural delay,” triggering review and training improvements.
Step 2: Analyse Root Causes and Impacts
Each lesson learned should be reviewed to determine its root cause and potential systemic impact on critical services.
Key actions:
- Apply root cause analysis tools (e.g., 5 Whys, Fishbone Diagram).
- Assess which CBS systems or processes were most affected.
- Identify contributing factors such as resource shortages, unclear escalation, or technology dependencies.
Example:
In a disruption to Payments and Fund Transfers (CBS-2), analysis revealed that delayed incident escalation was due to unclear role ownership. This root cause analysis led to a revised incident response matrix defining explicit decision rights and escalation triggers.
Step 3: Prioritise Improvements and Assign Ownership
The lessons learned must be translated into targeted corrective and preventive actions.
Key actions:
- Categorise actions as Immediate, Medium-term, or Strategic.
- Assign responsible units and deadlines for each improvement item.
- Integrate improvement actions into Metrobank’s Operational Resilience Action Tracker.
Example:
A repeated network latency issue identified during testing of ATM Services (CBS-3) prompted IT Infrastructure to commit to deploying network redundancy by Q2 2026, while Risk Oversight monitors implementation progress.
Step 4: Integrate into Frameworks, Policies, and Training
Operational improvements must be embedded into the bank’s frameworks, policies, and staff training programs.
Key actions:
- Update the Business Continuity Plan (BCP) and Crisis Management Procedures.
- Incorporate new controls or metrics into the Operational Risk Management Framework.
- Deliver targeted training or communication refreshers to staff.
Example:
Following a phishing-related disruption, Metrobank’s Security Operations Centre incorporated new response checklists, and HR mandated quarterly phishing simulations for all employees in sensitive functions.
Step 5: Validate Improvements Through Retesting
To ensure effectiveness, improvements must be retested and validated in subsequent scenario tests or live events.
Key actions:
- Design follow-up exercises focusing on previously identified weaknesses.
- Measure performance improvement (e.g., reduced downtime, faster escalation).
- Confirm closure of improvement actions in official reports.
Example:
A follow-up cyber incident simulation showed a 35% reduction in detection-to-response time — validating the success of the prior procedural and training enhancements.
Step 6: Report and Review at Management Level
All findings, actions, and improvement results should be consolidated and presented to senior management and relevant governance committees.
Key actions:
- Present a “Lessons Learned Summary Report” during Operational Risk Committee meetings.
- Highlight major trends, recurring issues, and achieved improvements.
- Recommend policy updates for Board approval when systemic changes are required.
This practice aligns with BSP expectations for transparent governance and the Board’s ultimate accountability for maintaining operational resilience.
Example of BSP Compliance References
Metrobank’s improvement of lessons learned directly supports compliance with the following BSP requirements:
|
BSP Guideline Reference |
Summary of Expectation |
Metrobank Compliance Approach |
|
BSP Memorandum M-2022-043: Operational Resilience Framework |
Institutions must establish mechanisms to capture lessons learned from disruptions and ensure continuous improvement. |
Implementation of structured post-incident reviews and updates to policies and procedures. |
|
BSP Circular No. 1124: Operational Risk Management |
Banks must maintain an effective operational risk framework that incorporates feedback and promotes learning from incidents. |
Integration of lessons learned into operational risk and business continuity processes. |
|
BSP Circular No. 808: IT Risk Management Framework |
Continuous improvement through testing, monitoring, and reviewing IT resilience. |
Validation of improvement through regular IT system testing and enhanced response coordination. |
Template for Management Review: Lessons Learned Summary
|
CBS Code |
Critical Business Service |
Incident / Scenario Tested |
Key Lessons Learned |
Root Cause Identified |
Corrective Action / Owner |
Target Completion Date |
Validation Method |
Status |
|
CBS-1 |
Deposit and Withdrawal Services |
Data centre outage simulation |
Communication delay between branches and HQ |
Inadequate notification protocol |
Update alert escalation flow (Ops Manager) |
Mar 2026 |
Retest in Q2 2026 scenario |
In progress |
|
CBS-2 |
Payments and Fund Transfers |
System downtime during high transaction volume |
Lack of load balancing |
Capacity planning gaps |
Upgrade middleware server (IT) |
Jan 2026 |
Load test validation |
Completed |
|
CBS-3 |
ATM Services |
Network failure due to telco disruption |
Single point of failure in the network route |
Insufficient redundancy |
Deploy dual telco links (IT Infra) |
May 2026 |
Post-deployment connectivity test |
Planned |
Summing Up…
The Improving Lessons Learned stage marks the evolution of Metrobank’s operational resilience from reactive management to proactive foresight. By embedding structured learning mechanisms, Metrobank ensures that each experience — whether a crisis, test, or near-miss — becomes a catalyst for institutional growth.
This ongoing process not only refines Metrobank’s resilience posture but also reinforces its commitment to BSP’s expectations for continuous enhancement, robust governance, and sustained public confidence.
Through this discipline, Metrobank strengthens its ability to safeguard customer trust, protect critical operations, and uphold the stability of the Philippine financial ecosystem.
Ultimately, operational resilience is not a static goal — it is a dynamic journey of learning, improving, and adapting to an ever-changing risk landscape.
Metrobank’s structured approach to improving lessons learned ensures that it remains ahead of emerging challenges while continually raising the benchmark for resilience excellence in the banking industry.
Building Resilient Banking Operations: The Metrobank Operational Resilience Implementation Guide |
|
|
|
|||||
"Implement" Phase of the Operational Resilience Planning Methodology |
|
|
|
|||||
| C8 | C9 | C10 | C11 | C12 | C13 | |||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|||
Gain Competency: For organisations looking to accelerate their journey, BCM Institute’s training and certification programs, including the OR-5000 Operational Resilience Expert Implementer course, provide in-depth insights and practical toolkits for effectively embedding this model.

![BB OR [Grab] Payment Gateway 2 BB OR [Grab] Payment Gateway 2](https://blog.bcm-institute.org/hs-fs/hubfs/BB%20OR%20Grab%20Id/Pictures%20Grab%20Id/BB%20OR%20%5BGrab%5D%20Payment%20Gateway%202.jpg?width=2000&height=1333&name=BB%20OR%20%5BGrab%5D%20Payment%20Gateway%202.jpg)



![[OR] [MBT] [P2] [S1-S5] [C8] Five Stages of the _Implement_ Phase](https://no-cache.hubspot.com/cta/default/3893111/ee0a428b-6e4f-46c4-a047-fa5e6f155e09.png)
![[OR] [MBT] [E2] [P2] [S1] [C9] Identifying Critical Business Services](https://no-cache.hubspot.com/cta/default/3893111/fb91e4c0-1e37-4965-ac60-33e83fa1b644.png)
![[OR] [MBT] [E2] [P2] [S2] [C10] Mapping of Processes and Resources](https://no-cache.hubspot.com/cta/default/3893111/c41af3a1-4cb4-40d3-903c-bfae040902bc.png)
![[OR] [MBT] [E2] [P2] [S3] [C11] Establishing Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/dcbdd3db-20c3-4d27-95d4-f8c5f89ad62f.png)
![[OR] [MBT] [E2] [P2] [S4] [C12] Performing Scenario Testing](https://no-cache.hubspot.com/cta/default/3893111/2b0cc99e-29fb-432a-a9c4-033e86a0e9c2.png)





![[BL-OR] [3-4-5] View Schedule](https://no-cache.hubspot.com/cta/default/3893111/d0d733a1-16c0-4b68-a26d-adbfd4fc6069.png)
![[BL-OR] [3] FAQ OR-300](https://no-cache.hubspot.com/cta/default/3893111/f20c71b4-f5e8-4aa5-8056-c374ca33a091.png)
![Email to Sales Team [BCM Institute]](https://no-cache.hubspot.com/cta/default/3893111/3c53daeb-2836-4843-b0e0-645baee2ab9e.png)








