By Ahon Sarkar, VP of BaaS Product & Strategy at Q2
Many fintechs come to Q2 interested in adding banking services to their base product offering. Unfortunately, many are ill-prepared.
It’s not that they lack the necessary product development talent — that’s usually abundant. After all, it’s how they created compelling product offerings in the first place. But when it comes to adding banking services, they struggle to orient themselves toward product success.
We’ve outlined a five-step process for designing a great banking product. The first is where many of the difficulties lie: defining the problem.
Before we dive in, it’s important to lay out a few concepts. The first is differentiation — conceptual and practical.
The difference between these two types of differentiation plays into the concept of growing your moat. What is a moat? It’s a sustainable competitive advantage. Warren Buffett paints the following picture to elucidate this concept:
“We have a company called See’s Candy out on the west coast…. If you give a box of See’s chocolates to your girlfriend on a first date and she kisses you, we own you. We can raise the price tomorrow and you’ll buy the same box. You’re not gonna fool around with success. The key there is the response.… Price, to a degree, is immaterial. If you’ve got an economic castle, people are gonna come and want to take that castle away from you, and you better have a strong moat.”
Practical differentiation is sustainable. It grows your moat, and should be the type of differentiation you’re trying to achieve when adding banking services. While the moats that many of Warren Buffett’s companies boast are hefty due to brand, technology companies typically require the right kind of features, deployed toward the right problem, to sustain themselves as differentiated.
Fintechs often come to us because they believe a card and a checking account alone will differentiate their business. But this is only conceptual differentiation. Their competitor could easily add the same services, and now their competitive advantage is gone.
To achieve practical differentiation, it’s important to focus on creating synergy between your primary product and your new banking products. This synergy comes from combining banking products with your primary offering in a way that solves a problem for the first time or in a new way. While most fintechs have already performed this exercise once with their primary product, it’s important to identify a second problem that banking services will solve before adding them to your fintech’s repertoire.
The problem you solve, and how well you solve it, will serve as the centerpiece of your product design process. Here are a couple of examples:
The only way to determine how well you’re solving your priority problem is to measure it. And the most effective way to measure your solution’s effectiveness is to choose one or two priority metrics from hundreds of possibilities, as emphasized by Gartner in 3 Steps to Craft an Impactful Customer Experience Strategy:
“A strategy means being focused and selecting how victory can be declared. A strategy needs to state how to keep score. This means making tough choices and boiling the strategy down to one (or sometimes two) top-level measures of success. This does not mean the other metrics are irrelevant to implementing the strategy; they should all be worked upon for improvement to achieve the top-level goal. But knowing whether the strategy has been successful means picking a measure.”
Let’s return to the examples from our first step to explore what a priority metric might look like for a banking service product:
“There are two main reasons why trust should be built into every level of your product. Finances are personal and important to a person’s well-being, and banking with a technology company is a new experience. It’s personal.”
How do you manage this requirement for trust? First, you have to figure out the ways you can destroy trust. There are landmines scattered all over the place, and your job is to determine where they are so you can avoid them.
Once you’ve avoided ways to destroy trust, you have to build it. Trust is simply a matter of successful interactions over time, and reputation is a matter of trust over time. Openness and transparency are useful along your journey as well. If you guide people on the path to succeeding with your product — it could be with public help content, for instance, that isn’t just more marketing — you’ll catalyze your journey toward a positive reputation. But it takes courage to be open and transparent, as competitors are always watching. So don’t start a trust war if you don’t think you can win.
Finally, you have to reinforce trust at every level of your product. Here are three examples:
There are three primary methods for gathering product data:
The key here is balance and spreading your efforts out across multiple feedback channels. In Oracle’s guide to optimizing customer experience, they emphasize the importance of reading “digital body language” instead of overwhelming your customer with direct feedback requests:
“Instead of asking customers to give up their time and effort to communicate their feedback to you, think about what their behavior and interactions are already telling you. By focusing on digital body language — the psychology of customers at various digital touchpoints — you position yourself in a far better way to understand them, providing the opportunity to change your approach and provide personalized CX. Like in real life, if a customer is showing body language that signals frustration you should not ignore this and react as if they were showing positive body language. Reading customer signals is all about taking this idea and mirroring it in the digital domain.”
It can be tempting to spam your customers with surveys because it’s relatively easy to do and provides very clear feedback in the exact format that you want it for analysis. But keep in mind that “people often don’t think what they feel, don’t say what they think, and don’t do what they say,” according to David Ogilvy. Direct feedback has its place, but it can often be misleading. You still have to look for the underlying feelings that motivate their responses, and then light the way for your customers. So in addition to short, highly potent surveys, scour the web for discussion about your product. Look at your usage data to identify user drop-off points. And always, always bring the data together in the context of the problem you’re trying to solve.
One of the most difficult parts of designing a great banking product is drawing insights from data and incorporating those insights into your larger strategy. The exact methodology for doing so is complex. We recommend hiring people with expertise data science to help with this process.
However, we can provide some areas of product development where data analysis will yield useful insights, including:
Then comes the challenge of combining these insights to make sense of your priority metric. While measuring your priority metric may be relatively straightforward, such as a single-question survey that asks directly for the information you need, improving your single metric may require widespread data analysis from many aspects of your company, as listed above.
One general piece of advice: Pay attention to how your best users are using your product, and then think about ways to encourage other people to start behaving like your best users. Errors in using your product are ripe for modification. You want it to be safe to make mistakes because safety means discoverability. If mistakes can’t be easily undone, people will be discouraged from exploring.
Over the coming months, we’ll explore different ways to tackle this challenge for the various verticals who benefit most from banking as a service.
For an inclusive look at banking as a service and the changing fintech landscape, read our eBook: The Age of Abundant Banking: How to stay innovative when every company offers a debit card.