From MVP to Bedrock: Building Financial Products That Last

Building financial products that truly resonate with users is no easy feat. Many promising ideas skyrocket in popularity only to fizzle out within months. The key to longevity lies not in piling on features, but in identifying and perfecting a core value—what we call the 'bedrock.' This Q&A explores common pitfalls, the MVP approach, and how to create products that stick.

What's the biggest mistake product builders make with financial apps?

The most common error is prioritizing features over user needs. In the rush to compete, teams often add every possible functionality, hoping something will resonate. This 'feature-first' mindset leads to bloated, confusing interfaces that overwhelm users. In financial apps, where trust and clarity are paramount, this approach is especially damaging. Users want simplicity, not a Swiss Army knife of options. Instead of asking 'What else can we add?,' successful builders ask 'What can we remove?' Focus on the one thing your product does exceptionally well, and resist the urge to cater to every internal department's wishlist.

Why does adding more features often backfire?

Every new feature increases complexity—both for developers and users. Hidden costs include longer load times, higher bug rates, and a steeper learning curve. In financial products, this can erode trust when security teams (the 'narcs') reject a feature late in development, or when a popular addition breaks under unforeseen complexity. Moreover, users rarely need 50 features; they need three reliable ones. The 'Columbo Effect'—the temptation to add 'just one more thing'—plagues product teams. What starts as a focused app becomes a confusing mess, leading to low retention and high churn.

How does the Minimum Viable Product (MVP) approach help?

An MVP delivers just enough value to keep users engaged without overwhelming them or the development team. As Jason Fried advocates in Getting Real, it's about building the smallest possible version that solves a core problem. For financial products, that might be a simple savings tracker or a seamless money transfer. The trick is having the courage to say no to non-essential features. An MVP lets you test assumptions, gather real feedback, and iterate quickly. It prevents wasted resources on features nobody wants and ensures your product evolves based on actual user behavior, not internal politics.

What is the 'feature salad' and why is it harmful?

'Feature salad' describes a product that tries to be everything to everyone—a jumble of unrelated functions resulting from competing internal department demands. Marketing wants a referral bonus. Compliance needs a disclosure tool. Engineering adds a chatbot. The result is a disjointed experience where users feel lost. In finance, this is especially dangerous: a confusing interface can lead to errors with real money. Products become 'unlovable' because they lack a clear identity. The fix is to ruthlessly prioritize based on user research, not internal politics, and to ensure every feature aligns with a single, strong value proposition.

How do internal politics ruin user experience?

When product decisions are driven by the needs of departments rather than users, the app becomes a political compromise. For example, security may insist on multi-step verification that frustrates users, while marketing demands flashy animations that slow performance. Each internal stakeholder fights for their pet feature, and the product manager ends up with a Frankenstein’s monster. Users detect this lack of focus—they see a tool built for corporate convenience, not for them. To create a product that sticks, you must insulate the design process from internal bargaining. Let user data and clear business goals guide every decision.

What is 'bedrock' and how does it create sticky products?

'Bedrock' is the core feature or journey that provides lasting value to users. For retail banking, this might be the regular account servicing experience—checking balances, paying bills, tracking transactions. People don't open new accounts often, but they interact with these basics daily. A strong bedrock means perfecting these fundamental flows before adding advanced features. When the bedrock is solid, users form habits and trust. They keep coming back because the product reliably solves their most frequent needs. To find your bedrock, ask: What is the one thing users do most often? Make that flawless. Everything else is secondary.