This is one of those decisions where the obvious approach isn't always the right one. A better starting place is batching meetings.
Key takeaways
- Getting batching meetings right early saves a second round of changes later.
- Protecting a consistent block is worth deciding deliberately, not defaulting into.
- Realistic recovery time between blocks matters more in practice than it looks like on paper.
Batching meetings
Consider batching meetings in the context of everything else in play, not on its own. A choice that works in isolation can still throw off the balance of the rest.
Protecting a consistent block
Protecting a consistent block matters more than it might seem at first. Getting this part right tends to save a second round of changes later.
Realistic recovery time between blocks
Consider realistic recovery time between blocks in the context of everything else in play, not on its own. A choice that works in isolation can still throw off the balance of the rest.
Lab note
Make the smallest change first. It's usually reversible, and it tells you whether the bigger version of the project is even worth doing.
Frequently asked questions
How long does this usually take to get right?
It depends on the scope of what you're changing, but most people see the biggest improvement from the first few adjustments rather than from doing everything at once.
Do I need to spend a lot of money to see a difference?
Not necessarily. Many of the ideas here are about planning and habit rather than new purchases, and they're worth trying before spending on anything new.
What's the most common mistake people make here?
Skipping the planning step and going straight to a purchase or a big change, then having to undo part of it once the practical issues show up.
