Designing a bank customers could trust to act on their behalf.

The assumption behind mobile banking is breaking

For decades, the mobile app has been the primary interface between a customer and their bank. AI assistants are now becoming more capable of interpreting information, making recommendations, coordinating actions, and resolving routine needs. At the same time, open banking and greater data portability make it easier for financial experiences to exist apart from the institutions holding the accounts.

Once a customer can ask any capable assistant—Can I afford this? Why did I spend so much last month? Move enough money to cover my bills. Find a better place for my savings.—the advantage of merely providing access to financial products begins to erode.

Move from features to beliefs

Future-state work can easily become a collection of plausible features: conversational interfaces, predictive insights, autonomous agents, personalized recommendations. Those ideas are easy to generate and difficult to argue with. The team needed something more durable.

I helped shift the conversation toward two explicit beliefs about the world around banking:

• Intelligence is ubiquitous. AI is becoming an ambient layer across operating systems, commerce, vehicles, communications, and everyday services. Customers will expect products to understand context and reduce manual work.
• Data is portable. Financial lives already cross institutional boundaries. Aggregation, APIs, and open banking make it easier to assemble a whole picture regardless of where the underlying accounts sit.

Together, those forces make trust more fragile and loyalty more fickle. When every system can recommend an action, customers have to decide whose intelligence serves their interests. When financial context moves easily, holding the accounts is no longer the same as holding the relationship.

The next generation of banking will compete for delegation

Most financial products are designed around engagement: open the app, check the balance, find the transaction, move the money, pay the bill. As intelligence improves, many of those interactions become unnecessary. The most valuable experience may be the one customers need to operate the least.

The next generation of banking will compete for delegation, not attention.

That conviction created a sharper design challenge: build an experience customers trust enough to understand their financial lives, anticipate what matters, recommend what to do next, and—when appropriate—act on their behalf. Delegation is granted by the customer. It is never assumed by the product.

Six principles for earning delegation

• Understand the whole financial picture. Design for the customer’s complete context, not only the products held with the bank.
• Make intelligence contextual. Recommendations should reflect goals, behaviors, obligations, preferences, and current circumstances.
• Move from tools to orchestration. Coordinate capabilities around the customer’s intended outcome.
• Make the system legible. Show what it knows, why it is recommending something, and what will happen before action is taken.
• Keep the customer in control. Let customers decide what the system may observe, recommend, prepare, execute, or automate.
• Prove value before asking for trust. Demonstrate competence, transparency, and alignment before seeking greater autonomy.

Structure the experience around intent

If banking is shifting from navigation to orchestration, adding AI features to the old information architecture is not enough. We explored six spaces, each organized around a customer question rather than an institutional product line:

• Home — What matters right now? A contextual view of priorities and emerging needs.
• Chat — What can I ask or accomplish? A conversational path to understand, decide, navigate, and act.
• Money — What do I have and how is it working? A comprehensive view across accounts, assets, liabilities, and institutions.
• Explore — What could improve my financial life? Relevant opportunities without turning the whole experience into a sales surface.
• Add — What can I bring into my financial world? Products, external accounts, and relationships that expand the system’s understanding.
• Profile — What does the system know about me? Identity, permissions, connected data, personalization, and delegation controls.

The result was more than a navigation model. It was an attempt to define the operating system of a future financial relationship.

Make the future tangible enough to debate

Strategy work fails when it stays abstract. I created and shaped strategic narratives, future-state concepts, interaction models, wireframes, high-fidelity explorations, prototypes, experience architecture, AI orchestration concepts, product principles, alignment workshops, and validation frameworks.

Each artifact had a different job. Some established conviction. Some exposed disagreement. Others revealed that a compelling idea rested on an assumption nobody had validated. The design work functioned less as visualization and more as a decision-making tool.

Turn ambiguity into a progression

Astro operated across several layers of the organization, and each wanted something different: a bold vision, product concepts, proof, or connection to work already underway. Without a shared frame, the project risked changing direction based on whoever spoke last.

• Understand the changing environment.
• Form strategic convictions.
• Translate those convictions into experience principles.
• Make the principles tangible through design.
• Name the assumptions embedded in the vision.
• Validate the assumptions most likely to change the direction.

That progression gave the team a shared language for distinguishing what we believed, what we had designed, and what we still needed to learn.

The app becomes a command center

Astro proposed a different purpose for the mobile banking app. Rather than acting mainly as a destination for manual tasks, it becomes the visible control surface for an intelligent financial system that observes, interprets, advises, coordinates, acts, and learns—with customer permission at every step.

The app does not disappear. Its purpose changes: less a remote control for bank products, more a command center for the customer’s financial life.

Impact

Project Astro gave the organization a more coherent way to discuss the future of mobile banking. Teams could evaluate concepts against a shared view of the changing competitive environment, rising customer expectations, the institution’s potential role, the boundaries of AI, and what customers would need before trusting greater autonomy.

The work turned an ambiguous exploration into a strategic narrative, experience hypothesis, design system, and validation path. Its goal was not to predict exactly what banking would look like in 2030, but to establish a point of view strong enough to test.

If intelligence becomes ubiquitous and financial data increasingly portable, the institutions that win will be those customers trust enough to delegate to.

My role

As Design Lead, I worked across strategy, storytelling, product definition, and experience design. My contribution was connecting three levels that are often separated: macro change, business strategy, and the experience customers would actually see and use.

The work was not simply about imagining a future interface. It was about making a possible future specific enough to debate, tangible enough to experience, and structured enough to act on.