Written as it actually goes, including the part where it goes back
Every one of these works today in a spreadsheet, an email chain and a chat group. What breaks is not the happy path — it is the week somebody is away, or the question of who approved this in March.
A team that just needs to talk
1A channel per team, private ones where they need to be, direct messages for two.
2Threads keep a tangent out of the main room and notify only the people in it.
3Mentions, reactions, pins and saved messages, so the useful thing is findable next week.
4A voice huddle when typing has stopped working, and a poll when it only needs a show of hands.
5You can stop here. Nothing makes you raise a request, and the rest is waiting when you need it.
Running a project
1A channel for the project, and the files shared in it are the project’s files.
2The message that asked for something becomes a task, keeping the message.
3Tasks carry an assignee, a due date, a priority and the project they belong to.
4Everyone sees their own day across every project, with a reminder before the deadline.
5Comments stay on the task, so the discussion about it is not three rooms away.
Getting the hour and the room
1The meeting is scheduled from the conversation that decided it was needed.
2Attendees accept or decline, and the deadlines view puts it beside what is due.
3Find a room that is free then — by size, by equipment, in the building’s own timezone.
4A room that needs permission asks the person who can give it and holds the slot meanwhile.
5Cancel the meeting and the room comes back on its own. The sign by the door keeps up.
Purchasing something
1Somebody asks in the channel where purchases are discussed, with the quotation attached.
2The message becomes a request, and the quotation goes with it as evidence.
3It reaches the budget holder, then Finance — by seat, so a transfer does not strand it.
4Finance returns it for a second quotation. The request keeps its number and its trail.
5Approved, signed, and the trail answers who agreed to what, months later.
Taking leave
1The form knows the balance, so the request cannot be raised for days nobody has.
2It goes to the line manager the org chart already knows about.
3Away that week, their delegate decides it — as themselves, on the record.
4The calendar and the team both learn about it without anybody being told twice.
Issuing a policy
1The draft is uploaded and owned by the unit that wrote it, with a responsible person named.
2It is submitted for approval through the same engine every other request uses.
3Approved, it is marked in force from the first of the month.
4Next year it expires on its own date rather than on somebody remembering.
5Anyone can open it and see which version was in force when.
Asking another department
1A request crosses to a unit you do not manage and cannot see the inside of.
2They see the request and its attachments. Nothing else of yours.
3Their decision comes back to your trail, not to an inbox somebody has to forward.
Start with one of these
Pick the process that hurts most and move it first.