Lenny's PodcastDmitry Zlokazov: How Revolut turns PMs into local CEOs
Through cross-functional product owners running as local CEOs; Revolut hires raw intellect over experience and ships only wow-grade v1 products.
CHAPTERS
- 0:00 – 0:53
Revolut’s PM philosophy: raw intellect, hunger, and “wow” as the bar
The episode opens with Dmitry’s core beliefs about what makes great product leaders at Revolut. He frames Revolut’s edge as prioritizing raw intellect and builder energy, and setting an uncompromising quality bar so early products are lovable—not just functional.
- •Revolut optimizes for raw intellect and hunger to build over resume experience
- •Quality/UX/aesthetics are never compromised, even in early versions
- •A “wow” bar reduces uncertainty about whether an idea failed vs. execution failed
- •Teaser principles: ownership, execution, and depth
- 0:53 – 6:58
What Revolut is and why Europe’s banking landscape made it possible
Lenny gets Dmitry to explain Revolut simply, especially for a US audience. Dmitry describes the fragmented European currency and banking experience that created a clear wedge for a multi-currency, transparent product that later expanded into a “finance super app.”
- •Europe’s multi-currency reality created pain around FX fees and poor rates
- •Revolut started as a multi-currency card with transparency and simplicity
- •Trust and traction enabled rapid expansion into transfers, crypto, savings, credit
- •Context: Revolut operates across ~50 countries
- 6:58 – 8:41
“Product owners” as true owners: the Local CEO model
They unpack why Revolut calls PMs “product owners” and what that implies structurally. Dmitry explains end-to-end accountability, GM-like scope, and how cross-functional teams are organized so product owners can drive outcomes, not just roadmaps.
- •“Product owner” is about ownership, not Scrum ceremony
- •End-to-end responsibility: product, business metrics, customer happiness
- •Product owners run cross-functional teams and execute relentlessly
- •Local CEO framing: autonomy with real accountability
- 8:41 – 9:28
How teams are managed: line vs functional management in cross-functional squads
Dmitry explains Revolut’s operating model: small cross-functional teams where the product owner is the line manager, while functional leaders ensure craft quality. This split is designed to keep execution fast while protecting standards.
- •Teams include engineers, design, data, ops, and more
- •Product owner is line manager: defines what gets done
- •Functional managers define how it’s built and quality expectations
- •Structure supports speed, accountability, and high quality bars
- 9:28 – 12:42
Three archetypes of product owners (UX, Tech, Data Science) and shared fundamentals
Revolut differentiates product owners into three specializations, but Dmitry emphasizes most of the job is common across them. He details the traits they expect: problem solving, customer empathy, technical depth, and business acumen.
- •Three PO types: UX, Technical, Data Science
- •Specialization is ~5–15%; core craft is shared (~85–90%)
- •Strong linear thinking + creative approaches for non-linear problems
- •Deep detail orientation plus business acumen and technical fluency
- 12:42 – 15:54
What “going deep” really means: regulation, country launches, and scaling processes
Lenny pushes for a concrete example of depth, and Dmitry uses the reality of launching bank branches across countries. He describes reverse-engineering successful launches, then formalizing scalable, algorithm-like processes with gates, SLAs, and staffing models.
- •Country expansion requires licensing, regulator reporting, local payment rails
- •Lean teams scope complex work across many jurisdictions
- •Zoom-in/zoom-out skill: deep detail work then abstraction into a scalable framework
- •Formalized processes: steps, quality gates, staffing timing, execution playbooks
- 15:54 – 18:05
Building “wow” products: UX obsession and maintaining broad context
Dmitry adds a key ingredient behind Revolut alumni success: an obsession with “wow.” He explains that beyond speed and cost, Revolut invests in look-and-feel, frictionless flows, and the tiny details that make products lovable—while handling second-order effects across a big product surface area.
- •Fintech often neglects delight; Revolut treats it as a core differentiator
- •Optimize funnels and clicks, but also aesthetics and emotional resonance
- •Teams build habits around nuance and product polish
- •Strong context management: multiple dimensions, second-order effects
- 18:05 – 20:20
Operationalizing quality: weekly founder product reviews and screen-level scrutiny
They dig into how the “wow” bar is enforced. Dmitry explains Revolut’s flat structure and the founders’ hands-on involvement: weekly product reviews and review of essentially every shipped screen, with many “eyeballs” stress-testing edge cases and nuances.
- •Small teams + flat hierarchy enable direct founder involvement
- •Weekly product reviews: teams show increments and get steering
- •Founders review shipped screens; high scrutiny for edge cases and UX quality
- •Process reinforces craftsmanship and accountability across teams
- 20:20 – 29:03
Hiring for builders: raw intellect over experience, plus internal transfers as a strength
The conversation shifts to hiring: Revolut prefers hungry builders with strong intellect rather than seasoned specialists. Dmitry explains why experienced hires can ramp slowly or resist change, and why internal transfers (ops, engineering) often become standout product owners.
- •Revolut prioritizes intellect + drive over years in the domain
- •Senior hires can have longer adoption curves and culture mismatch risk
- •Tech co-founders/startup builders often thrive in the PO role
- •Internal transfers are a ‘positive self-select’ with domain + culture match
- 29:03 – 31:29
Sourcing and recruitment as sprints: targeting great product builders
Dmitry describes how recruiting operates like a sprint-based team with weekly syncs. They pick focus areas each sprint and often target companies known for excellent products in specific domains, sometimes extending to schools and other pipelines.
- •Recruiting runs in sprints with weekly prioritization and reviews
- •Sourcing targets companies/products Revolut admires for excellence
- •Focus areas shift sprint-to-sprint based on needs
- •Systematic approach to finding high-performers early in their trajectory
- 31:29 – 37:21
Managing at Revolut: go extremely deep on a few high-impact projects (without micromanaging)
Lenny asks for contrarian management practices, and Dmitry shares his approach: among ~100 simultaneous initiatives, he chooses 7–10 to scrutinize at extreme depth, even down to code-level understanding. This creates a signaling and discipline effect across the org while preserving autonomy.
- •Revolut runs many parallel projects; leaders can’t status-check everything
- •Deep-dive on 7–10 most impactful items to add real value and catch issues
- •Org learns priorities through formal/informal channels; scrutiny drives discipline
- •Deep oversight is framed as accountability, not micromanagement
- 37:21 – 44:39
Scaling breadth: platform leverage, autonomy, and a super-app product portfolio
They explore how Revolut can ship fast across many jurisdictions: autonomy plus strong platform foundations. Lenny lists major offerings; Dmitry expands into investing breadth, crypto features, BNPL, and mortgages—highlighting the underlying platform approach that avoids bespoke country-by-country builds.
- •Autonomy enables speed; founder oversight provides coherence and quality
- •Platform investments make solutions scalable ‘from the get-go’ (avoid custom builds)
- •Massive product breadth: trading (ETFs/bonds), staking, acquiring, BNPL, mortgages
- •Complexity multiplier: many products across ~50 jurisdictions and regulations
- 44:39 – 55:49
Launching new products: lean teams, low bureaucracy, and “polished before you scale”
Dmitry explains Revolut’s framework for new bets, including non-bank-adjacent features like hotel booking and loyalty (RevPoints). The model: quick green light, assemble a small team, ship a first version fast to learn, but keep it polished and avoid scaling until retention and metrics prove out.
- •New ideas can come from anyone; startup-like evaluation (market, business case, edge)
- •Very low bureaucracy due to founder-led decision-making
- •Build V1 quickly for feedback, but keep quality ‘wow’ even for small cohorts
- •Scale after proof: retention/metrics strong; leverage 50M customers for distribution
- 55:49 – 1:04:07
Execution mindset and Fail Corner: 99% done is closer to 0%, plus an early startup lesson
They reinforce execution as a defining trait: a product isn’t done until it’s adopted and operationalized across support/marketing/sales. In Fail Corner, Dmitry shares a university-era startup building online cinema tickets with custom hardware—technically impressive but financially premature—distilling lessons about staying lean and validating before scaling.
- •Great POs are hands-on and relentlessly execution-focused
- •‘99% done is closer to 0%’: shipping includes enablement and adoption, not just code
- •Failure story: over-invested in hardware before proving demand and unit economics
- •Lessons: validate early, manage burn rate, avoid scaling before traction
- 1:04:07 – 1:10:01
Lightning round: books, tools, principles, and an underrated Revolut feature
The episode closes with quick personal recommendations and a product tip. Dmitry shares influential books, an AI tool he loved (Manus), a planning motto, and a security feature he believes is underused: wealth protection with selfie verification for large transfers.
- •Book recs: The Hard Thing About Hard Things; Build (Tony Fadell)
- •Favorite product: Manus AI agent; uses it for small personal apps
- •Motto: ‘Plans are worthless, but planning is everything’
- •Underrated feature: Wealth protection transfer limits + selfie check security
