01From objectives to operating routines
Translate an agreed service objective into a visible completion condition and recurring work. Distinguish the result sought from the tasks used to pursue it. In Willow Document, “send a complete, checked pack” requires intake, preparation, checking and dispatch, not simply a high number of messages. Explain how a routine supports a strategic choice while leaving decisions about the service’s overall direction to the appropriate authority.
02Process mapping: inputs, steps and outputs
Read a simple completed process map from request to delivery. Identify the input needed to begin, the sequence of steps, a decision point and the output expected by the next role. Follow an incomplete brief returning to intake rather than silently moving downstream. Distinguish working time, waiting and rework; define the start and finish of the process so that two observers are not describing different flows.
03Roles, handoffs and decision rights
Explain who performs a step, who checks it and who can resolve an exception. A handoff needs an expected output, required information and a receiving role, not merely a sent message. In the fictional service, preparation cannot infer a missing delivery requirement. Compare a clear acceptance condition with a vague instruction to “take care of it”, and recognise when an unresolved issue should be raised to an authorised decision-maker.
04Capacity, workload and queues
Compare incoming work, available time, required competence and existing commitments before accepting more requests. Distinguish effort from elapsed delivery time, and locate a queue without assuming its cause. In Willow Document, several completed drafts await one checking role; starting more drafts does not itself clear that queue. Explain a completed choice to limit starts or adjust commitments, acknowledging dependencies and the limits of the case information.
05Quality standards and checks at the right point
Define quality through an explicit acceptance condition rather than a general request to be careful. Read a fictional checklist covering required sections, correct destination and a final completeness check. Separate a check that detects a defect from a change that prevents recurrence. Explain why rushing a handoff can move missing information downstream, and why a high output count must be read alongside completeness and rework observations.
06Problem-solving and operational indicators
Describe an observable problem, separate possible causes from verified observations and interpret a small proposed test of a process change. Connect indicators to the work: incoming requests, waiting at checking, rework and delivery completion each need a clear definition and observation period. Compare like with like before drawing a conclusion. In the case, a completed intake clarification test illustrates reasoning, not proof of a universal cause or guaranteed improvement.
07Daily coordination and escalation
Interpret a short coordination routine that makes priorities, blocked work, capacity conflicts and decisions visible. Distinguish information-sharing from resolving an issue with an owner and a next check. Willow Document’s review identifies a missing brief and a checking queue; explain which role can act and which conflict requires escalation. A dashboard supports a conversation but does not decide priorities, remove constraints or replace authority.
08Continuous improvement and follow-through
Follow a completed improvement cycle: name the problem, propose a limited change, observe defined signals and decide whether to retain, revise or stop it. Check effects on the whole process rather than celebrate a faster individual step that creates downstream work. In Willow Document, a clearer intake requirement is reviewed alongside waiting and rework. Record the responsible role and review point; distinguish a local operating adjustment from a question that should reopen strategic scope.
Original editorial curriculum for a new standalone self-paced course. Strategy concerns direction and choices; operations concerns execution and reliability. The two courses are complementary, not interchangeable.