Canteen menus and staff shuttles: small things, most viewed

Most managers looking at intranet analytics for the first time are surprised by the same thing: the most viewed content isn't the carefully written strategy announcement, it's today's canteen menu. The shuttle timetable comes next.

That isn't surprising so much as instructive: people return to information that makes their day easier. And those two items are the shortest route to turning an intranet into a habit.

Why so many views?

Three reasons. Daily repetition: it changes every day and is wondered about every day. It produces a decision: do I go out, do I bring lunch, do I need to catch the shuttle? The alternative is inconvenient: checking the noticeboard means walking downstairs.

For an intranet to earn a daily visit habit it needs this kind of "needed every day" content. Strategy announcements are read once a month; the menu every day.

How should the menu be managed?

Weekly bulk entry is far more sustainable than daily entry. The canteen supervisor enters the whole week on Monday morning and doesn't touch it again.

Simplicity of entry is critical. Calorie counts, allergen lists and nutritional values look good, but five fields to fill in daily start being left blank by the third week. The only mandatory field should be the dish name; the rest optional.

Allergen information is an exception: because it concerns health, if it is entered it must be correct. An incomplete allergen list is riskier than none at all.

Where should today's menu appear?

Its own page isn't enough. The menu's real place is the homepage — the screen the employee already looks at. Rotating it on shared-area screens means it's seen without walking into the kitchen.

That is a natural pairing with the digital signage module; the menu is among the most-watched content on a screen.

Staff shuttles: routes and times

Shuttle information consists of two things: routes (which lines, which stops) and times. The only question that matters to an employee is: what time does it leave from my stop?

So the information should be presented per stop. Rather than showing the whole line, letting people select and see their own stop is far more useful.

Shuttle changes — a cancelled route, a time change, a delay due to weather — should travel through the announcement channel instead; that is critical, time-sensitive information.

Meal card information

Showing a meal card balance in the intranet is a frequent request but often isn't possible: most meal card providers don't offer a public balance API.

In that situation the honest solution is a static information card rather than a fake balance: which provider, the daily amount, how to check it, and who to contact in which situation. A balance indicator that doesn't work is worse than none at all.

Who will keep it updated?

The owner of these two pieces of content is usually the facilities team, and the update load is low — a few minutes a week. But without a named owner it gets entered in week one and forgotten by week three.

An empty menu screen is the first place an intranet looks neglected. Hence a practical rule: if no menu has been entered, don't show the area at all — no box saying "no menu found".

The scope boundary

This module has a tempting but dangerous direction of expansion: meal booking, headcount forecasting, payment tracking. Those turn into a separate operational system and usually clash with the caterer's own infrastructure.

Keeping it simple gives better results: showing information isn't running an operation.

Collecting feedback

Food quality is one of the most commented-on topics in employee surveys. A simple one-click rating next to the menu collects that feedback without waiting for a survey cycle.

What matters is that the collected data is actually used. A dish that scores low for months and stays on the menu shows the feedback mechanism isn't working, and participation dies. We cover the measurement and action loop in our surveys article.

Measurement

• Daily views — visits to the menu and shuttle information; usually the intranet's highest number.
• Currency rate — the percentage of working days with a menu entered.
• Homepage effect — the change in overall daily visits after the menu widget was switched on.

The last shows the module's real value: a small piece of information brings the employee back every day, and during that visit the announcements get seen too. We cover general ways to sustain participation in our engagement article.