The Banking Balancing Act
Where should we draw the line between convenience, compliance, control and agility?
Across industries, professions and walks of life.
Start with a topic that interests you. Stay for a perspective you might not have expected.
Money, institutions, inclusion and the future of financial services.
02How technology changes organisations, decisions and everyday lives.
03Strategy, execution and the experience of making change happen.
04Teams, careers and the choices that shape how we work.
05Voices and experiences that help us understand one another.
06Personal journeys, discoveries and lessons gathered along the way.
Our planned banking series explore trade-offs, operating realities and the consequences that a strategy slide can miss. Each article will stand on its own.
Where should we draw the line between convenience, compliance, control and agility?
Classification, governance and the boundaries of customer-data use.
Read seriesThe integration and architecture decisions that determine how a bank actually works.
Access, recovery and monitoring that hold up when dependencies fail.
Read seriesWhen does a report change a decision, rather than simply document it?
Read seriesLeadership thought experiments with real operating constraints.
Intervention, false positives and the customer cost of preventing fraud.
Read seriesExamine trust, economics, assistance and exception handling in both models.
Begin with a situation, learn the concepts and try a changed condition. Explore the opening missions in our Learning series.
Products, deposits, lending, payments and the work behind the customer journey.
Explore this learning pathCore systems, interfaces, queues and the systems that connect them.
Explore this learning pathIdentity, privileged access, privacy, fraud and operational risk.
Explore this learning pathClassification, ownership, lineage, reporting and decision-making.
Explore this learning pathFollow a transaction, locate its dependencies and understand its failure paths.
Explore this learning pathLearn how it works, then examine what its assumptions leave out. These are the topics in our first banking cycle.
| Subject | Learning mission angle | Perspective angle |
|---|---|---|
| Banking reports: intraday, IRIS, SAS and operations | A report arrives late. Which decision has already been missed? | Which reporting investments actually contribute to bank growth? Banking Intelligence |
| Data classification and trusted custodianship | A customer file needs to travel. What should each field reveal? | Why a classification label cannot replace responsibility for data use. Trust by Design |
| Middleware, APIs, events and data in transit | The payment timed out. Is it safe to try again? | When does the banking backbone become the bottleneck or a single point of failure? Inside the Banking Backbone |
| SSO, PAM and break-glass access | Your bank cannot sign in. Who can still restore service? | When your security controls become your single point of failure. Operational Resilience |
| Bank products, third-party providers and data-sharing boundaries | A product partner asks for the entire customer file. What can it receive? | Does permission to sell a product justify broader customer-data access? Trust by Design |
| Digital onboarding: CASA and loan origination | An application is almost complete. Which exception should stop onboarding? | Where should convenience yield to compliance, and who owns the exception? The Banking Balancing Act |
| A CISO runs the bank as CEO for a day | Compare the decisions a CEO, CISO and operations lead are accountable for. | What changes when security owns the growth target as well as the risk register? The Executive Chair |
| Why a bank needs a data-governance framework | Two dashboards disagree. Who owns the definition of the number? | Can governance succeed when accountability stays outside business teams? Trust by Design |
| Latency, TPS and system-design trade-offs | The average response looks fine. Why are customers still waiting? | What can change to meet throughput targets, and what must remain correct? Inside the Banking Backbone |
| Monitoring, observability and SIEM | A thousand alerts arrive. Which one should wake the on-call team? | What should be logged, what should be alerted, and what creates harmful noise? Operational Resilience |
| Fraud prevention and the customer cost of controls | A genuine payment looks suspicious. Which intervention is proportionate? | When do false positives and blocked access become customer harm? Fraud vs Controls |
| Traditional banking, digital-first banking and neobanks | The app works. The unusual customer problem does not. Who resolves it? | Compare the economics and exception-handling capabilities behind the customer experience. Traditional Banking vs New Banking |
| UPI merchant pricing and sustainable payment acceptance | The payment feels free. Who funds the rail? | How should merchant contribution fund reliable payments while protecting everyday access? The Banking Balancing Act |
A lesson from your profession. An experience that changed your mind. A question you think deserves a better conversation.
Share your perspective