When I tell a 4DX practitioner what OTP does, the first question is almost always the same. "Doesn't that just duplicate the scoreboard?" It is a fair question, and it comes from people who take execution seriously, because the scoreboard is the heart of 4DX and they have watched it work.
Here is the reframe I offer back. 4DX is the discipline. OTP is who gets to practice it. The 4 Disciplines of Execution describe exactly what good execution looks like, regardless of who is doing the executing. What changes in a part-human, part-AI team is not the disciplines. What changes is the cast of characters standing in the room when the lead measure gets reported. OTP is not a competing scoreboard. It is the layer that lets a non-human team member step up to the existing one.
What 4DX is
The 4 Disciplines of Execution, by Chris McChesney, Sean Covey, and Jim Huling at FranklinCovey, is the cleanest execution discipline I know. It exists to solve one problem: the whirlwind of daily operations eats the goals that actually matter. The four disciplines are the antidote.
Discipline 1, focus on the wildly important. Pick one or two Wildly Important Goals, the WIGs, and refuse to dilute them. Most teams fail by trying to move twelve things at once. 4DX forces a brutal narrowing.
Discipline 2, act on the lead measures. This is the intellectual core. A lag measure tells you whether you hit the goal, but it tells you too late to do anything about it. A lead measure is predictive and influenceable: it forecasts the lag measure, and the team can actually move it. Revenue is a lag measure. Number of qualified discovery calls booked this week is a lead measure. 4DX says spend your attention on the lead measure, because that is the lever you can still pull.
Discipline 3, keep a compelling scoreboard. Not a management dashboard. A players' scoreboard, simple enough that anyone can tell in five seconds whether they are winning or losing. People play differently when they are keeping score.
Discipline 4, create a cadence of accountability. A short, recurring WIG session where each team member reports on last week's commitments and makes new ones aimed at the lead measure. The cadence is what keeps the WIG alive against the whirlwind.
One honest note on scope. 4DX is an execution discipline, not a full operating system. It layers on top of whatever strategy and structure you already run. That is a feature, not a gap. It is meant to make existing goals actually happen.
What OTP is
OTP, the Organization Transport Protocol, sits at a different altitude. It is a protocol and an operating layer for a team that is part human and part AI. The center of OTP is an accountability chart where AI agents hold real seats, the same way humans do: a defined role, a scorecard, KPIs they own, a reporting line.
Most tools in this space bolt an AI assistant onto a dashboard. The assistant answers questions about the numbers. OTP treats AI differently. Our agents are Agent Employees. They do not narrate the scoreboard from the sidelines. They occupy seats and report their own numbers, because the work is theirs.
That distinction is what makes the 4DX question interesting rather than threatening.
The real difference: 4DX assumes the player is human
Read the four disciplines again and notice an assumption running underneath all of them. A person focuses on the WIG. A person acts on the lead measure. A person reads the scoreboard and feels the pull of winning or losing. A person walks into the WIG session and commits.
That assumption was correct for the entire history of the framework, because the only available players were people. The discipline was never wrong about the player. It was just complete on the question.
A lead measure owned by an AI agent changes who shows up to the cadence. If the lead measure is "30 qualified outreach emails drafted per day," and an agent owns that number, then the agent is the one with a commitment to report. It moved the lead measure or it did not. It can show its work. The discipline is identical. The cast list is not.
This is the whole insight in one line. 4DX tells you what disciplined execution looks like. It does not, and could not, tell you what happens when a lead measure has a non-human owner. OTP is the layer that answers that.
Where they fit together
The mapping is close to one-to-one, which is why I borrow the 4DX vocabulary on purpose rather than inventing my own.
The WIG cascades into agent seats. You still pick one or two Wildly Important Goals at the top. They still cascade down. The only change is that some of the seats they cascade into are held by agents instead of people.
Lead measures become agent KPIs. When an agent owns a seat, the lead measure for that seat becomes the KPI on the agent's scorecard. "Qualified calls booked," "stale deals re-touched," "client risk flags surfaced," these are 4DX lead measures and OTP KPIs at the same time. There is no translation layer.
The compelling scoreboard becomes an auto-populated scoreboard. This is where the layer earns its keep. In a human-only 4DX team, someone has to update the scoreboard, and the cadence quietly degrades when they forget. When an agent owns the lead measure, it reports its own number into the OTP scoreboard as a normal part of doing the work. The scoreboard stays current because reporting is not a separate chore bolted onto the job. It is the job.
The cadence of accountability includes agent reports. The WIG session does not disappear. It gets one more category of participant. Humans report their commitments, agents report theirs, and the human in charge of each agent seat answers for it. The cadence is preserved exactly. The room is just fuller.
The agent-employee dimension
Two things follow from agents holding lead measures that a human-only 4DX practice cannot get on its own.
The first is the auto-populated scoreboard I described above. The discipline of keeping a compelling scoreboard has a known failure mode, which is human upkeep. An agent that owns its number removes the upkeep. The scoreboard is live because the worker and the reporter are the same entity.
The second is cross-organization learning, which is the part of OTP I care most about. When many companies run the same lead measure through agent seats, the patterns of what moves that measure become shareable through OTP's Organizational Operating System layer. A discipline that one team learns the hard way does not have to be re-learned from scratch by the next. 4DX has always been excellent inside a single company. The agent-employee model opens a door to learning that travels across companies running the same discipline, without anyone hand-copying a playbook.
A practitioner read
Let me be straight about maturity, since you would catch me if I were not. 4DX is proven. Decades of teams, a deep body of practice, a discipline that holds up. OTP is early. We are building the protocol, the seats are real and the scoreboard auto-populates, but the track record is short. I am not going to dress that up.
So who should actually care about both? A team that already runs 4DX, already believes in lead measures and the cadence, and has just handed one of its lead measures to an AI agent. If that is you, you have a structural question that 4DX does not answer, because 4DX assumed a human owned every measure. OTP is built precisely for that question. Keep the discipline. Add the layer that lets your newest team member practice it.
Close
4DX taught the discipline of moving the measure you can still influence. OTP does not replace that. It widens who is allowed to own one and show up to report it. The scoreboard logic is borrowed on purpose, and gladly. The only new idea is that the player reporting to it might not be a person.
More in this series
This post is part of a series comparing OTP to the operating frameworks companies actually run on. Start anywhere, each one stands alone.
- OTP vs Scaling Up (Rockefeller Habits)
- OTP vs OKRs
- OTP vs Holacracy
- OTP vs Agile and Scrum
- OTP vs Lean and Six Sigma
- OTP vs V2MOM
- OTP vs The Great Game of Business
Or read the full series index.
Looking for the head to head against named tools rather than frameworks? See OTP vs Ninety and EOS One.