66% of Workers with Unlimited PTO Cap Themselves at 15 Days or Fewer—Companies Like Bolt Are Rolling It Back Citing "A-Performer Burnout." Is Unlimited PTO the Policy That Backfired?

66% of Workers with Unlimited PTO Cap Themselves at 15 Days or Fewer—Companies Like Bolt Are Rolling It Back Citing “A-Performer Burnout.” Is Unlimited PTO the Policy That Backfired?

I’ve been thinking about this a lot lately as we evaluate our PTO policy at my EdTech startup. We implemented unlimited PTO two years ago with the best intentions—trust our team, give them flexibility, treat them like adults. But the data coming out in 2026 is making me seriously question whether we did them any favors.

The Paradox Nobody Talks About

A 2026 Patriot Software survey of 1,000 employed Americans found that 66% of workers would cap themselves at 15 days or fewer even with no formal limit. Even more striking: a Namely study showed employees with unlimited PTO took an average of 13 days per year, compared to 15 days for those with traditional accrual-based PTO.

Read that again. The “unlimited” policy resulted in people taking less time off than a structured policy.

The Bolt Wake-Up Call

Then came the announcement that really got my attention. Bolt CEO Ryan Breslow killed their unlimited PTO policy in July 2025, citing exactly what I’ve been seeing on my own team:

“When time off is undefined, the good ones don’t take PTO. The bad ones take too much. This leads to A-performer burnout.”

Bolt replaced it with a mandatory four weeks of vacation with increases tied to tenure. They’re actively tracking PTO usage and working with managers to support top performers who underutilize time off.

What I’m Seeing on My Team

I pulled our own data and the pattern is uncomfortable:

  • Our senior engineers average 11.2 days off per year
  • Mid-level engineers take 14.8 days
  • Newer team members take 16.4 days

The people driving the most value are taking the least time off. And when I ask them about it in 1-on-1s, I hear variations of:

  • “I don’t know what’s normal here”
  • “I don’t want to look less committed than [teammate]”
  • “There’s always so much to do, I feel guilty taking time”
  • “If it’s unlimited, I can always take it later” (they never do)

The Psychological Trap

Without a defined allocation, there’s no benchmark. In a traditional system with 20 days PTO, taking 15-18 days feels normal. With “unlimited,” taking 15 days starts to feel like a lot. Am I the only one taking this much? Will people think I’m slacking?

The ambiguity creates anxiety, not freedom.

The Manager Variable

Here’s another thing the research confirms: psychological safety around time off is not built by removing a cap; it has to be modeled and reinforced by leadership. And when I audit PTO usage by manager, the variance is wild:

  • Manager A’s team averages 9.2 days (Manager A took 7 days)
  • Manager B’s team averages 17.5 days (Manager B took 21 days)
  • Manager C’s team averages 12.1 days (Manager C took 11 days)

The policy creates a local culture defined by each manager’s behavior, which means we’ve traded company-wide fairness for manager-dependent outcomes.

The Appeal of Structured Flexibility

The most interesting finding: when asked about pairing unlimited PTO with a mandatory minimum, 91% of respondents found that appealing. This suggests people want the floor defined, not the ceiling removed.

My Questions for This Community

  1. For those of you with unlimited PTO: What’s your actual utilization? Are your top performers taking less than others?

  2. For leaders who’ve implemented or rolled back unlimited PTO: What was the tipping point? What did you replace it with?

  3. Is there a hybrid model that works? Something like “minimum 15 days, maximum flexible” or mandatory shutdown weeks?

  4. How do you measure success? Is it days taken, team burnout metrics, retention of high performers?

I’m genuinely torn. The intent behind unlimited PTO aligns with my values—trust, autonomy, treating people like adults. But if the outcome is that high performers burn out while everyone else feels anxious about an undefined norm, are we just creating a different kind of problem?

What am I missing here?


Sources:

This hits close to home. We implemented unlimited PTO at my company in 2023 and I’ve been watching the same pattern play out.

The Culture Problem, Not the Policy Problem

Here’s my contrarian take: unlimited PTO isn’t inherently broken—it just reveals culture problems we were hiding behind structured policies. When you remove the guardrails, you see which managers actually model healthy work-life balance and which ones create burnout cultures.

In our case:

  • Engineering teams under managers who took 3+ weeks themselves averaged 16.2 days
  • Teams under managers who took <2 weeks averaged 9.8 days
  • The policy didn’t change. The culture per manager did.

What We Changed

Rather than kill unlimited PTO, we treated it as a culture problem:

  1. Redefined performance to include rest. We added “models sustainable work practices” to manager evaluations. If your team is consistently under 15 days PTO, that’s a red flag in your performance review, not a badge of honor.

  2. Made leadership PTO transparent. I publish my PTO calendar. Took 24 days last year. Explicitly told my directs: “If you’re taking less than 20 days, we need to talk about workload or culture.”

  3. Killed the hero culture. We used to celebrate “grind” and late nights. Now we celebrate outcomes achieved with sustainable effort. Changed our all-hands shoutouts to highlight efficient delivery, not heroic overtime.

