Fintech fear and loathing in banking
summary
Explains why partnering with a bank slows product velocity: legacy cores split by product while an abstraction layer is being built, budgeting that prioritizes mandatory compliance projects over customer-facing work, and a project culture that favors low‑impact changes. Gives numbers and tools: an early Java ME app grew from 200k to 40M users and sold to Fiserv; valley bank holds about $40 billion assets; one team rebuilt a Salesforce estate into three scrum teams shipping code every three weeks. Cites Alloy, interchange rules (banks under $10B), and Varo’s $575k/day burn as practical constraints.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:35Stuarts background
- 7:50Coming back to banks
- 11:07Budgeting in banks
- 15:30Legacy tech
- 21:07Product project culture
- 22:37Manage the technology stack
- 26:47Regulation
- 30:29Why work at a bank
- 32:30Police officers
- 33:12Selfawareness
- 36:27Challenger banks
- 38:22Consolidation
related talks
31mPanel: Why is the financial services industry struggling to embrace fintech?
23mThe New Neobanking Stack
44mStories from the trenches: Building product teams ...
01h 03mBeyond the innovator’s dilemma
30mPanel: Structuring teams and organizations in FinTech
46mBleeding edge engineering behavior is Apache Way
29mNavigating regulated scale: How Fiserv hones golden paths for 7,500 developers
24mFiguring out your Open Banking Strategy