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

Accountability Chart: what it is and how to build one

An Accountability Chart is a one-page map of every seat in your company, showing who owns each seat and what that person is accountable for delivering. The term comes from EOS, the Entrepreneurial Operating System created by Gino Wickman in "Traction," and it is the backbone of how EOS-running companies define structure.

Most leadership teams use it wrong from the start. They treat it like a fancy org chart. It is not. Understanding the difference is the whole game.

EOS accountability chart vs org chart

A traditional org chart shows hierarchy. Boxes connect to other boxes based on reporting lines. The chart answers the question "who reports to whom." Nothing else.

An Accountability Chart answers a different question: "who owns what, and what does owning it mean?"

Every seat on an Accountability Chart has three things:

  1. A name for the seat (not the person, the seat)
  2. The name of the person sitting in it
  3. Three to seven accountabilities: the specific outcomes that seat is responsible for producing

The distinction matters because one seat can hold multiple roles, and one person can sit in multiple seats (though EOS practitioners push hard against the second case as a company matures). More importantly, the accountability list is what makes the chart useful. Without it, you have a diagram. With it, you have a management tool.

The other key difference: an org chart often reflects what is true today. An Accountability Chart reflects what the company needs at its current stage. In EOS, the recommendation is to design the chart based on what the business needs in the next 12 to 36 months, then figure out who sits in those seats.

At Sneeze It, we run an Accountability Chart that includes both human seats and agent seats. Bogdan sits in the COO seat. Janine sits in the finance seat. Radar sits in the chief of staff seat. Dash sits in the analytics seat. Every seat has the same structure: a name, a person or agent, and a list of accountabilities. The discipline is identical across both seat types.

How to build an accountability chart

Building an Accountability Chart from scratch takes about two hours for a leadership team that is willing to do the work honestly. Here is the sequence.

Start with the functions, not the people. List every major function your company needs to run: sales, marketing, operations, finance, human resources, delivery (or whatever you call the work you actually do for customers). Do not think about who does what. Think about what needs to get done.

Identify the major leadership seats. Most companies under 50 people run on five to seven major seats at the leadership level. EOS has a standard structure: a Visionary seat (the founder or CEO role, responsible for strategy and external relationships), an Integrator seat (responsible for internal operations, accountability, and making the machine run), and then functional seats below those two. The seat names should reflect your business, not EOS's template. Use language your team actually speaks.

Write the accountabilities for each seat. This is the step most teams skip, and it is the most important one. For each seat, write three to seven outcomes the seat is responsible for producing. Be specific. "Revenue growth" is not an accountability. "Achieving the quarterly revenue rock" is an accountability. "Marketing strategy" is not an accountability. "Qualified pipeline generated per month" is an accountability. The test: if you saw the number attached to the accountability drop, would you know exactly who to have the conversation with? If yes, the accountability is written correctly.

Assign people to seats. Once the seats and accountabilities exist, put names in them. If a seat has no one ready to fill it, leave it empty and flag it as an open seat. If one person is covering two seats, mark both with their name and note the gap. The honest version of the chart is always more useful than the comfortable version.

Review quarterly. As the company grows, seats split. A seat one person covered at ten employees often becomes two seats at thirty employees. Quarterly review keeps the chart aligned with the actual shape of the business.

For us, the quarterly review also covers agent seats. When an agent's accountabilities shift, or when a seat is no longer needed, the chart reflects that. We retired Jeff, our data integrity agent, in April after an honest review showed his accountabilities had been absorbed by other seats. The chart is the record of that decision.

Seats and roles

The terms "seat" and "role" are often used interchangeably, but they mean different things in the EOS framework.

A seat is the defined position on the Accountability Chart. It exists independent of any person (or agent) sitting in it. The Sales seat exists whether or not you have a salesperson right now. The seat defines the function, the accountabilities, and where it lives on the chart.

