The next morning, one adviser was unexpectedly absent. Sana did not leave the previous capacity estimate on the board as if nothing had changed. She reviewed the bookings, contacted affected visitors where appropriate and arranged the available options. Eli explained the reduced capacity to new arrivals. Nobody was promised a fourteen-minute wait because fourteen had appeared in an earlier average.
A visitor asked why an appointment had been called before his walk-in number. Eli showed him the explanation of reserved periods and checked his place in the walk-in order. The visitor was still disappointed about the wait. Understanding the rule did not require him to enjoy it.
Another visitor needed to sit where the board was not visible. Eli agreed how that person would be called without losing their place. No private reason appeared beside the queue number. The arrangement was small, specific and checked with the person using it.
At the end of the morning, Sana kept the unresolved visits in the record and the staff absence beside the figures. She did not add extra appointments for the following week. The team would continue the limited trial, follow the unfinished groups and assess the clearer communication under comparable conditions. That was a decision, not a declaration that the queue had been solved.
To close your own first review, write one page: the service boundary, the queue and appointment rules, usable capacity by period, the counts including people who leave, and the next decision with its review date. State what you do not yet know. Keep an accountable person attached to the review so that a trial does not become permanent simply because nobody revisits it.
Before leaving, Eli removed the draft “Please be patient” sign from the counter. In its place was the agreed explanation, readable from the waiting area, with a way to ask for help. The queue had not vanished. People still had other places to be. But the team had stopped making them guess which promise the counter was trying to keep.
### Sources and reading note
Sources checked on 9 November 2026. They support only the limited concepts cited. All Cedar figures, dialogue, exercises and trial outcomes are original fictional illustrations, not measured performance or forecasts.
[1] MIT OpenCourseWare, *M/M/1 Queue*, 2.854/2.853 Introduction to Manufacturing Systems, Fall 2016. Used for the distinction between queue time and total time, not for applying its model to Cedar: https://ocw.mit.edu/courses/2-854-introduction-to-manufacturing-systems-fall-2016/927056a1af54772a587fd84ad4951e71_MIT2_854F16_Mm1Queue.pdf
[2] GOV.UK Service Manual, *Using performance data to improve your service: an introduction*, published 23 March 2016, updated 6 April 2022: https://www.gov.uk/service-manual/measuring-success/using-data-to-improve-your-service-an-introduction