I worked at a company once that conflated mean-spirited policies with "just business". The result was a downfall that was entirely preventable. Vacation and sick leave were combined ("PTO") which meant that you had to take a vacation day if you got sick. The result of this was that people came into work when ill and everyone was less productive. Very little ever got done in the winter, because it was just one constan…
As for PTO I appreciate my boss's explanation: "I just don't want any sniping over sick days. If you don't feel like you can come in and work, it should cost something. That way nobody will complain when someone calls in sick."
Similarly, I've heard a lot of complaints about open-plan offices, and frankly, I do think they're collaborative. Initially I didn't love the fact that I have to hear everyone's discussions around me, but it's certainly helped problems get solved quicker than they otherwise would. When two devs across the office are discussing a weird bug they're seeing it can have a lot of implications. Maybe you happened to see it two days ago it gives you the opportunity to chime in, or it allows the product manager to say "Guys, that feature isn't super important, if it's really hard we can just cut it", or it allows the QA guy to say "Let me know what area that affects so I can make sure to write some extra test cases". All of those situations seem innocuous when you're all working together, but if you're in separate offices or working remotely people will end up wasting time trying to figure these things out by themselves before reaching out for help.
These aren't ideal solutions, so you just have to be sure to take steps to mitigate the costs. With PTO you have to be generous with the time granted in order to account for the fact that it's employee's vacation + sick days, and with open offices you have to have a space employees can go to get serious work done without distractions. If you DO take those mitigating steps I think they're both good systems.