"Unlimited PTO" Policies in 2026: Flexibility or Psychological Trap Where No One Takes Vacation?

General
1

I need to be honest about something that’s been bothering me. We implemented unlimited PTO at our EdTech startup 18 months ago, and I’m seeing patterns that trouble me as a leader.

The Promise vs. The Reality

We rolled out unlimited PTO with the best intentions—trust our team, reduce administrative overhead, give people flexibility. The pitch to the board was compelling: tech companies that offer unlimited PTO attract better talent, show trust in their teams, and eliminate the accounting liability of accrued vacation days.

But here’s what actually happened: our engineering team is taking less time off than before.

Under our old 20-day PTO policy, the average engineer took 17.3 days per year. Now, with “unlimited” PTO, we’re averaging 12.8 days. Our highest performers? Some are taking as few as 8-9 days annually.

The Data Tells a Troubling Story

I’m not alone in seeing this. Recent research shows:

One of my senior engineering managers told me bluntly: “I don’t know what ‘unlimited’ means in practice. I see my peers taking 10-12 days, so I don’t want to be the person who takes 25 and gets labeled as uncommitted.”

The Psychological Dynamics

What I’ve observed falls into a few patterns:

  1. The Guilt Factor: High performers worry that taking “too much” time signals lack of commitment. Without a fixed number, there’s no objective benchmark—just peer comparison and anxiety.

  2. The Manager Effect: Managers account for 70% of the variance in employee engagement. When I take 15 days, my team feels comfortable taking 12-14. When I take 8, they take 6-8. The anchor I set matters more than the policy says.

  3. The Perception Trap: In a high-growth environment where everyone’s pushing hard to hit our Series B metrics, taking vacation can feel like opting out of the mission. “Unlimited” doesn’t fix that—it just removes the forcing function that a fixed allocation provides.

The Burnout Consequence

Here’s what worries me most: we’re seeing early signs of burnout. Our latest engagement survey showed a 12-point drop in “I have time to recharge” responses. Three senior engineers mentioned workload sustainability concerns in their most recent 1:1s.

Increased burnout among staff is a sure sign that the unlimited PTO policy is backfiring.

The Alternatives I’m Considering

I’m exploring a few options:

  1. Minimum PTO requirements: Set a floor (e.g., “take at least 15 days”) with manager check-ins if someone falls below
  2. Mandatory shutdown weeks: Company-wide breaks 2-3 times per year where everyone is off
  3. Transparent benchmarks: Publish anonymized data on average days taken to set clearer norms
  4. Leadership modeling: Executive team publicly commits to 20+ days and tracks it transparently

Some companies are moving to mandatory PTO, which is emerging as the new standard and boosting productivity by 12%.

My Question to This Community

For leaders who’ve implemented unlimited PTO: What have you seen? Are your teams actually taking more time off, or are you seeing the same paradox?

For ICs: Does “unlimited” PTO feel like freedom or pressure? What would make you feel genuinely comfortable taking 20+ days in a year?

I care deeply about building a sustainable, high-performing culture. But if our PTO policy is creating a psychological trap where people work more instead of rest, we’re failing—regardless of how progressive the policy sounds on paper.

What am I missing? What’s worked for you?

2

This resonates deeply. We went through almost the exact same experience at our financial services company, and I want to share what we learned—both the hard way and through trial and error.

Our “Unlimited PTO” Disaster

We rolled out unlimited PTO in 2024 for our 40+ engineering team. The results were worse than you’re describing: average days taken dropped from 16 to 9.5 within six months. We had senior engineers taking 5-6 days per year. Five days.

The breaking point came when one of our most respected tech leads burned out mid-project and took a sudden 3-week medical leave. In his exit conversation (yes, he left), he said: “I never felt like I could take time off without falling behind or letting the team down. At least with 15 days, I knew it was expected. With unlimited, I felt like taking vacation was a personal choice I was making against the team’s goals.”

That hit hard.

What We Changed (and What Actually Worked)

After that wake-up call, we implemented a hybrid model I call “Defined Unlimited”—which sounds like an oxymoron but hear me out:

  1. Set a floor, not a ceiling: Everyone must take at least 15 days per year. Manager check-in at 6 months if someone is below 7 days. This isn’t optional—it’s a performance expectation.

  2. Quarterly “use it or lose it” encouragement: We track days per quarter. If someone takes zero days in Q1, their manager has a 1:1 about it in early Q2. Not punitive, just: “Hey, are you okay? What’s blocking you from taking time?”

  3. Leadership transparency: Every quarter, our executive team shares how many days each of us took. I took 18 days last year and shared it publicly. Our CTO took 22. That set a new anchor.

  4. Shutdown weeks: We have two company-wide shutdown weeks (one in summer, one in winter). Everyone is off. No exceptions. No “I’ll just check Slack.” This removes the guilt because there’s literally no one working.

