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 expect something sticks because people’s true, hard-earned money is on the line, user expectations are high, and crowded market. However, this strategy is a formula for disaster. Why? How’s why:

The fatalities of feature-first growth

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 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 area. Even though Jason Fried doesn’t usually refer to it that way, his podcast Rework and his book Getting True 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. 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. 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 here. Rock is the main feature of your solution that really matters to customers. It serves as the foundation for the fundamental building block that creates benefit and maintains relevance over time.

The core must be in and around the standard servicing journeys in the retail banking industry, which is where I work. Individuals only look at their existing account once every five minutes, but they also look at it 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 persistently striving to make them simple, reliable, and trustworthy.

But how do you reach the foundation? By focusing on the” MVP” strategy, giving ease precedence, and working iteratively toward a clear value proposition. This entails removing needless functions and putting the emphasis on providing genuine value to your users.

It also requires having some nerve, as your coworkers might not always agree with you immediately. And dubiously, occasionally it can even suggest making it clear to customers that you won’t be coming to their house and making their breakfast. 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 financially successful items

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

What issue are you attempting to resolve first, and why? Who is it for? Before beginning any project, make sure your goal is completely clear. 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 price, and work from that.
When it comes to financial goods, clarity is often over difficulty. Eliminate unwanted details and concentrate solely on what matters most.
Accept constant iteration as Bedrock is a powerful process rather than a set destination. Continuously collect customer feedback, improve your product, and work toward that foundational state.
Cease, look, and listen: You don’t just have to test your product during the delivery process; you must also test it consistently in the field. Use it for yourself. A/B tests are run. User opinions on Gatter. Speak to those who use it, and change things up correctly.

The “bedrock dilemma”

This is an intriguing conundrum: sacrificing some of the potential for short-term progress in favor of long-term stability is at play. 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 quest to rock, then? Taking it one step at a time. 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.