A thinnest viable platform is the smallest set of APIs, documentation, and tools that accelerates teams developing modern software services and systems. It is a foundation for engineering teams, not a side project, and requires dedicated ownership and long-term funding when shared infrastructure has become neglected. section 13.5
Shape the platform around progressive delivery rather than a large up-front program:
- Build enough platform capability to deliver the first modernization slice, then extract and establish the reusable pieces. section 16.2.3
- Think big about the desired platform while working small enough to learn and refine direction. section 16.2.3
- Use a proof of concept first when production pathways may expose risks that cannot be resolved quickly. section 16.2.3
- Fund a dedicated platform team when common infrastructure increases product teams’ cognitive load or leaves engineers carrying unsustainable side work. section 13.5
A growing autonomous startup
A startup with highly autonomous teams initially resisted centralization. As common infrastructure became neglected, a few engineers maintained it alongside product work, increasing cognitive load and burnout. Expected team growth made a dedicated platform team increasingly appropriate. section 13.5
Walking skeleton
Platform and software engineers can collaborate on an initial slice through planning, daily coordination, and mob programming, then deploy a thin application version to production early. This establishes the production path while reducing later launch risk. section 16.2.3
