Culture
June 12

"Invisible" platform engineering

Users want platform products and services they feel complete autonomy and ownership over. They build it, fix it, and own it. “Invisible” platform engineering is how you make that happen.

Platform engineering solutions are often thought of as individual teams. Specifically, teams that need to be interacted with. Statements like “open a ticket,” “send a message,” and “ask their tech lead” are good indicators. The team is positioned for you to ask for something and then wait weeks. This structure is fraught with high lead time and a number of back-and-forth cycles.

“Invisible” platform engineering is a design practice that shifts this. Many great platforms have this embedded into them (even if you don’t know it). Their designs push you towards solutions yourself rather than asking for them. Invisibility means users don’t require heavy thought to understand its uses and are able to work within its boundaries. Join me to understand what it means to take and make a platform “invisible.”

Punit Lad
Lead Consultant, Enterprise Modernisation Platforms And Cloud, Thoughtworks
Punit Lad

Register for PlatformCon 2025

Connect with fellow platform practitioners, learn from the best in the industry and engage directly with speakers on Slack.
Community
Join over 20k platform engineers from all over the world
Slack
Share best practices, discuss new trends and tooling with 20k+ platform practitioners
Speakers
Engage with 200+ speakers in dedicated channels or directly in DMs