GRAIL · Function papers
What does an AI-augmented operations function look like?
By Johan Grönstedt · Last reviewed
Judgment stays with the person. The operating picture stays current. This free nine-page position paper sets out how the operating day changes when the live picture, coordination rules and expert methods become shared.
An AI-augmented operations function shares a live operating picture, coordination rules and expert methods across the work. The agent layer keeps the picture current and supports coordination, while people retain judgment over exceptions, commitments, conclusions and interventions. Judgment stays with the person, and the operation stays current.
The operating day
A day in The operation's 2028 day
The operating day is built from live records rather than a delayed reconstruction. Leaders start with briefings for their roles, while the operating layer follows changes, active assignments, completed work and the weekly view.
Morning
Each leader receives a role-specific briefing.
When the plan moves
The scheduling layer recomputes options when work overruns.
During delivery
The delivery layer follows active assignments.
At completion
Completed reports receive a first quality review against the method.
The week
Unit heads receive a short operating review built from live records.
The division of work
What runs, and what stays with the person
The agent layer maintains the operating record and works within defined constraints. It builds capacity scenarios, proposes schedules, follows assignment dependencies, reviews completed work against the accepted method and prepares daily exception views. When conditions change, it recomputes options and makes the live picture available to the role responsible for the decision.
The person remains responsible for trade-offs, protected commitments and customer-sensitive moves. Interpretation, corrective action, regulated conclusions, material advice and final sign-off also stay with people. The operating layer supplies current context and structured options; it does not take over the judgment attached to hiring, priorities, customers or formal conclusions.
This split carries the record with the work. It also turns expert methods into shared operating rules, so scheduling constraints, accepted quality examples and escalation thresholds can guide the function rather than remain private craft. Across the wider function, the agent layer can prepare supplier work packages, check qualifications, track responses and issue approved routine orders or reminders. It can produce a daily exception brief, compare relevant peers and record approved follow-up. It can also mine delays, rework and incidents, group recurring causes and draft controlled experiments. Supplier choice, negotiation, validating causes and choosing the hypothesis remain with people.
| Process | What the agent layer does | What stays with the person |
|---|---|---|
| Capacity and resource planning | Builds scenarios from backlog, role profiles and planning rules; with live access, maintains demand and capacity views by skill, site and week. | Hiring, subcontracting and priority trade-offs. |
| Scheduling and dispatch | Proposes the best qualified resource within travel, SLA, skills and working-time constraints; replans as conditions change. | Exceptions, customer-sensitive moves, overtime and protected commitments. |
| Project and assignment delivery | Maintains the assignment record, drafts updates, checks dependencies and flags scope, effort or margin drift. | Interpretation, customer commitments and corrective action. |
| Quality control of delivered work | Checks each deliverable against the method, contract, template and accepted examples; identifies omissions and unsupported claims. | Regulated conclusions, material advice and final sign-off. |
| Incident handling and delivery reporting | Structures the report, retrieves similar cases, checks required actions and drafts internal or customer updates. | Severity, safety decisions, root-cause judgment and external communication. |
Operating convictions
Six things GRAIL believes
The monthly report is too late to run the operation.
Governance can stay monthly.
The floor is faster coordination. The ceiling is equal attention.
Saving time on status collection is useful, but it is not the main prize.
Coordination rules are company infrastructure.
The best scheduler's constraints, the quality specialist's accepted examples and the delivery manager's escalation thresholds should not remain private craft.
The record must move with the work.
No operating layer can warn early from stale schedules, late time records or disputed definitions.
Augment the judgment and protect the physical work.
Travel, equipment, human dexterity, customer conversations, regulated conclusions and safety calls remain real constraints.
Role redesign begins before capacity appears.
Schedulers need to become exception managers.
These six beliefs concern how work is delivered and controlled, rather than taking a position on technology. Every tool inherits the cadence, definitions and decision boundaries the leadership team chooses.
Get the paper
Read the full position paper on how an AI-augmented operations function runs while judgment stays with the person.