Summary of "Đột phá về Chiến Lược với Tư Duy Thiết Kế | Dr. Sơn Đỗ Lệnh, Private bank hàng đầu Thuỵ Sỹ |#TQKS 60"
Thesis: Innovation = “Design Thinking” Applied to Business Transformation
- Core claim: Innovation is redefining an old problem through a new perspective.
- Design thinking is “the core” for both innovation and execution.
- Practical stance: avoid over-planning—generate options, test quickly, learn, and then scale what works.
Frameworks / Processes / Playbooks Mentioned
Design Thinking (Core Innovation Method)
A typical flow:
- Observe → ask many questions and collect observations/data from real workflows.
- Define the real problem (it may differ from the initial “request”).
- Generate many possibilities (open a “diamond” of ideas).
- Experiment cheaply/quickly to find the best “peak” to pursue.
- Iterate with immediate mistake-correction.
“Untangle the Mess” (Transformation Starting Point)
Transformation often begins by mapping complexity across:
- End-to-end journey: front office → middle office → back office
- Interdependencies: people, processes, systems, and handoffs
Key move: remove friction / untangle interdependent parts—not just update technology.
Three-Layer Operating Model (Portfolio/Investment Platform)
Layers:
- Bottom: technology + platforms + processes + organizational ownership
- Middle: process & organization (the most difficult layer)
- Top: user experience / customer experience
Building rule (in reverse order): start with the ideal end-to-end customer journey, then build the supporting tech and operating structure.
Rethink / Re-rate / Remove (Simplification Playbook)
- In practice, “rethink everything” is selective:
- revise some
- remove some
- discard completely some
Main principle: simplify first so re-rating can work—otherwise you’re trying to re-rate a “tangled mess.”
Transformation Types (Resource Allocation Lens)
- Efficiency transformation
- Make things faster / cheaper (often the dominant focus).
- Sustaining transformation
- Improve within the current model (incrementally add products/services).
- Comprehensive / transformative transformation
- Build a new business model & strategy (new direction, not incremental improvement).
Balance point: don’t fund only efficiency—selectively invest in exploration.
Key Business Problems & Concrete Examples
Bank Portfolio Management Transformation: Not a “Technology Issue”
- The main root cause emphasized is people + process + organization, which then creates inconsistent data flows.
- Even after decades of building, systems become outdated and manual handoffs remain—especially under changing regulations.
Regulatory Change Drives Process Complexity (Example: U.S. Client Ties Reporting)
Initial request (manual tradition):
- Bankers must report whether clients have American ties (annually), based on legal definitions (e.g., days lived, green card, citizenship).
- Workflow:
- government email → banker checks list → assistant searches → letter/report completion
Design thinking outcome:
- The real user need wasn’t “fill the form,” but “what should I do today?”
- Result: a daily to-do list concept (mobile app/dashboard/Outlook integration)
- triggers actions
- automates information gathering
Data Inconsistency & Bottlenecks
Example mechanics:
- Banker gathers client info
- Middle office validates
- Reputation/risk checks
- Data sent among multiple specialists (e.g., CPS—client portfolio specialists)
Underlying issue: lack of a consistent source across actors leads to fragmented, partly manual operations.
Efficiency Outcome Example: “x Days” to “y Minutes”
Before:
- Portfolio/investment delivery required multiple disconnected steps and human checks → took “x days.”
After transformation:
- Connect workflow logic starting from CRM entry
- Systems pull internet data
- Run scoring (e.g., PEP detection)
- Automate downstream checks
- Deliver targeted outputs in “y minutes”
Metrics / KPIs / Targets Mentioned
- Efficiency KPIs for portfolio/investment strategy changes were referenced, but no numeric targets were provided.
- A related KPI direction is faster execution and better responsiveness to strategic shifts (e.g., in an investment council decision context).
Implementation Recommendations & Leadership Tactics
Convince Leadership via “Pull” and Visible Benefits
- Transformation shouldn’t be purely “push” from the top.
- Show value quickly to overcome cultural resistance (people fear risk and relearning).
- Example cited: reduce repetitive manual work that nobody enjoys (e.g., assistant negative-news searching).
Use Cross-Functional, Multidisciplinary Teams
- Build teams spanning:
- technology
- process analysis
- sales/frontline
- compliance/risk
- Goal: “zoom out” so teams can see the full process/journey.
- Dr. Sơn positions himself as a translator between technology and business language.
Experiment Instead of Waiting for Long Documentation Cycles
A failure mode described:
- a massive specialized team (e.g., ~200 people)
- heavy documentation
- results not visible until ~two years
- leadership churn and benefits arriving too late
Lesson: waiting too long kills engagement; success must show measurable value earlier.
“Just Enough Planning”
- Don’t perfect plans months/years ahead.
- Make multiple small plans, test quickly, and adapt incrementally.
“Work the Talk”
- Leaders may talk about change but fail to align incentives.
- What matters is visible behavior.
- Trade-off: delay is costly, but fast experimentation must remain manageable by keeping tests cheap and small.
Strategic Framing: What “Transformation” Actually Includes
Transformation ≠ Only “Digital Transformation”
- Digital is a subset: use technology to transform:
- strategy
- business model
- operating model
- culture
- employees
- Strategic transformation is described as the most valuable because it shapes other transformations.
Balance Transformation Types
- Many organizations start with efficiency.
- Competitive markets require sustaining transformation and selective exploration.
Lessons Transferable to Vietnam / Developing Markets (High Level)
- Context matters: don’t copy-paste developed-country solutions (culture, people, operating realities differ).
- Avoid the “consultant plan then implement later” trap:
- strategy slides without simultaneous execution—especially when internal resistance exists.
- Change management means reducing manual pain and linking work to outcomes:
- business leaders don’t need deep technical jargon
- they need to connect daily work to revenue, profit, and customer results
Presenters / Sources
Presenters / Speakers
- Dr. Sơn Đỗ Lệnh — Director of Customer Experience in Asset Management Technology (leading private bank in Switzerland)
- Quốc Khánh — host of Quoc Khanh Show Podcast
Cited References / Public Figures
- Mike Tyson — quote contrasting planning vs. getting “punched”
- Steve Jobs — analogy contrasting Microsoft vs. Apple/cloud/parallel build
- Blockbuster / Netflix — strategy failure attributed to focusing on “efficient renting” instead of new competitive ground
- Microsoft / Azure / Stadia — example of building the next “house” in parallel
- Google — referenced as an example of visible “front” vs. business strategy origin
Category
Business
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...