Building Lasting Financial Products: The MVP-Bedrock Approach

Overview

Every product builder has witnessed the tragic arc: a promising idea rockets from zero to hero in weeks, only to crash and burn within months. In the high-stakes world of financial products—where real money, high user expectations, and crowded markets converge—the temptation to throw features at the wall is strong. But this feature-first development approach is a recipe for disaster. It leads to bloated, confusing experiences that satisfy internal politics rather than customer needs. This tutorial introduces a structured method to build products that stick: the MVP-Bedrock approach. You'll learn how to identify the core value (bedrock), define a minimal viable product around it, and resist feature creep, ensuring your product remains stable, user-friendly, and loved over the long term.

Prerequisites

To get the most from this guide, you should have:

• Basic understanding of product development lifecycle.
• Familiarity with Minimum Viable Product (MVP) concepts.
• Some experience in the financial domain (though principles apply broadly).
• A willingness to challenge internal pressures and put customer value first.

Step‑by‑Step Instructions

Step 1: Identify the Bedrock

Bedrock is the core element of your product that truly matters to users—the fundamental building block that provides lasting value. In retail banking, for example, bedrock often revolves around regular servicing journeys: customers open a current account once in a blue moon but interact with it daily. Focus on what people do repeatedly, not what they sign up for once.

Action: List all possible user tasks. Circle the ones that are performed at least weekly and solve a real pain point. Those are your bedrock candidates. Validate with user research or analytics.

Step 2: Define Your MVP Around the Bedrock

Once you have the bedrock, design a Minimum Viable Product that delivers just enough value to keep users engaged while avoiding complexity. The MVP should include only the bedrock feature and absolutely essential supporting functions. Everything else is deferred.

Example (pseudo‑code for feature prioritization):

bedrock_features = ["transaction_history", "balance_check"]
mvp_features = bedrock_features + ["login", "logout", "error_handling"]
# All other features (e.g., budget tools, investment recommendations) are post‑MVP

Document this in a prioritization matrix. Ruthlessly cut anything that doesn't directly serve the bedrock.

Step 3: Resist the “Columbo Effect”

Jason Fried’s Getting Real and Rework often highlight the danger of “just one more thing.” This Columbo Effect—always adding one more feature—destroys products. Equip your team with a clear product vision and a decision framework (e.g., “Does this feature directly support the bedrock? If not, it’s out.”).

Technique: Create a feature veto rule: any new feature must be approved by a product council that checks alignment with bedrock. If the feature doesn’t pass, it’s postponed for at least two release cycles.

Step 4: Test and Iterate with Real Users

Ship the MVP to a small group of real customers (a beta or early access program). Monitor usage: Is the bedrock feature being used daily? Are users hitting unexpected friction? Gather feedback only about the bedrock and blocker issues—ignore suggestions for new features during this phase.

Metrics to track: Daily active users (DAU) on bedrock actions, task completion rate, time to value. Set a target: e.g., 80% of users complete a balance check within 3 taps. Iterate on performance and usability, not feature count.

Step 5: Scale While Protecting the Bedrock

As you gain traction, start adding secondary features—but only those that strengthen the bedrock experience. For instance, if your bedrock is transaction history, then adding a search or filter feature is a logical expansion. Avoid unrelated “feature salads” that reflect internal department rivalries.

Guard against internal politics: Every feature request must include a user story explicitly linking to bedrock. If the security team demands a multi‑factor authentication (MFA) flow, accept it as a necessary enabler for trust—but don’t let it bloat the core experience. Keep the user journey lean.

Common Mistakes

• Building a Feature Salad: Adding features to satisfy internal departments rather than customer needs. Your product becomes a confusing mix of unrelated functionalities.
• Ignoring Security as a Bedrock Enabler: Security teams (the “narcs”) may block features. Instead of fighting them, incorporate security early as part of the bedrock experience—users trust your product because it’s secure.
• Falling for the Columbo Effect: Continuously adding “just one more thing” delays launch and dilutes value. Stick to your MVP and use data to justify additions.
• Over‑Engineering the MVP: Trying to build a perfect first release. The MVP should be viable, not polished. Release early, learn, and iterate.
• Neglecting User Research on Bedrock: Assuming you know what customers do daily without validation. Real usage data may surprise you.

Summary

The MVP‑Bedrock approach transforms product development from a chaotic feature race into a disciplined, user‑centered process. Identify the core value users return to again and again (the bedrock), build a minimal version around it, resist the urge to add noise, and iterate based on real usage. This method combats feature bloat, internal politics, and early burnout, creating products that not only launch but stick for years. In financial products, where trust is everything, a stable, focused experience wins over a flashy, complicated one.