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 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, 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 user 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? 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 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 significance to your users to keep them interested without becoming too hard or frustrating to use. 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 sections as opposed to a distinct 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 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 item that really matters to customers. 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 accounts 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 examine 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.
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 unnecessary functions and putting your customers first, and adding real value.
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 clients that you won’t be coming over to their home and 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.
Functional methods for creating stick-like economic items
What are the main learnings I’ve made from my own research and expertise?
- What trouble are you trying to solve first, and make a distinct “why”? Whom? Before beginning any project, make sure your vision is completely clear. Make certain it also complies with the goals of your business.
- Avoid the temptation to put too many characteristics at once and focus on getting that right first. Choose one that actually adds price, and work from that.
- When it comes to financial items, clarity is often over richness. 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 comments, make improvements to your product, and move toward that foundation.
- Stop, look, and listen: Don’t just go through with testing your product as part of the delivery process; test it consistently in the field. Use it for yourself. A/B tests are run. User opinions on Gear. Talk to those who use it, and change things up correctly.
The foundational conundrum
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 because 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 for rock, then? Taking it one step at a time. Start by identifying the essential components that your customers actually care about. Focus on developing and improving a second, potent have 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.









