Join OTP the operating platform for people and AI agents
Back to Blog
Founder Notes 2026-05-22 · David Steel

The Operations Manager seat plus AI inside EOS®

The Operations Manager (sometimes Director of Operations, COO, or Head of Ops) holds one of the highest-leverage seats on the Accountability Chart. Typical roles: deliver client work on time and on budget, maintain the Process Component, manage vendors, oversee tooling, run the project management system, hold the team accountable to SOPs.

If any seat benefits most directly from an AI agent layer, this is it. Operations work is the part of an EOS® company where execution discipline and information density both matter, and where humans have historically been most overloaded.

This post is for Operations Managers specifically.

What agents take off the Operations Manager's plate

Six workflows that should move to the agent layer.

Project status visibility. Every project in the PM system (Accelo, Asana, Linear, ClickUp, whatever) gets read each morning. Stale tickets, drifting milestones, unassigned tasks, resource conflicts. The Operations Manager walks in with a list, not a discovery process.

SOP adherence monitoring. Each documented SOP has measurable adherence checkpoints. An agent reads the work output and flags where the SOP was skipped or shortcut. Not punitive. Surfaces patterns. The Operations Manager coaches the team based on real data.

Resource allocation tracking. Hours logged per project per team member. Capacity vs commitment. Vacation and PTO impact. The agent does the math each Monday. The Operations Manager sees the staffing reality without typing into a spreadsheet.

Vendor and tooling health. Are subscriptions current. Are integrations working. Did any tool go down this week. An agent watches the heartbeats of every system the team depends on. The Operations Manager hears about a problem before a team member does.

Cross-team handoff status. Sales to delivery, delivery to support, support to renewal. Every handoff is a place work falls through. An agent watches the handoff seams and flags drops. The Operations Manager sees them in hours, not weeks.

Compliance and audit trail. SOC 2 review prep, ISO documentation, internal compliance checks. The agent maintains the running log. The Operations Manager submits the prepared package when the audit arrives.

These six together return roughly 8 to 15 hours per week to the Operations Manager in a 25-person company. The reclaimed time goes to coaching, hiring, and the process redesigns that actually move the team forward.

What stays in the Operations Manager's seat

Five workflows that should stay human.

Coaching team leads. Weekly 1-on-1s with each direct report. The agent prepares notes. The conversation is human.

Process redesign. Major changes to how the team delivers. New methodology adoption. Tool migrations. These are leadership decisions. The agent can stress-test. The Operations Manager chooses.

Vendor renegotiation and selection. The agent can pull usage data and pricing history. The negotiation is human.

Personnel decisions. Hiring, performance plans, terminations. All human.

Crisis response. When something breaks badly (a client crisis, a tool outage with revenue impact, a team conflict), the Operations Manager owns the call. The agent assists. The decisions are human.

What the Scorecard looks like for the Operations Manager seat

Common rows in an AI-integrated company:

  • On-time delivery rate (rolling 4 weeks).
  • Active projects in red status.
  • Utilization rate across billable team.
  • Average response time on internal escalations.
  • SOP adherence rate (sampled).
  • Stale tickets in the PM system (over 14 days untouched).
  • Vendor or tool outage minutes this week.

Each row has a sharp definition. The agent pulls and pushes. The Operations Manager spot-checks Monday morning.

What this looks like in practice

A 30-person professional services firm runs this rhythm.

Monday 6 a.m. Crystal (the operations visibility agent) reads Accelo and produces the project status report. Red, yellow, green on each active project. Resource conflicts. Stale tickets.

Monday 8 a.m. The Operations Manager reads the report in 12 minutes. Eight projects need touch this week. Three resource conflicts need negotiation. Two stale tickets need owner reassignment.

Tuesday L10®. The Operations Manager presents the project portfolio in three minutes. The Customer Headlines section catches any client-facing risks the agent flagged. IDS handles the resource conflicts that the team needs to solve together.

Wednesday to Friday. The Operations Manager spends time on the work the agent cannot do. Coaching team leads. Working with the Visionary on next quarter's process redesign. Reviewing the SOP backlog. Maintaining the vendor relationships.

Same week. Different shape. The work that produces the most value gets the most time.

What to deploy in the first 90 days

If you are an Operations Manager starting AI integration, prioritize.

Week 1 to 4. Project status visibility agent. Highest immediate value because the team's PM system is usually the most complete data source.

Week 4 to 8. Resource allocation tracking agent. Pull from the time tracking system. Surface utilization weekly.

Week 8 to 12. SOP adherence agent. The work that begins to reshape the Process Component.

The next quarter adds vendor health, cross-team handoff, and audit-trail agents. The seat is meaningfully different by month six.

The Operations Manager and the Integrator

In small companies, these are the same person. The post above describes both.

In larger companies, the Operations Manager reports to the Integrator. The agent layer that supports the Operations Manager also supports the Integrator. Same data, two consumers. The Operations Manager owns the day-to-day. The Integrator owns the strategic view.

This is the same as classic EOS®. The agent layer simply makes the information flow between the two seats cleaner and faster.

FAQ

What about PMP, Scrum, or Agile frameworks alongside EOS®? Compatible. The Operations Manager can run any of those underneath the EOS® framework. The agent layer reads whichever PM tool the team uses.

Should the Operations Manager build the agents personally? Generally no. The Operations Manager is the consumer and the accountability partner. Building is a separate technical seat or an outside agency.

Will agents replace project managers? No. Agents replace project manager status-update work, not project management. The judgment, relationships, and prioritization remain human.

What about Operations Managers in regulated industries? Add the compliance overlay from the regulated industries post earlier in this series. The framework holds.

EOS®, Entrepreneurial Operating System®, V/TO™, Level 10 Meeting®, L10®, Rocks™, Scorecard, Issues List, Process Component, Accountability Chart, IDS, Customer Headlines, and Integrator are concepts and trademarks of EOS Worldwide, LLC. This article is an independent practitioner perspective and is not affiliated with or endorsed by EOS Worldwide.

DS
David Steel

Founder of OTP. Runs an AI agent army at a digital agency. Building OTP because nobody else seems to be building it. Notes from inside the build, not from the conference circuit.

More about David →

More posts on the blog index.

All posts