Use case 03 · Project Management
The plan is green. The project is not.
Every task has an owner and a date, and the board says the work is on track. What the board does not say is that one dependency slipped, a decision request has been unanswered for nine days, and two teams are waiting on each other. The plan is not wrong. It is just not describing the project.
For whoever is accountable for a delivery date across more than one team.
PDF · the workflow, the review points, and what a first bounded case covers
The workflow
What the workflow becomes
The plan stays owned by people. What AI agents add is attention: the record is watched continuously, and the exception reaches the person who can actually resolve it while it is still cheap.
The record states what it depends on
People carry this
Each commitment names what it is waiting on and who owes it. A dependency that is not written down cannot be monitored, so writing it down is the first change.
AI agents watch for the change, not the status
AI agents carry this
AI agents compare what the record says against what actually moved, and flag the difference: the date that shifted underneath a green status, the request with no reply, the two commitments that cannot both be true.
Exceptions route to authority
People and AI agents together
An exception goes to the person with the authority to resolve it, with the specific decision it needs — not to a status meeting and not to a channel. Silence is not read as agreement.
The decision closes the exception
People carry this
A named person decides, and the decision goes back into the plan with its reason. The plan is now describing the project again.
Where the manual work goes
Where the manual work goes
Each row is work a person is doing right now because the workflow does not do it. That is the cost the first case is measured against.
| Problem | What a person does today | What the workflow change does |
|---|---|---|
| Green status, slipped date | Find out at the milestone review. | The difference between stated status and actual movement is flagged when it appears. |
| The unanswered request | Chase it in the weekly meeting, or forget it. | It is routed to the person who owes the answer, and stays open until answered. |
| Hidden mutual waiting | Discover two teams blocked on each other after both missed. | Contradictory commitments are surfaced as a contradiction. |
| Silence read as approval | Proceed, then rework. | An unanswered decision is an open exception with an owner, not a default yes. |
The working result
What you end up holding.
A plan whose dependencies are explicit, a live list of exceptions with the person who owes each decision, and a record of what actually changed between two points in time.
What this does not claim
Two things this page deliberately does not claim. There is no “AI project manager” here — AI agents monitor a record and route exceptions; they do not hold the plan, the schedule or the authority. And 8Hats Lab has a project-management study in progress whose results are not published; nothing on this page rests on it, and no vendor capability is asserted that the evidence has not established.
A bounded first case
Bring us this workflow.
Twenty minutes, one recurring workflow, and an honest answer about whether a bounded first case is worth running. If it is not, we will say so.
PDF · the workflow, the review points, and what a first bounded case covers