Why Most Banking Apps Feel Like Tax Software
Every few years someone publishes a piece about how banking apps have finally gotten good. Then you try to dispute a charge on your Chase app and find yourself four screens deep in a menu tree that appears to have been organized by a committee that has never met a user.
The bad UX of traditional bank apps isn’t a mystery. It’s a direct consequence of how large financial institutions are structured.
The org chart is the product
Most traditional bank apps are assembled from components built by different internal teams, each with their own roadmap, their own technology stack, and their own definition of what “done” means. The checking account experience was built by one group. Bill pay was built by another. Zelle integration came from a partnership. The investment account was acquired. Mortgage was an afterthought.
What you experience as an app is actually a thin shell around this fragmented reality. The navigation doesn’t make sense because the underlying systems don’t share a coherent data model — and the team that owns the app is usually not the team that owns the underlying features.
The interface reveals the org chart. Bad coherence in the product usually means bad coherence in the organization.
This is Conway’s Law applied to consumer banking. The structure of the communication will mirror the structure of the organization that produced it.
Why neobanks solve (some of) this
Chime, Ally, and similar neobanks have better UX not primarily because they’re younger or more design-forward (though both help) — it’s because they started with a simpler product scope and a unified codebase. When your app only does checking, savings, and debit, you can make those three things excellent. You haven’t inherited three decades of product additions that each own their own corner of the app.
The limitation is the reverse of the advantage. When you need something more complex — a mortgage, estate planning, a commercial line of credit — the neobank’s product gaps open up fast.
The slow improvement path
Traditional banks know this. The ones that are serious about it have been running multi-year “platform modernization” programs — essentially trying to migrate from the fragmented reality to something unified. These programs are expensive, slow, and frequently fail, because the organizational transformation required is harder than the technical transformation.
The apps will get better. They’ll probably get good at roughly the pace of the underlying organizational change, which is to say: slowly, unevenly, and with certain corners remaining stubbornly bad for longer than seems reasonable.
That’s not pessimism — it’s just a realistic read of what the improvement path actually requires.