Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
You arrive at the morning meeting with three expansion requests, each described as the priority. Scheduling needs support staff, follow-up messaging needs the same team, and a contact-correction service is waiting. The committee might approve each request separately and then discover that available staff hours support only one. The decision unit must therefore be the combined service portfolio. Your task is to expose dependencies on shared people, information, and channels, then allocate capacity while protecting current commitments. Start with a practical question: which work will be delayed tomorrow if we approve this today? The World Health Organization's digital implementation investment guidance places planning within system needs and resources. The worksheet developed here is a teaching method for applying that perspective, rather than an official allocation formula.
Draw the portfolio at two levels. At the top, name services users recognize: changing an appointment, receiving confirmation, and correcting contact details. Underneath, name the resources supporting the work: a staff member who verifies a request, a duty holder receiving a message, a scheduling record, and an alternative contact channel. Connect each service to its resources. A repeatedly used resource suggests competition, but the connection alone does not establish a bottleneck. Two teams may use the same database without exhausting its capacity, while both depend on one employee authorized to approve corrections. Ask how much time the resource has, when it is available, and which skills it actually provides. One hour of general support is not interchangeable with an hour requiring a specific review authority, even if the finance report gives them the same label.
Build the capacity budget from actual work. Estimate intake, checking, handling, and recording time, and include rework observed in the sample. Make training, meetings, and leave visible before allocating hours to services. Use mean handling time for the first estimate, then inspect cases requiring substantially longer work. Two services can have the same mean while one accumulates long tasks near the end of a shift. Check whether demand and staffing occur at compatible times as well. Ten spare evening hours will not solve work the institution needs its authorized team to review in the morning. Maintain a column describing uncertainty: sample size, differences in employee experience, and changing weekday demand. Those qualifications make the estimate reviewable when better operating evidence arrives, rather than turning an initial estimate into a permanent staffing rule.
After reconciling demand, establish an order for tradeoffs. Start with commitments whose suspension would leave open work or users without an alternative. Next consider activities preventing defects in other services, such as correcting destinations used by messaging. Then compare optional additions by expected benefit, evidence, and reversibility. Record why each item receives its position, because priorities depend on the situation. A small training investment may improve three services more than sending additional messages. Yet moving staff into lengthy training could also leave a shift without a receiving team. A useful decision considers investment timing and continuity together. Present sequential implementation, reduced scope, and a deferral with an operating alternative. Those concrete choices reveal what funding would change, whereas an unrestricted request for more resources leaves the underlying decision unresolved.
Make review responsive to changed assumptions. In the Muscat exercise, suppose contact correction rises from eight to eleven hours. Base demand becomes twenty-nine hours, and the smaller expansion adds another two. The combined thirty-one exceeds the available thirty by one hour, so the decision needs reconsideration. Options include reducing the test, changing its timing, or supplying demonstrably qualified capacity. A scheduled weekly review helps, but an established shortage may need action before that meeting. Give operators visible warning measures: the age of the oldest request, the count of unassigned tasks, and time spent on rework. These reveal different aspects of pressure. Check their definitions so that an increase can be distinguished between genuine demand and a failure to record task closure. Evidence should explain a change in the operating choice, not merely decorate a dashboard.
Write a portfolio decision on a page a duty team can use. Name the function allowed to expand, its scale, and its start time. State the capacity reserved for existing work, the reserve, and who may change either. Link each adjustment to an observable event. The trigger might be the number of older requests reaching a threshold the institution chose for its pilot, or the absence of an essential authorized role. Name the person recording the event and the person deciding the response; these may differ where review requires separation. Then rehearse the page in a brief meeting: an operator presents one changed fact and a colleague explains the next action. Different answers reveal an ambiguous instruction or conflicting authority. Repair that problem before enlarging the worksheet or buying a new management tool.
Weekly averages can conceal a daily conflict. Suppose ten hours of shared work arrive on Sunday morning while the plan spreads hours evenly across five days. The worksheet shows a weekly reserve, yet users experience a growing queue before qualified staff become available. Redistribute demand by day and task, then compare capacity at matching times. You could move a non-urgent report review, adjust a shift through institutional arrangements, or change intake timing. Choose an implementable change and record its effect on displaced work. Rescheduling may succeed without extra hours, or demonstrate that demand cannot move. Arrival and completion records should distinguish those explanations. Ask an operator to explain one peak before treating it as a permanent pattern across every week.
Allocation also needs a way to resolve disagreement. Each sponsor may claim that losing hours threatens safety, leaving the discussion trapped in general assertions. Ask each to identify one delayed task, the affected person, and the available alternative. The qualified safety role considers potential health significance; the operating manager establishes what known capacity can deliver. Escalate a conflict outside their authority to the appropriate decision holder. Record a minority view and the evidence it requests. Visible disagreement is preferable to silent agreement concealing an important condition. Distinguish reconsideration based on new information from repeating the same objection without evidence. This protects committee time while preserving a way to reopen a decision whose foundation has actually changed.
When presenting the portfolio, make alternatives comparable. Hold the estimation period, demand volume, and kind of staff hours constant across columns. Show fixed work once, then add what changes under each option. Separate initial preparation from recurring operation. A small setup investment may reasonably relieve a short surge, but comparing one week's cost directly with preparation serving several months obscures judgment. Label what was observed, what was estimated from a sample, and what remains unknown. Rather than bury uncertainty in a footnote, show how the preferred option changes with demand or handling time. The decision holder can then choose a smaller test or larger reserve from an explicit consequence instead of a general impression that the presentation sounds confident.
Lesson summary
Prioritizing a service portfolio sharing one team.