As a product builder, to mention in many years, I have just lost the count in a few weeks that I have seen ideas going from zero to the hero in a few weeks, just to wander within months.
The article continues below
Financial products, which I work, have no exception. With the real labor money of people on the line, raising the customer’s expectations, and a crowded market, it is tempted to throw more and more features on the wall and hope that there is something sticks. But this approach is a version of destruction. Why here:
First development losses of feature#Section 2
When you start building financial products from groundup, or migrating to existing customer travel from paper or telephone channels on online banking or mobile apps, it is easy to get into the excitement of creating new features. You can think, “If I can add only one thing that solves this particular issue of the user, they will love me!” But what happens when you inevitably hit a road block because Narcas (your security team!) Doesn’t like it? When a hard struggle feature is not as popular as you thought, or does it break due to unexpected complexity?
This is the place where the concept of the least viable product (MVP) comes. Jason Freud’s book Being real And his pod cast Work again Often touching the idea, even if they don’t always say it. An MVP is a product that only gives your users so much value to engage, but not so much that it becomes too much or becomes difficult to maintain. It looks like a simple concept, but it requires a sharp eye, a ruthless edge and dares to live according to your opinion because it is easy to seduce through the “Colombo Effect” … when always exists “.Just another thing …“Someone wants to include.
However, the problem with most finance apps is that they often reflect the internal politics of the business rather than the experience designed around the customer. This means that the focus is focused on providing more and more features and utility to meet the needs and wishes of the internal departments, rather than focusing on what people in the real world want. As a result, these products can be very easily confused, irrelevant and eventually a mixed bag of useful consumer experiences.
The importance of the bedrock#Section 3
So what is better than that? How can we produce products that are stable, user-friendly, and most importantly-stacked?
This is where the concept of “bedrock” comes. Badrick is the main element of your product that is really important to consumers. This is the basic building block that provides the price and remains relevant over time.
In the world of retail banking, where I work, Baderick has to stay in and around regular services. People open their current account once in the blue moon, but they see it every day. They sign up for credit cards every or two years, but they check their balance and pay their bill at least once a month.
Identifying basic tasks that people want to do and then try to make them easily, reliable and reliable, where Gravi is the place.
But how would you reach the bedrock? By focusing on the “MVP” approach, preferring simplicity, and pointing to a clear value suggestion. This means reducing unnecessary features and focusing on providing real value to your customers.
It also means to have some courage, because your partner may not immediately start your vision. And controversially, sometimes it can also mean to make consumers clear that you will not come to their homes and will not make food. Occasionally “voter user interface design” (ie, CLC CLC workwroup of edge cases) Sometimes you need to use a concept to test a concept or you buy a place to work on something else.
Practical strategies for construction of financial products that remain#Section 4
So what important strategies have I learned from my experience and research?
- Start with a clear “Why”: Which problem are you trying to solve? For whom? Make sure your mission is clear before building anything. Make sure it is align with your company’s goals.
- Focus on one, the basic feature and obsession with getting this right before going to something else: at the same time, fight the temptation of adding a lot of features. Instead, choose someone who provides real value and repetitions from there.
- Prefer more simplicity over complexity: When it comes to financial products, it is often low. Cut unnecessary bells and whistles and focus on what is most important.
- Hugging continuous repetition: Baderick is not a fixed destination – this is a dynamic process. Permanently submit the user’s feedback, improve your product, and repeat it towards this badmick state.
- Wait, look and listen: Don’t just test your product as part of your delivery process – this is because it is repeatedly in the field. Use it yourself. Run A/B Test. Submit user feedback. Talk to people who use it, and do it accordingly.
Bederick Paradox#Section 5
Here is an interesting contradiction in the game: Bederick’s building means sacrificing some short -term growth ability in favor of long -term stability. But the payment is worth it. Products created with focus on the bedrock will surpass their rivals and provide consumers with a permanent price over time.
So, how would you start your journey toward the bedrock? Take it one step at a time. Start by identifying the basic elements that are really important to your users. Focus on the construction and disposition of a single, powerful feature that provides real value. And above all, test Abraham, Abraham Lincoln, Allen, or Peter Doker (which you believe !!), “The best way to predict the future is to create it.”
0 Comments