"Nobody told me." If stores had a counter for that sentence, many would clock double digits a week. The promo that started this morning, which the afternoon colleague learns about from a customer. The recalled product someone put back on the shelf. The new Saturday hours that half the team knows and half does not.
The easy diagnosis is "we communicate too little". It is almost always wrong: you communicate enormously, everything, constantly, in the same place. And that is precisely the problem.
Three kinds of information, three different fates
The chaos comes from treating every piece of information the same way. In reality three very different species circulate in a store. Today's operational notes (the customer collecting at 5pm, the temperamental card terminal): short-lived, needed by whoever is on shift now and whoever comes next. The rules that stay (the new returns procedure, the summer hours): long-lived, they must be findable a month from now. And the social noise (the birthday wishes, the memes, the "who's seen the keys?"): good for morale, lethal when it buries the other two.
The group chat treats all three identically: it stacks them. And information stacked under twenty messages is, for all practical purposes, information lost.
Each species in its own home
The solution is not yet another app: it is agreement on where each thing lives. Operational handovers in one fixed spot that whoever starts a shift reads first (counter notebook, whiteboard, shared note: one of these, not all three). Permanent rules in one findable place (binder or folder, with old versions removed: an outdated procedure still pinned up is worse than none). The chat keeps quick coordination and social life, with a single rule: whatever must outlive the day cannot live only there.
And one habit worth gold: whoever has read it, ticks or initials it. Not for surveillance, but because "I posted it in the chat" and "everyone knows" are two different sentences, and the difference always reveals itself at the worst moment.
The real culprit is often the calendar
There is a slice of this problem no channel discipline can fix: the people who were not there. The team gathered on Tuesday morning decides three things, and whoever works Thursday nights discovers them by inference. That is not bad communication: it is information travelling by attendance, and attendance in a store is by definition a patchwork.
Two countermeasures. First: every decision made out loud has an owner who writes it down by evening, in the right place. Second, subtler: look at the shift plan before choosing when to announce important things. If the announcement that concerns everyone always happens in the slot where the same people always work, you have built a two-speed store without meaning to.
The Thursday-night test
Want to know if your communication works? Take the person with the most marginal shifts (Thursday nights, Sundays) and ask them for the week's three pieces of news. Their answer is an exact photograph of how far your system reaches from the centre. If they know everything, it works. If they have no idea what you are talking about, the problem is not theirs: it is the system's.
Half of these stumbles shrink when the team has one place it checks daily for shifts and notes: Sked Solve was born to be that place, as the site shows.