The Bun Maska Principle: Why Resilient Banks Need a Ritual, Not Just an App

What does a neighborhood restaurant serving tea have to teach a bank about surviving a crisis?

At first, almost nothing. One deals in deposits, credit, and digital interfaces. The other serves biscuits, omelets, rolls, and sweet tea. One is governed by capital requirements and revenue forecasts. The other is remembered through furniture, smells, habits, and stories.

Yet they confront the same strategic problem: how do you remain essential when the transaction itself becomes easy to replace?

A crisis exposes the answer. It does not merely punish weak balance sheets or outdated technology. It reveals whether an institution has become part of the rhythm of people’s lives. A bank may offer loans and accounts, just as a restaurant may offer food and drink. But durable loyalty comes from something more difficult to copy: a recognizable ritual that combines reliability with a sense of belonging.

The lesson is not that banks should imitate cafes. It is that both businesses show how resilience is built. The strongest institutions preserve a common core while allowing meaningful variation around it. They turn repeated transactions into habits, and habits into trust.

The crisis reveals what was actually valuable

The pandemic created a brutal test for retail banks. Consumer lending and deposit revenues came under pressure, while customers became more dependent on remote access and digital service. This produced a familiar executive response: accelerate digitization, redesign the customer journey, and move more of the bank’s operations into an integrated digital system.

That response is necessary, but it is not sufficient. Technology can make a service available. It does not automatically make the service meaningful.

A customer who opens an account through an app has completed a transaction. A customer who checks the app every morning, uses it to manage uncertainty, trusts its alerts, and turns to the bank when circumstances change has entered a relationship. The distinction matters because transactions are vulnerable to comparison. Relationships are more resistant to substitution.

A purely transactional bank competes on interest rates, fees, speed, and convenience. These are important, but competitors can often match them. A relationship bank competes on confidence: the feeling that the institution understands the customer’s situation and will behave predictably when life becomes unpredictable.

The pandemic therefore exposed a deeper weakness in many business models. Revenue streams were treated as if they were the institution itself. When lending slowed and deposit economics deteriorated, the question became how to replace lost income. The more important question was: what recurring human need can the institution organize itself around?

This is where the old neighborhood restaurant offers an unexpected clue.

The menu changes, but the ritual survives

The Irani restaurants of Mumbai were distinctive because each had a memorable specialty. One was associated with mini biscuits, another with a particular roll, another with tea cakes, and another with an enormous omelet. Their identities were not identical. In fact, their differences were part of their appeal.

But beneath that variety was a common ritual: bun maska and chai.

This combination did not erase the individuality of each restaurant. It created a shared grammar. Customers knew what kind of place they were entering, what basic experience to expect, and how the visit might fit into the day. The signature items gave each establishment character. The common ritual made the category legible and dependable.

That is a powerful design principle for any institution:

Standardize the ritual, not the entire experience.

A restaurant that sells only novelty becomes exhausting. A restaurant that offers only sameness becomes forgettable. The durable model is a stable center surrounded by distinctive choices.

Banks face the same tension. Their common ritual might include immediate visibility into money, reliable payments, transparent alerts, fast problem resolution, and a credible path to help during financial stress. These should work consistently for everyone. Around that core, the bank can provide specialized experiences for a young professional, a small business owner, a migrant worker, a family saving for education, or an older customer who still values human assistance.

The mistake is to confuse personalization with fragmentation. Personalization means changing the relevance of the experience while preserving confidence in the underlying system. Fragmentation means forcing every customer to learn a different institution.

A customer should not have to wonder whether a new feature is safe, whether a transfer has disappeared, or whether support will answer. The surface may vary. The promise must not.

Digital convenience is not the same as digital belonging

The phrase digital bank can conceal two very different ambitions.

The first is operational: digitize forms, automate decisions, reduce branch dependence, and make transactions faster. This lowers cost and improves access. It is the financial equivalent of putting a menu online and enabling delivery.

The second is relational: use digital infrastructure to become a more useful presence in the customer’s life. This requires a deeper redesign. The app must not merely display products. It must help customers interpret their financial reality.

Consider the difference between these two notifications:

“Your balance is low.”

“Your recurring bills are due in five days. Based on your usual income pattern, you may want to move money from savings or adjust this week’s discretionary spending.”

The first reports a condition. The second provides context and a possible action. One treats the user as an account holder. The other treats the user as a person managing a life.

This is where an integrated digital bank can become more than a cheaper distribution channel. It can create a financial ritual. A weekly money check in. A monthly cash flow review. A timely prompt before a predictable shortfall. A simple explanation of why a credit decision was made. A savings goal that feels visible and attainable.

These rituals matter because financial behavior is often less about knowledge than about cadence. People do not need a new lesson in compound interest every day. They need a dependable moment in which their attention returns to what matters.

The restaurant’s chai works in a similar way. It is not valuable because tea is rare. It is valuable because it marks a pause, a meeting, a beginning, or a return. Its meaning comes from repetition and context.

Banks should ask: what recurring moment do we own?

If the only answer is payday, the relationship is dangerously narrow. A bank that appears only when money arrives or a loan is requested is participating in events. A bank that helps customers prepare, decide, recover, and progress is participating in continuity.

The real product is confidence under changing conditions

A useful way to think about resilience is to separate an institution into three layers.

1. The invariant layer

