The short answer.

AI does not get a box on your org chart. AI goes beside each role, as the workflows that role runs: under the accounts payable role, the workflow that matches invoices to orders; under the estimator, the workflow that drafts a first estimate. An org chart shows who reports to whom, and the plan adds what each role does and which part of that work AI prepares. One person owns the plan, and that person is an existing leader taking on a responsibility, not the head of a new department.

Placing AI on the chart is one part of planning a company’s use of AI. How organizations plan their use of AI sets out the whole method: plan it, develop the workflows, deploy them. This piece answers where AI sits.

Is AI a new department, a new role or a box on the chart?

AI is none of the three in a company of 10 to 200 people. AI is work that existing roles do differently.

  • Not a new department.A department owns a body of work. AI has no work of its own: every invoice, proposal and schedule it prepares already belongs to a team.
  • Not a new role.A role is a kind of job within a team, named for the work: intake, estimator, accounts payable. “AI” describes how a role does part of its work, so it sits inside the role, the way a spreadsheet does.
  • Not a box.A box on an org chart means a person, or a group of people, who report to someone. A box labelled “AI” claims a reporting line that does not exist and leaves every real role looking unchanged.

The question of whether to treat AI as a colleague or as a better way for your people to work is settled at more length in An AI employee or a more capable team?

A box for AI hides two things that matter.

Drawing AI as a team member with its own box hides which person decides and who owns the method. Those two facts are what make AI in a company safe to rely on.

  • Which person decides.A workflow prepares; a person decides. The draft estimate, the matched invoice and the reply to a customer each need a named person who approves them. On a chart where AI has its own box, the work appears to belong to the box, and nobody can see who signs off.
  • Who owns the method.Every workflow follows a written method: the steps, the rules and the examples of good work. Someone in the team that uses the workflow owns that method and keeps it current when the procedure changes. A box for AI suggests the method lives with the AI, when it lives with your people.

Put the workflows under the roles instead, and both facts are on the page.

Should AI report to someone?

AI does not report to anyone, because workflows are not people. People own workflows, and the ownership runs in two layers.

  1. One person owns the plan.One leader, by name, keeps the plan current, settles which team is next and runs a monthly review. In most companies under 200 people that is the head of operations, the chief of staff or the owner. Owning the plan is a responsibility added to that leader’s existing job. Who should own AI in a company your size? covers how to choose that person.
  2. Each workflow has an owner in its team.The owner is the person who knows the work best and keeps the workflow’s method current. The owner sits in the team that runs the workflow, under that team’s usual manager.

The reporting lines on your chart stay as they are.

Mark up your org chart in one sitting.

You mark up an org chart by writing the workflows under each role and an owner beside each workflow. Work through your current chart with this template.

  1. Start with teams.Circle each team on the chart. Work one team at a time.
  2. Name the roles for the work.Under each team, list its roles by what they do, not by who holds them.
  3. Write two or three workflows under each role.Pick work the role repeats every week and does from a known starting point.
  4. Write the owner of each workflow.One name per workflow: the person who keeps its method current.
  5. Write who decides.For each workflow, the role that approves what it prepares.
  6. Mark the work between teams.Where a workflow touches two teams, draw a line between them and name the team that owns it.
  7. Choose what comes first.Star one workflow per team to build first.

For each role, the entry reads like this:

  • Team:
  • Role:
  • Workflow 1:Owner: / Who decides: / Starts from:
  • Workflow 2:Owner: / Who decides: / Starts from:
  • Workflow 3:Owner: / Who decides: / Starts from:
  • Other teams this work touches:
  • Build first:

The work between teams is where most org charts go quiet. An AI org chart should show the work between teams covers that line in detail, and Add AI workflows to your chart of seats applies the same idea to a chart of seats.

One company, marked up.

Illustrative example.

Take a 130-person specialty food manufacturer with five teams: sales, customer service, production planning, quality and finance. The leadership team had discussed adding an “AI lead” box beside operations, and marked up the chart instead.

  • Customer service.The order desk role got two workflows: one that turns an emailed order into an order entry ready to check, and one that drafts replies to delivery questions. The senior order desk coordinator owns both methods. The person on the order desk approves every entry before it goes into the order system.
  • Quality.The quality technician role got a workflow that drafts the batch record summary from the day’s checks. The quality manager owns the method and signs every summary.
  • Finance.The accounts receivable role got a workflow that drafts reminders for overdue invoices, owned by the finance lead, with the accounts receivable clerk deciding which ones go out.
  • Between teams.The order entry workflow touches customer service and production planning. The chart drew a line between the two and named customer service as the owner.

The head of operations took ownership of the plan as part of the existing job. There was no new box. The order entry workflow was starred to build first.

What is different in a company of under 200 people.

Most advice about AI on the org chart is written for large enterprises, where a central AI team or a chief AI officer makes sense because thousands of people share platforms and rules. A company of under 200 people works differently.

  • The chart fits on one page.You can mark up every role at once, so the plan covers the whole company from the start.
  • The leader who owns the plan already knows every team.That leader can settle which team goes first in one conversation.
  • The people who own the methods are doing the work.The person who knows the order desk best is on the order desk. Ownership sits where the knowledge is.
  • You already pay for the AI.Workflows run in your company’s own ChatGPT, Claude, Copilot or Gemini, run by your own people. Nothing on the chart needs a new team to operate it.

If different teams are already using AI in different ways, How to manage AI across teams without everyone doing their own thing shows how the marked-up chart brings undirected use into one directed plan.

Where the marked-up chart lives.

A first marked-up chart can live on paper or in a document. The marked-up chart strains once several teams edit it and one workflow belongs to two teams. FullyPowered Planner is where the plan lives after that: you set out your teams, their roles and the work between them, and choose what to build first. Your colleagues add their own teams, and everyone sees their part of the same plan.

FullyPowered AI is a better way to plan your company’s use of AI, develop the workflows and deploy them. AI goes beside each role, and your people stay on the chart.