Drawing platform boundaries
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
place boundaries so product teams wait less on each other.
Planned topics
- A good boundary has a stable interface and a team that can change the inside alone.
- Extract a platform when several teams repeat the same work and the need is stable.
- Keep volatile, differentiating logic in product domains.
- Watch cognitive load: a platform should lower what a product team must know.
Draft outline details
Demonstration
a before/after sketch of the "payments" capability: three teams each integrating a provider, versus one payments platform with a self-service API and a service-level objective.
Check your understanding
Which should become a platform first: a stable repeated need or a fast-changing differentiator?
Show answer
The stable repeated need.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.