Using the shoulder season for the work that never fits
The weeks either side of peak are the only time a seasonal business can change anything. Most of them are spent recovering instead. Turning quiet periods into planned improvement work also depends on initiative; this guide develops that idea.
Every seasonal operator knows the feeling of arriving at the shoulder season with a list of things that should have been dealt with during the summer, and reaching the end of it having completed almost none of them. The quieter-season work described here benefits from basic project management disciplines.
The reason is usually not laziness. It is that the list exists in fragments — in people's memories, in complaint records, in half-finished conversations — and assembling it takes energy that is in short supply at exactly that point in the year.
Keep the list during the season, not after it
The discipline that changes this is trivially simple and rarely done: capture items as they occur, in one place, throughout the busy months.
The capture format should be minimal — one line, and who noticed it. Anything requiring a form will not be filled in during peak season. A shared note, a physical book at the desk, a channel in whatever messaging tool the team already uses; the medium matters far less than the fact that it is single and always available.
A defect noticed in July and written down in one line will be fixed in October. The same defect noticed and remembered will not be, because by October it has been absorbed into how the building simply is.
Sort by what the season made impossible
The shoulder list should be prioritised by a specific criterion: what can only be done when the property is empty or quiet. That is the comparative advantage of the period and the only work that genuinely cannot be scheduled elsewhere.
- Anything requiring a room, a floor or a facility to be out of service for more than a day.
- Work that is noisy, dusty or disruptive across a wide area.
- Process changes needing everyone in the same room for an afternoon.
- Re-measurement of standard times, which requires unhurried observation.
- System changes and migrations, which require a period where mistakes are survivable.
Work that could have been done during the season should generally not consume shoulder weeks, and if it is consuming them, that is a finding about capacity during the season rather than about the shoulder.
Treat process work as a real project
Intentions to improve a process rarely survive contact with the shoulder season, because improvement work has no deadline and everything else does.
Give it the same handling as physical work: a named owner, a defined output, a date. Rewriting the handover format is a project with a deliverable. Reviewing the previous season's cover log is a project with a deliverable. Without that framing, both get displaced by painting, which at least has the virtue of being obviously finished when it is finished.
Debrief while it is still fresh
The end-of-season review has to happen in the first fortnight after closing, while people are still present and still remember. Held in the following spring, it becomes an exercise in reconstructing what people think probably happened.
It also has to include the people who will not be returning, whose accounts are usually the most candid available and who have no reason to soften anything. That is uncomfortable and it is the most valuable input the review will get.
Protect some of it as rest
A shoulder season entirely consumed by projects produces a management team that starts the next season already depleted, which is a false economy in a business whose peak depends on stamina.
Plan the rest deliberately — a defined block, in the calendar, before the project list is allocated across the remaining weeks. Otherwise the projects expand to fill the entire period, and the recovery that the season required never happens.