I wish companies would stop using the word "unlimited" for this. It's unspecified vacation policy, not unlimited.
I’ll put it this way: The company tried the “As long as you get work done, it doesn’t matter how many hours you work” approach.
The problematic part of this equation is that “your work” isn’t a fixed quantity. When we allocate tasks and set weekly goals according to how much people can reasonably accomplish in a week, the “your work” variable becomes a proxy for how much that person is willing to work that week.
The loophole is to minimize the number of tasks assigned to yourself while maximizing the perception of how long it took. The honest team members didn’t play this game and naturally ended up around 40 hours, mostly 9-5ish. It was the people gaming the system who played this game the most, obviously, and they tended to claim off hours and weekends as extra time spent working alone, assuming we couldn’t disprove it.
Sure, but the larger point would be that the companies call it that way, which would still be dumb even if we didn't get into that discussion right now.
(BTW, was "unlimited" the term that was actually used where you worked?)
> The problematic part of this equation is that “your work” isn’t a fixed quantity. When we allocate tasks and set weekly goals according to how much people can reasonably accomplish in a week, the “your work” variable becomes a proxy for how much that person is willing to work that week.
Yes, of course. What is puzzling to me is - how is this not completely obvious right from the start to everyone involved?
> It was the people gaming the system who played this game the most, obviously, and they tended to claim off hours and weekends as extra time spent working alone, assuming we couldn’t disprove it.
This part sounds more related to "work whenever you want policy" than "work as much as you want". It was obviously the case that people were expected to work 40-ish hours/week and take roughly the same amount of vacation as was the norm before unlimited/unspecified vacation policy.
Whether that rubs up against some idealized mythological puritan work ethic doesn't change the fact of the matter.
Deal with the discrepancy by rewarding high output.
I’ve worked at two companies that tried genuinely unlimited vacation policies. The theory was that happy and well-rested employees who lived very fulfilling lives outside of the office would be naturally more motivated to do work for the company that granted them this benefit.
For the people who needed flexible schedules (young children at home, caring for aging parents, personal health issues, irregular sleep patterns) this was a success. People who fit this description were overjoyed to find a company willing to accommodate them, and they returned the favor with great, efficient work.
On the other hand, there was a subset of people who approached the system like a game: Just how little work could they do without getting fired? How could they claim the easiest tasks for themselves?
This becomes a major problem when the workload is shared across a team, where one person’s reduced output becomes an increased burden on someone else. The people gaming the system weren’t doing so at the company’s expense. They were doing so at their team member’s expense.
In theory we’d all get the same allowances regardless of the reason. In practice, people are infinitely happier to cover for a hard working coworker who needs an unplanned day off to tend to a sick child than they are to cover for an otherwise unencumbered coworker who simply decided they didn’t feel like working today.
You could argue that the business should be allowed to slow down, but when your competitors are not slowing down and your profit margins aren’t infinite, that’s not a sustainable option. Eventually you need to start cutting headcount to compensate for the reduced productivity, which begins to defeat the purpose of catering to the employees. There is no free lunch.