The numbers are off. Is the product the problem?
Maybe.
A product missing its growth target doesn’t necessarily mean the product is bad. And a product hitting its growth target doesn’t necessarily mean it’s good.
I’ve seen organizations start changing pricing, adding features or launching campaigns before answering a more basic question: what exactly isn’t working?
Start with the data.
Look at who is opening the product, how they’re using it, what it’s costing to acquire and serve them, what revenue or balances they’re generating, and whether their behavior matches what the product was designed to accomplish.
The objective isn’t to find a bad metric. It’s to find the problem behind it.
Start with the outcome the product was supposed to create
Every product should exist for a reason.
A deposit product might be designed to acquire new households, deepen existing relationships, generate stable balances, or provide funding.
A payments product might be intended to increase transaction activity, generate fee or interchange revenue, improve retention or make the primary account more valuable.
A lending product may be expected to generate profitable balances, serve a particular customer need or deepen a broader relationship.
Those are different objectives.
Before deciding whether the product is performing, define what success was supposed to look like.
If nobody can answer that consistently, the first problem isn’t performance measurement. It’s product strategy.
Don't confuse volume with value
,Growth is easy to celebrate.
Ten thousand new accounts sounds good. A hundred million dollars in new balances sounds good. Transaction volume going up sounds good.
But what did it cost?
A high-rate deposit promotion can generate substantial balances while attracting customers who leave as soon as the promotion ends. An account-acquisition campaign can produce thousands of accounts that remain lightly funded and barely used. A payment feature can generate activity while adding operating expense, fraud losses, or servicing costs that erode the economics behind it.
Volume tells you what happened.
Value tells you whether you should want more of it.
A useful product review puts acquisition, usage, revenue, balances, cost and risk in the same conversation.
Look at customer behavior after acquisition
Opening the product is the beginning of the story, not the end.
What happens 30, 90 or 180 days later?
Are deposit customers maintaining balances? Are they establishing direct deposit? Are they using debit cards, bill pay or other services? Are they adding other products? Are accounts becoming inactive or closing?
For a payments product, are customers actually adopting the capability? How frequently are they using it? Has it displaced another transaction type or simply added another cost?
Behavior tells you whether customers are finding the value you expected them to find.
It can also expose a segmentation problem. A product may perform very well for one group of customers and poorly for another.
Looking only at portfolio averages can hide both.
Understand the economics underneath the product
A product can be popular and still have bad economics.
Pricing is part of that, but product economics go much further.
For deposits, consider balances, funding costs, fee revenue, transaction behavior, servicing expense, and the value of the broader relationship.
For payments, understand interchange or other revenue, network and processor costs, fraud and dispute expense, incentives, technology costs and operating support.
For lending, pricing has to be considered alongside credit losses, funding, operating expense and capital.
The exact model will differ by product.
The principle doesn’t.
If the organization can’t explain how the product creates economic value, growth alone isn’t enough evidence that it is performing.
Look for operational friction
Sometimes the product is fine and the process around it is broken.
Applications may abandon because the opening process is cumbersome. Employees may avoid recommending a product because the eligibility rules are confusing. Customers may call repeatedly because disclosures or servicing processes don’t make sense.
Operations can also make an otherwise successful product unnecessarily expensive.
Manual exceptions, reconciliations, dispute handling, workarounds, and repeated servicing contacts all become part of the product’s real cost.
Product performance therefore can’t be measured entirely from a product dashboard.
Talk to the people who sell it, service it and support it.
They often know where the friction is before the metrics make it obvious.
Compare the product with the alternatives
Performance also needs context.
What are competitors offering? How is the market priced? Have customer expectations changed? Has technology made something that once differentiated the product commonplace?
But competitive analysis shouldn’t become feature matching.
The fact that three competitors added a feature does not automatically mean you need it.
Ask whether the feature solves a meaningful customer problem, improves the economics or supports the strategy of the product.
Otherwise, you’re allowing competitors to write your roadmap.
Decide what actually needs to change
Once the problem is understood, the answer may be surprisingly small.
Pricing may need to change.
The target segment may need to change.
An eligibility rule or operational process may be creating unnecessary friction.
A feature may need improvement.
The acquisition strategy may be attracting the wrong customers.
Or the product itself may no longer have a compelling reason to exist.
Those are very different problems, and they require very different solutions.
Changing the product before identifying which problem you have is how organizations spend a lot of money without materially changing the outcome.
Product performance starts with the right question
The question isn’t simply: “Is the product hitting its target?”
It’s: “Is this product creating the customer and business outcomes we built it to create?”
Answer that with customer behavior, economics, operational performance, and market context rather than one headline metric.
A Product & Payments Strategy engagement can help define those measures, diagnose where performance is breaking down and determine whether the right answer is pricing, process, positioning, enhancement or a larger product change.
The goal isn’t to build something new. It’s to solve the right problem.