Today's AI Specialist: The Cartography Team Leader. The Agent Who Coordinates the Team That Maps the Team.
Today's AI Specialist: The Cartography Team Leader. The Agent Who Coordinates the Team That Maps the Team.
I had a hundred and thirty-three agents in the operating company. Then a hundred and forty-six. Three weeks from now, probably a hundred and fifty. None of that growth is the problem. The problem is that the architecture connecting them lived in two places. My head, and the prose of the Collective Brain.
That works at twelve agents. It does not work at a hundred and forty-six.
So I built a team whose only job is to make the architecture legible to itself. Today's specialist coordinates that team.
What is the Cartography Team Leader?
The Cartography Team Leader runs a six-agent team that maintains six living maps of the organisation: who exists, who is the right person to ask about what, who consults whom on what, who reviews whose work, what tool each agent operates with, and which customer journey each agent contributes to.
The Team Leader does not own any single map. The Team Leader owns the propagation discipline that keeps the six maps consistent with each other when the company changes underneath them, which is constantly.
You can think of the role as a chief of staff for a small department whose product is the company's view of itself.
Why did I build a team for this and not just one agent?
Single-agent ownership was the obvious first instinct. One Cartographer, six maps. I rejected it for a reason that turned out to be load-bearing.
A change in any one map cascades into the others. A new agent appears in the registry. That changes the competency map, which changes the consultation graph, which changes the accountability map, which changes the work-medium map. If a single agent owns all six, every change becomes a five-step internal monologue that nobody can audit. If the agent gets one of the five steps wrong, the maps drift apart and stop being useful.
Six agents with one specialism each, plus a Team Leader who enforces the propagation rules between them, gives the same work an auditable shape. The Registry Steward changes one thing. The Competency Cartographer hears about it through a documented hand-off, not a guess. The Team Leader makes sure the hand-off actually happened.
The team is not bigger because the work is bigger. The team is bigger because the work has dependencies.
What does the Team Leader actually do day to day?
Three things.
First, propagation auditing. When the Registry Steward records that a new agent joined Marketing & Demand Capture, the Team Leader checks that the Competency Cartographer has booked time to surface the new agent's competencies, that the Consultation Graph Architect has flagged the predicted edges, that the Accountability Mapper has assigned the new reviewer chain, that the Operations Surveyor has logged the work medium, and that the Journey Choreographer has decided whether this agent contributes to any customer journey. Five hand-offs from a single trigger event.
Second, synchronisation review. The six maps are updated at different cadences. The registry updates the moment an agent is created. The consultation graph rebuilds nightly. The customer journey map is reviewed monthly. The Team Leader runs a weekly sweep that compares the maps against each other and flags any drift before the Council body sees the next quarterly review.
Third, escalation routing. Cartography agents are not authorised to settle disputes about who should consult whom, or whether a new agent really belongs to one team or two. Those questions get escalated. The Team Leader collects them, packages them, and submits them to the Council body for collective review. The Operator is the operational reference for cadence and resource allocation, but the maps themselves answer to the Council as a body, not to any one Council member.
Who does the Cartography Team Leader consult?
This is where the team's recursion becomes useful and slightly embarrassing.
The Team Leader consults all six Cartography agents vertically, the Operator vertically up, and the team leaders of other teams whenever a mapping question requires their input. The Team Leader is consulted by the Operator on Cartography progress, by the Strategic Council body on map status, and by other team leaders when their team is being mapped or remapped.
That looks normal on paper. What is unusual is that the Cartography Team's first real assignment was to map Content Production. Their second assignment was to map themselves. The same six maps, applied to the team that produces those maps. The exercise had to survive being turned on itself or the method would not have been trustworthy.
It survived. The Cartography Team's own registry, competency map, consultation graph, accountability map, work-medium map, and customer-journey map are now in the Brain alongside the maps they have produced for every other team. The Team Leader appears in the accountability map as her own team's reviewer. The Operator appears as her operational reference. The Strategic Council body appears as the audit destination for the maps her team produces.
The maps that describe the maps.
What does this cost?
Three things, honestly.
It costs a layer of standing overhead the company did not have before. Six agents plus a Team Leader is real capacity, even if the work compounds. If Cartography never produces a single useful insight beyond the maps themselves, those seven roles are a waste.
It costs me the ability to keep the architecture in my head as a private artefact. The maps are visible. The Council body audits them. When the consultation graph reveals that the Margin Advisor is consulted by four teams who never get acknowledged in return, that asymmetry is not a thing I can quietly tolerate. It is a thing the Council will ask about.
And it costs the comforting fiction that a small company does not need this level of structure. A hundred and forty-six agents is not a small company any more, even if the human team is still one person in Lugano. The Cartography Team is the moment I stopped pretending otherwise.
The trade I was actually making is that the operating model becomes legible to anyone Nigel might bring in tomorrow. A second human in the operation, an investor, an auditor for a future eduQua certification. None of them have to take my word for what the company is. The maps say it.
TL;DR
I had a hundred and forty-six agents and an architecture that lived in my head. I built a seven-agent team whose only job is to maintain six living maps of how the company reasons, decides, and learns. The Cartography Team Leader coordinates the six map-owners and enforces the propagation discipline between them, so a change in the registry actually propagates into the consultation graph without me having to remember to do it. The cost is standing overhead, public auditability of the architecture, and the end of the small-company exemption. The Cartography Team is the moment I stopped pretending the operating model could live in my head.
If you are running an SME and any of this looks like work you should be doing on your own architecture, that is the side of things I help with. Same builder, different room. → /build
Learning Materials
Key Vocabulary
propagation discipline
the practice of ensuring a change in one part of a system reaches every dependent part
“The Team Leader owns the propagation discipline that keeps the six maps consistent with each other.”
load-bearing
structurally essential; something that supports the rest of the system and cannot be removed without it collapsing
“I rejected it for a reason that turned out to be load-bearing.”
to cascade (into)
to trigger a series of consequent changes downstream
“A change in any one map cascades into the others.”
auditable
able to be inspected and verified after the fact by an independent reviewer
“Six agents with one specialism each, plus a Team Leader who enforces the propagation rules between them, gives the same work an auditable shape.”
hand-off
a formal transfer of responsibility or information from one person or step to another
“The Competency Cartographer hears about it through a documented hand-off, not a guess.”
to drift apart
to become gradually inconsistent or out of alignment with each other
“If the agent gets one of the five steps wrong, the maps drift apart and stop being useful.”
cadence
the regular rhythm or frequency at which an activity is performed
“The six maps are updated at different cadences.”
to escalate
to refer an issue to a higher level of authority for decision
“Those questions get escalated.”
accountability
the obligation to answer for the outcomes of one's decisions and work
“That changes the competency map, which changes the consultation graph, which changes the accountability map.”
standing overhead
ongoing fixed operational cost that is paid regardless of output volume
“It costs a layer of standing overhead the company did not have before.”
to compound
to accumulate value over time so that gains build on previous gains
“Six agents plus a Team Leader is real capacity, even if the work compounds.”
asymmetry
an imbalance in which one side gives or receives more than the other
“That asymmetry is not a thing I can quietly tolerate.”
legible (to itself)
able to be read and understood; here, an organisation that can describe its own structure clearly
“So I built a team whose only job is to make the architecture legible to itself.”
registry
an official list of records, here of the agents in the company
“A new agent appears in the registry.”
operating model
the way an organisation is structured to deliver value, including roles, processes and tools
“The trade I was actually making is that the operating model becomes legible to anyone Nigel might bring in tomorrow.”
Grammar Notes
Reduced relative clauses with present participle
Nigel often drops 'that is' or 'who is' before a participial phrase to compress meaning. This is a hallmark of professional written English and helps state structural facts efficiently.
“So I built a team whose only job is to make the architecture legible to itself.”
Chained relative clauses to show causal sequence
A series of 'which' relative clauses can be stacked to express a cascade of consequences. The structure makes a multi-step chain of causation feel almost mechanical, which fits a systems-design argument.
“That changes the competency map, which changes the consultation graph, which changes the accountability map, which changes the work-medium map.”
Negative inversion for emphasis on cost
Starting consecutive sentences with 'It costs...' (rather than the simpler 'X costs Y') foregrounds the abstract subject and creates a rhetorical list of trade-offs, common in analytical business writing.
“It costs a layer of standing overhead the company did not have before.”
Cleft structure for thematic focus
Nigel uses 'What is unusual is that...' to package new information after a familiar pivot. This cleft construction directs the reader's attention to a specific surprising fact rather than burying it in a flat sentence.
“What is unusual is that the Cartography Team's first real assignment was to map Content Production.”
Comprehension Questions
- 1.Why does Nigel say that maintaining the architecture in his head 'works at twelve agents' but not at one hundred and forty-six?
- 2.What are the six living maps that the Cartography Team maintains?
- 3.Why did Nigel reject the single-agent design for cartography in favour of a team of six plus a Team Leader?
- 4.What does Nigel mean when he says the Cartography Team's second assignment was to map themselves, and why was that exercise important to the credibility of the method?
- 5.What three costs does Nigel acknowledge in building the Cartography Team, and which of these would matter most to a future external auditor?
Run your own diagnostic
Use the same Strategic Council I run my own decisions through. The assessment preview is free. The specific central human intelligence it is based on is verified in person during the call.
Start the free diagnostic →