Building Products That Last: The Bedrock Approach over Feature Overload

Building a product that truly sticks with users is a challenge many teams face. In the financial sector, where trust and reliability are paramount, the temptation to add endless features often leads to bloated, confusing experiences. This Q&A explores why many products fizzle out and introduces the concept of 'bedrock'—the core value that keeps users coming back. Drawing from real-world banking examples, we'll dive into strategies for creating stable, user-friendly products that endure.

1. Why do so many promising products fail to gain lasting traction?

Often, the downfall begins with a rush to add features. Teams get excited about solving every possible user problem, leading to a cluttered product that lacks a clear identity. In financial apps, this can result in a confusing mix of services that tries to please everyone but satisfies no one. Additionally, internal politics within organizations can push teams to prioritize department goals over user needs. The product becomes a reflection of corporate battles rather than a tool for customers. Without a clear, unwavering core value, users quickly lose interest and move on to simpler, more focused alternatives.

2. What is the feature-first development trap, and how does it hurt products?

The feature-first approach means building every idea that comes to mind, hoping something will resonate. This often leads to 'feature salad'—a mix of unrelated functionalities that overwhelm users. For example, a banking app might add budgeting tools, investment tracking, and payment reminders all at once, but none are executed well. The result is high complexity, low usability, and difficult maintenance. Security teams may block features due to risks, and user adoption remains low because the product tries to do too much. This approach wastes resources and dilutes the product's core promise.

3. How does the Minimum Viable Product (MVP) philosophy counter feature bloat?

An MVP focuses on delivering just enough value to solve a core problem for early users. Instead of building everything at once, you identify the one thing that matters most and perfect it. This requires discipline—saying no to 'just one more' feature, a tendency known as the Columbo Effect. By starting small, you can test assumptions, gather feedback, and iterate. In financial products, an MVP might be a simple, reliable transaction history view rather than a full analytics suite. The key is to prioritize user engagement over feature quantity, ensuring the product is stable and lovable from day one.

4. What is the 'Columbo Effect' in product development?

Named after the detective who always had 'one more question,' the Columbo Effect describes the irresistible urge to add just one more feature before launch. Stakeholders, team members, or even your own instincts push for that extra element, claiming it will make the product perfect. However, this mindset is dangerous—it delays release, increases complexity, and often derails the original vision. Especially in financial apps, where regulatory and security reviews add time, each extra feature multiplies risk. Resisting the Columbo Effect requires courage and a clear understanding of what users truly need versus what is nice to have.

5. Why do financial apps often become 'feature salads'?

Financial apps frequently suffer from internal politics. Different departments—marketing, compliance, product, engineering—each push for features that serve their own goals. The result is a product that tries to be everything to everyone: a savings account with investment options, credit scores, and bill pay all in one. This 'salad' lacks a cohesive vision. Customer experience suffers because the product is confusing and hard to navigate. Instead of a clear value proposition, users face a hodgepodge of tools. The solution is to align the team around a single, customer-validated bedrock feature that drives retention and satisfaction.

6. What is 'bedrock' in product development, and why is it crucial?

Bedrock is the core feature or functionality that provides lasting value to users. It's the fundamental reason people keep using your product over time. For retail banking apps, bedrock often revolves around regular servicing journeys—like checking balances, viewing transactions, or making transfers. These are daily actions that build habit and trust. By identifying and perfecting your bedrock, you create a stable foundation that resists the temptation of feature creep. Bedrock ensures your product remains focused, reliable, and beloved, even as you add complementary features later. It's the opposite of a feature salad: a simple, strong core that users can't live without.

7. How can you identify the bedrock for your financial product?

Start by analyzing user behavior and feedback to find the action they perform most frequently or the problem they complain about most. In banking, this is often the current account—opened rarely but checked daily. Look for the journey that, if removed, would cause the most frustration. Then, simplify that journey to its essence: remove friction, ensure speed, and make it intuitive. Avoid adding unrelated features during this phase. Validate with user testing and metrics like retention and daily active usage. Bedrock is not about what executives think is cool; it's about what customers rely on. Once found, protect it fiercely from feature bloat and internal politics.