Strip 2 · The Menu of Services · Part 2 — The Scale Model

The Menu That Wasn't

Sam is drowning in one-off requests. There's no menu — every order is a special order.

Panel 1

Sam's inbox: 212 unread. Each one a slightly different flavor of the same request.

Sam: "Every customer gets a custom answer because we've never written down what we actually offer."

Panel 2

Elena leans over the cubicle wall with a printed one-pager.

Elena: "That's because we're running Ops without an API. No defined services, no owners, no playbooks — just improvisation with a Slack channel."

Panel 3

Yuki, from two desks over, without looking up.

Yuki: "An API tells software what to expect and who's responsible when it breaks. A Menu of Services does the same thing for a team of humans."

Panel 4

The whiteboard fills in: SERVICE LEVEL · TRACKING · INSIGHTS · GOVERNANCE · ENABLEMENT · FRAMEWORK. Sam, hopeful for the first time all week.

Sam: "So I stop inventing a new process every time someone emails us?"