When I left fintech to build a children's mobile app, everyone assumed it would be a step down in complexity. Banking products are serious. Children's apps are... cute.

They were wrong. But the assumption taught me something important: the skills that make you dangerous in a regulated, high-stakes environment are exactly the skills that consumer product teams are missing. And vice versa.

I spent five years leading product in financial services — at VTB and Sber, two of Russia's largest state banks — before moving to Riki Family, a mobile app built on one of the world's most widely distributed animation IP. Here is what crossed over, what didn't, and what I would tell any PM making a similar transition.

What banking gets right that consumer apps ignore

1. Metrics that actually mean something

In banking, every metric has a consequence. A 0.3% drop in conversion on a loan application flow means millions in lost revenue. A spike in failed transactions means a call from compliance before lunch. You learn, fast, to build measurement systems that catch real problems before they become disasters.

Consumer apps — especially in the early stage — often measure vanity. Downloads. Ratings. Engagement without a clear definition. When I joined Riki Family, one of the first things I did was define what a successful session actually meant for a four-year-old. Not time-in-app. Not opens. We landed on a combination of intentional game completions and return within 48 hours — two signals that correlate with what parents actually want: a child who finds genuine value and comes back by choice.

That discipline came directly from banking. Define the metric before you build the feature. Know what you're measuring and why before you look at the dashboard.

2. Stakeholder complexity as a feature, not a bug

Banking products are a negotiation sport. Legal, compliance, risk, treasury, IT security, the regulator — everyone has a veto. PMs who survive in that environment develop a specific skill: the ability to find the version of a solution that satisfies constraints no one told you existed until the day before launch.

Consumer apps look simpler on the surface. But a children's app has its own hidden stakeholder map: the child (the user), the parent (the economic decision-maker and trust gatekeeper), the regulator (COPPA, GDPR-K, and their equivalents), and the IP licensor (in our case, a global animation group with brand guidelines enforced across 100+ countries).

Banking trains you to see constraints as the design brief, not the obstacle.

3. Trust as a product feature

In banking, trust is not a marketing concept — it is the product. A user who doesn't trust their bank's app will not complete a transaction. Full stop. Every interaction either builds or erodes that trust, and the cost of a single breach is catastrophic.

In children's apps, I discovered that the banking instinct was exactly right. Parents are more skeptical than any banking customer I've ever studied. They read app store reviews before downloading. They watch the first session over their child's shoulder. The teams that win in this space treat parental trust with the same seriousness that a bank treats its credit rating.

What consumer apps taught me that banking never could

1. Ship before you're ready

Banking product timelines are measured in quarters. Regulatory review, security audit, UAT, staged rollout — by the time a feature reaches a user, it has been tested by fifty people who are not the user. The upside is quality. The downside is almost no feedback loop on real behavior until it's very expensive to change anything.

We shipped the achievements system in Riki Family in a form that was clearly incomplete — placeholder artwork, no sound, two achievement types instead of twelve. Within a week we had session data showing us which completion moments generated return visits and which didn't. That data shaped the next three months of roadmap better than any internal testing would have.

2. Emotion is a product metric

In banking, emotion is a problem to be managed. Anxious users call support. Confused users abandon flows. The goal is clarity, not feeling.

In a children's app, emotion is the entire value proposition. A child who feels proud completes the achievement. A child who feels surprised keeps playing. A child who feels seen comes back tomorrow. The first time I watched a child's face light up when a Smeshariki character reacted to their in-game action — that was a product metric. It just wasn't in any dashboard.

Banking made me rigorous. Consumer apps made me human.

3. Your user cannot tell you what they want

A four-year-old cannot tell you why they stopped playing. They drop the phone and walk away. You have session recordings, heatmaps, and the parent's face. That's it.

This forced me to become a much better observer. I stopped writing users want X in product docs and started writing we believe users want X, and here is how we will know within two weeks if we're wrong. That habit is one I've since applied to everything.

The thing no one tells you about switching tracks

The hardest part of moving from banking to consumer wasn't the skills gap. It was the identity gap. In banking, seniority is visible. In consumer — especially in an early-stage product — none of that translates. You're starting from zero on a different scoreboard.

What I found, two years in, is that the scoreboard that matters is the one you build yourself: the metrics you define, the systems you design, the team you develop. The banking background became a lens that lets me see things my consumer-native colleagues sometimes miss.

If you're a PM considering a similar move: the gap is real, and it's worth crossing.