- Why headcount is the wrong measure
- What three, five and ten people need
- Which feature to introduce first
- Six ways groupware makes things worse
The short answer
Headcount is the wrong measure. The question is whether the work has outgrown the range of your own voice. If everyone sits in one room and can see each other's day, groupware will not reduce the effort of communicating. It becomes worth considering once people are out visiting customers, working from a second location, or working at different hours.
And if you do introduce it, do not switch on everything. Limiting yourself to one or two features is what makes it stick.
What changes with size
At three people
Three people manage with conversation and chat. The only thing worth adding is a shared view of the day. If there are stretches where nobody can say who is out and until when, create one shared calendar. The other features will sit unused.
At this size, rules beat tools. Writing down one line about where files go achieves more than adding functionality.
At five people
At five, telling everybody the same thing starts to cost real time. What helps here is putting announcements in one place, because "I said it out loud" increasingly fails to reach whoever was not in the room.
Whether to add task management depends on the shape of the work. If each job stays with one owner throughout, a task list adds nothing. If several people split a single job, seeing who holds which piece is useful.
At around ten people
Past ten, nobody can hold everyone else's situation in their head. Schedules, announcements and an agreed place for files are all faster when they are shared.
This is also the size at which visibility needs to differ by person. If everything is built on the assumption that everyone sees everything, sensitive material quietly moves to a side channel — and that side channel becomes the real one.
Which piece first
Work down this list, one item at a time, giving each a month.
- Shared schedules. Easy to evaluate, and cheap to abandon if it does not help.
- Announcements. One place for messages to everyone. Do not demand read receipts at the start; just have a place to post.
- An agreed location for files. Agree the location and stop there. Do not turn it into a full folder reorganisation.
- Tasks. Only when work genuinely moves between people.
- Chat. If something already works, leave it alone.
In a company where chat is already established, moving it is what generates the most resistance. Leaving the messaging tool where it is and moving only schedules and announcements is a perfectly workable outcome.
When it makes things worse
Introducing groupware backfires in these situations. If they describe you, the work goes better without it.
- Covering ground that conversation already covers. Asking people who can see each other to also write it down just adds a task.
- Two parallel channels. Anything said in chat also has to be posted in the groupware. The effort doubles, and one of the two goes stale.
- Filling it in becomes the job. Adding calendar entries is treated as the work, and the calendar fills with entries that do not match reality. Then people stop reading it.
- Everything switched on at once. With every feature available on day one, nobody knows where anything should go. Unused areas linger and information scatters.
- No one administering it. Without a named person for adding and removing accounts and reviewing access, leavers' accounts stay active.
- It reads as surveillance. Track who viewed what too closely and people simply stop writing.
If the reason for introducing groupware is "I want more visibility into what people are doing," look first at why that visibility is missing. Changing the tool often leaves the actual cause of missing reports untouched.
What this looks like in practice
A haulage company with ten staff: three in the office, the rest out in vehicles.
Start with shared schedules. Simply knowing who is due back and when cuts the number of calls out from the office. Next, move announcements into one place — vehicle inspection dates, closure days, anything that goes to everyone unchanged.
Daily reports and delivery records, on the other hand, should wait. Drivers cannot enter them while driving, so the office ends up entering them on their behalf, which recreates duplicate entry. Leaving those on paper, or solving them another way, is more realistic.
After three months, check which features are actually being opened. The ones that are not can be switched off. Leaving unused areas in place makes new starters wonder whether they are supposed to write there too.
At the same time, ask in one line why each unused feature was not used. "There was never a moment to enter anything" and "it was awkward to enter" lead to different next steps: switch it off in the first case, rethink where and how people enter it in the second.
In short
The measure is not headcount but whether work has outgrown the range of your voice. At three, a shared calendar is enough. At five, put announcements in one place. At ten, add an agreed location for files and start thinking about who sees what. Introduce one piece at a time, a month apart. If a feature has created a second parallel channel, or turned data entry into the job itself, turn it off. Leaving unused features in place scatters information rather than organising it.
APOUL Calendar
APOUL Mail Box