Demo: Larkspur's operating model on a single page
On This Lesson 3 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
worked session producing a one-page operating model; prepares ARC-038-LAB1.
Draft outline details
Step by step
- List services and integrations from the architecture: web, app, order, stock, payments, ERP, CRM, carriers, reporting.
- Assign an owner team, support tier, and hours to each.
- Define monitoring per service including SaaS synthetic checks, and the on-call route.
- Planned mistake: leave integrations unowned because "both teams touch them". Fix: assign one owner per integration with the other side as a named contact.
- Add vendor escalation paths and operational acceptance criteria; review with a role-played head of IT operations.
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.