Skip to content
Back to Knowledge

Framework · F02

The Operator's Contract

The seven agreements a product leader owes the people they lead — and the ones they owe themselves.

This framework began as a working note. It survived contact with three real teams before it earned the name it carries now.

The problem it solves

Most teams don't fail because they lack ambition. They fail because the operating rhythm they inherited was designed for a different job.

The practice

Seven agreements: on the bar, on the cadence, on the trade-offs, on the credit, on the postmortem, on the exit, and on the silence. Written once, revisited quarterly.

What it looks like in the room

A short, defensible cadence. A named owner for each bet. A shutdown criterion written before the work starts. And a postmortem the whole room actually reads.

The Operator's Contract is not a slide. It is what the team does on a Wednesday afternoon when nobody is watching.

Where to start

Pick one bet. Assign one owner. Write one shutdown criterion. Ship the first cycle in six weeks, not six months. The rest compounds from there.

The full framework — templates, meeting shapes, and the postmortem worksheet — is available to engagement clients and reader-list subscribers on request.

Put the framework to work

Bring this into your team.