The Measurement Question

To your question about measuring success: we track three metrics quarterly:

  1. PTO utilization by level/tenure (are senior people burning out?)
  2. Manager variance (are some managers creating local burnout cultures?)
  3. Exit interview PTO mentions (are people leaving because of overwork?)

In Q1 2026, our company-wide average hit 17.3 days—up from 12.1 in 2023. Senior engineers went from 11.4 to 15.8 days. Still not perfect, but trending right.

The Uncomfortable Truth

Unlimited PTO fails in unhealthy cultures. If your baseline is “work until you drop,” removing the PTO ceiling just means people work until they drop indefinitely.

But if you have a culture that genuinely values rest, unlimited PTO works because people actually take time off without the bureaucracy.

Bolt’s problem wasn’t unlimited PTO. Bolt’s problem was a culture where high performers felt they couldn’t take time off. The mandatory four weeks forced a culture change they couldn’t achieve through leadership modeling.

My Advice

Before you kill unlimited PTO, ask yourself:

  • Have you modeled taking 3+ weeks yourself?
  • Do you celebrate efficiency or glorify grind?
  • Do your managers understand that team burnout is their failure, not the team’s weakness?

If the answer to any of those is “no,” then yes—switch to mandatory minimums. Force the culture change. But don’t blame the policy for revealing the culture you were already building.

We went through this exact journey at my Fortune 500 financial services company. Spoiler: we killed unlimited PTO after 18 months and I’m relieved we did.

The “Unlimited PTO Disaster” Timeline

  • 2024 Q1: Rolled out unlimited PTO with fanfare. “We trust you!” messaging everywhere.
  • 2024 Q4: Average PTO dropped from 16 days (under old 20-day policy) to 9.5 days. Senior engineers taking 5-6 days.
  • 2025 Q2: Lost our best tech lead to burnout. Exit interview: “I never knew when it was okay to take time off, so I just… didn’t.”
  • 2025 Q3: Switched to what we call “Defined Unlimited”

What “Defined Unlimited” Means

We kept the spirit but added structure:

  1. 15-day minimum (you must take at least 15 days or we have a performance conversation about workload)
  2. No maximum (want to take 25? 30? Go for it, just coordinate with your team)
  3. Quarterly PTO tracking (managers get dashboard showing team utilization)
  4. Leadership transparency (all directors+ publish PTO calendars)
  5. Mandatory shutdown weeks (full company closed between Christmas and New Year’s, plus one week in summer)

Results after 12 months:

  • Average PTO: 16.8 days (up from 9.5)
  • Senior engineers: 15.2 days (up from 5.6)
  • Engagement scores: +18 points
  • Senior engineer turnover: 40% lower than during “unlimited” period

The Pattern I Keep Seeing

High performers don’t need freedom—they need permission. When you say “unlimited,” they hear “prove you don’t need much.” When you say “minimum 15,” they hear “it’s expected and normal to take time off.”

The psychological shift is huge. Under unlimited PTO, taking two weeks felt indulgent. Under defined unlimited, taking two weeks felt like the bare minimum.

Michelle’s Point About Culture Is Right… But

@cto_michelle I agree with you that culture matters enormously. But here’s where I differ: I don’t think most companies can change culture from the top down fast enough to make unlimited PTO work.

Your approach worked because you’re the CTO and you took 24 days and made it visible. But in a 40+ person org with 6 managers, I have limited control over what each manager models. Manager A is a workaholic. Manager C has young kids and takes lots of time. Their teams inherit completely different norms.

The policy created the variance you’re trying to fix through culture change. In our case, it was faster and more effective to just… change the policy back.

The “Unlimited PTO as Solution Looking for a Problem” Theory

Here’s my cynical take: unlimited PTO was never about employee wellbeing. It was about two things:

  1. Financial: Don’t accrue PTO liability on the balance sheet
  2. Talent branding: Sound progressive in job postings

It worked great for those goals. It was terrible for the actual humans working here.

What Actually Works

If I were designing a PTO policy from scratch today:

  • 20 days standard (this is the floor, not the ceiling)
  • 25 days at 3 years (tenure reward)
  • 30 days at 5 years (loyalty reward)
  • Manager dashboards (flag teams under 80% utilization)
  • Shutdown weeks (remove decision fatigue, normalize time off)

Clear. Fair. No ambiguity. People know what to expect.

To Answer Your Questions

> For those of you with unlimited PTO: What’s your actual utilization?

