From Beta to Bedrock: Build Products that Stick.

I’ve lost count of the times I’ve watched promising thoughts go from zero to warrior in a few days before failing to deliver within weeks as a product developer for very long.

Financial items, which is the industry in which I work, are no exception. It’s tempting to put as many features at the ceiling as possible and hope someone sticks because people’s true, hard-earned money is on the line, user expectations are high, and a crammed market. However, this strategy is a formula for disaster. Why? How’s why:

The perils of feature-first creation

It’s easy to get swept up in the enthusiasm of developing innovative features when you start developing a financial product from scratch or are migrating existing client journeys from papers or telephony channels to online bank or mobile applications. They may believe,” If I may only add one more thing that solves this particular person problem, they’ll enjoy me”! But what happens if you eventually encounter a roadblock as a result of your security team’s negligence? don’t like it, right? When a battle-tested film isn’t as well-known as you anticipated, or when it fails due to unforeseen difficulty?

The concept of Minimum Viable Product ( MVP ) is applied to this. Even if Jason Fried doesn’t usually refer to this concept, his book Getting Real and his audio Rework frequently discuss it. An MVP is a product that offers only enough significance to your users to keep them interested without becoming too hard or frustrating to use. Although the idea seems simple, it requires a razor-sharp eye, a brutal edge, and the courage to stand up for your position because” the Columbo Effect” makes it easy to fall for something when one always says” just one more thing …” to add.

The issue with most fund apps is that they frequently turn out to be reflections of the company’s internal politics rather than an knowledge created specifically for the customer. Instead of offering a distinct value statement that is focused on what people in the real world want, the focus should be on delivering as some features and functionalities as possible to satisfy the needs and wants of competing inside sections. As a result, these products can very quickly became a mixed bag of misleading, related, and finally unhappy customer experiences—a feature salad, you might say.

The significance of the foundation

What’s a better course of action then? How can we create products that are reliable, user-friendly, and most importantly, stick?

The concept of “bedrock” comes into play here. The mainstay of your product is really important to users, and Bedrock is that. It’s the fundamental building block that creates value and maintains relevance over time.

The bedrock has got to be in and around the regular servicing journeys in the world of retail banking, which is where I work. People only look at their current account once every blue moon, but they do so every day. They purchase a credit card every year or two, but they at least once a month check their balance and pay their bills.

The key is in identifying the core tasks that people want to complete and then relentlessly striving to make them simple, reliable, and trustworthy.

How can you reach the foundation, though? By focusing on the” MVP” approach, giving simplicity the top priority, and working toward a clear value proposition. This means avoiding unnecessary features and putting your users first, and adding real value.

It also requires having some guts, as your coworkers might not always agree with you immediately. And in some cases, it might even mean making it clear to customers that you won’t be coming over to their house to prepare their meal. Sometimes you need to use the sporadic “opinionated user interface design” ( i .e. clunky workaround for edge cases ) to test a concept or to give yourself some more time to work on something more crucial.

Practical methods for creating stick-like financial products

What are the main learnings I’ve made from my own research and experience, then?

What problem are you trying to solve first and foremost with a clear “why”? Whom? Before beginning any project, make sure your mission is completely clear. Make sure it also complies with the goals of your business.
Avoid putting too many features on the list at once; instead, focus on getting that right first. Choose one that actually adds value, and work from there.
When it comes to financial products, simplicity is often over complexity. Eliminate unnecessary details and concentrate solely on what matters most.
Accept continuous iteration as Bedrock is a dynamic process rather than a fixed destination. Continuously collect user feedback, make product improvements, and advance in that direction.
Stop, look, and listen: You must test your product frequently in the field rather than just as part of the delivery process. Use it for yourself. Run the A/B tests. User feedback on Gear. Talk to the users of it and make adjustments accordingly.

The “bedrock paradox”

This is an intriguing paradox: sacrificing some of the potential for short-term growth in favor of long-term stability. But the payoff is worthwhile: products built with a focus on bedrock will outlive and outperform their rivals over time and provide users with long-term value.

How do you begin your quest for bedrock, then? Take it slowly. Start by identifying the underlying factors that your users actually care about. Focus on developing and improving a single, potent feature that delivers real value. And most importantly, make an obsessive effort because, in the words of Abraham Lincoln, Alan Kay, or Peter Drucker ( whew! The best way to foretell the future is to create it, he said.