The Cloud Playbook

The Cloud Playbook

Share this post

The Cloud Playbook
The Cloud Playbook
TCP #68: Platform Engineering That Actually Works
Copy link
Facebook
Email
Notes
More

TCP #68: Platform Engineering That Actually Works

From Zero Adoption to 90% in Six Weeks

Amrut Patil's avatar
Amrut Patil
Jun 04, 2025
∙ Paid

Share this post

The Cloud Playbook
The Cloud Playbook
TCP #68: Platform Engineering That Actually Works
Copy link
Facebook
Email
Notes
More
Share

You can also read my newsletters from the Substack mobile app and be notified when a new issue is available.

Get more from Amrut Patil in the Substack app
Available for iOS and Android

Become a Founding Member

As a founding member, you will receive:

  • Everything included in paid subscriber benefits + exclusive toolkits and templates.

  • High-quality content from my 11+ years of industry experience, where I solve specific business problems in the real world using AWS Cloud. Learn from my actionable insights, strategies, and decision-making process.

  • Quarterly report on emerging trends, AWS updates, and cloud innovations with strategic insights.

  • Public recognition in the newsletter under the “Founding Member Spotlight” section.

  • Early access to deep dives, case studies, and special reports before they’re released to paid subscribers.

Upgrade to Founding at 50% off


After spending 18 months building an internal developer platform that gathered digital dust, our team pivoted and rebuilt it in just six weeks, achieving 90% adoption across engineering. What changed wasn't the core concept but how we delivered it.

TL;DR: Internal platforms fail because of poor UX, not because engineers hate platforms. This issue breaks down the exact toolchain, components, and strategies that transformed our platform from unused to indispensable.

Source: Unsplash

The Developer Experience Imperative

Engineers don't reject platforms because they're resistant to change. They reject friction.

Our post-mortem on the failed first attempt revealed a critical insight: any platform requiring more than a 5-minute learning curve or forcing context switching will be abandoned.

The adoption equation is simple:

  • Value delivered must exponentially exceed the effort required

  • Integration with existing workflows beats creating new ones

  • Specific solutions to real pain points outperform generic frameworks

Starting With the Golden Path

Rather than boiling the ocean, we identified deployment friction as our engineers' number one pain point and built a "Golden Path" solution:

Keep reading with a 7-day free trial

Subscribe to The Cloud Playbook to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Amrut Patil
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share

Copy link
Facebook
Email
Notes
More