Calling this low hanging fruit on purpose — zero risk, and from shipping this exact feature on a past project, I know a dev + product can knock out a first version in 1-2 days.
This is a low hanging fruit: make a navigation similar to one we all have in phone settings:
The idea is dead simple: create and index of important screens and actions in the app, then let people search it. Want to send an e-transfer? Type “transfer” (or “e-transfer”) and search shows you every place that action lives.
I built this before, so I can say with confidence it’s technically easy — it’s just an index plus basic term search. The only real constraint is how your existing app navigation is structured.
Bonus for product: you get a live feed of what people are actually searching for, which is basically free usage data — what people want, what they can’t find, what’s getting used.
This kind of navigation lets people find stuff without hunting for it. At the last social, a bunch of people were asking where to find things in the app — with search, you never have to remember where anything lives in the first place.
Quick data point for anyone skeptical: roughly 1 in 5 users default to search over browsing menus when it’s available, and once people do search, they tend to complete what they came to do at noticeably higher rates than people who click around menus instead. Not banking-specific data, but the pattern (“search beats hunting through menus”) is pretty well established.
Works the same way in app and web, too.
Fun side note from when we shipped this last time: some of the “old timers” on the team were genuinely surprised that search is just… the default way younger users navigate now. Kids don’t think in screen/page hierarchies — they just search.
Hit me up if you want more technical details.