Building Rock-Solid Products: From MVP to Bedrock

Overview

Every product builder knows the heartbreak of a launch that soars for weeks only to fizzle into obscurity. In the financial sector—where real money, high user expectations, and fierce competition converge—the temptation to solve every problem with a new feature is especially strong. But this scatter-shot approach often yields a confusing, bloated experience and a product that fails to stick. This guide walks you through a proven alternative: building around a core bedrock value, using a disciplined Minimum Viable Product (MVP) strategy inspired by thinkers like Jason Fried. You will learn how to identify your product's fundamental building block, ship a focused offering, avoid common pitfalls, and create something users genuinely love—and keep using.

Prerequisites

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

• Basic product management knowledge – Familiarity with concepts like user stories, roadmaps, and iterative development is helpful.
• Understanding of your target domain – While this guide uses financial examples (e.g., retail banking), the principles apply broadly. If you work in fintech, bring domain-specific context.
• A willingness to say “no” – Building for stickiness requires ruthless prioritization. Prepare to push back on internal demands that dilute your core value.
• Access to user feedback channels – You'll need a way to test assumptions with real users early and often.

Step-by-Step Instructions

Step 1: Identify Your Bedrock

The bedrock is the one core activity or promise that users come to your product for again and again. In retail banking, for example, it’s not opening a new account (a rare event) but the daily ritual of checking balances, tracking spending, and transferring money. These “regular servicing journeys” form the bedrock because they deliver value repeatedly and build trust over time. To find your bedrock, ask: What is the single most essential job your product does for users that, if removed, would make the product useless?

Action: Write down three candidate bedrock ideas. For each, map the repeated usage frequency and the depth of emotional or financial value. Choose the one that scores highest on both.

Step 2: Define Your MVP Around the Bedrock

Once you have your bedrock, resist the urge to add extra features. An MVP is not the smallest feature set possible; it’s the smallest viable version of your bedrock that users will find valuable enough to engage with repeatedly. This requires a “razor sharp eye” and the courage to ignore the “Columbo Effect”—that persistent feeling there’s always just one more thing to add. For a banking app, an MVP might include only transaction history, balance display, and a simple transfer function. No budgeting tools or loan calculators yet. Example: If your bedrock is daily balance checking, launch with a clean, low‑latency view of account status. Test if users keep coming back.

Code/Prototype Snippet (conceptual):

// Pseudocode for MVP endpoint
app.get('/api/v1/accounts/:id/balance', (req, res) => {
  const balance = fetchCurrentBalance(req.params.id);
  res.json({ account: req.params.id, balance, asOf: Date.now() });
});

Keep it simple. No caching layers, no historical graphs. Just the raw data users need.

Step 3: Beta Test with Ruthless Focus

Release your MVP to a small group of real users. Gather qualitative and quantitative feedback. Pay special attention to friction points: “The app crashes when I refresh,” or “I can’t find my transaction date.” Crucially, listen for signs that users connect the bedrock value. In financial products, security teams (affectionately called “narcs” in the original text) will raise concerns. That’s healthy—address approval issues early, but don’t let them derail the core. Common beta iteration: After two weeks, if 70% of testers access the app daily, you’re on solid ground. If not, revisit your bedrock or the minimal feature set.

Tip: Create a simple feedback survey with three questions: (1) What’s the one thing you use this app for most? (2) What’s missing? (3) What would make you stop using it? Map answers back to your bedrock.

Step 4: Scale and Protect the Bedrock

Once your MVP gains traction, you can expand—but only in ways that support the bedrock. Every new feature must answer: “Does this deepen user engagement with the core activity?” Avoid the “feature salad” pitfall where internal politics drives development. For example, adding a cryptocurrency widget because the blockchain team wants visibility is dangerous if your bedrock is daily banking. Instead, prioritize features that reduce friction in the core journey: instant push notifications for transactions, faster loading times, or a more intuitive transaction search. Action: Create a decision matrix: every proposed feature gets scored on (a) alignment with bedrock, (b) development cost, (c) expected user retention lift. Discard anything scoring low on (a).

Common Mistakes

• Feature‑first development – Adding features to please internal stakeholders rather than users. This leads to a bloated product with no clear identity. The result: high churn and low word‑of‑mouth.
• Ignoring the “Columbo Effect” – Succumbing to endless requests for “one more thing.” Every addition dilutes the focus on the bedrock. Learn to say no gracefully.
• Building around internal politics – When your product mirrors departmental interests instead of user needs, you get a confusing mishmash. Reject features that exist only to satisfy a team’s agenda.
• Neglecting security and compliance early – In fintech, waiting to involve security until after launch can force expensive rework. Engage your “narcs” during the MVP phase to ensure the bedrock is built on a compliant foundation.
• Forgetting the bedrock once scaled – As you add features, always reassess: are you still optimizing the core daily experience, or are you chasing shiny objects? Set a regular “bedrock check” meeting monthly.

Summary

Building products that stick means moving from a feature‑first mindset to a bedrock‑first strategy. Identify the one activity users return to repeatedly, build a ruthless MVP around that core, test it with real people, and scale only in ways that reinforce the bedrock. Avoid the temptations of internal politics and the ever‑present “Columbo Effect.” By staying focused on what truly matters, you can create financial products that are stable, loved, and used every day—not just in beta, but as bedrock.