Skip to content
Vishwa Raj logoVishwa Raj
Back to projects
Kalkine App Overhaul

Case study

Kalkine App Overhaul

A product-led overhaul of the Kalkine mobile experience—improving information hierarchy, navigation clarity, and time-to-insight for investors.

MobileFintechUXProduct strategy

Outcome focus: user trust and decision speed

Risk reduced: costly roadmap drift

Reusable assets: sequence, scoring, and instrumentation

TL;DR

Kalkine’s previous mobile experience was dense and inconsistent—users struggled to scan market information quickly and find the next best action.

I led a product-led overhaul that rebuilt the experience into a fast, trustworthy, decision-ready flow: clearer hierarchy, one-tap access to core jobs (alerts, watchlists, portfolio), and consistent UI patterns users can rely on.

I led a product-led overhaul focused on:

  • Information hierarchy: reduce cognitive load and improve scanability
  • Navigation clarity: put primary actions within one tap
  • Trust: consistent patterns and better “what to do next” cues

This case study is written from a Product Manager perspective and uses assumptions where exact numbers were not available for publication.

Key UX enhancements overview

1) Context

Product area

Fintech mobile app experience across:

  • Market overview and insights
  • Real-time alerts
  • Watchlists and portfolio tracking

The user job-to-be-done

“Help me understand what changed, why it matters, and what action I should take—fast.”

2) The problem

What users experienced

  1. Cognitive overload: dense screens + weak hierarchy made markets hard to scan
  2. Slow time-to-action: critical actions (alerts, watchlist, portfolio) were buried behind extra steps
  3. Inconsistent patterns: visual and interaction inconsistencies reduced trust
  4. Unclear next steps: users landed on screens without an obvious “what should I do now?”

Why it was happening (root causes)

  • Too many competing elements above the fold
  • Navigation didn’t reflect the most frequent jobs (alerts, watchlists, portfolio)
  • No consistent component patterns (cards, tables, charts, empty states)

3) Goals & success metrics

Goals

  • Improve scanability and confidence (“I get it in 5–10 seconds”)
  • Reduce friction to primary actions (alerts, watchlist, portfolio actions)
  • Increase perceived trust and clarity through consistency

Metrics (directional)

  • Time-to-insight (TTI): time to locate key change and implied action
  • Alert engagement: open → click-through → follow action
  • Watchlist adoption: % of active users setting at least one watchlist item
  • Portfolio action rate: adds/edits/insight views per user

4) Discovery (what I did)

Research inputs

  • Product analytics review (top screens, drop-offs, repeat usage) [assumption]
  • Support tickets and qualitative feedback themes
  • Competitive scan of investor apps (patterns and expectations) [assumption]

Key insights

  • Users scanned first for signal (big movers, watchlist changes, alerts)
  • The app’s hierarchy showed “everything” but not “what matters now”
  • Trust was tied to consistency (formatting, terminology, and predictable actions)

5) The solution (what changed)

5.1 Navigation and IA refresh

  • Re-ordered primary nav to reflect core jobs (alerts, watchlist, portfolio) [assumption]
  • Standardized screen layouts: header → primary KPI → supporting detail
  • Added clearer entry points for “quick actions”

5.2 Scannable market data

  • Improved typography, spacing, and grouping
  • Reduced noise with progressive disclosure (“tap for details”)
  • Stronger contrast between primary and secondary information

5.3 Alert-first UX

  • Faster access to real-time alerts and follow-ups
  • Clearer alert cards (trigger, why it fired, what changed, CTA)

5.4 Portfolio clarity

  • Simplified portfolio insights and “what changed” context
  • Added predictable action placement (buy/sell/learn more) [assumption]

6) Delivery approach (how I shipped it)

  • Built an IA + component inventory and used it as a delivery contract
  • Defined MVP scope and backlog by expected impact and complexity
  • Worked in weekly cycles:
    • UX spec → engineering handoff → QA → iteration
  • Established “consistency rules” (spacing, type scales, card patterns)

7) Results (directional / assumptions)

  • Faster discovery of key insights and actions from the home experience
  • Clearer UI patterns increased perceived credibility
  • Reduced friction in primary flows (alerts, watchlists, portfolio actions)

Directional metrics (assumed, based on typical fintech UX improvements):

  • ~20–30% reduction in time-to-key-actions
  • ~10–15% uplift in watchlist/alerts adoption

8) Learnings

  • “Less data” isn’t the goal—clear hierarchy is the goal.
  • Speed-to-insight drives engagement more than adding new features.
  • Consistency is a trust feature in finance.

9) Next steps

  • Tie alert relevance to user preferences and behavior (see: multi-channel platform case study)
  • Introduce a compact “daily digest” for low-frequency users
  • Expand instrumentation to measure “action taken” rather than just opens/clicks

If you're working on something similar

If you're rebuilding a mobile experience (especially in finance, health, or any data-heavy domain), these prompts help keep the effort outcome-led:

  • Where do users lose confidence (unclear next step, missing context, inconsistent patterns)?
  • What are the 3–5 jobs-to-be-done that must be one tap away?
  • Which metrics will confirm improved clarity (time-to-insight, repeat usage, task completion)?