Platform as a Product as a Transformation Enabler Within One of the Top 4 Banks in the UK
Panelat Platform Engineering Day 2025 - Europe · on Tuesday, 2025-04-01· at 12:45· Level 1 | Hall Entrance N10 | Room H·
summary
NatWest describes a two‑year Platform as a Product push that trains teams with 18 months of bootcamps and hackathons, uses Cintaso’s cratics to codify domain rules as “promises,” and moves from Terraform modules to a compound promise that bundles account, connectivity and EKS so provisioning drops from two+ weeks to under a day. Platform work follows the platform maturity model, targets the 80% of use cases, and shrinks EKS provisioning to about 35 minutes for common workloads.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06Why platform engineering matters
- 3:53Defining platform engineering
- 8:24Tooling and maturity model
- 10:52Cratics framework and NatWest journey
- 14:24Training and team strategies
- 15:48Boot camps and hackathons
- 18:37Ashley’s cloud journey
- 21:46Reducing cognitive load
- 24:36Operating patterns in platform engineering
- 27:04Self-service and EKS simplification
- 29:09Regulations versus developer needs
- 31:16Compliance in platform products
- 33:47Legacy systems and modernization
related talks
24mSignificance of Platforms in Product Development
45mTaming the FinTech Beast
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
32mPlatform Engineering for Software Developers and Architects (Redux)
25mPlatformization" as a model for transforming
29mLeading With The Platform: A Platform Engineering Approach To Tech Debt
25mInternal Platform as a Product
58mPlatforms: Build abstractions, not illusions