DBS Bank Customer Experience: How 'Live More, Bank Less' Works

Most banks want you to spend more time in the app. DBS wants you to spend less. That single inversion — stated plainly in the bank's own brand promise, "Live more, Bank less," and its stated ambition to "make banking joyful" — is the clearest piece of customer-experience strategy to come out of Asian banking in a decade, and almost nobody outside Singapore has unpacked why it works.

The thesis is simple and slightly uncomfortable for an industry addicted to engagement metrics: DBS built its experience strategy around subtraction, not addition. Instead of asking "how do we get customers to interact with us more," Singapore's largest bank asked "how do we get out of the way of their lives." That is a fundamentally different design brief, and it changes everything downstream — the architecture of the app, the way friction is treated, and what "success" even means for a product team.

What is DBS's customer experience strategy actually built on?

DBS's experience strategy rests on two public commitments: the brand promise "Live more, Bank less" and a corporate vision to "make banking joyful." Together they reframe banking from a destination customers should want to visit into a background utility customers should barely notice. The bank is explicit that the goal is not more banking — it is less friction standing between a customer and the rest of their life.

That reframing matters because most financial institutions still measure experience the way they measure a retail app: sessions, time-on-app, click-through. A bank chasing "Live more, Bank less" cannot use those metrics without contradicting its own promise. If customers are genuinely banking less — because transfers clear instantly, because a loan pre-approval needed no branch visit, because a card dispute resolved itself — then falling engagement is the win condition, not the warning sign.

Why would a bank deliberately want customers to use it less?

Because attention is not loyalty in financial services the way it is in media or retail. Nobody opens a banking app for pleasure the way they open a shopping app for a browse. Every unscheduled visit to a bank app is, more often than not, a symptom of something going wrong — a failed payment, a confusing statement, a card that will not authorise. Treating "more usage" as success in this category rewards the wrong behaviour: it quietly incentivises making self-service harder, not easier, because friction manufactures the very engagement the dashboard celebrates.

Richard Thaler, the Nobel laureate behind modern nudge theory, drew exactly this distinction when he coined the term "sludge" — friction deliberately or carelessly left in a process that should be effortless. In his 2018 piece in the journal Science, Thaler argued that organisations should be judged not only on the nudges they add but on the sludge they fail to remove. A bank that measures itself by how long customers linger in its app is, structurally, rewarding sludge. "Live more, Bank less" is a promise that inverts that incentive at the level of corporate strategy, not just UX copy.

How does "making banking joyful" show up in practice?

Joy, in a banking context, rarely means delight in the consumer sense — confetti animations and cheerful microcopy. It more often means the quiet absence of dread. DBS's own public materials frame the ambition around making banking seamless: embedding financial tasks into the moments customers already have, rather than forcing them into a separate banking occasion. The underlying design logic is contextual banking — money management that shows up inside the task a person is already doing, instead of demanding they open a dedicated channel and start from zero.

This is where the behavioural economics gets interesting. Daniel Kahneman's peak-end rule — demonstrated in his 1993 study with Barbara Fredrickson, Charles Schreiber and Donald Redelmeier, published in Psychological Science, which showed that people judge an experience largely by its most intense moment and its ending rather than its average — explains why a single bad resolution can undo months of smooth transactions. A customer who successfully pays bills for a year but is made to fax a form to dispute one transaction will remember the fax. Designing for "joy" is, in practice, designing for the handful of emotionally charged moments — a disputed charge, a lost card, a first mortgage — where the ending of the interaction carries disproportionate weight in how the whole relationship gets remembered.

The affect heuristic reinforces the same point from a different angle: people make judgements about risk and trust based on how a decision feels in the moment, not on a cool calculation of the facts. A loan process that feels anxious — ambiguous timelines, unexplained holds, silence after submission — generates distrust even when the eventual outcome is favourable. A bank chasing joy has to design the feeling of the journey, not just its endpoint.

What does "less banking" demand from the back office?

A promise like "Live more, Bank less" cannot be delivered by the front-end app alone. It is, by necessity, an operating-model statement before it is an interface statement. Every manual approval step, every departmental handoff, every policy requiring a customer to re-prove something the bank already knows becomes a direct violation of the brand promise. This is the uncomfortable truth most CX teams discover too late: you cannot design a frictionless front door onto a building full of friction-generating back rooms.

That is why a strategy like this has to be read as an organisational transformation effort as much as a design one. Removing sludge from a claims process, a card-replacement workflow, or a mortgage pre-approval usually means redrawing the service blueprint, renegotiating ownership between departments, and in many cases retraining or restructuring the teams who currently "own" the friction because it protects their function from risk. Renascence's work in service design consistently finds the same pattern across industries: the friction customers feel is rarely a UX failure. It is an operating-model decision that nobody has revisited since it was made.

Where do most banks get this wrong?

Most banks pursue the opposite instinct. Faced with declining branch footfall, many financial institutions respond by trying to manufacture digital engagement — gamified savings challenges, push notifications, loyalty points for logging in. These tactics borrow retail and gaming mechanics wholesale, without asking whether more time in a banking app is actually a value exchange the customer wants.

