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 months to being useless after working as a solution designer for too long to notice.

Financial goods, which is my area of expertise, 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 will lead to disaster. Why, you see this:

The perils 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 user journeys from papers or telephony channels to online bank or mobile apps. They may think,” 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 radio Rework frequently discuss it. An MVP is a product that offers only enough significance to your users to keep them interested, but not so much that it becomes difficult to keep up. Although it seems like an easy idea, 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 specifically 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. These products may therefore quickly become a muddled mess of confusing, related, and finally unlovable client experiences—a feature salad, you might say.

The significance of the foundation

What is a better strategy, then? How can we create items that are reliable, user-friendly, 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. The foundation of worth and relevance over time is built upon it.

The core has 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 moon, but they do so daily. They purchase a credit card every year or every other year, but they at least once a month assess their stability and pay their bills.

The key is in identifying the main tasks that people want to complete and working relentlessly to render them simple, reliable, and trustworthy.

How can you reach the foundation, though? By focusing on the” MVP” strategy, giving ease precedence, and working iteratively toward a clear value proposition. This means avoiding unnecessary functions and putting your users first, and adding real value.

It also requires some nerve, as your coworkers might not always agree on your perspective right away. And in some cases, it might even mean making it clear to clients that you won’t be coming over to their home and prepare their meal. Sometimes you need to use “opinionated user interface design” ( i .e., clumsy workaround for edge cases ) to test a concept or to give yourself some more time to work on something else.

Functional methods for creating reliable economic items

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

What trouble are you trying to solve first and foremost with a distinct “why”? For whom? Before beginning any project, make sure your vision is completely clear. Make certain it also aligns with the goals of your business.
Avoid putting too many features on the list at again; instead, focus on getting that right first. Choose one that actually adds benefit, and work from that.
When it comes to financial items, clarity is often over difficulty. Eliminate unwanted details and concentrate solely on what matters most.
Accept ongoing iteration: Bedrock is not a fixed destination; it is a fluid process. Continuously collect customer feedback, improve your product, and work toward that foundational position.
Stop, glance, and listen: 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 testing. User opinions on Gatter. Talk to those who use it, and change things up correctly.

The foundational dilemma

Building towards rock implies sacrificing some short-term expansion potential in favor of long-term balance, which is an interesting paradox at play here. But the reward is worthwhile: products built with a focus on rock will outlive and surpass their rivals over time and provide users with long-term value.

How do you begin your journey to 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, in the words of Abraham Lincoln, Alan Kay, or Peter Drucker ( whew! The best way to foretell the future is to build it, he said.