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