• Confusing activity with value. A spike in app opens caused by a confusing new fee structure looks identical, on a dashboard, to a spike caused by a popular new feature. Without qualitative context, engagement metrics reward both equally.
• Treating every touchpoint the same. Not every interaction carries equal emotional weight. A balance check and a fraud dispute are both "sessions," but only one of them determines whether the customer trusts the institution with their income.
• Outsourcing friction to the customer. Document re-uploads, repeated identity checks, and "please call us" dead-ends shift the bank's operational cost onto the customer's time — a classic case of sludge disguised as due diligence.
• Optimising the app while ignoring the policy layer. A beautifully designed interface sitting on top of a 1990s-era approval workflow still produces a slow, frustrating outcome — just with better typography.

The common thread is a failure to separate necessary friction — the kind that protects the customer, such as fraud checks — from unnecessary friction, the sludge that exists only because nobody has been tasked with removing it. A bank that cannot make that distinction will keep adding "engagement features" to disguise a process that should simply be shorter.

How can other CX leaders apply the "subtraction" principle?

The DBS approach generalises well beyond banking, because the underlying discipline — subtract friction before you add features — applies to any regulated, high-stakes service category: insurance, healthcare, telecoms, government services. Leaders looking to borrow the logic can follow a structured sequence rather than trying to copy the interface.

1. Map the journey as it is actually lived, not as the org chart describes it. Most friction hides at the handoffs between departments — the moment a mortgage application leaves "digital" and enters "credit risk." A proper journey mapping exercise exposes these seams rather than the single-department view most teams default to.
2. Separate protective friction from sludge. For every step that slows a customer down, ask explicitly who it protects. If the honest answer is "the department, not the customer," it is a candidate for removal.
3. Redefine the success metric before redesigning the interface. If the goal is genuinely "less banking," then declining app sessions on routine tasks should be treated as evidence of success, while time-to-resolution on service issues should be the metric under pressure.
4. Design the ending of every high-stakes journey deliberately. Apply the peak-end rule on purpose: a loan approval, a dispute resolution, or an account closure should end on the clearest, calmest note the process allows, because that moment disproportionately shapes how the whole relationship is remembered.
5. Push the fix upstream into policy and process, not just screens. A redesigned form on top of an unchanged approval chain still produces the old outcome. Structural friction requires structural change management, not a visual refresh.
6. Re-test with real customers, not internal stakeholders. Internal teams are the worst judges of whether a process feels effortless, because they already know how to navigate it. Independent evaluation — the kind delivered through mystery shopping or structured customer feedback — catches the friction employees have stopped noticing.

None of these steps require a bank the size of DBS. They require the discipline to treat friction removal as a strategic metric, not a backlog item that loses every prioritisation fight to a new feature.

What's the behavioural lesson behind "Live more, Bank less"?

The deeper lesson is about where trust actually gets built in financial services. Trust is not won in the moments a customer chooses to engage — it is won, or lost, in the moments they are forced to. A promotional email is optional; a card dispute is not. Loss aversion, the behavioural tendency identified by Daniel Kahneman and Amos Tversky in their foundational prospect theory work, means customers weigh the pain of a bad service experience roughly twice as heavily as the pleasure of a good one. A bank obsessed with adding delightful features while leaving its complaints process slow is optimising the wrong side of that asymmetry.

Removing friction a customer never notices is worth more to loyalty than adding a feature they rarely use — because the absence of pain compounds, and the presence of a feature usually doesn't.

This is the uncomfortable discipline "Live more, Bank less" imposes on an organisation: it forces leadership to resist the temptation to prove value through visible additions, and instead prove it through invisible subtractions that are much harder to put in a quarterly deck. That is precisely why so few institutions attempt it, and why it is such a durable differentiator when one does.

Other regional banks have taken different routes to building loyalty and trust — some through tiered rewards, some through community-anchored service models. It is worth comparing approaches: Al Rajhi Bank's loyalty model and First Abu Dhabi Bank's experience strategy both show that there is more than one valid path to earning a customer's trust in banking, even if the underlying behavioural mechanics — loss aversion, friction cost, the weight of endings — remain constant across markets.

The closing argument: design for absence, not attention

Most experience strategies are written as a list of things to add: a feature, a reward, a touchpoint, a notification. DBS's brand promise does the opposite — it commits the organisation, publicly and permanently, to being noticed less. That is a harder metric to hit than engagement, and a far more durable one to defend, because a customer who forgets they have a bank — in the sense that nothing ever goes wrong enough to think about it — is the closest thing financial services has to true loyalty.

The institutions that will win the next decade of banking experience are unlikely to be the ones with the loudest app. They will be the ones customers can genuinely forget about, right up until the one moment it matters — and that moment, handled well, is the whole relationship.

If your organisation is still measuring experience by how much attention it captures rather than how much friction it removes, that gap is worth quantifying before it becomes a loyalty problem. Renascence's customer experience and behavioural economics teams work with banks across the region to find exactly where protective friction ends and costly sludge begins — and to build the operating model, not just the interface, that makes "less" genuinely possible.