My position, before the analysis
I will say this plainly: I do not think this was a good move.
It was not strategic. It looks much more like a leader who did not know what to do — and who fired the people telling him what was going wrong instead of fixing what was going wrong.
HR was almost certainly telling him what was going wrong. They see the burnout first. They see the manager attrition first. They see the friction inside the work first. They sit with the complaints customers have not yet posted. When growth outpaces the structure that was built for smaller scale, HR is the team handed the job of explaining why everything feels harder — and the job of holding the line while leadership decides what to do about it.
When you fire the people bringing you the problems, the problems do not go away. You just stop hearing them. And when you stop hearing them, they get more expensive — because by the time they surface again, they have grown.
The company is now much smaller than it was at peak. That is not the same thing as having solved the underlying problem. A smaller company is a more manageable company. But making a company manageable by making it smaller is not strategy. It is reduction. The original problem — whatever it actually was — has not been addressed. It has been hidden under a smaller headcount.
The problem will keep coming back. Because the gap between what leadership wants the company to deliver and what the company is actually built to deliver was never closed. People will quit. Top performers will leave. Strategic misalignment will widen. And the next time growth pressure shows up, the company will not be built to absorb it — because the leadership skill required to design through that pressure is the same skill that was missing the first time.
Firing the department did not solve the problem. It solved an annoyance. It got things to a point where leadership felt like something had been done. That is not the same thing as fixing the root.
This is why it is important to look at a situation from every angle — including the ones that are uncomfortable, including the ones that might be wrong. It is the only way to know whether a decision is actually fixing the root of the problem or simply removing the symptom that was warning you the root existed.
That is the lens I am using to look at the Bolt story.
The debate so far
Everyone is debating whether Bolt made a mistake.
Some people think eliminating the HR function proves companies are cutting too aggressively. Others think it proves HR creates unnecessary complexity. Most of the coverage has been a fight over the role itself.
I think both sides may be asking the wrong question.
Because this may not be an HR story at all.
It may be an operating model story.
What actually happened at Bolt
In May 2026, Bolt CEO Ryan Breslow eliminated the company’s entire HR team as part of a broader restructuring that cut roughly 30% of the workforce. The HR function was replaced with a smaller “People Operations” team focused on training. Breslow said the prior team had been “creating problems that didn’t exist.”
The backdrop matters. Bolt reached an $11B valuation in 2022. By 2024, that valuation had reportedly collapsed to roughly $300M. Breslow returned as CEO in 2025, gave the existing workforce sixty days to adapt to a leaner culture, and reported that 99% could not make the shift.
The headlines focused on the HR decision. The story underneath is about an operating model that had quietly stopped working — and a leader trying to redesign it under enormous pressure.
What leaders actually say when the operating model has drifted
Leaders rarely wake up and say “our operating model is broken.”
They say things like:
- “Why are we moving slower?”
- “Why does everything require coordination?”
- “Why are managers overwhelmed?”
- “Why are we discussing the same problems every quarter?”
- “Why are we adding more but getting less?”
These are not separate problems. They are the same problem surfacing in five different ways. The operating model has accumulated weight, and the company is paying for it before anyone has named what is actually happening.
Organizations don’t become complex. They inherit complexity.
Nobody intentionally builds a company that is difficult to run.
Complexity accumulates one reasonable decision at a time. A new approval. A new report. A new meeting. A new policy. A new platform. A new layer of oversight. A new function. A new team that owns the thing the old team used to own.
Most begin with good intentions. But every layer changes how work moves. Every layer changes how decisions move. Every layer changes how customer feedback moves.
Eventually organizations reach a point where they have to ask a different question — not “are we executing the plan” but “does the way we run the business still support the value we want customers to receive?”
Because customers do not buy organizational layers.
Customers buy:
- Responsiveness.
- Consistency.
- Trust.
- Confidence.
Anything inside the organization that does not move toward those four things is a candidate for redesign. That is true whether the layer is HR, finance, ops, IT, or a process that nobody can remember why it was created.
Get the next essay before it goes anywhere else.
One piece each week. Written from inside $25M+ growth-stage operations. What I am seeing before the dashboard catches it.
What caught my attention about Bolt
It was not that Bolt removed HR.
It was the possibility that leadership believed the company had become too heavy to deliver the value it was built to deliver. That is a serious diagnostic — and it is one most leadership teams arrive at much too late.
The interesting question is not “should HR exist?”
The interesting question is:
Was Bolt removing complexity — or simply relocating it?
Because complexity rarely disappears. It moves.
If responsiveness improves and customer trust strengthens, then perhaps the complexity was actually removed. The operating model got lighter and the customer experience got better.
If feedback loops become longer and customer signals become weaker, then the complexity may simply reappear somewhere else later — inside the people-ops team, inside the manager population, inside the CEO’s calendar, inside the customer escalations the company can no longer see. The cost moves. The weight does not.
We will not know which one Bolt did for another twelve to eighteen months. The customer numbers will tell us.
The question that matters for every company right now
This is the same pattern I keep watching in every company I work with — restaurants, $25M growth-stage SaaS firms, private-equity portfolio investments. The version of the operating model that worked at one scale stops working at the next. Layers accumulate. Decisions slow. The customer experience drifts. Leadership concludes the problem must be the people, or the technology, or the market.
The implementation almost always works. The investment doesn’t. The technology launches. The training program runs. The reorg ships. But the underlying organizational design — the part nobody redesigned — keeps producing the same operational reality it always has.
The question is not whether complexity exists in your organization. It does. The question is whether it is helping create customer value or quietly getting in the way.
Most companies discover they are paying for misalignment long before they realize they are paying for it.
The cost of misdiagnosing the operating model is not paid by the function that gets eliminated. It is paid by the customers who eventually leave because the work no longer moves the way it used to — and by the leadership team still wondering why the original problem keeps coming back, wearing a different name each time.
Start here
If you are watching the same Bolt-style questions show up inside your own organization — managers overwhelmed, decisions slowing, customer signals weakening, the same problems returning every quarter — the Theory Reality Gap is already open inside your operating model. The longer it stays open, the more it costs.
There are two ways to start.
Self-assess. The Theory Reality Gap Scorecard takes 6 minutes and identifies the specific places where the gap is widest inside your organization.
Or talk it through. Sixty minutes. No cost. No pitch. We map what you are seeing, identify where the gap likely lives, and figure out whether Cassidine Consulting is the right partner to help close it.
Schedule a One-Hour Strategic Discussion →
No obligation. No proposal. Just clarity.
Get the next essay before it goes anywhere else.
One piece each week. Written from inside $25M+ growth-stage operations. What I am seeing before the dashboard catches it.
FAQ
Bolt CEO Ryan Breslow eliminated the company’s HR function in May 2026 as part of a broader restructuring that cut roughly 30% of the workforce. Breslow said the prior HR team had been creating problems that did not exist, and replaced the function with a smaller “People Operations” team focused on training.
HR is rarely the root cause. When organizations slow down, the underlying issue is usually that the operating model has accumulated layers — approvals, reporting structures, coordination requirements — that the business has outgrown. Removing any single function without redesigning the surrounding operating model often simply relocates the complexity.
What is the Theory Real
Five signals show up consistently: leaders ask why things are moving slower, why everything requires coordination, why managers are overwhelmed, why the same problems return every quarter, and why the company is adding more but getting less. When those five questions are showing up regularly, the operating model has drifted from the value it was built to deliver.