The Results

After 12 months:

  • Average days taken: 16.8 (up from 9.5 under unlimited, roughly matching our old fixed policy)
  • Engagement survey “I have time to recharge”: +18 points
  • Turnover among senior engineers: Down 40%

What I Learned About the Psychology

You nailed it with the manager effect. Research shows managers account for 70% of variance in engagement, and that extends to PTO usage. When I took 8 days in 2024, my team averaged 7. When I took 18 days in 2025, my team averaged 15.

The other insight: High performers need permission, not freedom. The unlimited policy says “you can take time,” but high performers hear “it’s up to you to decide when it’s okay to step away.” That’s a burden, not a benefit. A fixed allocation says “the company has decided you should take this time.” That’s permission.

My Unsolicited Advice

If I were you, I’d:

  1. Acknowledge the problem publicly with your team. “We implemented unlimited PTO with good intentions, but the data shows people are taking less time off. That’s on us as leadership.”

  2. Implement a minimum (15 days) and track it. Make it a manager responsibility to ensure their team hits it.

  3. Model it aggressively. Take 20+ days yourself this year and talk about it openly.

  4. Consider shutdown weeks. They’re the single highest-ROI change we made.

One last thought: unlimited PTO might be a solution looking for a problem. The accounting liability savings are real, but they’re dwarfed by the cost of burned-out senior engineers leaving. If your team was taking 17 days under a 20-day policy, that policy was working. The problem wasn’t the policy—it was probably approval friction or manager inconsistency. Fix those without throwing out the structure that was protecting your team from themselves.

Good luck. This is fixable, but it requires acknowledging that “progressive” doesn’t always mean “better.”

3

I’m going to push back on something here—not because I disagree with your diagnosis, but because I think the solution isn’t to fix unlimited PTO. It’s to ask why we needed it in the first place.

Unlimited PTO Is a Band-Aid on a Culture Problem

At my previous company (120-person engineering org), we had unlimited PTO for four years. The results mirrored what you’re both describing: people took less time, burned out more, and the policy created anxiety instead of freedom.

But here’s what we discovered when we dug deeper: the PTO policy wasn’t the root problem. The root problem was a culture that measured value by visibility and output, not by outcomes and impact. Unlimited PTO didn’t create that culture—it just exposed it.

When we switched back to a fixed 20-day policy with a minimum 15-day requirement, guess what happened? People still took an average of 12 days. The policy change didn’t fix burnout. It just gave us a different metric to feel bad about.

What Actually Changed Things

What did work was addressing the culture directly:

  1. Redefine “performance”: We stopped celebrating “crushing it” and started celebrating sustainable delivery. In performance reviews, we explicitly asked: “Did this person take adequate time off?” and “Did they encourage their team to do the same?” Those became promotion criteria.

  2. Make rest a strategic priority: I started talking about rest the way I talk about technical debt. “If we don’t invest in rest now, we’ll pay 10x the cost in turnover and mistakes later.” That framing resonated with business-minded leaders.

  3. Kill the hero culture: We had a cultural problem where people who worked weekends and skipped vacation were celebrated as “committed.” I called that out explicitly in all-hands: “Working every weekend is a failure of planning, not a badge of honor. If you can’t take vacation without the team falling apart, we have a single-point-of-failure problem.”

  4. Outcomes over activity: We moved to outcome-based goals. Ship the feature by Q2, not “work 50 hours/week in Q1.” This decoupled effort from impact. People started optimizing for leverage, not just hours.

The CTO Accountability Piece

Here’s the hard truth: Managers account for 70% of engagement variance, and CTOs account for 100% of culture-setting. If your team isn’t taking time off, it’s because they’ve learned—directly or indirectly—that taking time off is a career risk.

I took 24 days last year. I talked about my vacation plans in exec meetings. I posted photos from my trip in our company Slack. I came back and said publicly: “I was completely offline for 10 days, and the team crushed it without me. That’s what good systems look like.”

When I promoted our Director of Platform Engineering last quarter, I cited his vacation habits in the promotion announcement: “He took three weeks off last year, and his team’s delivery didn’t skip a beat. That’s world-class leadership.”

My Contrarian Take

Unlimited PTO isn’t inherently bad—it’s just a terrible policy for companies with unhealthy cultures. It’s like giving someone with a broken leg the “freedom” to walk without crutches. Sure, it’s freedom, but they’ll just hurt themselves more.

