The Two Groups Sitting in the Same Shock
There is a moment after a large layoff when two very different groups of people are sitting with the same shock, and neither one can fully see the other.
The people who were let go are processing loss. Loss of income, identity, routine, and the team they built something with. Some move fast, updating profiles, reaching out, activating every network they have. Some go quiet. Some need to grieve before they can do anything else. All of it is valid.
The people who stayed are processing something harder to name. Relief, maybe, followed immediately by guilt about feeling relieved. Fear about what comes next for them. A sudden awareness that their closest collaborators are gone. And on top of all of that, the work left behind. Projects mid-stream. Institutional knowledge that walked out the door. A calendar full of meetings with people who are no longer there.
Both groups are struggling. They just cannot always see each other clearly enough to say so.
I was on the outside of a recent large-scale reduction. My entire org was impacted. And in the days that followed, I found myself talking to people on both sides. What struck me was not the differences in what they were feeling. It was how much overlap there was, and how little space existed for either group to acknowledge it.
---
What the outside looks like
When a layoff eliminates entire functions, the disorientation is structural, not just emotional. It is not simply that you lost your job. It is that the team you belonged to, the discipline you represented, the work you were building, all of it was categorically removed. That is a different kind of loss than an individual role elimination.
What people need in that moment is rarely what the official offboarding process provides. HR handles logistics. It cannot hold grief. It cannot tell you that your work mattered. It cannot introduce you to someone hiring in your space, or sit with you while you figure out what you actually want to do next.
That gap is where community fills in. And when community forms fast, and with intention, it becomes something genuinely powerful. Not a replacement for what was lost, but a different kind of structure. One built on trust instead of org charts. One that can hold both the practical and the emotional at the same time.
In the situation I was part of, a discord space was live within the hour. Job leads, regional channels, peer support, all of it grew organically in the days that followed. What made it work was not the tools. It was the decision to create a floor for people to land on, and then let the community tell us what it needed next.
---
What the inside looks like
The people who remain after a layoff are often forgotten in the narrative. And that is a mistake, both humanly and operationally.
Survivors, and that word carries weight for a reason, are not simply relieved. They are managing fear about their own futures. They are absorbing the workload of colleagues who are gone. They are fielding messages from friends now job searching, wanting to help but unsure what they can say or share without crossing lines. They are sitting in meetings that feel quieter and stranger than they did a few days ago.
In the community we built, we made a deliberate choice early on: remind members consistently that some people in the channel are still employed. Treat them with the same kindness and care you would want for yourself. Do not ask for information that could put anyone at risk. Do not assume that because someone stayed, they are fine.
They are here because they want to help. Let them do that within what is possible for them. That boundary is not a wall. It is a form of respect.
---
What operations practitioners can do
Whether you are inside or outside, an operations mindset is one of the most useful things you can bring to a moment like this.
You already know how to stand up infrastructure quickly. You know how to coordinate without authority. You know how to ask what people need before assuming you know the answer. You know that the org chart is a map, and when the map disappears, people still need to navigate.
The work in the aftermath of a layoff is not glamorous. It is channel moderation and contact list maintenance and following up with the person who went quiet in week two. It is reminding people that job searching at scale is a marathon, not a sprint. It is holding space for grief without rushing everyone toward the pivot.
It is, in other words, exactly what operations people do. Just without the job title for a while.
Speed over perfection, meet people where they are.
Speed matters in moments like this. Not perfection. People do not need a perfectly designed system on day one. They need somewhere to land.
What stayed with me most from this experience was how quickly people tried to take care of each other once the org chart disappeared.
Former coworkers sharing leads before processing their own loss. Members step up organize the moderate channels, answering questions when chaos and confusion took hold for most.
This is infrastructure too.
Not corporate infrastructure. Human infrastructure.
And maybe that is the real lesson operations people should carry forward: When formal systems fail suddenly, communities become the continuity layer.
The work is not to solve grief. It is to reduce isolation long enough for people to find their footing again.
I go deeper into the operational playbook here. What to build first, how to sustain momentum without bureaucracy, and the specific structures that helped this community hold together through the long tail of uncertainty.


I'm so sorry to hear about the layoffs at Cloudflare. Layoffs are a jarring experience and takes time to process and recover from. Thank you for sharing the perspective on both sides.
If you have any design ops teams members ready for a new role or who want to chat generally, I just opened one up for horizontal ops programming at Mercury.
Wishing you and your team well