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 area of my specialization, 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 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 user journeys from papers or telephony channels to online bank or mobile applications. They may think,” If I may only add one more thing that solves this particular person problem, they’ll appreciate 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 guide Getting Real frequently address this concept. An MVP is a product that offers only enough value 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 funding apps is that they frequently turn out to be reflections of the company’s internal politics rather than an experience created exclusively for the customer. This implies that the priority is to provide as many features and functionalities as possible to satisfy the requirements and desires of competing inside ministries as opposed to a distinct 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 may we create products that are user-friendly, firm, and, most importantly, stick?

The concept of “bedrock” comes into play in this context. Rock is the main feature of your solution that really matters to customers. It’s the fundamental building block that creates price and maintains relevance over time.

The rock has got to be in and around the standard cleaning journeys in the world of retail bank, which is where I work. People only look at their existing accounts once every blue sky, 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 jobs that people want to complete and working relentlessly to render them simple, reliable, and trustworthy.

But how do you reach the foundation? By focusing on the” MVP” strategy, giving convenience precedence, and working incrementally toward a clear value proposition. This means avoiding pointless extras and putting your people first, making the most of them.

It also requires some fortitude, as your coworkers might not always agree on your vision at first. And in some cases, it might even mean making it clear to consumers that you won’t be coming over to their home and 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.

Functional methods for creating stick-like economic items

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”? For whom? Make sure your goal is unmistakable before beginning any work. Make certain it also aligns with the goals of your business.
Avoid the temptation to put too many characteristics at once by focusing on one, key feature and focusing on getting that right before moving on to something else. Choose one that actually adds value, and work from there.
When it comes to financial products, simplicity is often more important than complexity. Eliminate unnecessary details and concentrate on what matters most.
Accept continuous iteration: Bedrock is not a fixed destination; it is a dynamic process. Continuously collect user feedback, make product improvements, and advance in that direction.
Stop, look, and listen: Don’t just go through with testing your product as part of the delivery process; test it repeatedly in the field. Use it for yourself. Run the A/B tests. User feedback on Gatter. Talk to those who use it, and change things up 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 because products created with a focus on bedrock will outlive and outperform their competitors and provide users with ongoing value over time.

How do you begin your quest for bedrock, then? Take it gradually. Start by identifying the underlying factors that your users actually care about. Concentrate 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.