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 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 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 drawbacks 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 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 ) comes into play in this context. 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 without becoming too hard or frustrating to use. 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 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 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 mainstay of your product is really important to consumers, and Bedrock is that. It’s the fundamental building block that creates price and maintains relevance over time.
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 sign up for a credit card every year or two, but they check their stability and pay their bill at least once a quarter.
The key is in identifying the main tasks that individuals want to complete and therefore persistently striving to make them simple, reliable, and trustworthy.
How can you reach the foundation, though? By focusing on the” MVP” strategy, giving ease the top priority, and working toward a distinct 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 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.
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 complies 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 price, and work from that.
- Give clarity the precedence it deserves over difficulty when it comes to financial products. 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.
- Stop, look, and listen: Don’t just go through with testing your product as part of the delivery process; test it frequently in the field. Use it for yourself. Move the A/B testing. User opinions on Gatter. Speak to users and make adjustments accordingly.
The “bedrock dilemma”
Building towards rock implies sacrificing some short-term growth prospective in favor of long-term balance, which is an interesting paradox at play here. 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 have 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.
