Org Health Diagnostic

22% engineering attrition in 5 months is a systemic issue, not bad luck. "Lack of direction" and "slow decision-making" are proxies for deeper problems — let's decode them.

What engineers mean by "lack of direction":

• They were asked to build things that got canceled or deprioritized without explanation
• Product roadmap changed frequently and engineers felt like they were building sandcastles
• They couldn't see how their work connected to company outcomes
• Engineering work was reactive (bug fixes, customer requests) with no investment in technical vision

What "slow decision-making" means technically:

• PRs sitting in review for days without feedback
• Architecture decisions requiring founder sign-off that took 2+ weeks
• Being blocked on external dependencies (design, product) without a clear escalation path
• Tech debt discussions going nowhere because no one had authority to invest in them

Diagnostic Steps:

1. Stay interviews now — ask your 3 most valuable remaining engineers directly: "What would make you leave? What would make you stay?"
2. Decision audit — trace the last 5 engineering decisions >1 week: what caused the delay?
3. Roadmap change log — how many roadmap pivots in the last 6 months? How were they communicated?

Quick fixes that signal you've heard them:

• Weekly 30-min engineering forum where roadmap changes are explained before they happen
• Delegate architecture decisions to your tech lead with a documented approval threshold
• Create a "tech investment" budget: 20% of engineering capacity for engineers to own

Who is your most trusted remaining senior engineer?

Six weeks post-RIF and the pattern you're describing — surface-level compliance, hidden job searching, velocity drop — is textbook. Understanding why requires naming the specific psychological dynamics before you can address them.

What's happening inside your team right now

Post-layoff teams experience four simultaneous pressures:

1. Survivor guilt. People who remained feel relief, then guilt about feeling relief. They wonder why they stayed when colleagues they respected didn't. This creates emotional drag that shows up as disengagement, not stated distress.
2. Trust breach. Even if the RIF was necessary and handled well, the implicit contract ("if I perform, I'm safe") broke. It takes months to rebuild, and it can't be rebuilt with words — only with consistent, transparent behavior.
3. Uncertainty anxiety. Without explicit information, people fill the gap with their worst-case interpretation. "Are more layoffs coming?" is the most common unspoken question in every 1:1.
4. Increased cognitive load. Twenty-five percent fewer people doing the same or more work. The remaining team is stretched, even if they haven't said it directly.

The 8-dimension diagnostic in a post-RIF context

Not all dimensions are equally at risk. Expect these to be most broken:

How to gather real data

1:1 conversations (weeks 1–2): Ask every person on your team these questions directly:

• "What's the one thing you're most uncertain about right now?"
• "What would make the biggest difference to your ability to do good work?"
• "What are you hearing from the team that I should know?"

The third question unlocks what people won't say to you directly.

Anonymous pulse survey (short, 5 questions max):

1. On a scale of 1–10, how confident are you in the company's direction right now?
2. Do you feel your workload is sustainable? (Yes / Somewhat / No)
3. Do you feel informed about decisions that affect your work? (Yes / Somewhat / No)
4. How likely are you to still be here in 6 months? (Very likely / Uncertain / Unlikely)
5. Open text: "What's one thing leadership could do differently right now?"

Question 4 is your early attrition signal. Anyone answering "Uncertain" or "Unlikely" needs a direct conversation this week.

Observational data: PR review time, sprint completion rate, meeting participation quality, Slack response latency. These are symptoms but they're directional — a 30% drop in PR throughput usually maps to a combination of capacity loss and motivation loss.

Symptoms vs. root causes

Quiet in meetings is a symptom. The root cause is that people don't believe candid input is safe or consequential. Short Slack responses are a symptom. The root cause is emotional withdrawal — people are doing the minimum while they evaluate whether to stay.

Don't treat the symptoms. Treat the root causes: psychological safety first, clarity of direction second, workload sustainability third.

Sequenced recovery plan

Week 1: Radical transparency. Host an all-hands where you explain the RIF rationale again, what it accomplished, and what the path forward looks like specifically. Answer questions in real time, including hard ones. Silence from leadership in the weeks after a RIF is the most damaging thing you can do.

Month 1: 1:1 retention conversations with your highest performers. Ask them directly: "What would make you consider leaving? What would make you certain you want to stay?" Make commitments you can keep. Don't overpromise.

Month 2–3: Structural relief. Reduce scope or adjust timelines to reflect actual capacity. If you laid off 25% of the team and haven't adjusted delivery expectations by at least 15–20%, you're running people into the ground.

Who you must retain at all cost

Identify your top 5 performers right now — the people whose departure would cause a cascading problem. Have direct retention conversations with each of them this week. Compensation, equity refresh, role clarity, title. Use whatever levers you have. These are not conversations to schedule for next month.

Some attrition after a RIF is unavoidable and not entirely bad — occasionally the people who leave were already disengaged. But losing your top performers because you waited too long is the most preventable outcome here.

What does your current data show about which teams have been hit hardest?