CONCEPT Cited by 1 source
Platform evolution¶
Definition¶
The progression of infrastructure from a single-purpose internal tool to a shared internal platform to an externally available capability. This trajectory is not planned upfront but emerges when multiple teams independently discover they share the same underlying problem and one team's solution becomes the canonical implementation.
Stages¶
- Internal tool — built by one team to solve their specific problem. No formal platform contract or plugin model.
- Organic adoption — other teams discover they can reuse the tool rather than building their own. Early consumers accept the existing interface.
- Shared platform — explicit investment in extensibility (plugin models, stable APIs, documentation). Platform team owns core; product teams contribute capabilities.
- Network-effect flywheel — each new consumer makes the platform more capable, which attracts the next consumer. Improvements benefit all consumers simultaneously.
- External API — capabilities mature enough to expose outside the organization. The internal platform becomes a product.
Key insight¶
A platform becomes more valuable over time — unlike a feature, which delivers value once. Each new adoption introduces new requirements that make the platform more capable for subsequent adopters. This creates a compounding return on the initial investment.
Enabling conditions¶
- Plugin architecture — extensibility without modifying core (patterns/plugin-based-extensibility).
- Clear ownership boundary — platform team owns infrastructure; product teams own business logic (concepts/platform-team-vs-application-team-split).
- Caching / deduplication — shared infrastructure means shared computation savings.
- Stable intermediate formats — common interchange representations that multiple consumers can build on.
Risks¶
- Premature platformization — investing in extensibility before the second consumer exists wastes effort.
- Platform team bottleneck — if the platform team must approve every change, adoption slows (concepts/platform-team-bottleneck).
- Scope creep — without clear boundaries, a platform absorbs responsibilities that don't belong.
Known instances¶
- systems/dropbox-riviera — internal preview service (2014) → shared platform (Search, Replay, Sign, Dash) → public API + MCP (2026). (Source: sources/2026-07-20-dropbox-riviera-universal-content-processing-platform)