When we had it: 9.5 days company-wide. Top performers: 5.6 days. It was a disaster.

> Is there a hybrid model that works?

Yes—defined unlimited with a mandatory floor. But honestly, it’s just “generous PTO with flexible overages” rebranded. Why not just call it that?

> How do you measure success?

We track:

  • Average PTO by level (are seniors burning out?)
  • % of employees taking <12 days (red flag threshold)
  • Manager variance (are some teams dysfunctional?)
  • Correlation with engagement and retention

Bottom Line

Unlimited PTO sounds like treating people like adults. In practice, it treated them like test subjects in a psychological experiment. Most failed the test not because they’re bad at autonomy, but because the test itself was designed poorly.

Give people clear expectations. They’ll meet them. Remove expectations and they’ll optimize for fear of judgment.

Coming at this from a product lens: unlimited PTO is a product design failure.

The “job to be done” for a PTO policy is to ensure employees get adequate rest. Unlimited PTO is failing at that job—it’s delivering 13 days when traditional policies deliver 15 days. That’s like launching a feature that makes the core metric worse.

Why It Fails: Ambiguous UX

Think about any product you’ve shipped. When users have unlimited options with no defaults, what happens?

  • Analysis paralysis
  • Fear of doing the “wrong” thing
  • Defaulting to the most conservative choice

Sound familiar? That’s exactly what’s happening with unlimited PTO.

Good product design gives you:

  • Clear defaults (not unlimited choices)
  • Nudges toward the right behavior (not ambiguity)
  • Social proof (not isolation)
  • Feedback loops (not silence)

Unlimited PTO has none of these.

The Missing Instrumentation

When we launch a feature, we instrument it. We measure adoption, usage patterns, drop-off points. We run A/B tests. We interview users.

How many companies with unlimited PTO actually:

  • Measure utilization vs. target (what is the target?)
  • Track sentiment about the policy (do people like it?)
  • Run retrospectives (is it working?)
  • Have success criteria (what does “good” look like?)

Most rolled it out like a marketing campaign, not a product. “Unlimited PTO! We’re progressive!” Then never measured if it achieved its actual goal.

The A/B Test We Should Run

What if you treated PTO policy like a product experiment?

  • Cohort A: Traditional 20 days
  • Cohort B: Unlimited PTO
  • Cohort C: “Defined unlimited” (15-day minimum, no max)

Success metrics:

  • Days taken per year
  • Employee satisfaction with policy
  • Reported burnout levels
  • Manager variance (fairness measure)

My hypothesis: Cohort C wins on all metrics. Traditional beats unlimited on most.

The “Why Did We Want This?” Question

@eng_director_luis nailed it—this was about balance sheet liability and branding, not employee outcomes. But here’s what kills me: we kept measuring the wrong things.

We measured:

  • :white_check_mark: Did we reduce PTO liability? (yes)
  • :white_check_mark: Did candidates like it in job postings? (yes)

We didn’t measure:

  • :cross_mark: Are people actually taking time off?
  • :cross_mark: Are top performers burning out?
  • :cross_mark: Is this better than the old system?

Product Thinking for PTO Policy

If I were designing this as a product:

  1. Set the default, not the limit. “You have 20 days. Want more? Just ask your manager.” Most people will take ~20. High performers have an escape valve.

  2. Build in nudges. Email at 10 months: “You’ve used 8 days. Most people at your level take 15-18. Want help planning your time off?”

  3. Make it visible. Team dashboard showing PTO usage (anonymized). Social proof matters. “Oh, everyone takes 2-3 weeks? Okay, I will too.”

  4. Remove decision fatigue. Mandatory shutdown weeks eliminate 5-7 days of “should I take time off?” decisions.

The Uncomfortable Question

When 91% of people say they prefer a mandatory minimum paired with unlimited, that tells you something: they want the floor defined, not the ceiling removed.

It’s like saying “users love having guardrails.” Yes. They do. Product designers know this. HR apparently didn’t get the memo.

My Answer to “Is This the Policy That Backfired?”

Yes. But not because unlimited PTO is inherently wrong—it’s because we shipped it without:

  • Clear success metrics
  • Baseline measurement
  • An MVP approach (test it on one team first?)
  • Instrumentation to know if it’s working
  • Willingness to kill the feature if it fails

We treated it like a press release, not a product. And employees paid the price.

If you wouldn’t ship a feature this way, why would you ship a people policy this way?

What I find fascinating is the productivity paradox: remote teams measure productivity by output, while office teams measure it by presence.

Our hybrid model:

  • Core hours: 10am-3pm local time (for synchronous collaboration)
  • Deep work blocks: mornings/evenings (protected from meetings)
  • Office optional: Come in when it’s useful, not mandated

Productivity is up 18% YoY. Retention is up 23%. Turns out flexibility > location.