Practical guide
AI fluency for operations managers: plan a service handoff
Use a fictional queue to distinguish incoming work, available capacity and the responsibilities carried into the next shift.
An operations manager can practice AI-assisted planning by producing a service handoff that reconciles work and capacity. This fictional desk-support exercise uses a small queue, explicit task sizes and a changing arrival assumption. It concerns continuity between shifts, not staffing decisions about named employees or a forecast of real productivity.
Define the unit of work
Count effort in the same units before comparing a queue with available capacity.
The fictional desk has four standard requests needing one work unit each and two complex requests needing three units each. The starting queue therefore contains six requests but ten work units. The morning shift has eight work units of available capacity. Treat those task sizes as exercise assumptions, not observed handling times.
Ask AI to build the queue summary and show the arithmetic. A statement that eight units can clear six requests would confuse requests with effort. Record whether partially completed complex work can carry into the next shift; the initial exercise allows it only with a written handoff.
Plan the handoff rather than promising an empty queue
A capacity shortfall needs an explicit residual workload and ownership.
With ten units of starting work and eight units available, at least two units remain if no new work arrives. That is an arithmetic balance, not a scheduling promise. Which requests remain depends on the sequence and any constraints on partial completion. State the selected sequence and its consequence.
One illustrative plan completes four standard requests and one complex request, using seven units. The last unit begins the remaining complex request, leaving two units for the next shift. Mark that request as in progress and identify the completed step so another worker does not repeat it.
Add arrivals without hiding the assumption
New demand changes the handoff even if the team completes the original plan.
Now introduce three new standard requests during the shift. Total work rises from ten to thirteen units. With the same eight-unit capacity, the residual becomes five units. Do not describe the larger queue as evidence that the team slowed down; the exercise changed incoming demand.
Use separate fields for opening work, arrivals, completed work and closing work. Ask AI to reconcile them and explain any mismatch. Keep estimates for future arrivals in an assumptions column, separate from the three arrivals supplied in this case. Do not make an invented probability look like a measured service forecast.
Preserve service constraints in the sequence
An arithmetically feasible plan can still miss the most important deadline.
Add a fictional constraint: one complex request must reach a review step before noon. Reconsider the sequence and determine whether the constraint changes which standard requests wait. If review availability is unknown, flag it instead of assuming the review happens immediately after preparation.
Write the next action, owner role and prerequisite for the priority request. AI can propose options, but it cannot authorize overtime, contact customers or change a service commitment. Keep this as a planning simulation. If a plan requires additional capacity, label the authorization needed rather than presenting it as available.
Deliver a reproducible shift note
The next shift needs the remaining work and its state, not just a summary of effort.
Include the opening balance, new arrivals, completed units, remaining requests and the partially completed complex item. State which facts are supplied and which task-duration assumptions need validation before real use. A short note is sufficient if it preserves the balance and the handoff instructions.
To review the exercise, remove permission for partial completion and ask the worker to revise the sequence and residual. Look for an explanation of why unused capacity might remain. The useful capability is constraint-aware planning and clear handover, not a promise that AI can eliminate every queue.
Sources and scope
NIST: AI risk management. Skills England: workplace AI foundations.
These references provide background, not validation or endorsement of this exercise. The case details, calculations and suggested review questions are original instructional material. Use them to discuss observable work, not to infer customer outcomes, professional credentials or performance in every setting. Before adapting the exercise, confirm the relevant facts, approved tools, data permissions and decision owners. If you change the case, revisit the expected answers and checks as well. These examples describe practice tasks, not a promise that a particular product includes the fictional features.
Sources: [1] [2]
Sources
- 1.AI RMF Core · NIST
- 2.AI foundation skills for work benchmark · Skills England