Your Career OS is a Living System
#049: The system only works if you allow it to grow and evolve. The final part of Design Your Next Move.
The Design Your Next Move Series:
Part 1: Your Design Career Won’t Be Killed by AI; It’ll Be Killed by Inertia
Part 9: Your Career OS Is a Living System
The biggest mistake people make after building something like what we’ve covered over the last several weeks is assuming the work is done. They write the Career Vision Narrative, define the mission, set the filters, inventory their skills, map their network, drop it all into a tidy PDF, feel good about themselves for a few days, and then the file goes into a folder where it collects dust because life happens.
The system only works if you use it, constantly and actively, as a living thing rather than an artifact you finished in one weekend.
Make it visible
Rule one for a system that actually functions is that it has to be somewhere you can see it. Not a Notion workspace you’ll never open again, not a PDF buried four folders deep on your hard drive, but somewhere visible and persistent enough that it’s harder to ignore than to engage.
A few things that work for me. Print your Career Vision Narrative and tape it above your desk, because there’s something about seeing your own words in physical space that does work the digital version doesn’t quite manage. Keep your mission and filters on a single sheet that lives in your notes app or your calendar, somewhere you’d actually reference more than once a quarter. Pull your Career Hypotheses into your weekly planning doc so you’re checking which ones are proving true and which ones are quietly falling apart. And build yourself a digital home for the whole system in Notion, Airtable, Miro, or whatever tool you actually open, so the OS lives in one place and you have somewhere to land when you go looking for it.
The tool isn’t the point. The point is that the system has a footprint in your life that isn’t easy to forget about.
Use it to make decisions
This is where the system becomes useful instead of just nice to look at.
When a new project lands in your inbox, run it through your filters before excitement or fear or external pressure has a chance to take over. Get the cold facts on the table first, then let the feelings into the conversation, and decide once you’ve actually looked at both.
An example. A job offer comes in with a great title, a significant raise, and stock options, the kind of package that should trigger an immediate yes. But two of your filters are “allows for 3+ hours of uninterrupted deep work daily” and “serves a mission I care about.” You do the research and find that the role is light on deep work and heavy on stakeholder management, and the company’s mission is making a social media platform better at engagement and ad targeting, which is something you’ve literally said out loud you don’t care about. The role fails both filters, and actually fails most of your filters once you keep going down the list. So you don’t take it.
That sounds simple in writing, but in the moment, with the title and the money sitting on the table, it isn’t simple at all. The only thing that makes it simple is having written down what matters to you in advance, so you’re not deciding in the heat of the moment based on what feels good right now.
Share it, strategically
You don’t have to keep all of this to yourself, and there’s real value in letting other people in.
Share your mission with your manager so they understand the throughline of what you’re trying to build. That conversation might steer them toward giving you projects that actually matter to you, or it might surface that your current role isn’t aligned with where you’re heading. Either piece of information is useful.
Share your Career Hypotheses with a mentor and ask them to push back. Telling someone you trust “I believe learning AI-assisted design will make me more valuable in civic tech roles” gets you a real reaction from someone with perspective, instead of you marinating in your own thinking.
Share your skill goals with peers for accountability, because once your peer group knows you’re trying to get strong at design systems this year, they can point you at resources, opportunities, and people you wouldn’t have found on your own.
Sharing this stuff isn’t the same as broadcasting it. It’s selective transparency with the handful of people who actually care and can help.
Recognize when to pivot
Your Career OS will change. Your vision will evolve, your mission will shift, and that doesn’t mean you got it wrong the first time, it means you’re paying attention. There are a few specific triggers worth watching for.
Your Career Vision Narrative is starting to feel impossible in your current environment. You wanted deep work, your organization is meetings-by-default, and nothing about that is going to shift in the next year. That’s a signal.
Your mission has changed and your current role is irrelevant to it. You used to care about corporate e-commerce and now you care about civic technology, and your director role at a retailer doesn’t serve the new direction. That isn’t a problem to solve, it’s clarity to act on.
You’ve hit a learning plateau. You’ve been in this role for three years, you’ve learned what there is to learn, and you’re not growing anymore. That doesn’t mean panic, it means it’s probably time to move.
Market shifts are reducing the value of your current skill set. AI is reshaping design work right now, and you can either pretend you don’t need to adapt or you can put learning AI-assisted design into your hypothesis stack. The market is telling you something, and it’s worth listening.
Build a review rhythm
This isn’t a set-it-and-forget-it artifact, so build the check-ins into your calendar.
Quarterly, look at your skills inventory and ask whether you’ve gotten stronger in the areas you said mattered, or whether new skills are showing up that you didn’t expect. Update your hypotheses, see which ones are still true and which are being disproven, and decide what new experiments you want to run. Look at your network gaps and identify the people you should be connecting with.
Annually, do the bigger refresh. Revisit your Career Vision Narrative and ask whether it still resonates or whether what you actually want has shifted. Adjust your filters and check whether they still reflect your values, and whether there are new criteria that matter now that didn’t matter a year ago. Reassess your mission and see if it still energizes you.
When something significant happens, like a big move, a burnout moment, a market crash, or a breakthrough in your thinking, revisit the whole thing. Sometimes a crisis is exactly what forces you to get clear about what actually matters.
Tools to keep it alive
You need something to prevent it from going into a drawer.
Notion if you like building dashboards. Coda if you want something that feels more like a document. Miro or FigJam if you’re visual. Trello if you want dead simple. Google Calendar if you mostly need a recurring event that drags you back to the OS once a quarter.
The tool isn’t the thing. The system is the thing. The tool is just what makes the system visible and actionable.
Full circle
This whole series started with a question: what if you designed your career with the same rigor and intentionality you bring to designing a product?
A product OS is a system that helps you make consistent decisions, with constraints and criteria and feedback loops that evolve as real-world input comes in. Your Career OS is the same idea applied to your own life. It isn’t a one-time plan so much as a design practice, and the more you use it the more it adapts with you, gets more accurate, and actually starts guiding your decisions instead of just looking nice on a page.
I spent most of my early career making moves based on what sounded good in the moment, the promotions that looked perfect on paper and the companies with great brands and the roles with the right title. Some of those moves worked out and some didn’t, but I wasn’t making them systematically. I was making them based on noise.
The Career OS gave me a way to think systematically about something that’s usually chaotic and emotional. It gave me a decision engine, and that engine has been worth more to me than any title or raise.
Your turn
Do an OS review. Have you lived a week that actually resembles your Career Vision Narrative, and how did it feel? Does your mission still light you up, or has it shifted? Which of your Career Hypotheses have you proven or disproven, and what did you learn from the ones that didn’t work? Do your filters still make sense, or have your values changed? What new experiments do you want to run in the next quarter?
Write it down, not to make a perfect document but to know where you actually are and where you’re trying to go.
That’s your system. Use it, let it be messy, let it be wrong sometimes, because that’s how it gets better.
Thanks for reading Systems & Signals through this entire series. If you’ve built any part of your Career OS, I’d love to hear about it. The system only becomes real when you use it, and it only stays alive when other people use theirs too.
We’re back to standard posting later this week. See you then!
— Justin