Quick answer (TL;DR): I spent weeks building a sophisticated AI-powered working system inside a job — then got laid off in the middle of it. For a few days the work felt worthless. It wasn’t. The projects belonged to the company; the method belonged to me. The single most portable, layoff-proof career asset you can build is not a project or a title — it’s a system for how you think and work. This post explains how to build that asset on purpose, so that when a job ends, the capability walks out the door with you.
This is the most personal post in this series, so let me be honest about where it comes from.
What happened
I was building something at work that I was genuinely proud of: a complete system for working with an AI assistant as a true collaborator. A second brain of structured files. Protocols for keeping parallel workstreams in sync. Pipelines for producing real deliverables. Habits for catching dropped work before it became a fire. It had taken weeks of trial, error, and refinement, and it had changed how I did my job.
Then, in the middle of all that, I was laid off. The role was marketing operations at a SaaS company; the specifics don’t matter. What matters is the feeling that follows that news — the one a lot of you reading this already know intimately. Anger. Exhaustion. And a particular, hollow version of grief: the sense that all the work you just poured yourself into is now worthless, because the projects it served are no longer yours.
I sat in that for a few days. It’s a legitimate place to sit. If you’re there right now, you don’t have to climb out on anyone’s schedule but your own.
But then something shifted, and it’s the reason this post exists.
The projects were never the valuable part
Here’s what I realized when the fog cleared enough to think: the projects were never the asset. The method was.
The campaigns I’d been running evaporated the moment my access did. But the way of working I’d built — the architecture of the second brain, the session rituals, the reconcile process, the review gates, the discipline of honest record-keeping — none of that belonged to the employer. It wasn’t on their servers in any way that mattered. It was in my head and in a structure I could rebuild anywhere in an afternoon.
The specific work was theirs. The capability was mine. And capability is portable in a way that a job title, a project, or a company badge simply is not.
That distinction — between the work you do for a company and the way of working you develop while doing it — is, I’d argue, the single most important career insight of the AI era. Because the way of working is the thing that compounds, transfers, and survives.
Why “how you think” is the ultimate portable asset
Consider what actually leaves with you when a job ends:
- Not the projects. Access revoked, context gone.
- Not the internal tools. They stay behind.
- Not the institutional relationships, mostly. Some contacts persist; most fade.
- Not even most of your domain knowledge, which is often more company-specific than we like to admit.
What does leave with you:
- The systems you built for managing complexity.
- The workflows you designed for getting leverage out of your tools.
- The judgment you developed about what to automate, what to verify, and what to never delegate.
- The method.
In a world where AI can do an enormous amount of the doing, the differentiated, durable skill is increasingly the orchestration: knowing how to structure work so that you plus your tools produce something neither could alone. That skill doesn’t live in any company’s systems. It lives in you. You cannot be laid off from it.
How to build a layoff-proof method on purpose
This isn’t just a comforting reframe after the fact. You can build for portability deliberately, starting today, whether or not your job feels secure. Here’s how.
1. Treat your working system as yours from day one
When you build a workflow — an AI second brain, a personal tracker, a set of templates, a way of running your meetings — keep a version of it in a form you control and can take with you. Not the company’s confidential data, obviously, but the structure: the file architecture, the protocols, the templates with the sensitive parts stripped out. The shape is yours. The shape is the asset.
2. Generalize as you go
As you build, keep asking: “What’s the general principle here, separate from this specific job?” The campaign tracker is specific; the idea of a single source of truth with a session ritual is general. The specific deck pipeline is company-flavored; the principle of “draft freely, send deliberately, verify the result” is universal. Capture the general principle, not just the specific instance. That’s what transfers.
3. Write it down — ideally teach it
The act of writing your method down (a doc, a personal wiki, a blog series like this one) forces you to separate the durable principle from the disposable specifics. It also turns tacit skill into something you can show. “Here’s the system I built and how it works” is a far stronger interview signal than “I’m good with AI.” One is a claim; the other is evidence.
4. Build the meta-skill, not just the task skill
The most valuable thing you can get good at right now isn’t any single tool — tools change. It’s the meta-skill of rapidly building a working method around whatever tools you’re handed. That’s the skill that made my system possible, and it’s the skill I’ll walk into the next role already holding. If you can demonstrate that you arrive somewhere and quickly construct leverage out of the available tools, you are valuable in a way that survives any specific job.
If you’re reading this between jobs
Let me say this part directly, because I needed to hear it.
The weeks you spent building your way of working were not wasted, even if the projects they served are gone. You didn’t lose the method when you lost the job. You’re still holding it. It’s in your hands right now.
The layoff took the work. It did not take the way you learned to work. That came home with you, and it’s worth more than the projects ever were — because you can deploy it again, somewhere that has the sense to keep you.
So if you have any energy for it (and it’s completely fine if you don’t yet), the most useful thing you can do in the in-between is to write your method down. Turn the pile of habits and files into something teachable and portable. Not for the company that let you go — for the you that shows up to the next thing already equipped.
The reframe that actually helps
There’s a lot of hollow “everything happens for a reason” advice aimed at laid-off workers, and most of it deserves to be ignored. This isn’t that. This is something concrete and true:
They can lay you off. They cannot lay off how you think. The org chart you were on was never the asset. The way of working you built while you were on it — that’s the thing. Build accordingly, keep it in a form you own, and carry it forward.
The job was temporary. The method is yours. Go use it somewhere that deserves it.
Frequently asked questions
What’s the most portable skill to build at a job? The meta-skill of rapidly building a working method around whatever tools you’re given — including how you structure information, orchestrate AI, and manage complexity. Unlike projects or company-specific knowledge, this travels with you to any role.
How do I make my work survive a layoff? Treat your working systems (not the confidential data) as yours from day one: keep the structure, templates, and protocols in a form you control, generalize the principles away from job-specifics, and write them down so they’re teachable and portable.
Is it worth building systems at a job that might lay me off? Yes — arguably more so. The systems and methods you build are the part that survives the layoff. The projects are temporary; the way of working you develop is a durable, transferable career asset.
What should I do with my skills right after being laid off? When you have the energy, write your method down — turn your habits and systems into something teachable and portable. It clarifies what you actually know, gives you strong evidence for interviews, and prepares you to deploy your capability immediately in the next role.
This is Part 2 of a series on building a working method with AI. The rest of the series details the exact system referenced here — the second brain, the rituals, and the protocols — so you can build your own.