<aside> 📄
The full project definition: the problem, evidence, principles and hypotheses I set before designing. For the short version, see the main Strom page.
</aside>
| Project | AI-powered neobank: reducing financial overwhelm through adaptive intelligence |
|---|---|
| Type | Solo concept project, product design and UX case study |
| Duration | 1 month |
| Role | Solo product designer: strategy, research, IA, flows, interaction design, visual design, prototype |
| Approach | Secondary research, benchmark analysis, opportunity mapping. No primary user research. |
Banking apps have grown from simple tools into ecosystems that combine budgeting, subscriptions, analytics, investments, insurance, savings and lifestyle services. More functionality brings new friction:
I looked for targeted interventions at these three points instead of redesigning a whole banking experience.
These three problems are connected. Each one affects how people understand information, make decisions and trust a financial product.
Banking apps now put budgeting, subscriptions, investments, analytics, cashback, insurance and savings into one interface. As it grows, people face information overload, hidden features, confusing navigation and more mental effort.
Evidence: 77% of respondents in a mobile banking study had problems with the apps they used, most often navigation, unclear terminology and difficulty using existing features.
| Principle | Current pattern | Design implication |
|---|---|---|
| Hick's Law: decision time grows with the number and complexity of choices | More features → more decisions → higher effort → slower tasks | Surface relevant actions at the right moment instead of showing every feature equally |
| Tesler's Law: some complexity can't be removed, only managed | More products → more information → more complexity → overwhelm | Distribute complexity: keep what matters now in front, the rest a step away |
Move from static, feature-heavy dashboards to adaptive experiences that surface relevant actions.