Boundaries for chat apps: start with the conclusion
Advice on boundaries for chat apps tends to split in two: impossibly complex, or sold as one click. Reality sits between. It needs some patience and…
Keeping meetings short: adapting to different settings
Most people do not fail at keeping meetings short from misunderstanding it. They fail because understanding is not doing. What follows is the doing…
Recording decisions: how to do it concretely
Most people want recording decisions to make things better. The workable version of that goal is steadier: a floor you can hit on a bad day.…
Writing a retrospective: rhythm decides it
Let us set the limits of writing a retrospective first: it reliably improves backups that survive a power cut, and it does not deliver overnight.…
Permissions in shared documents: the four usual traps
Put permissions in shared documents back into a real week, with overtime, travel and days you cannot be bothered. Any plan that only survives good…
Using version history: what to do first
Put using version history back into a real week, with overtime, travel and days you cannot be bothered. Any plan that only survives good months will…
A convention for comments: putting effort where it counts
Advice on a convention for comments tends to split in two: impossibly complex, or sold as one click. Reality sits between. It needs some patience and…
A meeting-notes template: what to do first
Let us set the limits of a meeting-notes template first: it reliably improves no reinstalling from scratch, and it does not deliver overnight.…
Preparing for screen sharing: putting effort where it counts
Anyone who has spent time on preparing for screen sharing has a failure story: a strong start, a collapse in the middle, then silence. This is not…
Bandwidth for remote meetings: the workable version
Separate two things in bandwidth for remote meetings: the outcome you want and the action you can sustain. When the gap is too wide, shrink the…
Setting up team folders: start with the conclusion
There is plenty written about setting up team folders and little you can act on. This piece stays concrete: every action can be done beside the…
File naming across a team: start with the conclusion
Separate two things in file naming across a team: the outcome you want and the action you can sustain. When the gap is too wide, shrink the action…
A handover checklist: start with the conclusion
Advice on a handover checklist tends to split in two: impossibly complex, or sold as one click. Reality sits between. It needs some patience and some…
Using a task board: adapting to different settings
If you have already tried using a task board and dropped it, the fault is usually in the setup: a starting point set too high, an environment never…
When a Gantt chart helps: one full walkthrough
Most people want when a Gantt chart helps to make things better. The workable version of that goal is steadier: a floor you can hit on a bad day.…
Buffers in a schedule: from judgement to finish
If you have already tried buffers in a schedule and dropped it, the fault is usually in the setup: a starting point set too high, an environment…
Working across time zones: the four usual traps
If you have already tried working across time zones and dropped it, the fault is usually in the setup: a starting point set too high, an environment…
Defining the final version: the four usual traps
Anyone who has spent time on defining the final version has a failure story: a strong start, a collapse in the middle, then silence. This is not…
Building a template library: rhythm decides it
If you only read one paragraph, read this: building a template library depends on how the situation is set up, not on how you feel at the time.…
Structuring a knowledge base: adapting to different settings
Let us set the limits of structuring a knowledge base first: it reliably improves devices that stay pleasant to use, and it does not deliver…