/Career-job-opportunities

Many founders make decisions that, months later, force them to do one of the hardest things a leader will ever face: look at a room full of people they hired and tell them there is no longer a place for them. I went through that. The decision to hire wasn't irrational at the time I made it. The company was showing clear signs of growth, we had everything in place to scale, and it was with that conviction that we moved forward. But the market didn't behave the way we expected. And I had to undo in weeks what I had built over months. This article is not a confession and it's not a crisis management manual. It's an honest analysis of the decision-making process: what led me to build, what failed, and how you manage the exit with integrity when things don't go as planned. I'm writing it for founders who are going through this right now, or who want to avoid going through it tomorrow. The real question here isn't how to justify the mistake. It's how to make hard decisions with the right information, and how to take responsibility when the outcome doesn't match the intention. **Before you talk to anyone, do the diagnosis** There is work that has to be done before you speak to the public, to investors, or to your team: understanding exactly what happened and why. This step seems obvious, but most founders skip it under time pressure or because of discomfort with what they're going to find. The diagnosis starts with three questions that need to be answered with cold clarity, preferably with data rather than memory alone. The first is: what was the core assumption that didn't hold? Every decision to hire before revenue justifies it rests on a concrete bet. Not "we thought we were going to grow," but something like "our revenue projection for Q3 was X, based on Y contracts with an estimated close probability of Z percent." Making that assumption explicit is the first step toward understanding where the analysis broke down. The second is: what was knowable at the time, and what wasn't? There is a fundamental difference between ignoring available signals and making decisions with genuinely incomplete information. Analyzing the data that existed when the decision was made, not the data that came afterward, is what allows you to separate a misjudgment from a reasonable bet that didn't work out. That distinction matters, not for absolution, but for accuracy. The third is: what changed, and when did it change? Market, product, revenue, runway, external context. Identifying the exact moment when the assumptions stopped being valid helps you understand whether the team reacted in time or not. Most layoff situations don't result from a bad initial decision. They result from a delayed reaction to information that was already available. Only after answering these three questions does it make sense to prepare any communication. Communicating without a diagnosis produces vague, defensive, or contradictory messages. And the team always feels the difference. **Justifying is not the same as making excuses** This distinction sits at the center of everything you communicate next. When a founder says "it made sense at the time" without further context, it sounds like evasion. When they say "I was wrong, full stop" without explaining their reasoning, they lose credibility as a decision-maker, because it signals that their decisions are arbitrary and unstructured. What investors, co-founders, and team members need to hear is the process, not the verdict. An honest justification rests on four things. First, the assumptions that supported the decision, made explicit and concrete. Second, the information that was available and what wasn't, because no decision is made with complete information, and demonstrating that with rigor is different from dodging accountability. Third, the moment those assumptions stopped being valid, which is the most delicate point of all, because if the information that invalidated the decision was available months ago and the reaction only came now, that needs to be addressed directly. Fourth, what you would do differently, not as an act of contrition, but as proof that real learning took place. There is also what you should not say. Avoid blaming the market as if it were a completely unforeseeable force. Avoid blaming team members in collective communications. And avoid language that suggests the situation "happened to" the company rather than resulting from concrete decisions. Founders who rebuild trust after a layoff speak in the first person plural: we decided, we bet, we didn't see it coming. Even when the decision was made by one person. **The conversation with those who are leaving** This is the conversation people remember forever. There is no second chance to get it right. It needs to be direct, individual whenever possible, and prepared in advance. No euphemisms, no language that artificially softens what is happening. "The company cannot sustain your position" is a hard sentence to say, but it is respectful. "We are restructuring to optimize our value proposition" is not. People who have just received bad news need concrete information about what happens next: severance, system access, references, timelines. Not speeches about the company's future. And they need space to react. This conversation doesn't close in ten minutes. Those leaving deserve time to process, to ask questions, and if necessary, to express frustration, without the founder feeling compelled to manage that emotion in real time. What I learned is that how you treat the people who leave defines the culture for those who stay. They are not two separate audiences. They are the same community. **The conversation with those who stay** This is often the most underestimated conversation in the entire process, and it's where many layoffs fail even when the communication with those leaving was handled well. Those who stay need to understand what happened and why, need to know whether their position is secure, and need to see a path forward. None of those questions should go unanswered, even if the answer to some of them is "we don't have full certainty yet, but here is what we know today." What destroys the morale of a team that survives a layoff is not the layoff itself. It's the ambiguity that follows. Teams handle bad news with far more resilience than they handle incomplete information and contradictory messages. Silence is not management. It's abandonment. **What you owe the people who leave** Beyond legal obligations, there is a question of character. Active references, not passive ones. Introductions to people in your network who might genuinely help. Clarity on equity and vesting schedules, approached with the spirit of doing what is fair rather than just what is required. An offboarding with a defined timeline, prepared materials, and a process that doesn't humiliate anyone. These things cost little financially and cost a great deal emotionally for a founder who is already exhausted. But they are exactly what separates a company that people recommend even after leaving from one they spend years warning others about. **How to rebuild after the cut** After a layoff, the people who stay are watching. They are observing how the founder reacts, how they speak about those who left, how they talk about the future. They are quietly deciding whether to stay or start looking elsewhere. What stabilizes a team in this moment is not promises. It's concrete signals that there is a direction, that decisions are being made with criteria, and that what happened has been genuinely processed and not just survived. A team meeting where the founder speaks openly, answers hard questions without deflecting, and presents clear priorities for the coming weeks is worth more than any well-written internal memo. Survivor syndrome is real. Those who remain feel guilt, uncertainty, and sometimes resentment. Acknowledging that out loud is not weakness. It is exactly the kind of leadership that retains the right people at the right moments. **What this experience can teach you about future hiring** The most important lesson I took from this was not "hire less." It was "hire for what exists, not for what you hope will exist." There is a difference between hiring for anticipated growth, which is a bet, and hiring for installed capacity, which is a decision. Both can be right. But they require different criteria, different conversations, and a different tolerance for risk. What changed in how I think about hiring since then is simple: before opening any position, I ask what assumption this hire validates, and what happens to the role if that assumption doesn't hold in the next six months. If the answer is "I'm not sure" or "let's hope it doesn't come to that," the hire waits. **Leading well includes knowing how to manage what went wrong** No founder hires to fire. But the ones who last are those who can move through the hard moments without losing clarity about what happened, without losing respect for the people they affected, and without losing the ability to make decisions the next day. I went through this. It was not the end. But it shaped profoundly the way I lead since then, and I believe there is something in that experience worth sharing, not to impress, but so that others face it with a little more preparation than I had.