Platform Enterprise (Category Architecture)
O'Reilly appeared Early release of Platform Enterprise. Two chapters are available: “Framing enterprises as sociotechnical platforms” and “Organizational structures and people”. The author of the book is Lesley Cordero, a staff software engineer/tech lead at The New York Times and, judging by the public conference profiles, works at the intersection of observability, reliability, shared platforms and building engineering teams.
I was asked to rate how interesting the book was, and I decided to read this couple of chapters -- to sum it up, it's about how the corporation itself can be seen as a platform -- with layers of technology, people, roles, rules, contracts, incentives and constraints. It’s funny that usually conversations about platforms quickly narrow down to tools: CI/CD, service directory, golden paths, surveillance, user and rights management, shared infra. That's all important, but it doesn't explain why platforms often don't take off. Technically everything is there, and adoption is weak. The author tries to approach the platform not as a set of services, but as a way to coordinate a large organization.
1️⃣ Enterprise as sociotechnical platform The first chapter defines the framework in the title itself - the author talks about the sociotechnical system: architecture, organizational structure, processes, ownership, governance and feedback culture live together. You can’t just optimize the infra part and expect the delivery speed to magically improve. A good platform in such a framework is not just a self-service UI, but a set of interfaces between teams: technical, organizational and management. What can I do on my own? Where are the limits of responsibility? Which solutions are centralized? Where do you need security and where are guardrails?
2️⃣ Organizational structures and people Wo In the second chapter, the author recalls Conway’s law, but only when applied to platforms that begin to reflect organizational structure. If ownership is blurred, the platform will be a collection of no-one's components. If the incentives for product teams and platform teams don’t match, adoption will become a perpetual “please use our tool” sale. If governance is built as a control committee, the golden path will quickly become a forced path.)
It’s a useful reminder that people are not an “implementation problem” to be solved after the system is designed. People and teams are part of the design of the system.
In general, the book still looks like an interesting application - the author's experience is good, the topic is interesting, the first couple of chapters are written well in the topic, but without any insights. (for me). The truth in the book is still planned. 19 We will have to look at the end of the year - the planned end date is in December. 2026 year
#Architecture #Engineering #PlatformEngineering #Management #DevEx #EnterpriseArchitecture