This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 7 · Lesson 7.5 · 12 min

Designing Your Agentic Org Chart

Map human roles and AI roles side by side so everyone knows who does what, who approves, and who is accountable.

Module 7
Your AI Department

Subagents and teams that check each other's work

Bruno Ashford
Bruno Ashford · Module 701 / 13
The problem
You would never ask one employee to prospect, write, do the books and proofread in the same meeting. Stop asking your AI to.
Bruno Ashford
Bruno Ashford · Module 702 / 13
7.1 One agent per role

What a subagent is

A specialist with its own instructions, context and tools.

  • Starts with a clean context
  • Reads its own job description
  • Uses only the tools you allow
  • Returns a summary, keeps the noise
Bruno Ashford · Module 703 / 13
The three-question test

Does this task deserve a specialist?

  1. 1Repeats weekly?Recurring work earns a role
  2. 2Different mindset?Writing versus checking
  3. 3Lots of noise?Research and data crunching
Bruno Ashford · Module 704 / 13
7.2 The file

Anatomy of a subagent

FieldWhat it does
nameUnique id, lowercase with hyphens
descriptionWhen Claude should hand work to it
toolsAllowed tools, comma separated
modelsonnet, opus, haiku or inherit
bodyThe job description in plain English

Project agents: .claude/agents/. Personal agents: ~/.claude/agents/.

Bruno Ashford · Module 705 / 13
7.2 Least privilege

Only the tools the role needs

Leave tools out and the agent inherits everything.

  • Analyst: read, search, write reports
  • Researcher: read, web search, web fetch
  • Reviewer: read and search only
  • Nobody gets send by default
Bruno Ashford · Module 706 / 13
7.3 The reviewer
Writing and checking are different jobs. Give them to different agents.
Bruno Ashford
Bruno Ashford · Module 707 / 13
The loop

Write, review, fix, review

  1. 1WriteSpecialist drafts
  2. 2ReviewRead-only checklist
  3. 3FixEvery issue addressed
  4. 4Review againFixes create new mistakes
Bruno Ashford · Module 708 / 13
7.4 Parallel work

Independent views in minutes

Same question, several specialists, no groupthink.

  • Same inputs for every agent
  • Same output format
  • Read the disagreements first
  • Save it for decisions that matter
Bruno Ashford · Module 709 / 13
Accounting practice task map (illustrative case)

23 recurring tasks, sorted

6human only
14agent drafts, human approves
3agent alone
Bruno Ashford · Module 710 / 13
7.5 Org chart

Every agent has a human owner

AgentJobOwnerApproval
sdr-researcherLead researchSales leadNone, internal
copywriterOutreach draftsMarketingHuman sends
data-analystWeekly numbersOwnerNone, internal
reviewerChecks client workOperationsBlockers stop it
Bruno Ashford · Module 711 / 13
Project

Your first AI team

Three to five specialists, one real workflow.

  • Fill the org chart worksheet
  • Create agents with /agents
  • Restrict every tools line
  • Reviewer is always the last step
Bruno Ashford · Module 712 / 13
Recap
A department is not more AI. It is clear roles, clean context, limited tools and a human who owns every result.
Bruno Ashford
Bruno Ashford · Module 713 / 13
01 / 13

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1List the recurring work, not the job titles

Start from tasks, not people: research leads, draft follow-ups, prepare the weekly report, check proposals. Pull them from the Weekly Time Map you built in Module 0.

2Assign each task to human, agent or both

For each task decide: human only (relationships, negotiations, final decisions), agent drafts and human approves (most client-facing work), or agent alone (internal research and data prep). Most small businesses end up with the middle category for 60 to 70 percent of tasks.

3Give every agent a human owner

Every subagent has one named person who owns its instructions, reviews its output quality and decides when it changes. No owner, no agent. This one rule solves most accountability questions.

4Fill the worksheet

Use the Agentic Org Chart Worksheet from the materials. Ask Claude to prefill it from your business context, then correct it yourself.

Prompt for Claude
Using CLAUDE.md, my subagents in .claude/agents/ and my weekly time map, fill in materials/07-agentic-org-chart-worksheet.csv for my business. One row per role. Mark clearly where you are guessing. Then list any recurring task that has no owner.
5Share it with the team

Put the finished chart where the team can see it and commit the .claude/agents/ folder with the project so everyone uses the same specialists. When someone asks who writes the follow-ups, the answer is on one page.

Here is a question that makes owners go quiet: if an AI agent sends the wrong number to a client, whose fault is it? If you cannot answer in one sentence, you do not have an AI department. You have a collection of experiments.

The agentic org chart is a simple table. Every subagent has a human owner, a clear job, a list of allowed tools, an approval step and a measure of success. It is the document that turns clever prompts into a department you can manage.

Key points

  • Map tasks first, then decide human, agent or both.
  • Every agent has one named human owner.
  • Most client-facing work is 'agent drafts, human approves'.
  • Share the chart and the agents folder so the whole team works the same way.

Avoid

  • Designing agents around job titles instead of recurring tasks.
  • Leaving an agent with no human owner.
  • Moving client-facing tasks to 'agent alone' before months of evidence.
Real-world example: an accounting practice

A seven-person accounting practice mapped 23 recurring tasks. Six stayed human only (client meetings, advice calls, sign-offs). Fourteen became agent drafts, human approves, including engagement letters and document chasers. Three became agent alone: data extraction from bank statements, deadline reminders for the team, and the weekly workload report. Each of the four subagents got a named owner, and the managing partner finally had one page showing who did what.

Bruno Ashford Subscribe