TCP #109: The trust event that killed your platform adoption
Platforms rarely “fade.” One unannounced breaking change quietly trains teams to avoid you. This issue shows you how to surface that moment.
You can also read my newsletters from the Substack mobile app and be notified when a new issue is available.
When developers stop using your platform, the problem is not adoption. It is trust.
Adoption is a behavior. Trust is what drives it.
When developers route around your platform, open tickets in the wrong queue, or write their own Terraform instead of using your modules, they are telling you something.
Most platform teams respond by addressing the behavior. The right response is to diagnose what broke the signal underneath it.
WHAT PLATFORM TEAMS SEE FIRST
The symptom surfaces quietly.
Golden path usage drops. A team submits a request to bypass the CI pipeline for a one-off deployment. Another team forks the shared Terraform module instead of requesting a change. A senior engineer casually mentions that the platform adds a step that wasn’t there before.
Nobody files a ticket saying, “I do not trust this platform.” They just stop using it.
The metrics follow a few weeks later. Deployment frequency drops on platform-managed services.
Support requests thin out, which looks like a good thing until you realize it means teams stopped asking and started working around. Usage of the internal developer portal flatlines.
The signal is not loud. That is what makes it easy to misread.
THE REFLEXIVE RESPONSE THAT MAKES IT WORSE
Most platform teams respond to dropping adoption the same way.
