From Beta to Bedrock: Build Products that Stick.

I’ve lost count of the times when promising ideas go from being useless in a few days to being useless after working as a solution designer for too long to explain.

Financial goods, 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, please:

The drawbacks of feature-first creation

It’s simple 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 apps. 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? not like it? 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 ) comes into play in this context. Even though Jason Fried doesn’t usually refer to it that way, his podcast Rework and his book Getting Real frequently address this concept. An MVP is a product that offers only sufficient value to your users to keep them interested, but not so much that it becomes difficult to keep up. Although the idea seems simple, it requires a razor-sharp eye, a ruthless edge, and the courage to stand up for your position because it is easy to fall for” the Columbo Effect” when there is always” 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 experience created purely for the customer. This implies that the priority should be given to delivering as many features and functionalities as possible in order to satisfy the requirements and wishes of competing internal departments as opposed to crafting a compelling value statement that is focused on what people in the real world actually want. 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 may we create products that are user-friendly, firm, and, most importantly, stick?

The concept of “bedrock” comes into play in this context. The main component of your item that really matters to people is Bedrock. It’s the fundamental building block that creates benefit and maintains relevance over time.

The rock has got to be in and around the standard servicing journeys in the world of retail bank, which is where I work. People only look at their existing account once every blue sky, but they do so daily. They purchase a credit card every year or two, but they at least once a month assess their stability and pay their bills.

The key is in identifying the main tasks that individuals want to complete and therefore relentlessly striving to make them simple, reliable, and trustworthy.

How can you reach the foundation, though? By focusing on the” MVP” strategy, giving clarity the top priority, and working toward a distinct value proposition. This means avoiding pointless extras and putting your customers first, making the most of them.

It also requires some nerve, as your coworkers might not always agree on your eyesight right away. And in some cases, it might even mean making it clear to consumers that you won’t be coming over to their home to prepare their meal. Sometimes you may 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 room to work on something more crucial stuff.

Realistic methods for creating financially successful products

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

What trouble are you trying to solve first, and make a distinct “why”? Who is it for? Make sure your goal is unmistakable before beginning any work. Make certain it also aligns with the goals of your business.
Avoid putting too many features on the list at after; instead, focus on getting that right first. Choose one that actually adds price, and work from that.
When it comes to financial goods, clarity is often over difficulty. Eliminate unwanted details and concentrate on what matters most.
Accept constant iteration as Bedrock is a powerful process rather than a set destination. Continuously collect customer feedback, make product improvements, and advance in that direction.
Stop, glance, and talk: You must test your product frequently in the field rather than just as part of the shipping process. Use it for yourself. Work A/B tests. User opinions on Gear. Speak to users and make adjustments accordingly.

The “bedrock dilemma”

This is an intriguing conundrum: sacrificing some of the potential for short-term progress in favor of long-term stability. But the reward is worthwhile because products created with a concentrate on core will outlive and outperform their competitors and provide people with ongoing value over time.

How do you begin your quest for rock, then? Consider it gradually. Start by identifying the underlying factors that your customers actually care about. Focus on developing and improving a second, potent function that delivers real value. And most importantly, make an obsessive effort because, whatever you think, Abraham Lincoln, Alan Kay, or Peter Drucker, you can’t deny it! The best way to foretell the future is to make it, he said.