The next frontier: Driving innovation with platform standardization
summary
Capital One builds a UX platform on AWS (CloudFront, S3, Route 53, containers) with CI/CD pipelines, automated security scans, and a modular plugin architecture called toolbox; the codebase shrinks from 150 front-end repos to 3 and feature teams ship independently. The platform has ~800 front-end contributors, serves tens of millions monthly, holds 5M+ App Store reviews, targets 85% unit test coverage, uses a developer portal and inner‑sourcing, and achieves reduced incidents by over 80% while improving NPS.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:21Familiar Problem
- 1:13The Mission...
- 3:04Why Build a Platform?
- 6:21Types of Platform
- 7:39Keys to a Successful Platform
- 10:47Build for Excellence
- 12:40Enable Developer Community
- 14:16Engage with the Community
- 15:46Empower the Community
- 18:02Empower Through Contribution
- 20:29Become an Ecosystem
- 22:59About Capital One
- 23:42What Does Scale Look Like @CapitalOne?
- 27:14Well Architected: Resilient by Design
- 29:52Well Architected: Secure by Design
- 33:04We Built Common Tooling
- 34:58Automate through Pipelines
- 36:17Self-Service Developer Portal
- 37:05Self-Guided Training
- 38:08Intent Review to reuse and optimize
- 39:43Voice of the Customer
- 40:57Measure Satisfaction
- 42:15Platform Contributions
- 43:39We Changed How We Work
- 45:25Key Takeaways
related talks
35mLoosely Coupled - Micro-Frontends And Capital One’s Contact Centers
40mLoosely Coupled - Micro-Frontends And Capital One’s Contact Centers
23mFront-End Platform Engineering
15mEstablishing Platform Teams to Utilize the Economy of Scale
44m5 Building Blocks for Successful Frontend Platform
24mSignificance of Platforms in Product Development
54mDeveloper experience platforms
25mEnterprise Final Frontier – is it possible to change the corporate ways...