Module 1 — Foundations · Lesson 1.1
What Management Actually Is, Now
Why the job changed when AI started shipping the work
~12 min
What you'll learn
- Name the four primitives every era of management rediscovers
- Articulate what shifted in the manager's job once AI could ship work
- Explain why alignment, not throughput, is the new bottleneck
- Recognize the failure mode of running an AI-amplified team without explicit intention
Strip the word 'management' back and what is left is a verb: to handle, to direct, to aim. The Italians of the Renaissance called the discipline maneggiare — the art of getting a half-ton animal with a will of its own to produce a coordinated outcome under saddle. Five centuries later we use the same word for what a CEO does on Monday morning. The interface is different. The job is the same: hold an intention steady through noise, long enough for a group to actually produce it.
The four primitives every era rediscovers
Across cuneiform ration tablets, legion rolls, monastic horaria, factory time-and-motion studies, and modern OKR documents, four operations recur. Call them the primitives.
Direction. Naming the outcome the group is trying to produce. Without it, work fragments into individually rational but collectively pointless effort.
Allocation. Matching people, time, money, and attention to that outcome. The hardest of the four because every yes is also a no.
Feedback. Knowing whether the work is hitting the outcome — fast enough to course-correct, not learn at the post-mortem.
Consequence. Rewarding what worked, correcting what did not, removing what cannot be corrected. Without consequence, the other three decay into theater.
Every framework you have ever heard of — Sun Tzu, Drucker, Deming, Six Sigma, Agile, OKRs, Shape Up — is a different choreography of these four. The frameworks differ. The primitives do not.
What changed in the last three years
For most of the discipline's history, the binding constraint on output was human throughput. A team could only ship as much as it could write, design, or build by hand. Management was, in large part, a craft of squeezing more work out of a fixed labor pool — through scheduling, motivation, division of labor, and the steady removal of friction.
Generative AI broke that constraint — on the right work. Controlled trials find large gains on well-bounded tasks: writing time down about 40% with quality up (Noy and Zhang 2023), a coding task finished 56% faster with an AI assistant (Peng et al. 2023), consultants inside the AI's competence 25% faster at higher quality (Dell'Acqua et al. 2023). On the right task, a single contributor with a competent agent can produce in a day what used to take a team a week. But the gain is uneven, not a uniform multiplier: in a 2025 randomized trial, experienced developers working in their own mature codebases were actually 19% slower with AI while believing they were faster (METR 2025), and across a large industry survey a jump in AI adoption came with a small drop in delivery throughput and stability (DORA 2024). The bottleneck still moved. It is no longer how much the team can produce — it is whether what they produce is the right thing, in the right order, at a quality bar a customer will pay for.
That shift moves the manager's job decisively up the four primitives. Direction matters more, because on the work AI does accelerate, the same labor hour can create far more output — and far more drift if pointed at the wrong outcome. Allocation matters more, because attention is the only scarce resource left. Feedback matters more, because the gap between 'we shipped it' and 'it was wrong' now takes hours instead of weeks. Consequence still matters exactly as much as it ever did, which is to say it is the rate-limiting step on whether anything you learn actually changes behavior.
Alignment, not throughput, is the new bottleneck
The cheap mental model is to imagine AI as a faster pair of hands. The accurate mental model is to imagine AI as a junior employee who will faithfully execute the ambiguity in your instructions, including the ambiguity you did not realize was there. Hand it a task with only positive direction — 'build this' — and it will fill the unspoken space with its own priors, not yours. The output looks plausible. It is also, often, not what you actually wanted.
The practical consequence is that the parts of management most people used to consider 'soft' — clarifying intent, naming what is in scope, naming what is explicitly out of scope, deciding what 'good' looks like — have become hard load-bearing requirements. You can no longer compensate for vague direction by personally re-doing the work. The team will keep going at AI speed, in whichever direction the ambiguity pushes them, and you will discover the misalignment days or weeks later.
Kavanah is built around this premise. The KVN methodology — Know-How, Vision, Negation — is an explicit forcing function for the three axes where ambiguity hides. The whole product, from the way conversations become tasks to the way personas are scoped, is an attempt to make alignment cheap enough to do every day.
What this course is about
This is a project management course written for the moment we are in. It teaches the discipline as it has always been practiced — the four primitives, the cadence, the metrics — and grounds every part of it in the specific surfaces Kavanah provides. Each lesson is short. Each ends with a concrete action you take inside the product, and a metric you watch to see whether the action is working. By the end, you will have stood up a workspace, captured your team's standing intentions, instrumented a measurable operating rhythm, and routed the right work to the right people — some of whom may be AI Employees.
The course assumes no prior management experience and no prior Kavanah experience. It does assume you are interested in why each technique exists, not just how to click it. If you skip the why, the techniques become rituals — and rituals decay the moment the team you learned them on changes.
Set the frame for the rest of the course
- 1
This is your standing view of work in flight — the home base every lesson will return to.
- 2
Skim your KVN workspace charter
If it is empty, that is fine. Module 5 walks you through filling it in. For now, notice the three fields are there.
- 3
The agent is where most of your conversation-to-task automation will happen. We do not use it yet — just see where it lives.
What to watch from day one
- Stated direction per active project
- Does every in-flight project have a one-sentence outcome that the team can recite?
- Healthy signal: 100%. Less than 100% means at least one project is running on muscle memory.
- Direction-to-drift latency
- How long does it take to notice when an in-flight project starts producing work that no longer matches its stated outcome?
- Healthy signal: Hours, not weeks. In Kavanah the fast path is the KVN gate, which catches drift at the moment work is created rather than after it has been done — the agent's weekly report and the daily Morning Briefing summarize state, they do not judge it against your charter. For a project you suspect has already wandered, ask the agent to sweep it for false friends; that is an on-demand check, not something that runs on a timer.
Key takeaways
- ·Management is one verb — handle — applied to four operations: direct, allocate, feedback, consequence.
- ·AI removed throughput as the bottleneck. Alignment took its place.
- ·Ambiguity in your instructions becomes drift in your output, at AI speed.
- ·This course teaches the discipline and the Kavanah surface together; every lesson ends with an action and a metric.
The rest of the course is a tour of the four primitives — first in the abstract, then in the Kavanah surface, then in the metrics you use to know whether each is actually working. We start with the framework the product is built around: KVN.
Sources
- 1.manage (etymology)
Douglas Harper, Online Etymology Dictionary · etymonline.com · 2024
'Manage' derives from Italian maneggiare, 'to handle or control a horse,' from Latin manus, 'hand.'
- 2.Accounting in Proto-Cuneiform
Robert K. Englund · The Oxford Handbook of Cuneiform Culture (Oxford University Press) · 2011
The earliest proto-cuneiform tablets (Uruk, c. 3300 BC) are administrative ration and labor accounts — the 'cuneiform ration tablets.'
- 3.Tab.Vindol. 154 — Strength report of the First Cohort of Tungrians
Roman Inscriptions of Britain (Bowman & Thomas, eds.) · romaninscriptionsofbritain.org · c. AD 92–97
A Roman unit strength report (752 total, present/absent/sick) — the 'legion rolls.'
- 4.The Rule of St. Benedict
St. Benedict of Nursia · Project Gutenberg · c. 516
Prescribes an hour-by-hour daily schedule of office, labour and reading — the 'monastic horaria.'
- 5.The Principles of Scientific Management
Frederick Winslow Taylor · Harper & Brothers (Project Gutenberg) · 1911
The canonical source for factory time-study management.
- 6.Experimental evidence on the productivity effects of generative artificial intelligence
Shakked Noy, Whitney Zhang · Science 381(6654) · 2023
RCT: AI cut professional writing time ~40% and raised quality — evidence for large gains on well-bounded work.
- 7.The Impact of AI on Developer Productivity: Evidence from GitHub Copilot
Sida Peng, Eirini Kalliamvakou, Peter Cihon, Mert Demirer · arXiv:2302.06590 · 2023
A controlled coding task finished 56% faster with an AI assistant — a large gain on a clean, well-specified micro-task.
- 8.Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality
Fabrizio Dell'Acqua, Ethan Mollick, Karim Lakhani, et al. · Harvard Business School Working Paper 24-013 · 2023
Consultants inside the AI 'frontier' were 25% faster at higher quality; outside it, more likely to be wrong — the gain is task-dependent.
- 9.Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity
Joel Becker, Nate Rush, Beth Barnes, David Rein (METR) · METR (arXiv:2507.09089) · 2025
The countervailing finding: experienced developers were 19% slower with AI on real tasks while believing they were faster. The gain is uneven, not a uniform multiplier.
- 10.Announcing the 2024 DORA report
Google Cloud / DORA · cloud.google.com · 2024
A 25% rise in AI adoption was associated with small drops in delivery throughput and stability — individual output up, system alignment the new bottleneck.