Building Lasting Financial Products: The Bedrock Approach Beyond MVPs

In the fast-paced world of financial product development, many promising ideas skyrocket to success only to crash and burn within months. Why do so many apps and platforms fail to retain users? This Q&A explores the common pitfalls—like feature-first development, internal politics, and the Columbo Effect—and introduces the concept of 'bedrock' as the foundation for products that truly stick. Drawing from real-world retail banking experiences, we'll uncover how to build stable, user-focused solutions that survive the test of time.

What is the feature-first trap in financial product development?

The feature-first trap occurs when product teams prioritize adding new capabilities over solving core user needs. In financial products, where trust and reliability are paramount, this approach is particularly dangerous. Teams get excited by shiny new features—like budgeting tools or investment trackers—hoping each one will win user loyalty. But without a clear strategy, these features often conflict with security requirements, fail to gain traction, or create unforeseen complexity. For example, a banking app might add a peer-to-peer payment feature without considering fraud risks, leading to costly fixes later. The result is a bloated product that confuses users and drains resources. Instead of asking 'What more can we build?,' teams should ask 'What problem must we solve?' This shift in mindset helps avoid the feature-first trap and keeps the product focused on delivering real, sustainable value.

Building Lasting Financial Products: The Bedrock Approach Beyond MVPs

Why do promising financial products often fail after initial success?

Initial success can be deceptive. A product might gain traction through a well-timed launch or a unique feature, but sustaining that momentum requires more than novelty. Many financial products fail because they fall victim to what's known as the 'Columbo Effect'—the temptation to add 'just one more thing' to please stakeholders or users. Each addition increases complexity, making the product harder to maintain and less intuitive. Meanwhile, the original value proposition gets diluted. For instance, a popular budgeting app might add loan comparisons, credit score tracking, and investment tips, turning a simple tool into a confusing all-in-one platform. Users who loved the original simplicity abandon it. To avoid this fate, product builders must resist the urge to pile on features and instead double down on the core experience that made the product successful in the first place.

How does the Minimum Viable Product (MVP) concept apply to financial apps?

The MVP concept, popularized by Jason Fried in his book Getting Real, is about delivering just enough value to engage users without overcomplicating the product. In financial apps, this means focusing on one or two essential functions—such as secure login and transaction history—before adding extras. An MVP should solve a real pain point, like helping users track spending or automate savings, while avoiding unnecessary features that introduce risk or confusion. However, many finance teams misinterpret MVP as 'bare minimum' and release buggy or incomplete products. A true MVP is ruthlessly focused: it provides a stable, trustworthy foundation that can be iterated based on user feedback. For retail banking, the MVP might be a simple current account dashboard with real-time balance updates. Once users find value in that, additional features like bill pay or alerts can be layered in gradually.

What is a 'feature salad' and how do internal politics create it?

A 'feature salad' is a product overloaded with unrelated features that serve internal stakeholders rather than users. It happens when different departments—marketing, compliance, product, sales—each demand their own pet features. Instead of a coherent experience, users get a confusing mix of tools that don't work well together. For example, a mobile banking app might include a mortgage calculator, a rewards catalog, a stock trading window, and a chat bot—all because each team wanted to 'add value' without considering the bigger picture. This approach leads to bloated interfaces, longer load times, and frustrated customers who can't find basic functions. The solution is to create a unified product vision that prioritizes user needs over internal agendas. Product leaders must have the courage to say 'no' to requests that don't align with the core value proposition, even if they come from powerful internal voices.

What is the 'bedrock' concept and why is it crucial for sticky products?

Bedrock refers to the fundamental, unchanging component of a product that delivers consistent value to users. In financial products, bedrock is the stable foundation upon which all other features rest. It's the element that users rely on daily and that remains relevant even as trends change. For example, in retail banking, the bedrock is often the regular servicing journey—checking balances, reviewing transactions, and making payments. Users interact with these features daily, even if they only open a new account once. By focusing on perfecting the bedrock, product builders create a habit-forming experience that makes the product indispensable. Bedrock features are not flashy, but they are reliable and user-friendly. When a product has strong bedrock, users trust it, return to it often, and are more forgiving of imperfections elsewhere. Without bedrock, products feel fragile and easily replaced.

How can product builders identify the bedrock in retail banking?

In retail banking, the bedrock is typically the regular servicing journeys: actions customers perform most frequently, such as viewing account balances, checking recent transactions, making transfers, and receiving alerts. These tasks are not exciting, but they are essential. To identify bedrock, product builders should analyze usage data to find the highest-frequency user actions. They should also conduct user interviews to understand what bankers consider 'table stakes'—the features they would never switch banks for. Once identified, the team must optimize these journeys for speed, clarity, and reliability. For instance, simplifying the login process or showing the current balance on the home screen without extra clicks. By strengthening the bedrock, builders ensure that the product becomes a daily habit rather than a one-time tool. Neglecting bedrock in favor of fancy features leads to high churn rates, as users find better core experiences elsewhere.

What practical steps can teams take to shift from feature bloat to bedrock focus?

Shifting from feature bloat to bedrock focus requires a disciplined approach. First, conduct a product audit to identify features that are rarely used or complex to maintain—consider cutting or simplifying them. Second, define a clear product vision that prioritizes one primary user goal (e.g., 'help users track spending effortlessly'). Third, adopt a ruthless prioritization framework, such as scoring features by impact on bedrock vs. internal politics. Fourth, implement regular user testing to validate that new features don't undermine the core experience. Fifth, empower product managers to say 'no' to requests that don't align with bedrock, using data as a shield. Finally, celebrate small wins in improving bedrock features—such as reducing load times or increasing daily active usage. A culture that values depth over breadth creates products that stick. Remember, a stable, simple product that does one thing well will always outlast a complex feature salad.

Tags: