This is the index for a short series comparing OTP (Organization Transport Protocol) to the eight operating, execution, and alignment frameworks small and mid-market companies actually run on. If you came here searching for one of these head to head matchups, start with that post. They each stand alone.
I want to be clear about the frame before you read any of them, because it is the whole point. OTP is not a rival framework. It does not compete with Scaling Up or OKRs or 4DX the way those compete with each other. OTP sits on a different layer. The frameworks decide what the company should do. OTP is the operating layer underneath, the accountability chart where the work gets assigned, executed, and reported, by a workforce that is now part human and part AI.
Every framework in this series was designed for a workforce made entirely of people. That assumption held for the entire history of business and it is no longer true. The frameworks can stay exactly as they are. The layer underneath them has to absorb the change. That is what OTP is for: a chart where some seats are people with names and some seats are agents, and both have an owner, a scorecard, and a KPI.
So none of these posts argue that OTP beats the framework. They argue that you run the framework on top of OTP, and they show exactly where the two interlock once some of your doers are not human.
The comparisons
- OTP vs Scaling Up (Rockefeller Habits) Where the framework ends and the operating layer begins. The OPSP becomes the agent preamble, the FACS gains agent rows.
- OTP vs OKRs The metrics layer meets the operating layer. A Key Result is a metric, not an owner. OTP supplies the seat that owns it.
- OTP vs 4DX The cadence of accountability when an agent owns a lead measure. 4DX is the discipline, OTP is who can practice it.
- OTP vs Holacracy Roles, circles, and what happens when a role is filled by an agent. Holacracy already split the role from the person, which is the cleanest on-ramp to seating agents.
- OTP vs Agile and Scrum Sprints, standups, and an agent on the team. A delivery cadence is not an org model.
- OTP vs Lean and Six Sigma Process quality when an agent runs the process. A method is not a worker.
- OTP vs V2MOM Alignment on paper meets accountability on the chart. A Measure needs a seat that reports it.
- OTP vs The Great Game of Business Open-book scoreboards when an agent keeps score. The warmest fit on the list, because the whole philosophy already is the scoreboard.
The one thing they all share
Read any of the eight and you will find the same hinge. The framework assumes a person sits in every box. OTP holds two kinds of worker on one chart. The agent reports its own number, carries its own accountability, and, through OOS (our cross-org learning layer), can get better using what other companies' agents already figured out. A single-company framework cannot do that last part by design. The framework makes your company better at running the framework. The protocol underneath is where the compounding happens.
If you already run one of these frameworks and have started putting AI agents to real work with nowhere to seat them on your chart, that gap is the thing OTP exists to close. Pick the post that matches your framework and start there.
If you would rather compare OTP to specific products instead of frameworks, see OTP vs Ninety and EOS One, the head to head against named tools.