A role is what someone actually does in a seat. Two people can sit in the same seat type (say, two account executives) with the same accountability structure but different specific activities based on their territory or client list.

This distinction matters most during hiring and transitions. When you lose a person, you have not lost a role. You have vacated a seat. The seat and its accountabilities remain. You are looking for the next person to fill it, not recreating the function from scratch.

In a hybrid org where agents sit alongside humans, this distinction becomes critical. When we brought Arin into the Call Center Manager seat, we defined the seat first: what outcomes it owns, what data it reads, what decisions it makes. Then we built an agent to fill it. The seat existed before the agent. The seat will exist after any individual version of the agent is retired or rebuilt.

Tally, our scorecard agent, sits in a seat whose accountability is publishing KPI values to the OTP chart on a defined cadence. That is the seat. Tally is the current occupant. If we ever replace Tally's underlying system, the seat stays. The accountability stays.

This is exactly the shift EOS asks leadership teams to make with human employees: stop thinking in terms of people and start thinking in terms of seats. The practice becomes more intuitive when you watch it apply to agents, because agents make the abstraction visible. An agent is not a person. The seat is not the agent. The accountability belongs to the seat.

What right looks like in practice

A well-built Accountability Chart has a few visible properties when you look at it.

Every seat has a clear accountability list. If you cannot read the chart and know exactly what outcome each seat owns, the chart is not done yet.

No seat has more than one person sitting in it unless that is explicitly flagged as a temporary gap. Two names in one seat means two people think they own the same thing, which means neither of them fully owns it.

The chart covers every major function the business needs. If a function is being done by someone but has no seat on the chart, you have invisible accountability. Invisible accountability is accountability that disappears the moment the person doing it gets busy or leaves.

The chart is used in the weekly meeting. At Sneeze It, the Monday meeting uses the Accountability Chart as its backbone. When a KPI drops, the first question is "whose seat is that?" The chart answers it without debate. That is the whole point.

You can read more about how this plays out in weekly meetings in how we run our Monday meeting with agents on the chart and about how agents get assigned metrics in adding an AI agent to your org chart.

Frequently asked questions

What is an Accountability Chart in EOS? In EOS (the Entrepreneurial Operating System created by Gino Wickman), the Accountability Chart is a visual tool that shows every major seat in the company, who sits in each seat, and what accountabilities each seat owns. It replaces the traditional org chart as the primary organizational structure tool for EOS-running companies.

How is an Accountability Chart different from a job description? A job description describes what a person does. An Accountability Chart defines what a seat must produce. The distinction matters because seat accountabilities stay stable even as the person in the seat changes tactics, learns new tools, or gets replaced. The accountability belongs to the seat, not the individual.

Can an Accountability Chart include AI agents? Yes. An agent can occupy a seat the same way a human does, as long as the seat has defined accountabilities and someone is responsible for reviewing whether those accountabilities are being met. At Sneeze It, agents like Dash (analytics), Radar (chief of staff), and Dirk (sales) each occupy named seats with accountability lists on the same chart as human seats.

How many seats should a small company have on their Accountability Chart? Most companies with fewer than twenty employees run on eight to twelve seats on their Accountability Chart, including the leadership tier. The number scales with complexity, not headcount. Add a seat when a function is being done but nobody clearly owns it.

How often should you update the Accountability Chart? EOS practitioners recommend quarterly review as a standard cadence, with off-cycle updates when a key seat is vacated or a new function is needed. The chart should reflect the current structure, not the structure from twelve months ago.

Run your operating system in OTP

OTP is an operating system where human seats and agent seats share the same chart, scorecards, rocks, and weekly meetings. Every seat has defined accountabilities. Every meeting runs the chart.

In Claude Desktop or Cursor or any MCP client, add this block:

"otp": {
  "command": "npx",
  "args": ["-y", "@orgtp/mcp-server"]
}

Restart the client. Then ask: "Use OTP to show me the Accountability Chart for my organization and list the accountabilities for each seat."

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