This is the promise that must remain stable under pressure. For a bank, it includes security, accuracy, availability, fairness, and clear communication. If these fail, no amount of personalization can rescue the relationship.

2. The adaptive layer

This is the part that changes with the customer and the environment. Credit limits, repayment options, savings tools, communication channels, and guidance should respond to circumstances. During a crisis, the adaptive layer becomes especially important because yesterday’s assumptions no longer hold.

3. The expressive layer

This is how the institution feels and becomes memorable. It may include language, visual design, human support, educational content, community initiatives, or specialized products. This is where differentiation lives.

The Irani restaurant model works because these layers reinforce each other. The common experience provides continuity. The specialties provide identity. The setting turns a purchase into a place people remember.

In banking, the equivalent failure occurs when institutions invest heavily in the expressive layer while neglecting the invariant one. A beautifully designed app cannot compensate for unexplained fees or unreliable support. The opposite failure is equally common: a bank delivers technically dependable services but gives customers no reason to prefer it emotionally or habitually.

Resilience requires both trust and texture.

Trust answers the question, “Can I rely on this?” Texture answers, “Why does this feel like mine?”

This distinction also clarifies why consumer loans and deposits can become fragile revenue sources during disruption. Products are exposed to economic cycles. Relationships can absorb and redirect those cycles. A customer may borrow less, save differently, or need payment relief, but a trusted institution can remain useful by helping the customer navigate the change.

That does not eliminate financial risk. It changes the basis of endurance. The bank is no longer dependent on one product behaving normally. It is connected to the broader job of helping a customer manage money across changing conditions.

From product portfolio to ritual portfolio

Most banks organize strategy around products: current accounts, cards, deposits, mortgages, personal loans, wealth products, and insurance. This is convenient for internal reporting, but it reflects the bank’s structure rather than the customer’s life.

Customers do not experience “a product portfolio.” They experience moments: receiving income, paying rent, handling an emergency, planning a purchase, sending money to family, recovering from a shock, or trying to build a cushion.

A stronger strategic question is: which rituals and transitions can the bank support better than anyone else?

For example, a bank might build a “first salary” ritual for young customers. The experience could combine automatic allocation into savings, a clear explanation of deductions, a spending overview, and an invitation to set one realistic financial goal. The point is not to sell five products on the first day. The point is to establish a useful pattern of return.

For a small business, the ritual could be a weekly cash flow pulse. Instead of waiting for an overdraft request, the bank could show expected inflows, upcoming obligations, and a range of safe spending. For a household, it could provide a monthly planning moment that brings bills, savings, and debt into one understandable view.

Each of these experiences can include products. But the product becomes the ingredient, not the identity.

This shift has practical consequences for measurement. Product metrics such as accounts opened, loans issued, or deposits gathered still matter. Yet they should be complemented by ritual metrics:

• How often do customers return for a useful reason?
• Do they complete preventive actions before a financial problem occurs?
• How quickly do they seek help when circumstances change?
• Do they understand the institution’s guidance?
• Does the customer use more than one service because the services fit together, or because of aggressive cross selling?

The last question is particularly important. A relationship is not proven by the number of products a customer owns. It is proven when the institution becomes easier to rely on because its services form a coherent whole.

What leaders can build now

The broad lesson can be turned into a practical design exercise. Begin by identifying the institution’s equivalent of bun maska and chai: the small set of repeated experiences that should feel unmistakably dependable.

Do not start with a technology roadmap. Start with a customer rhythm. Observe what customers do before a payment, after a paycheck, during a cash shortfall, or when they receive an unexpected expense. Look for moments of uncertainty, not merely moments of transaction.

Then design around three questions:

1. What must never vary? Define the nonnegotiable promise, such as accurate balances, transparent explanations, secure access, and responsive recovery when something goes wrong.
2. Where should the experience vary? Use data and human judgment to adapt support, language, timing, and recommendations to the customer’s circumstances.
3. What will make the relationship memorable? Create a distinctive way of helping, whether through unusually clear financial guidance, exceptional support, or a ritual that customers look forward to.

The aim is not to make banking theatrical. It is to make it recognizably useful.

Key Takeaways

• Build around recurring moments, not isolated products. Identify when customers need confidence and guidance, then design a dependable experience around that moment.
• Protect the invariant core. Security, accuracy, transparency, and recovery must remain consistent even as products and interfaces change.
• Personalize the edges. Give different customers relevant tools and guidance without making the underlying institution feel inconsistent.
• Turn digital access into a cadence. Notifications, reviews, and prompts should help customers form useful financial habits, not simply increase app activity.
• Measure relationship quality. Track whether customers return for meaningful help, take preventive actions, and remain engaged during difficult conditions.

The institution people return to

The most resilient bank may not be the one with the most features. It may be the one that has identified a small set of human rituals and made them dependable, intelligent, and personal.

That is why the comparison with a neighborhood restaurant is more than a charming analogy. A memorable institution does not force customers to choose between consistency and individuality. It offers a familiar center, then gives people reasons to make the experience their own.

The future of retail banking will certainly involve better apps, automated decisions, and more integrated systems. But those are means, not the final advantage. The deeper advantage is becoming part of the customer’s rhythm before a crisis arrives, so that when conditions change, the institution is not merely available. It is trusted.

A bank should therefore stop asking only, “How do we digitize the transaction?” The more consequential question is this: what is our version of the daily cup of chai, the small dependable experience that turns a service into a place people return to?