Read the signals: is your role actually at risk

Two failure modes cost people the most when layoffs are in the air: catastrophizing every reorg into a personal threat and burning weeks on panic, or denying clear warning signs because strong past reviews feel like insurance. Neither is a read; both are feelings. This lesson replaces them with a scored read built only from observable signals, the things you could point to on a page, so you know whether to keep compounding calmly or move with urgency. It is a diagnostic, not a verdict, and its one job is to set your priorities for the five lessons that follow.

Start with org-level signals, which are about the company and your function, not about you personally. Watch where the money and attention are moving: a hiring freeze or budget cut that touches your function, layoffs in adjacent teams, the company missing targets or under funding pressure, a reorg or acquisition, a new senior leader over your area, your team's projects getting deprioritized, or your function increasingly described as something to outsource or consolidate. Separate company-wide risk from role-specific risk deliberately, because a broad reduction and a targeted one call for different moves, and confusing the two either makes you paranoid or makes you complacent. Calibrate against how ordinary separations actually are: in May 2026, 1.7 million U.S. workers were laid off, but 3.1 million quit voluntarily, so most movement inside a company is normal churn, not a reduction (BLS Job Openings and Labor Turnover Survey, May 2026, preliminary). Score an org signal as elevated only when the money or the headcount is moving against your specific function, not merely because the headlines feel bad.

Then read the role-level signals, which are about you specifically, and treat the PIP-adjacent ones with particular seriousness. The quiet tells are: being removed from projects or decisions you used to own, meetings that used to include you now happening without you, a new leader bringing in their own people, feedback tone shifting and getting documented in writing, and being asked to document your processes or cross-train others. Sudden formalization of feedback that used to be casual, or any talk of a performance plan, is a strong signal. Be honest about a PIP: in many cases it is paperwork produced after a decision, not a fresh chance, so do the work fully and completely, but do not read it as reassurance.

The most durable question underneath all of this is where you sit on the value chain: how close are you to the money and the core problem the business exists to solve. Roles that touch revenue, retention, critical risk, or the core product get cut last, because cutting them is visibly expensive. Roles that are pure overhead, easily outsourced, or fully proceduralized get cut first, because on a spreadsheet they look like cost with no attached value. Map where you actually sit, because your value-chain position is the strongest single predictor in this read, and the one you have the most power to change.

Now score it, so the read is a rubric and not a vibe. Count your checked boxes in each section. Org-level: zero to one signal is low, two to three is watch, four or more is elevated. Role-level uses the same thresholds with one override, any PIP-adjacent signal in Part 3 forces your role-level read to elevated regardless of the count, because formalized feedback is usually the paperwork stage, not a fresh chance. Your composite read is the higher of the org and role reads, then adjusted by the value chain: a weak value-chain position bumps you up one band, and only a strong position with zero role-level signals lets you hold one band lower. Then route it. Low means keep compounding: run the value and leverage lessons at a calm cadence and re-read in a month. Watch means make your value legible now (lesson 2), start the manage-up rhythm this week (lesson 5), and begin the parachute (lesson 6). Elevated means run all six lessons on a compressed timeline and treat the parachute as urgent, and if the signals ever move from elevated to a confirmed reduction or a PIP that is clearly paperwork, that is the clean handoff into the recovery, job-search, and negotiation courses, which you now enter from strength instead of shock. The decision tree in the template maps each read to its exact next move.

• Fill the org and role sections of the Role Risk Read using only observable facts from the last 90 days, no interpretation yet.
• Count checked boxes and score org and role with the thresholds: 0-1 low, 2-3 watch, 4+ elevated; any PIP-adjacent signal forces role to elevated.
• Place your role on the value chain: close to revenue/retention/risk/product, adjacent, or pure overhead.
• Set your composite read as the higher of org and role, then bump up one band if your value-chain position is weak.
• Use the decision tree to route your composite read to its one next move, and put that move on your calendar.
• Set a monthly cadence to revisit this read rather than re-scoring it in an anxious loop every day.

Priya ran finance ops at a 400-person company and felt a low hum of worry she wanted turned into a real read. She filled the Role Risk Read with facts only: budget-planning meetings that used to include finance-ops now happened without her (role signal), two roles on an adjacent operations team had just been cut (org signal), a new CFO had brought a deputy from a previous company (role signal), and she had been asked to 'document your monthly close process for the team' (role signal, and a documentation ask). Scored, that was org-level watch and role-level elevated on three signals, with a weak value-chain position because her reports read as overhead rather than decision-driving. Composite: elevated, not imminent. The rubric did its job. Instead of leaving her to panic or dismiss it, it routed her straight to lesson 2, making her work drive decisions. She reworked her monthly close into a one-page decision brief the CFO's deputy started using in planning, moving herself from overhead toward the money, which is exactly what an elevated-but-not-imminent read is for.

• Reading every reorg, budget cut, or bad quarter as a personal threat and spending your energy on panic. Score company-wide risk separately from role-specific risk. Most org turbulence is not about you; the read tells you which kind you're facing so you respond to the real one.
• Ignoring clear individual signals because your past reviews were strong or 'they'd never cut me.' Past performance is not insurance against a reorg or a new leader. Score the observable role-level signals honestly, especially documentation asks and lost inclusion, and believe the page over the reassurance.
• Treating a PIP as a genuine second chance and easing off. Do the work fully, but read a PIP as an elevated signal, often paperwork produced after a decision. Use the time to accelerate everything else in this course, not to relax.
• Re-scoring the read every day in an anxious loop, so the diagnostic becomes the anxiety. Score it once, act on the single move it points to, and set a fixed monthly re-read. The read exists to end the daily spiral, not to feed it.