Your data platform team is drowning. Not in technical complexity, but in business domain expectations. While they should be building world-class distributed systems and developer experiences, they're instead trying to understand supply chain optimization, marketing attribution, and financial forecasting. This is a recipe for failure.
This talk confronts the uncomfortable truth: many organizations are destroying their data platform teams by expecting them to be both platform engineers AND business domain experts across every department. Using Team Topologies principles, we'll establish clear boundaries between platform capabilities and business ownership.
You'll learn:
- Why stream-aligned teams must own their data models and business rules, period.
- How to build data platform APIs and tooling that empower without requiring business context
- The critical difference between enabling data ownership vs. being the data owner
- Practical patterns using Event Storming and DDD to create clear contracts between teams
- Why treating 'data modeling as optional' is organizational malpractice

Data platform teams should excel at building platforms: scalable infrastructure, intuitive APIs, smooth developer experience, and yes - enablement through documentation and support. But they cannot and should not own your business logic. It's time to stop the cognitive overload and let data platform teams be platform teams.