If your culture rewards presence over impact, celebrates overwork, and treats rest as weakness, then unlimited PTO will make things worse—because it removes the structural protection (fixed days) that was at least forcing some baseline rest.

The solution isn’t to go back to fixed PTO. The solution is to fix the culture, then decide if unlimited PTO makes sense.

What I’d Do in Your Shoes

  1. Short-term: Implement minimum PTO (15 days) and shutdown weeks. This is a forcing function while you fix the culture.

  2. Medium-term: Change how you evaluate and promote people. Make “sustainable delivery” and “enabling team rest” explicit criteria.

  3. Long-term: Kill the hero culture. Celebrate people who deliver outcomes while taking 20+ days off, not people who “grind.”

If after 12 months of culture work, people still aren’t taking time off, then consider reverting to fixed PTO. But honestly, if the culture is right, the policy won’t matter as much as you think.

Luis’s “Defined Unlimited” approach is solid, but I’d go further: ask whether your company culture can sustain any form of unlimited flexibility, or whether you need structure to protect people from a system that doesn’t yet value rest.

That’s the real question.

4

Coming at this from the product side, and I want to add a dimension that’s getting overlooked: unlimited PTO is a product design failure disguised as an HR policy.

The Product Lens on Unlimited PTO

Think about it like a product. What job is PTO policy hired to do?

The job isn’t “be flexible” or “show trust.” The job is: ensure employees take adequate rest to maintain sustainable performance.

Judged against that outcome, unlimited PTO is failing. Employees with unlimited PTO take 12-13 days on average, versus 15 days with traditional policies. The product isn’t solving the job it was hired for.

This is a classic “user experience” problem:

  • Ambiguous UX: What does “unlimited” mean? Users (employees) don’t know, so they default to conservative behaviors.
  • No defaults: Good products set smart defaults. Traditional PTO gives you 20 days—that’s a default. Unlimited gives you nothing, forcing each user to invent their own default.
  • No feedback loops: With traditional PTO, you see your balance depleting. That’s feedback. With unlimited, there’s no signal telling you “you’re below target.”

What Product Design Teaches Us

If I were designing a PTO policy as a product:

  1. Set a default, not a limit: “You have 20 days. Use them. You can take more if needed, but 20 is the expectation.” This gives people an anchor without creating a ceiling.

  2. Build in nudges: Quarterly email: “You’ve taken 3 days so far this year. Your peers average 8 days at this point. Schedule some time off!” (Same playbook as Fitbit nudging you to hit 10K steps.)

  3. Make it visual: Dashboard showing “Days taken” vs “Suggested pace” (e.g., 5 days per quarter). Gamify it if you want—green if you’re on track, yellow if you’re behind.

  4. Remove decision fatigue: Shutdown weeks remove the “should I take off?” decision. The company decided for you. That’s good UX.

The Framing Problem

Here’s where I think both Keisha and Luis are right, but from different angles:

But here’s the product insight: good design reduces the burden on culture. Yes, culture matters. But if your product design fights against good behavior, you’re making culture do all the heavy lifting.

My Advice: Treat This Like a Product Problem

  1. Define success metrics: What’s the target outcome? (e.g., “Average 18 days taken per employee, with no one below 12”)

  2. Measure baseline: Where are you now? (12.8 days average, some as low as 8)

  3. Ship an MVP: Try “Defined Unlimited” (15-day minimum + shutdown weeks) for 6 months.

  4. Instrument it: Track days taken by role, by manager, by team. Look for patterns.

  5. Iterate: After 6 months, survey your team. “Does this policy help you rest? What would make it better?”

  6. Be willing to kill it: If after 12 months of iteration, unlimited PTO still isn’t delivering the outcome, sunset it. Switch to a fixed 20-day policy with manager flexibility for more. No shame in reverting a feature that didn’t work.

The Uncomfortable Question

Here’s what I keep coming back to: Why did we want unlimited PTO in the first place?

If the answer is “to reduce accounting liability and administrative overhead,” that’s a business optimization that came at the cost of employee wellbeing. Own that.

If the answer is “to show trust and flexibility,” ask whether the outcome matches the intent. Trust isn’t measured by policy language—it’s measured by whether people feel safe taking time off. Right now, they don’t. So the product failed the job.

The good news? Product failures are fixable. You iterate, you test, you learn. Don’t get attached to the policy because it sounds progressive. Get attached to the outcome: people taking adequate rest to sustain high performance.

Ship the fix, measure the impact, and be honest about whether unlimited PTO is helping or hurting.