action7 min read

The One Meeting That Can Save Your Job During AI Restructuring

Let me tell you about a meeting that takes 30 minutes and might be the most important half hour of your career.

It's not a performance review. It's not a one-to-one. It's not an interview. It's a meeting you request, you set the agenda for, and you control. And the purpose is to make yourself indispensable before someone decides you're dispensable.

i've watched restructuring processes from the inside as a consultant. The people who keep their jobs during AI-driven cuts share one trait: they took action before the consultation letters arrived. This meeting is that action.

What the meeting is

You're going to request a 30-minute meeting with your manager (and ideally your skip-level manager too, but we'll get to that) where you present a concrete proposal for how AI can be used in your team, with you at the centre of it.

Not a vague "I think AI is interesting" chat. Not a "what's happening with AI?" question session. A proper, specific, here's-what-I-propose meeting.

The difference between asking about AI and proposing an AI solution is the difference between looking worried and looking valuable. One of those people gets restructured. The other leads the restructuring.

When to have it

Timing matters enormously.

Too early = before there are any signs of restructuring. If nothing is happening, your proposal might land but it might also feel random.

Too late = after consultation letters have gone out. By then, the decisions are made and no meeting is changing them.

Just right = when you can see the signs but before anything has been formally announced. When the town hall language has shifted. When the efficiency talk has started. When the new Head of AI is doing their rounds. This is the window. In this window, decisions about the future team structure are being made but haven't been finalised. Your proposal can influence those decisions.

If you're not sure where you are on this timeline, have the meeting anyway. Even if the timing isn't perfect, the act of presenting a concrete AI proposal can only help you.

How to prepare (one evening)

You need three things:

1. One specific AI application for your team.

Not a generic "we should use AI" suggestion. A specific problem, a specific AI tool, and a specific expected outcome.

"Our team spends approximately 15 hours per week on [specific task]. I've tested using [specific AI tool] to assist with this. In my testing, it reduced the time to approximately 5 hours while maintaining quality. If we implemented this across the team, we could redirect 40 hours per week to [higher-value work]."

If you haven't tested anything yet, spend tonight building a quick proof of concept. Even rough results are better than theoretical proposals.

2. Your role in the solution.

This is the critical part. Your proposal needs to position you as the person who makes it work.

"I'd like to lead the implementation of this. I've already built the initial workflow and I understand both the AI tools and our team's processes. I can have a full pilot running within two weeks and results to share within four."

You're not asking for permission to play with AI. You're offering to drive measurable improvement. There's a universe of difference.

3. The numbers.

Time saved. Cost saved. Quality improved. Whatever metric matters to your manager, attach a number to your proposal. Rough numbers are fine. Exact numbers are better. But any number beats no number.

"Estimated time saving: 40 hours per week across the team." "Estimated annual cost saving: £85,000." "Estimated error reduction: 30% based on initial testing."

Managers live and die by numbers. Give them numbers they can put in their own business case.

This topic is covered in detail in AI Proof Your Job: The 30-Day Survival Checklist Get it for $7

The meeting itself

Request it simply: "I've been working on something I'd like to show you. Can I get 30 minutes this week?" No need to oversell it.

Minutes 1-5: The problem. Describe the specific inefficiency or pain point you've identified. Use the team's own language. Make sure they recognise the problem as real and annoying.

Minutes 5-15: The solution. Demo what you've built or tested. Show real examples. "Here's what the input looks like. Here's what the AI produces. Here's the final output after my review." Keep it practical. No theory. No slides about "the future of AI." Just "here's the thing, here's what it does, here's the result."

Minutes 15-20: The proposal. "I'd like to lead a two-week pilot. I need [minimal resources]. I'll track [specific metrics]. At the end of two weeks, I'll present results and a recommendation for whether to roll it out."

Minutes 20-30: Discussion. Answer questions. Listen to concerns. Be honest about limitations. "The AI isn't perfect at [specific thing]. That's why human review is still needed. But it handles the routine parts well enough to save significant time."

What happens after

One of three things:

Best case: Your manager says yes. You run the pilot. It works. You've now demonstrated AI capability, initiative, and leadership. When restructuring decisions are made, you're the person who showed they can work in the AI-augmented future. You're not on the "at risk" list. You might be the one managing the transition.

Middle case: Your manager says "interesting, let me think about it." Follow up in a week. Whether they approve the pilot or not, you've changed how they see you. You're the person who brought a concrete AI solution to the table. That perception shift matters during restructuring conversations.

Worst case: Your manager says no. That's fine. You've still demonstrated initiative and AI capability. You've still shifted the perception. And you've built something you can put on your LinkedIn and talk about in interviews. Nothing is wasted.

The skip-level version

If you can get your manager's manager in the room, the impact multiplies. Skip-level managers are often the ones making restructuring decisions. Having direct exposure to you and your ideas means you're not just a name on a spreadsheet.

Don't go behind your manager's back. Ask your manager: "Would it be useful to present this to [skip-level manager] as well? I think the efficiency case is strong enough for their attention."

Most managers will see this as a win for them too. Their team member is driving innovation. That reflects well on them.

Why this works

During restructuring, the people making decisions are sorting everyone into two categories: "future" and "past." They're asking: who fits in the new AI-augmented organisation and who doesn't?

This meeting moves you firmly into the "future" column. Not because of a title or a certification or a course you took. Because you showed up with a working solution, a clear plan, and the initiative to make it happen. That's what people who belong in the future organisation look like.

i wish i'd had this meeting before my own redundancy. i had the skills. i had the ideas. i just didn't have the sense to present them before someone else decided i was expendable. Don't make my mistake.

The one thing to do today: identify the one process in your team that wastes the most time. Write down what it is, how many hours it takes, and how AI might help. That's your meeting preparation started. Now book the meeting.

Get the 30-Day Checklist — $7

Instant download. 30-day money-back guarantee.

Includes 7 role-specific playbooks, AI glossary, and redundancy rights cheat sheets for US & UK.

Not ready to buy? That’s fine.

Get 3 free tips from the guide. No spam.