I suspect this would cause more problems than it solves. There are usually enough daily or on-demand tasks that at least a skeleton crew needs to be available always, and the nature of crowds and pricing is such that many people want to take vacation when others AREN’T. And in-company coordination fails when people at different companies want to vacation together.
Combine this with the general desirability of building businesses/teams that DON’T stop working when any one employee is missing, and the intent (even if not the execution) to remove those bottlenecks, and it’s very difficult to stand up and say it’s worth any inconvenience to reduce the impacts, instead of working to reduce the causes.
I suspect this would cause more problems than it solves. There are usually enough daily or on-demand tasks that at least a skeleton crew needs to be available always, and the nature of crowds and pricing is such that many people want to take vacation when others AREN’T. And in-company coordination fails when people at different companies want to vacation together.
Combine this with the general desirability of building businesses/teams that DON’T stop working when any one employee is missing, and the intent (even if not the execution) to remove those bottlenecks, and it’s very difficult to stand up and say it’s worth any inconvenience to reduce the impacts, instead of working to reduce the causes.