A restructure arrives dressed as an organisational chart. New reporting lines, a changed title, maybe a role that no longer exists. It reads like a logistics problem, the kind you'd solve with a spreadsheet and a calm conversation with HR. Underneath, it's almost never that. It's a question about who you are when the structure that used to answer that question for you is gone.
Most people respond to a restructure by working harder at the visible problem: updating the CV, mapping the new org chart, rehearsing the conversation with the new manager. All of that matters, and none of it touches the actual thing that's been disturbed, which is quieter and older: the story you'd been telling yourself about what your position proved about your worth.
If your sense of standing was resting on a title, a team size, a seat at a particular table, the restructure doesn't just remove the seat. It exposes that the ground under you was borrowed in the first place, held up by an org chart rather than by anything you actually own. That's the disorienting part, not the redundancy itself, but the sudden view of how much was resting on something that was never fully yours to keep.
This is why so much restructure advice lands flat. "Update your LinkedIn, network hard, stay positive," none of it is wrong, and none of it addresses the actual question sitting underneath the practical one, which is closer to: if the title goes, what's still true about you? Answer only the logistics question and you can end up perfectly re-employed and just as unsettled as before, because the real question never got asked.
The honest answer to that deeper question rarely arrives quickly, and it rarely arrives once. You circle it while updating the CV, again a few weeks into the new role, again a year later when something else shakes loose the same ground. Each pass, if you let it, goes a little deeper than the practical scramble that triggered it. That's not a detour from dealing with the restructure. For most people, it's the actual work the restructure was asking for all along.
The Threshold Framework exists for exactly this: not to make the logistics faster, but to make room for the older question underneath them, deliberately, instead of leaving it to surface on its own at 2am six months into the new job.