In the competitive world of financial products, creating something that customers truly love and stick with is a constant challenge. Many promising ideas soar briefly only to crash and burn. The key lies in avoiding common traps like feature overload and internal politics. This Q&A explores how to build stable, user-centric products using concepts like Minimum Viable Product (MVP) and a core 'bedrock' feature. Learn to shift from a feature-first mindset to one focused on lasting value.
Why do many financial products fail to gain long-term traction?
Despite initial excitement, many financial products fizzle out because teams fall into the feature-first development trap. They try to solve every user problem at once, adding more and more features in hopes that something will stick. This approach is especially risky in finance, where users entrust their money and demand high reliability. When security teams (often called 'narcs' humorously) push back, or when a feature breaks due to complexity, the product becomes fragile. The result is a bloated, confusing experience that turns users away. Instead, building a product that sticks requires focusing on core value first—a principle known as the Minimum Viable Product (MVP).
What exactly is a Minimum Viable Product (MVP) and why is it hard to execute?
An MVP is the simplest version of your product that delivers enough value to keep early users engaged, without overwhelming them or your development team. Inspired by ideas from Jason Fried's Getting Real and the Rework podcast, this approach demands ruthless prioritization. The challenge is resisting the 'Columbo Effect'—the temptation to add 'just one more thing' to please internal stakeholders or perfectionist instincts. In financial products, an MVP might be a basic savings tracker or a secure payment flow, not a full digital bank. Executing an MVP requires courage to ship an imperfect but useful product, and a sharp eye to cut non-essentials. When done right, it prevents feature bloat and keeps the user at the center.
How does internal politics ruin a financial product's user experience?
Many financial apps become a reflection of internal politics rather than customer needs. Different departments—marketing, compliance, product, engineering—each push for features that serve their own goals. The product ends up as a 'feature salad' of unrelated, confusing experiences. For example, a banking app might include a mortgage calculator, a stock trading widget, and a rewards program—all bolted on to satisfy competing internal demands. Users face a cluttered interface that lacks a clear value proposition. The only way to avoid this is to have a strong product vision that puts the customer first, overruling internal silos. A clear, unified purpose prevents bloat and creates a lovable, sticky product.
What is 'bedrock' in product development and why is it crucial?
'Bedrock' is the core feature of your product that truly matters to users—the fundamental building block that stays relevant over time. In retail banking, for example, the bedrock is likely the regular servicing journey: checking balances, reviewing transactions, or making payments. People open a new account rarely, but they interact with their account daily. If that daily experience is smooth, secure, and helpful, the product becomes indispensable. The bedrock provides a stable foundation upon which other features can be built, but it must never be compromised. Identifying bedrock requires deep customer understanding and a focus on what delivers continuous value, not just initial novelty.
How can you identify the bedrock feature for your financial product?
To find your product's bedrock, ask: What do users do most often, and what provides the most consistent value? For a budgeting app, bedrock might be automatic transaction categorization. For a payment app, it could be instant transfers. Avoid shiny features that attract once but aren't used daily. Analyze user behavior data, customer support tickets, and churn reasons. Look for the one function that, if removed, would make the product useless for most people. Once identified, invest heavily in making that feature rock-solid. For example, a bank's transaction history must be fast, accurate, and user-friendly. That bedrock becomes your product's anchor, making it 'sticky' even as you add complementary features later.
What role does security play in building a sticky financial product?
Security is both a constraint and a protector. While it may feel like a roadblock (the 'narcs' from the security team), it's essential for trust. A security flaw can instantly destroy a product's stickiness. However, over-engineering security can also ruin user experience, e.g., requiring too many verification steps. The key is to strike a balance: build security into the bedrock from the start, not as an afterthought. For instance, use biometrics for quick access but strong encryption for data. When users feel their money is safe, they engage more freely. The best products make security seamless—invisible when it works, but ironclad against threats. This trust is the glue that makes customers stay.
How can product teams avoid creating a 'feature salad'?
Avoiding feature salad requires disciplined product strategy. First, define your product's purpose narrowly—what single job does it do best? Then, resist the urge to add features just because competitors have them or because internal teams lobby for them. Use the MVP approach: launch with only the bedrock feature, then add only those features that directly enhance the core experience. Regularly review your product's feature set. If a feature isn't used by at least a significant portion of your audience, consider removing it. Embrace the courage to say no. Also, create a clear product roadmap that ties every new addition back to the bedrock. For example, a payment app might focus on speed and reliability before adding rewards or investments. A lean, focused product is far more likely to stick.
What are the key takeaways for building a product that sticks?
- Start with an MVP: Delight users with just enough value, then iterate.
- Resist the Columbo Effect: Don't add 'one more thing' that dilutes focus.
- Identify your bedrock: Find the daily-use feature that provides core value.
- Put users over politics: Don't let internal departments bloat the product.
- Make security seamless: Trust is the foundation of stickiness.
- Stay lean: Regularly prune features to avoid a confusing salad.
By building on a strong, user-centered bedrock, you create a product that not only attracts users but keeps them coming back day after day.