Lose fewer people, not more.


A longer letter this week, because the public article on LinkedIn could not say everything I wanted to say.

For full article link is here:

https://www.linkedin.com/pulse/why-leaders-who-run-transfer-window-lose-fewer-people-daniel-k%C3%A4fer-ba5hf

The piece I published — Why the leaders who run the Transfer Window lose fewer people, not more — argues that running an AI organisational redesign on purpose protects more of your team than waiting for one to be handed to you. The argument lands cleanly in public. The harder version, the one I wanted to write but did not, is this.

The reason most senior leaders hesitate to engage on this work is not because they doubt the framework. It is because they are afraid that asking for help signals weakness. If I bring someone in to lead a workshop on AI-driven organisational redesign, am I building the case for my own redundancy? Am I telling my CEO I cannot handle this? Am I putting a target on my back?

I cannot publish that fear in feed. Naming it publicly would feel like accusation. But I can say it here, because you opened this email, which means you are already inside the conversation.

The fear is real, and it is the wrong fear.

In every leadership team I have worked with over the last eighteen months, the senior person who initiated the Transfer Window work was not the one who got cut six months later. They were the one who shaped the redesign for the function. They were the one whose name got attached to the working plan that went to the board. They were the one the CEO called when the spreadsheet conversation arrived from above, because they had already done the thinking and had a defensible position.

The leaders who got caught were the ones who waited. Their function got redesigned by finance, by technology, by the board, or by a consulting firm that arrived with a framework they did not author. Their seat was not at risk because they engaged. Their seat was at risk because they did not.

This is the part the public newsletter could not say. It would have read as fear-mongering, or as a pitch dressed up as analysis. But it is also true, and you are reading this because you have probably been sitting with some version of the question yourself.

The other thing I want to say here, which the public article only gestured at, is what the work actually looks like inside a leadership team.

It is not what most people expect. There is no consultant deck. There is no maturity model. There is no slide that ranks your function against a benchmark. What there is, is a structured half-day conversation with you and your direct reports, where we score your own function against the fourteen archetypes together, find the seats that are misclassified on your current org chart, identify the three moves that matter most over the next two quarters, and work out what to do about the people whose roles are dissolving — before the dissolution arrives.

The leadership teams I have done this with describe it the same way afterwards. They use phrases like finally having the conversation we have been avoiding and seeing what was already there. The diagnostic does not invent new problems. It surfaces problems the team was already carrying privately, and gives them a structured way to talk about them.

The people who walk out of these rooms with the most relief are usually the most senior. Because they had been holding the redesign question alone, and they did not have to anymore.

So this is the thing I wanted to say to you specifically.

If you are sitting with this question in your own function — if you have read the article or the Transfer Window post and recognised something — the next step is not necessarily a Calendly call. It can be much simpler than that.

Reply to this email. Two or three sentences about where you are sitting and what the noise around the redesign actually sounds like in your function. I read every reply personally. We will find a way to have the conversation, on your terms, calibrated to what you actually need.

Some of those exchanges become workshops. Some become advisory engagements. Some become a longer email back from me with a few specific thoughts and nothing else. The point is not the funnel. The point is the conversation.

Reply if you want to start one.

Daniel

daniel@danielkafer.com

www.danielkafer.com

_________________________________________________________________________________

Daniel Käfer Strategic Advisor · Keynote Speaker · Author danielkafer.com

P.S. The full article is here if you have not read it yet — https://www.linkedin.com/pulse/why-leaders-who-run-transfer-window-lose-fewer-people-daniel-k%C3%A4fer-ba5hf

Daniel Kafer

Daniel Käfer is a visionary and international futurist, renowned for driving thought leadership through his writing, videos, and keynote speeches. At the forefront of future innovation, his expertise spans AI, the Metaverse, social media, digital transformation, and digital marketing.Globally recognized for his thought leadership, Daniel has delivered impactful keynotes and digital transformation workshops in major cities including Menlo Park, San Francisco, New York, Dubai, Riyadh, Paris, Basel, Hamburg, Copenhagen, Stockholm, Oslo, and Helsinki.As an accomplished author, Daniel has written "Medie Theory" released in 2012, "Release the brakes on growth" released in January 2020 and Hyperintelligence released globally by Wiley, Gyldendal and CITIC.With a professional background that includes serving as the country head of Meta and Group Director at Ooredoo, Daniel now focus on Futurism through his books, Podcast and keynotes.

Read more from Daniel Kafer

A month ago I published the first volume of The AI-Compressed Organisation, mapping how AI restructures the HR function inside a 10,000-person enterprise. The argument was that AI does not optimise functions. It restructures them, around four operating postures: AUTOMATE the execution layer, AMPLIFY the adaptation work, SUPPORT senior decisions with structurally better inputs, PROTECT the small reserved category where visible human craft is the value. Volume 2 is now published. It runs the...

AI Re-design sequence

Most AI transformations fail before the first tool is deployed. Not because the technology is wrong. Because the order is wrong. The organisations spending the most on AI in 2026 are making the same mistake. They start with the platform. The consultants. The go-live date. They treat AI transformation the way they treated digital transformation — as a technology project with a people component bolted on at the end. It does not work. It has never worked. And the data makes this uncomfortable...

If you subscribed after the Microsoft post, you already know the headline. HR is being redesigned around AI-era capabilities. The senior people leadership layer at Microsoft is gone. Oracle just told 30,000 people they were fired via a 6am email - with no HR conversation, no manager call, no human involved in the process at all. But the question I keep getting asked privately is not about Microsoft or Oracle. It is: what does this actually mean for my function, in my company, right now? So...