I’ve lost count of the times I’ve watched promising thoughts go from zero to warrior in a few days before failing to deliver within weeks as a product developer for very long.
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 will lead to disaster. Why, please:
The drawbacks of feature-first growth
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 client 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 safety team’s negligence? don’t 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 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 purely 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’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. The mainstay of your product is really important to people, and Bedrock is that. It serves as the foundation for the fundamental building block that creates price and maintains relevance over time.
The rock 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 sky, but they do so daily. They purchase a credit card every year or every other year, but they at least once a month examine 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 entails removing unneeded functions and putting the emphasis on providing genuine value to your users.
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 consumers 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 practice, then?
- What issue are you attempting to resolve first, and 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 the temptation to put too many features at once and focus on getting that right first. Choose one that actually adds price, and work from that.
- When it comes to financial goods, clarity is often more important than difficulty. 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 improvements to your product, and move toward that foundation.
- Stop, appearance, and talk: You must test your product frequently in the field rather than just as part of the shipping process. Use it for yourself. A/B tests are run. User comments on Gear. Speak to users and make adjustments accordingly.
The core 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 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 to rock, then? Get it gradually. 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.
