Isabel Luna 10/4/25 Isabel Luna 10/4/25

Navigating Layoffs with Compassion: Small Acts That Make a Big Difference

I’ve seen how empathy, paired with practical tools, can light the way. While we can’t stop layoffs, we can offer meaningful support to those affected.

Isabel Luna 7/17/25 Isabel Luna 7/17/25

Embracing the Challenges of ADHD Students: A Journey Toward Resilience

The true heart of this article though lies in my experiences with students diagnosed with ADHD—a group whose unique challenges have profoundly shaped my approach to mentoring and reminded me of the power of patience in design education.

1. Executive Summary & Strategic Problem Space

This case study evaluates a simultaneous, real-world security breach affecting two distinct banking systems holding accounts for the same customer, me: Bank 1 (a Local Commercial Bank) and Bank 2 (a Large-Scale Regional Bank).

The aftermath: While Bank 1 sent me a single letter, Bank 2 sent me a flurry of statements, multiple ATM cards, deposit slips, cheque books that poured over the course of a month.

The Core Dilemma: Security vs. Anxiety

When my financial accounts were compromised, I experienced acute psychological stress, characterised by an immediate drop in trust and a spike in cognitive load…for one bank, at least.

Bank 1 utilised an Orchestrated Service Framework, absorbing the operational friction on the backend, maintaining my everyday routine, and transforming a crisis into a high-loyalty retention event.
Bank 2 defaulted to a Fragmented System Loop, offloading technical debt and administrative overhead directly onto me through a multi-week, multi-channel failure cascade.

True design agility is not just about having a modern front-end app; it is about how seamlessly the front-stage touchpoints (CS, App, Branch) communicate with back-stage systems (Core Banking, Fraud Detection, Cards Management).

3. The Comparative Journey Teardown

Phase 1: Discovery & Triage (The Panic Horizon)

Phase 2: Containment & The Brick-and-Mortar Pivot

4. My Unforeseen Cascades (The True Pivot of Trust)

An organisation's true service maturity is revealed not when things go right, but how the system handles errors. This phase highlights Bank 2's total absence of Service Recovery Protocols during my recovery journey.

Bank 1: Zero Post-Incident Friction
My customer journey ended cleanly on Day 1. The loop was closed, my banking services resumed, and I felt highly valued.

Bank 2: My 6-Stage Failure Loop

The Administrative Error: A backend teller made a manual data entry mistake on my files, completely halting my application and forcing me to return to the branch on a Monday morning just to sign another document.
The Hardware-Software Disconnect: My new credit cards arrived but failed activation via PIN. When I called the hotline, frontline customer service agents lacked the system permissions or visibility to fix my issue, routing me back to a physical branch.
The Booking Engine Blindspot: When I attempted to book a branch appointment via the app as advised, the system's scheduling engine suffered a geographical blindspot—omitting the branch nearest to my office from the interface.
The Localisation/UX Fault: Upon returning to collect my physical ATM card, a junior employee handed me a Chinese-language-only card interface, which I could not activate, triggering an additional 5-day wait for an English card.
The Cross-Channel Product Gap: Once my new card arrived and digital services were restored, the card failed to integrate with my Apple Wallet. Customer service revealed to me that this newly issued regional card product was completely incompatible with Apple Wallet architecture—requiring yet another application from me for a UnionPay variation.
The Black Hole: My final UnionPay card failed to arrive within the promised 10-day operational SLA, leaving my journey open-ended, frustrating, and incomplete.

5. Strategic Service Recommendations

To transform these insights into systemic design patterns, both banks require distinct structural interventions based on their architectural maturity.

While Bank 1's performance was exemplary, high-performing services must protect against complacency:

Codify the Crisis Playbook: Institutionalise the exact workflow used by this senior branch member into a repeatable, automated training framework so that junior staff can deliver the same "Concierge" standard to others.
Predictive VIP Upgrades: Embed an automated flag in the CRM that detects when a user experiences a high-tier security threat, automatically applying premium benefits (like the "Preferred Client" status I received) as an automated retention trigger.

Recommendations for Bank 1 (Maintain & Leverage)

Recommendations for Bank 2 (Systemic Re-Engineering)

1. Implement "Zero-Repetition" Omnichannel CRM Data Continuity

The Fix: Eliminate data silos between the digital app, telephone CS, and physical branch networks.
The Design Pattern: When a customer triggers a "High Fraud/Account Freeze" event via phone or app, a unified Crisis Token must be generated. When that customer enters any physical branch, scanning their HKID should immediately pull up the unified token, pre-populating all forms and briefing the staff instantly without requiring oral data entry or repetition from the customer.

2. Re-engineer the Branch Environment for Data Privacy

The Fix: Move high-vulnerability compliance workflows away from public teller windows.
The Design Pattern: Implement an automated triage rule: Any customer presenting with an identity or fraud compromise must be automatically routed to a private acoustic environment (cubicle or office). Forcing clients to shout their national identity numbers (HKID) through a public window, as I had to do, is an unacceptable security and CX failure.

3. Establish Automated Quality Assurance for Physical Issuance

The Fix: Mitigate manual errors made by branch clerks that halt backend processing.
The Design Pattern: Introduce digital form-validation checkers at the teller desk. Forms should not be submittable to back-office processing if fields are incomplete or if the system detects language/localisation conflicts (e.g., mismatching the customer's preferred language with card stock distribution, which resulted in my Chinese-only card error).

4. Resolve the Regional Product & Digital Wallet Disconnect

The Fix: Align regional card provisioning with contemporary tokenisation expectations (Apple Wallet / Google Wallet).
The Design Pattern: During a forced account migration, the system should default to issuing a Universal Virtual Card directly into the customer's secure banking app within minutes of approval. This allows immediate tokenisation into Apple Wallet, granting the user access to their funds while the physical card is manufactured and mailed, eliminating multi-week financial freezes like the one I endured.

6. reflections

This case study demonstrates that security and user experience are not opposing forces on a zero-sum spectrum. True service design agility means building backend engineering and operational guardrails that absorb systemic complexity, keeping the customer safe not just financially, but emotionally.

Bank 1 designed a service that shielded me as a human and protected 100% of my capital; Bank 2 designed a bureaucracy that offloaded its defensive friction onto me, resulting in a $4,500 HKD loss and a total breakdown of organisational trust.

Let’s build together!

Building products or your team, I’m keen to be part of your solution.

Write me an email at isabelangelesluna@gmail.com or message me on LinkedIn or Instagram.
If all else fails, you can call me at +852 55038992