This month we've looked at which parts of your job are actually defensible and why your company's resilience training is designed to help you survive their decisions, not make your own.
Now here's how to use both frameworks together to build something organizations can't take away: genuine optionality.
And it's something you build on purpose: pairing the parts of your work that are hardest to automate with real independence from any single employer. Below: the framework, the three moves, and a 30-day plan.
The Problem With Organizational Resilience
Here's what I've realized after running development programs for two decades: when companies invest in your resilience, they're not investing in your ability to make choices. They're investing in your ability to absorb their choices.
The wellness campaigns. The adaptability workshops. The "thriving through change" seminars. They're all designed around the same premise: change is inevitable (because we're implementing it), so you need to get better at handling it (because we're not slowing down).
It's not that these programs are insincere. Most are delivered by people who genuinely care. But they're structurally designed to make you more flexible to organizational decisions, not more capable of making your own.
Last week we mapped your dependencies (the single points of failure that make you vulnerable to decisions you don't control). The week before, we assessed which parts of your job are actually defensible against automation and restructuring.
Both exercises were diagnostic. They help you see your position clearly. But diagnosis isn't strategy.
Why Most People Stay Stuck
The reason most people don't build genuine optionality isn't because they don't see the risk. It's because they confuse two different types of resilience:
- Organizational resilience: The ability to bounce back from changes your employer makes. Adapt to new tools. Adjust to restructured teams. Learn new processes. Stay productive through uncertainty.
- Personal resilience: The ability to make different choices when the current situation stops working for you. Not because you're fleeing problems, but because you've built enough capability and reduced enough dependency that you could make a different choice if needed.
Most resilience training teaches the first. Almost none teaches the second.
Because here's what organizations don't say out loud: they need you to be resilient to them, not resilient from them. They need you to adapt to their AI adoption plans, their restructuring decisions, their strategic pivots. They don't need you positioned to leave if those changes don't work for you.
Your employer's job is to optimize the organization. Your job is to optimize your position.
The Synthesis You Need
If you've been following this month's work you've done two assessments:
- Dependency mapping: What you're exposed to if things change.
- Capability assessment: What you can defend with if things change.
Now we're going to combine them into something actionable: a strategy for building genuine optionality that doesn't require you to quit your job or panic about the future.
This isn't about becoming paranoid. It's about becoming strategic. And it starts with understanding where your highest risks actually are.
The Combined Framework: Finding Your Highest-Risk Intersections
Here's what most people miss: your biggest vulnerability isn't your longest dependency list or your lowest-scoring capability. It's where those two things intersect.
When you're heavily dependent on something that you can't defend well, that's your highest-risk exposure. That's where organizational decisions hit hardest and fastest.
Mapping the Intersection Points
Take the two assessments you've already done.
From your Dependency Map, you identified:
- Tools and platforms you rely on
- Processes and workflows you need
- People and relationships that protect your function
- Assumptions about stability you're making
From your Capability Assessment, you scored your job components as:
- DEFEND: High across all dimensions (difficult to automate, valuable, strategically important)
- DEVELOP: Mixed scoring that needs strengthening
- DIVERSIFY: Low automation difficulty (getting automated eventually)
- DOCUMENT: High automation risk, high value extraction (actively being evaluated)
Now overlay them: Which of your dependencies rely on capabilities in the DIVERSIFY or DOCUMENT quadrants?
That's your danger zone.
A Real Example: The LMS Administrator
I worked with someone whose entire role was built around administering their company's learning management system. Let's call her Sarah.
Sarah's dependency map looked like this:
- Tool dependency: Complete reliance on one proprietary LMS.
- Process dependency: Her value came from managing workflows specific to that system.
- Relationship dependency: Reported to the VP of L&D who championed the current tech stack.
- Stability assumption: The company would continue investing in structured learning programs.
Her capability assessment told a different story:
- LMS administration: DIVERSIFY (low automation difficulty, medium value extraction, medium strategic importance)
- Reporting and analytics: DOCUMENT (medium automation difficulty, high value extraction, low strategic importance)
- Instructor support: DEVELOP (medium automation difficulty, medium value extraction, medium strategic importance)
- Content strategy: DEFEND (high automation difficulty, medium value extraction, high strategic importance)
The highest-risk intersection:
Tool dependency + DIVERSIFY capabilities + Single relationship protection
This isn't a resilience problem. It's a structural exposure problem. Organizational resilience training would tell Sarah to "embrace change." That teaches her to bounce back from decisions, not to reduce her exposure to those decisions in the first place.
The Three Strategic Moves
Once you've identified your highest-risk intersections, you need to move deliberately. Here are the three moves that actually work:
Move 1: Reduce High-Risk Dependencies on Low-Defense Capabilities
If you're heavily dependent on something that scores DIVERSIFY or DOCUMENT, that dependency needs a backup plan now.
For Tool Dependencies: If you're reliant on one platform, become expert in the category, not just the tool.
- The Move: Spend one hour per week learning adjacent tools. Not to replace your current expertise, but to make your expertise portable.
For Process Dependencies: If your value comes from managing one specific workflow, document the outcomes that workflow achieves, not just the process itself.
- The Move: Identify three different ways to achieve the same outcome your current process delivers. Pick one and prototype it.
For Relationship Dependencies: If one person protects your function, you need more advocates.
- The Move: Identify three stakeholders one level removed from your current protection. Make your work visible to them over the next quarter.
For Stability Assumptions: If you're assuming something will stay constant (budget, team structure), test that assumption now.
- The Move: Ask direct questions. "How is our learning strategy evolving?" Don't guess. Gather information.
Move 2: Convert Dependencies Into Portable Capabilities
A dependency is something you need that's controlled by someone else. A capability is something you can do that you control. When you become expert enough at managing a dependency that others need your expertise, you've converted it.
Sarah's conversion strategy: Instead of just using the LMS, she became the person who could:
- Evaluate and compare learning platforms (portable capability: technology assessment)
- Design learning experiences that work across different systems (portable capability: experience design)
- Train others to use learning tools effectively (portable capability: enablement)
Your conversion strategy: For each dependency on your map, ask: "What skill or expertise would I need to develop to make others dependent on me for managing this?"
Move 3: Build Your Minimum Viable Optionality
Genuine optionality isn't about having perfect fallback plans. It's about staying in your current role becoming a choice, not a necessity.
Minimum Viable Optionality means:
- You could have a credible conversation with another employer if you needed to.
- You have at least three capabilities that are valuable outside your current context.
- You have enough reduced dependency that a major change wouldn't destabilize your position.
- You have evidence of your impact that you control (not locked in systems you don't own).
The 30-Day Build: Your Implementation Roadmap
You don't need to do everything at once. You need to move deliberately over the next month.
Week 1: Run Both Audits
Days 1-3: Dependency Mapping. Document your dependencies across four categories:
- Tools and platforms you rely on
- Processes and workflows that define your role
- People and relationships that protect your function
- Assumptions you're making about stability
Days 4-7: Capability Assessment. Score your job components across three dimensions (Automation Difficulty, Value Extraction, Strategic Importance) and plot them into quadrants: DEFEND, DEVELOP, DIVERSIFY, DOCUMENT.
Week 2: Identify Your Highest-Risk Intersections
Days 8-10: Overlay the Assessments. Where do your dependencies land on capabilities in DIVERSIFY or DOCUMENT quadrants? Pick your top three highest-risk intersections.
Days 11-14: Gather Information. Test your stability assumptions. Ask direct questions regarding strategy evolution and leadership discussions.
Week 3: Build One Backup, Strengthen One Portable Capability
Days 15-21: Take Action. Pick one high-risk dependency and one portable capability to work on.
- Backup plan for dependency: Learn an adjacent platform, identify alternative processes, or build visibility with a new stakeholder.
- Strengthen portable capability: Identify what expertise level would make you valuable beyond your current context and take one concrete action (course, project, mentorship).
Week 4: Test Your Optionality
Days 22-28: Validate What You've Built. Take one of these actions:
- Have a conversation with a recruiter in your field (to understand market value).
- Reach out to someone in a parallel role at a different company.
- Apply your portable capability to a problem outside your current context.
- Update your LinkedIn profile to reflect portable capabilities, not just job titles.
Days 29-30: Reflection and Planning. Write down: What did I learn about my actual exposure? Which intersection points are higher risk than I thought? What's my plan for the next 90 days?
What Success Actually Looks Like
After 30 days of deliberate work, here's what changes:
The Automation Fear
- Before: "I hope they don't automate my role."
- After: "If they automate parts of my role, I have three other capabilities that remain valuable and two backup plans for the highest-risk areas."
The Manager Reliance
- Before: "I rely on my manager to protect my position."
- After: "I have four stakeholders who value my work, and my capabilities are visible across the organization."
The Career Agency
- Before: "If this job ends, I'd have to start from scratch."
- After: "If this job ends, I can articulate my value in ways that are immediately relevant to other organizations."
This Week's Action
Pick one intersection point where a dependency lands on a low-defense capability. Choose one of the three moves:
- Build a backup for that dependency
- Start converting it to a portable capability
- Test the stability assumption you're making
Don't try to fix everything. Move deliberately on the highest risk area. You're not being paranoid. You're being strategic.