In Banking, the Customer Journey Is the Product

4 MINS

In most consumer products, the customer journey is the path *to* the product. In banking, the journey is the product. There is nothing else for the customer to hold or experience — no box, no garnish, no app screen they fall in love with. There's just the moment they got their card unblocked, or didn't.

Why that distinction matters

I worked on Customer Care Agent Desktop modernisation at JPMorgan Chase, voice biometrics, OTP rollouts, IVR redesigns at Barclays. None of those projects were "exciting" in the consumer-product sense. None of them generated TechCrunch headlines.

But every single one of them was the single most important product moment of the customer's day. The card got unblocked. The fraud got resolved. The KYC got accepted. To the customer, that *is* the bank.

If you're a product manager in financial services and you're chasing the dashboard the customer logs into twice a year, you're optimising the wrong surface.

Where the journey breaks (and why)

Almost every banking journey breaks at the same three places:

The handoff — between channels, between systems, between agents and self-service

The wait — the silent gap between "your request has been received" and any sign of progress

The exception — the case the form didn't anticipate These are not engineering bugs. They're product gaps. The system is doing what the spec said. The spec just didn't capture what the customer actually needed. Voice biometrics worked at JPMorgan Chase because we didn't ship "a new authentication option". We shipped a way to **eliminate the most painful handoff** — the one where the customer has to repeat themselves to the agent who already had their account open. The technology was the easy part.

How I do journey mapping that doesn't get ignored

I've sat through a lot of journey-mapping workshops where the deliverable was a beautiful Miro board that nobody looked at again. Here's what I do differently now:

Map the journey with the agents handling the calls , not just with stakeholders. They know the broken bits.

Map the journey at the worst moment , not the happy path. If the journey works when fraud is suspected, it works always.

Tie every step to a system, an SLA, and a fallback. A journey without a fallback is fiction. After that, the map becomes a tool, not a poster. You can point at it in every standup, every escalation, every backlog grooming.

What AI changes here

The Agentic AI work I'm doing now is, fundamentally, a journey-orchestration tool wearing AI clothes. The agent's job is to make the journey shorter, the handoffs invisible, and the exceptions handleable.

If the agent doesn't reduce the customer's effort, it's a tech demo. If it does, it becomes the product — because in banking, the journey *is* the product, and the agent is now part of the journey.

That's the bar I hold every AI feature to. Not "is it smart?" — but "does the customer's day end better than it started?"

Waterfall-to-Agile Was the Easy Part. Agile-to-AI Is the Real Test.

Komal skipped presentations and built real AI products.

Komal Sikka was part of the March 2026 cohort at Curious PM, alongside 17 other talented participants.