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 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 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 client journeys from paper or phone channels to online bank or mobile apps. You might be thinking,” If I can only put one more thing that solves this particular person problem, they’ll enjoy me”! What happens, however, when you eventually encounter a roadblock caused by your safety team? 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 if Jason Fried doesn’t usually refer to this concept, his book Getting Real and his audio Rework frequently discuss it. An MVP is a product that offers only sufficient value to your users to keep them interested, but not so much that it becomes difficult to keep up. Although the idea seems simple, it requires a razor-sharp eye, a brutal edge, and the courage to stand up for your position because” the Columbo Effect” makes it easy to fall for something when one always says” 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 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 needs of competing internal departments as opposed to crafting a compelling 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’s a better course of action 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. It’s the fundamental building block that creates benefit and maintains relevance over time.
The rock must be in and around the standard servicing journeys in the retail banking industry, which is where I work. People only look at their existing account once every blue sky, but they do so every day. 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 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 the top priority, and working toward a distinct value proposition. This means avoiding pointless extras and putting your clients first, making the most of them.
It also requires some nerve, 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.
Realistic methods for creating financially successful products
What are the main learnings I’ve made from my own research and practice, then?
- What issue are you attempting to resolve first, and why? 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 price, and work from that.
- Give clarity the precedence it deserves over difficulty when it comes to financial products. Eliminate unwanted details and concentrate on what matters most.
- Accept constant iteration as Bedrock is a powerful process rather than a set destination. Continuously collect customer feedback, make product improvements, and advance in that direction.
- Halt, 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. Work A/B tests. User opinions on Gatter. Speak to users and make adjustments accordingly.
The rock dilemma
This is an intriguing conundrum: sacrificing some of the potential for short-term growth in favor of long-term stability is at play. But the payoff is worthwhile because products built with a emphasis on bedrock will outlive and surpass their rivals over time and provide users with long-term value.
How do you begin your quest to rock, then? Take it slowly. 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, check constantly because, whatever you think, Abraham Lincoln, Alan Kay, or Peter Drucker are all in the same boat! The best way to foretell the future is to make it, he said.
