Building Enduring Financial Products: The Bedrock Approach

Overview

Every product builder has experienced the same cycle: a promising idea gains traction quickly, only to fade into irrelevance within months. In the financial sector—where real money is at stake, user expectations are high, and competition is fierce—the temptation to pile on features can be overwhelming. But this feature-first mindset often leads to bloated, confusing products that users abandon. This guide presents a proven alternative: the Bedrock Approach, which focuses on identifying and perfecting the core element that delivers lasting value. You'll learn how to resist feature creep, navigate internal politics, and build products that truly stick.

Prerequisites

Before diving into the step-by-step process, ensure you have:

• Product management fundamentals – Familiarity with MVP, user stories, and iterative development.
• Understanding of financial products – Basic knowledge of retail banking, payments, or investment apps (e.g., current accounts, loan applications).
• Access to cross-functional stakeholders – Security, compliance, design, and engineering teams whose input will shape your decisions.
• Customer research data – User feedback, analytics, or journey maps to identify what truly matters to your audience.

Step 1: Identify Your Bedrock

The first and most critical step is to find your product's bedrock—the single core feature or service that provides the most consistent value to users. In retail banking, for example, the bedrock is often the everyday servicing journey: checking balances, viewing transactions, and managing payments. People open a current account rarely, but they interact with it daily. If that daily experience is broken, no amount of flashy extras will save you.

To identify your bedrock:

• Analyze usage patterns – Look at what users do repeatedly and what they complain about most when it's missing or glitchy.
• Interview customers – Ask: “What is the one thing our product must do well for you to keep using it?”
• Map the essential journey – Strip away every nice-to-have and ask, “If we could only deliver one thing, what would it be?”

Step 2: Build a Minimum Viable Product Around the Bedrock

Once you've identified the bedrock, build your Minimum Viable Product (MVP) around it. The MVP concept—popularized by Jason Fried in books like Getting Real and on the Rework podcast—is often misunderstood. It's not about releasing something half-baked; it's about delivering just enough value to keep users engaged without overcomplicating the system. The bedrock becomes your MVP's foundation.

Here's how to execute:

1. Define the one core workflow – For a banking app, this might be logging in, seeing balance, and making a transfer.
2. Eliminate all secondary features – Resist the temptation to add budgeting tools, savings goals, or investment dashboards in the first release.
3. Test rigorously – Ensure the bedrock workflow is rock-solid under load, secure, and intuitive.
4. Launch with clear messaging – Explain to users that this is version one, focused on what matters most.

Step 3: Resist Feature Creep and the Columbo Effect

The biggest challenge after launch is the relentless pressure to add features. This is what we call the Columbo Effect: there's always “just one more thing” someone wants to add—a new integration, a custom report, a niche use case. Succumbing to every request leads to a feature salad—a product that tries to be everything to everyone and ends up pleasing no one.

To defend your bedrock:

• Create a feature-budget – Allocate only a fixed percentage of each sprint to new features (e.g., 20%). The rest goes to improving the bedrock.
• Use a scoring system – Evaluate each request by its impact on the bedrock experience. If a feature detracts from core flows, reject it.
• Adopt a “no” culture – Empower product managers to say no politely but firmly, especially to powerful internal stakeholders.

Step 4: Test, Iterate, and Protect the Bedrock

Even after launch, your bedrock must evolve based on real-world feedback. But evolution should be focused and disciplined. Here's a continuous improvement loop:

1. Monitor key metrics – Track daily active usage of the bedrock feature, completion rates, and error rates.
2. Gather qualitative feedback – Run usability tests specifically on the core workflow. What's confusing? What's missing?
3. Iterate incrementally – Make small, data-driven tweaks. Avoid overhauling the entire bedrock at once.
4. Protect against internal politics – When departments push for their own features (e.g., marketing wants a promo banner, compliance wants a pop-up), remind them that the bedrock must remain clean. Use A/B testing to prove that adding clutter hurts engagement.

Common Mistakes

Mistake 1: Ignoring the Bedrock in Favor of Shiny Features

Many teams start by building the most exciting feature—like AI-driven financial advice—while neglecting essential flows like login or transaction history. This gives users a great first impression but a frustrating daily experience. Result: high churn.

Mistake 2: Letting Internal Politics Drive the Roadmap

When sales, marketing, and compliance each demand their own pet features, the product becomes a reflection of organizational infighting, not user needs. The bedrocks gets buried under conflicting priorities.

Mistake 3: Building an MVP That's Too Big

Some teams define their MVP as a full-fledged product with multiple features, thinking that's what “minimum” means. In reality, the minimum should be the absolute smallest set of features that delivers the core value—often just the bedrock itself.

Mistake 4: Failing to Resist the Columbo Effect

Even after defining the bedrock, product managers cave to “one more thing” requests without assessing the impact on complexity and maintenance. Over time, the bedrock erodes under the weight of extras.

Summary

Building products that stick—especially in the high-stakes world of finance—requires discipline. The bedrock approach forces you to identify, build, and protect the single most valuable element of your product. By starting with a tight MVP centered on that core, resisting feature creep (the Columbo Effect), and defending against internal politics, you create a product that users rely on daily rather than one they abandon after a few weeks. Remember: it's better to be great at one thing than mediocre at many.