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