A157 | The Dinner We Almost Did Not Have — Notes on Our Annual Gathering and What It Has Come to Mean

We nearly cancelled the annual dinner two years ago. The timing was difficult — a large export order had come in late, production was running behind, and the week we had reserved for the gathering was the same week the order needed to ship. The management team discussed it for most of an afternoon before deciding to keep the date and adjust the production schedule instead. It was not an easy call, and there were real costs to it. But looking back, it was the right one, and the reasons why tell us something about what the gathering has become over the past decade.

We have held an annual dinner at Smith Ribbon & Bow for as long as the current management team can remember. The format has changed over the years — it started as a simple meal in the factory canteen with whatever was left in the catering budget, and has since grown into a proper sit-down event in a local restaurant for the full workforce and their families, with a programme that includes some recognition of the year's work and some entertainment provided by the staff themselves. The budget has grown with the company, but the character of the event has not changed as much as the budget has.

What the Dinner Is Not

We want to be clear about what we are not trying to do with the annual gathering, because the distinction matters. It is not a team-building exercise in the programmatic sense — we do not bring in facilitators or run structured activities designed to produce predetermined outcomes in group dynamics. It is not a performance review vehicle or a forum for business announcements. We do not use it as an opportunity to communicate strategic direction or set targets for the coming year. Those things have their own appropriate forums.

The dinner is what it says it is: a meal, together, at the end of a year of shared work. The formality is low. The recognition element is genuine — we mark milestones, including long service and individual contributions that were significant during the year — but it is kept brief and proportionate. The rest of the time is unstructured. People eat, talk, drink tea, introduce their children to colleagues they have heard about for years. The entertainment programme, which rotates among the departments, is invariably slightly chaotic and entirely sincere — a song, a comedy sketch, a group performance that required more rehearsal than anyone admitted. These things matter.

What Happened the Year We Almost Cancelled

The year we almost cancelled, the dinner went ahead on schedule. The export order shipped two days later than originally planned — not because of the dinner, but because of a separate issue in the finishing department that would have delayed it regardless. We mention this not to vindicate the decision in retrospect but because it illustrates something about how these situations tend to work: the production cost of keeping a social commitment is usually smaller than it appears in the moment, and the cost of cancelling is harder to see but real.

In the weeks after that dinner, two things happened that we attributed, at least in part, to having kept the event. First, the finishing department — which had been under significant pressure during the late-order period and had absorbed the schedule change with considerable grace — showed noticeably higher engagement in the weeks following the gathering than it had in the preceding month. Second, three members of the production team who had been on the fence about renewing their contracts for the following year confirmed that they would be staying. We cannot prove causation. But the timing was not random.

The Recognition Segment

We have refined the recognition segment over the years toward less formality and more specificity. Early versions involved generic certificates for categories that felt somewhat arbitrary. The current approach involves a small number of recognitions per year — typically four to six — for things that were genuinely distinctive: a production team that solved a recurring quality problem that had frustrated everyone for eighteen months, an operator who identified a batch issue before it reached the client and prevented what would have been a significant return, a supervisor who managed a particularly difficult period with unusual steadiness.

The recognitions are proposed by the management team based on what they observed during the year, but the factory floor generally knows in advance roughly who the recipients will be — not because there are leaks, but because the things being recognised were visible to everyone who works in the factory. This is by design. Recognition that surprises the entire room is recognition of something the room did not witness. Recognition that surprises only the recipient — because they did not realise it had been noticed — is something else.

What It Has Come to Mean

The annual dinner has accumulated meaning over time that we did not plan for and cannot fully articulate. Workers who left the company years ago occasionally ask, through former colleagues, whether the dinner is still happening. New workers mention it within the first few months — they have heard about it from the people who recruited them or from colleagues who have been here longer. There is an expectation that it will happen, and when it does happen, there is a quality to the evening that is different from other social occasions we organise during the year.

We think this is because it is annual and reliable. A dinner that happens every year, consistently, regardless of how difficult the year has been, says something specific: that the relationship between the company and the people who work in it is not contingent on a good year. The year we nearly cancelled and did not — that decision carries more weight now than it did in the moment when we made it. We intend to keep making it the same way, for as long as we can.