In the fast-paced world of product development, especially within the financial sector, many promising ideas skyrocket from zero to hero in just a few weeks—only to crash and burn months later. Why? Because building a product that truly sticks requires more than just adding features. It demands a clear focus on what matters most to users and a ruthless pursuit of core value. This Q&A dives into the common pitfalls, the power of the Minimum Viable Product (MVP), and the crucial concept of 'bedrock' that ensures your product remains stable, useful, and loved over time.

Why do so many promising financial products fail shortly after launch?

Many products fail because teams fall into the feature-first development trap. Instead of solving a specific user problem, they get caught up in adding as many features as possible, hoping something sticks. In finance, where real money is at stake and users have high expectations, this approach is dangerous. Features often break under complexity, face pushback from security teams (the 'narcs'), or simply don't resonate with customers. The result? A bloated, confusing experience—what some call a feature salad. Products also suffer when they reflect internal politics rather than user needs. Different departments fight for their own priorities, diluting the core value. Without a clear, unwavering focus, products become unstable and unlovable, leading to rapid user drop-off.

What is a Minimum Viable Product (MVP) and why is it critical for financial apps?

An MVP is the simplest version of your product that delivers enough value to keep early users engaged, without overcomplicating development or maintenance. As Jason Fried emphasizes in Getting Real and his Rework podcast, an MVP requires a razor-sharp eye and the courage to say no to extra features. In financial apps, an MVP might focus on a single, essential service—like easy balance checking or instant transfers—rather than a full suite of tools. This approach prevents the Columbo effect (always adding 'just one more thing'), which leads to feature creep. By launching a lean product, you test real user demand early, gather feedback, and iterate intelligently. It’s far better to have a small, perfect feature that users love than a massive, clunky app they abandon.

What is the 'Columbo Effect' and how does it derail product development?

The Columbo Effect refers to the temptation to keep adding features—'just one more thing'—until the product becomes bloated and unfocused. Named after the detective who always had one more question, this mindset is seductive. Teams think each new feature will be the one that wins users over, but in reality, it often muddies the value proposition. For financial products, the stakes are higher: extra features can introduce security risks, raise complexity, and confuse users. A classic example is when product managers or stakeholders demand additions that cater to internal departments rather than external users. The Columbo Effect creates a feature salad that no one asked for, turning a potentially great product into a mediocre mess. Resisting it requires discipline and a clear vision of what the product’s bedrock should be.

How do internal politics create a 'feature salad' in financial products?

When building financial apps, internal politics often steer the product in conflicting directions. Different departments—like compliance, marketing, and operations—each push for features that serve their own goals. Compliance wants robust reporting, marketing wants flashy front-end widgets, and operations demands efficiency tools. These competing priorities result in a product that tries to please everyone but satisfies no one. The user experience becomes a confusing mix of unrelated functions, a feature salad. Instead of a clear, intuitive journey, users face a cluttered interface with no coherent value. For example, a banking app might have a dozen loan calculators, multiple savings trackers, and buried settings—all because different teams insisted on their own pet features. The customer loses sight of the product’s main purpose, leading to low engagement and high churn.

What is 'bedrock' in product design and why does it matter?

Bedrock is the core element of your product that delivers the most value and remains relevant over time—the fundamental reason users keep coming back. In retail banking, bedrock often revolves around regular servicing journeys: checking balances, viewing transactions, or transferring money. These are actions users perform daily or weekly, not just once in a blue moon. By identifying and perfecting your product’s bedrock, you ensure stability and user loyalty. Instead of chasing every new feature trend, you invest in what truly matters. Bedrock acts as the foundation; without it, additional features become unstable add-ons. Products that focus on their bedrock are easier to maintain, less prone to bloat, and more likely to stick in users’ lives. As the original text notes, people open a current account rarely but look at it every day—that daily touchpoint is bedrock.

Can you give a concrete example of bedrock in retail banking?

Absolutely. In retail banking, the bedrock for most users is the current account servicing journey. People may sign up for a new account only once every few years, but they check their balance, review statements, and make transfers almost daily. If you build a banking app that nails these daily tasks—fast loading, intuitive navigation, quick insights into spending—users will stick with it. Now, imagine adding exotic features like crypto trading or complex budgeting tools before the core experience is solid. Users will get frustrated by a sluggish balance check or a confusing transaction history. The bedrock approach means you prioritize the essential, high-frequency actions. Make them flawless. Only then consider adding complementary features. This is how big fintech apps succeed: they ensure the basics are so good that users don’t bother switching to competitors, even if those competitors offer more bells and whistles.

How can product teams avoid the feature-first trap and build products that stick?

To escape the feature-first mindset, teams must adopt a bedrock-first strategy. Start by identifying the single most important user need your product addresses—its core value. Then, build the simplest version (MVP) to fulfill that need, and resist adding anything else until you have validated that the core works. Use tools like user research, A/B testing, and direct feedback to understand what users truly rely on. Ruthlessly deprioritize requests that don’t serve the bedrock, even if they come from powerful stakeholders. Create a clear product vision that everyone understands, and use it as a filter. For financial products, also consider security and compliance as part of the bedrock—not as afterthoughts. Finally, measure success not by number of features launched, but by user retention and satisfaction on core journeys. This disciplined approach ensures your product becomes stable, loved, and long-lasting.