Category: Transformation

The reason your team isn’t using AI has nothing to do with AI

A few weeks ago I posted on LinkedIn that one topic got me out of bed early during my focus break. AI Agents. And more broadly: why AI adoption moves so much slower inside most organisations than it should. Those weeks didn’t just change how I think. They produced Linelia’s first workshop product.

I’ll be honest: six months ago I would have smiled politely and made quiet jokes about everyone becoming an AI expert overnight. What changed was time and focused attention. Scepticism turned into clarity. That is the only position from which I think it is worth offering anything to a client. Not enthusiasm. Clarity.

This post shares what we built, why, and three things your team can try today. No new tools required.

Start here: a five-minute audit for your team

Before any tool, before any prompt, there is one question worth asking honestly: where are you still doing manually what AI could already handle?

The right starting point is your last five working days. Run through these three questions:

🗂️ Where did you spend time formatting, summarising, or restructuring information?
Meeting notes into action items. Email chains into briefings. Reports rewritten for a different audience. Not glamorous. Exactly where AI saves the most time, fastest.

📄 Where did you start from a blank page when you didn’t need to?
First draft of a proposal. Opening of a difficult message. Structure for a presentation you’ve given a dozen times. Starting from zero is a habit, not a necessity.

🔀 Where did you context-switch instead of focus?
Information from three sources. A brief rewritten three times. Twenty minutes on something that should have taken five. AI removes the friction that makes task-switching so costly.

If you answered honestly, you probably identified two or three hours per week. Without changing a single tool in your stack.

The question is never which AI tool to use. It’s where in your actual workday the friction is highest.

One prompt technique worth trying this week

Tool-agnostic. Works in whatever your company already uses. It’s called the role-task-format prompt.

Instead of typing what you want, tell the AI three things: who it should be, what you need done, and what the output should look like.

❌ Weak prompt: “Summarise this meeting.”

✅ Strong prompt: “You are a senior project manager. Summarise this meeting transcript into five bullet points, each no longer than one sentence, focused on decisions made and next steps agreed. Flag any open questions that still need an owner.”

Same tool. Completely different output. AI responds to specificity the same way a good colleague does. Vague input produces vague output.

In the workshop, this is usually the moment something clicks. Not because the technique is complicated. Because people realise they have been treating AI like a search engine instead of a thinking partner.

🎙️ One more tip: use your voice. Speak your prompt instead of typing it. You’ll add context more naturally and get better results instantly. You already send voice messages without a second thought. Talking to your AI is exactly the same habit. Just more useful.

Vague input produces vague output. AI responds to specificity the same way a good colleague does.

The honest reason AI adoption for teams stalls, and it’s not the tools

Everything above, you could have figured out yourself. The audit questions are not proprietary. The role-task-format prompt is not a trade secret. So why are most teams still stuck at the curiosity stage?

Not because the content is hard to find. Because the calendar always wins.

In every organisation I have worked with across energy, FMCG, media, and agencies, the pattern is the same. A topic – like AI – goes on the agenda. Someone shares an article. A pilot gets discussed. Then a real deadline appears, and the topic goes to next quarter. Then the quarter after that. This is not a motivation problem. It is a structural one.

That is the actual reason external workshops exist. Not because the facilitator knows things your team does not. But because booking three hours with an outside person makes it real. The calendar gets blocked. Laptops come out. People work on their actual tasks, not invented scenarios.

In my work at Linelia, I designed the workshop around exactly this insight. No slides. No demos. No case studies from other industries. Teams share their real briefings and workflows in advance. Every output from the three hours is something participants can use the following Monday.

Three hours of protected focus time, working on real tasks, is worth more than six months of “we should really explore AI.”

What your team walks away with

The workshop runs two to three hours, groups of six to eight, in-person or remote, tool-agnostic by design. Every participant leaves with four things:

📚 Prompt library tailored to their specific role
📅 30-day action plan tied to real workflows
🗺️ Tool map that fits your existing stack, no vendor pitch
✅ Real outputs created during the session itself

The format is modular: a single pilot for one team, department-by-department rollout, or a company-wide programme including a leadership track covering governance and adoption. It scales to where you are.

The pilot starts with one kickoff call. If this sounds like something your organisation is ready for, find out more about it or get in touch directly.

Common questions

What does an AI adoption workshop actually involve?
The session runs two to three hours with a group of six to eight people working on their own real tasks, not invented scenarios. Before the session, participants share actual briefings, reports, or workflows they want to improve. Every output is something usable the following week.
Do we need specific AI tools installed before the workshop?
No. The workshop is tool-agnostic by design. It works with whatever your team already uses, whether that is Microsoft Copilot, Claude, ChatGPT, or any other AI assistant already in your stack. No new software or licences are required.
Why bring in an external facilitator instead of learning internally?
The content is freely available. The facilitator’s job is to create protected time where learning actually happens, focused on your real workflows, so every person leaves with something concrete rather than a slide deck they will never open again.
How quickly can we expect results after the workshop?
Participants leave with a 30-day action plan tied to specific tasks in their existing workflow. Most teams report meaningful time savings within the first two weeks, typically in the areas identified during the self-audit at the start of the session.
Working on an AI adoption challenge in your organisation? I am happy to talk it through. Reach out via linelia.io/contact/ or connect with me directly on LinkedIn.
May 7, 2026
Why most digital transformations fail before they start

The room was full of smart people. The strategy deck was polished. Leadership had approved the budget months earlier. And twelve months later, almost nothing had moved. It is the most common form of digital transformation failure I know.

I have watched this play out more times than I would like to admit. Across transformation mandates at companies including EnBW and L’Oréal, and across media businesses and agencies over the past fifteen years, I have seen well-funded digital initiatives stall, shrink, and quietly disappear. Not because the technology was wrong. Not because the market shifted. The conditions for success were simply never in place.

In my work at Linelia, digital transformation failure is what I keep coming back to:

Most digital transformation failure does not happen in execution. It happens before the first kick-off meeting.

Here is what that looks like in practice.

The problem is rarely the technology

When a transformation runs into trouble, the instinct is to look at the tools. The platform was wrong. Vendors had promised too much. Integration proved more complex than expected. These are real problems. But they are almost never the cause of failure. They are symptoms.

The actual failure usually happened three to six months earlier, in the room where the transformation was first defined. Specifically: no one defined what “digital transformation” actually meant for this organisation, at this moment, with these people and this budget. Everyone assumed it. A vague phrase became a project mandate. The mandate became a programme. The programme hired vendors and bought software. And then, somewhere in month four, someone asked a question no one could answer: what, exactly, are we trying to change?

The same applies to methodology. Agile ceremonies, OKR frameworks, design thinking workshops — these can become rituals that signal progress without driving it. I have sat in sprint reviews where no one could explain what was being transformed, or why. The process was running. The transformation was not.

Technology does not transform organisations. Decisions do. And if the decisions are not made clearly at the start, the technology becomes a distraction from the fact that they were never made at all. This is the root of most digital transformation failure.

Technology does not transform organizations.
Decisions do.

Transformation without a mandate

The second pattern I see consistently: leadership announces a transformation but never assigns the authority to drive it. Someone gets a title. A steering committee forms. A kick-off happens. But when the first difficult trade-off arrives, and it always does, no one is empowered to make the call.

Many transformations are announced not because leadership has identified a specific problem that needs solving, but because the topic is trending. Competitors are doing it. The board is asking about it. A consultant has presented a convincing deck. And so the program begins, with senior sponsorship that is visible on the launch slide and largely absent from the first difficult conversation. That is not a mandate. That is a press release.

This is particularly common in large, matrixed organizations where the culture defaults to consensus. Transformation requires someone with the mandate to say: we are moving in this direction, and we are stopping that. Without that clarity, the project becomes a negotiation. Every decision gets relitigated. Momentum slows. And eventually the transformation quietly becomes business as usual, just with more meetings.

I see this in interim mandates regularly. Organisations bring in external leadership precisely because the internal structure has struggled to move. But if no one has clearly defined the mandate from day one, even an experienced interim manager is navigating without a map.

The mandate question is not about hierarchy. It is about clarity. Who decides? Who has the right to stop something? And who carries accountability when the transformation stalls? If those questions do not have clean answers on day one, digital transformation failure is already underway.

If the mandate is not clearly defined from day one, even an experienced interim manager is navigating without a map.

The roadmap that ignores the organisation

The third pattern is perhaps the most seductive, because it produces beautiful slide decks.

An organisation invests significant time and money in a transformation roadmap. The team defines workstreams, sets milestones, and maps dependencies. It looks thorough. It looks serious. And then it runs straight into the organisation’s actual operating reality and stops.

Most transformation roadmaps are built around what needs to change, not around the organisation’s current capacity to absorb change. They treat the people, the processes, and the culture as a fixed backdrop against which the transformation unfolds. But those things are not fixed. They push back. And if the roadmap does not account for that, it becomes a document that describes the future without any honest reckoning with the present.

A transformation plan that ignores the organisation’s change capacity is not a plan. It is a wish.

Real transformation planning starts with an honest assessment of where the organisation actually is. Not just technically, but culturally. What is the leadership team’s appetite for disruption? Where are the informal power structures that will slow things down? What has been tried before and why did it stop? These questions are harder than building a Gantt chart. They are also more important.

A transformation plan that ignores the organisation’s change capacity is not a plan. It is a wish.

How to avoid digital transformation failure: what has to happen first

None of this is to say that transformation is impossible. It is not. But the organisations that move through it successfully tend to share a few things in common.

They define what they are actually trying to achieve in concrete terms, not aspirational language. They identify who has the authority and the accountability to drive change, and they protect that person’s mandate. Before committing to a pace and a scope, they take an honest look at their actual capacity for change. And they treat the early phase not as a formality to get through, but as the most important work the transformation will produce.

Getting the setup right is not the slowest path to transformation. It is the fastest one. The organisations that skip it spend the next eighteen months recovering from a start they should have taken more seriously.

This is where Linelia’s transformation work typically begins: not with a platform recommendation, but with a set of hard questions that most organisations find easier to defer than to answer.

Common questions

What is the most common reason digital transformations fail?
Most transformations stall not because of the technology, but because of a gap between strategic intent and execution capacity. The objectives are vague, the mandate is unclear, or the plan does not account for the organisation’s actual readiness to change. These are setup problems, and they rarely get resolved once the programme is running.
What does it mean to have a transformation mandate?
A transformation mandate is explicit authority to make decisions, stop things that are not working, and hold people accountable for progress. Without it, even a well-resourced transformation becomes a slow negotiation. It is not about hierarchy. It is about clarity of ownership.
How do I know if my organisation is ready for digital transformation?
Readiness is less about having the right technology and more about having the right conditions: clear strategic intent, leadership alignment, honest understanding of current capability, and appetite to make real decisions under uncertainty. A useful starting point is an honest assessment of where your organisation is, not where you would like it to be.
When does it make sense to bring in external consulting support?
External support, whether in the form of interim management, advisory, or project-based consulting, is most valuable when an organization needs to move faster than its current structure allows, when a specific challenge requires outside objectivity, or when a critical gap opens mid-programme. The key is defining the scope and mandate clearly from day one, so the external partner can actually move at the pace the situation requires.
If your organisation is at one of these inflection points, whether a transformation is just getting started or has already hit its first wall, I am happy to talk through what the setup should look like. Reach out via the Linelia contact page or connect with me on LinkedIn to start the conversation.
April 7, 2026
Visibility without cringe? Still working on it.
Learning to show up publicly as a founder is surprisingly challenging.

Not because I’m shy, quite the opposite. I genuinely enjoy being on stage, connecting with people, moderating discussions, and exchanging ideas. That part has always energized me.

But talking about myself?

Writing about how I work?

Sharing insights publicly?

That’s where things quickly move into the territory of visibility without cringe … a space I still haven’t fully mastered.

These days, a few people told me they enjoy reading my articles. Real people, not just the LinkedIn algorithm.

That feedback made me pause and reflect on why visibility still feels odd sometimes and why it’s becoming a skill I need to embrace.

Why good work alone doesn’t create visibility

Inside large organizations, great work usually finds its way: leadership updates, cross-functional meetings, stakeholder presentations, internal communication (and sometimes political play) help make your work seen.

As a founder, that entire system more or less disappears.

Good work only speaks for itself when people actually see it.

And that’s where the challenge begins:

How to build visibility without cringe, without becoming overly polished or overly promotional.

Visibility matters because it builds trust long before someone reaches out.

It connects dots you don’t even know you’re drawing.

Mini-Hack:
If you can, talk about a learning instead of an achievement. It makes visibility feel more natural and less like self-promotion.

Personal visibility still feels a little strange

I’m not a quiet person.

But shifting the communication toward myself still feels unfamiliar.

For many years, the “sale” wasn’t me, it was the product, the team, the brand, the strategy.

Now, clients buy my judgment, my approach, my experience.

That shift requires a level of personal visibility I’m still getting used to. What surprises me is this:

Visibility isn’t difficult because I’m uncomfortable speaking. It’s difficult because it’s personal.

And personal always brings a bit of vulnerability, even if you’re used to being on stage.

The nice surprise: Feedback actually helps

When someone tells you they enjoy your content, your articles, or your reflections, it suddenly feels less awkward.

A few people said exactly this these days and it meant more than expected to me.

Visibility without cringe seems to become easier when you remember there are people on the other side. People who find value, resonance, or simply a smile in what you share.

Micro-Practice:
Before publishing, ask yourself: “Would this help just one other person?” If yes, it’s worth posting.

Why I’m trying to be visible anyway

The reason is simple and strategic:

Opportunities grow out of connection, not invisibility.

People need to understand how you think, what you stand for, how you approach challenges, and what kind of problems you solve. And it also helps me to understand and sharpen exactly this as well.

Visibility helps people recognize fit long before the first call.

It’s not about shouting. It’s about being present.

Fortunately, “visibility without cringe” seems to be possible when it’s built on value, not vanity.

What I’m Trying to Practice (Even If It Doesn’t Always Work)

To make visibility feel more natural, I’m experimenting with tiny habits. Not to become a content creator, but to stay present in a way that feels authentic.

Here’s what I’m trying:
- Sharing learnings, not wins
- Writing thoughts as they come, not polishing endlessly
- Publishing weekly (when life allows… last week it didn’t)
- Showing small behind-the-scenes moments
- Connecting instead of promoting
And yes, sometimes this fails completely.

Last week was exactly like this: three days in Munich, remote meetings between trains and dinners, and a weekend fully dedicated to family time and my new espresso machine.

Zero writing.

Zero “visibility.”

Lots of life.

Mini-Hack:
Capture ideas when they show up. In Notes, voice memos, or screenshots. Most of my posts start as a single sentence written in a rush or a super quick voice memo, recorded while running.

I Also Need to Get Better at… Taking Photos

Another unexpected challenge in this “visibility without cringe” journey:

Finding fitting photos for my articles.

I’m not naturally someone who takes selfies, documents every moment, or snaps pictures in meetings.

But for storytelling – and especially for LinkedIn – images matter.

It’s a skill I’ll need to train:

Taking photos that feel real, unobtrusive, and still reflect what I want to say.

Because the right photo makes an article more human.

The wrong one makes it… well, cringe. Some you can see on my LinkedIn or even here in the blog.

So yes, another founder skill to learn.

Add it to the list.

Visibility as a Founder Skill

Being visible isn’t about volume or perfection.

It’s about clarity, intention, and connection.

For founders, visibility helps:
- Build trust
- Create opportunities
- Show how you think
- Let people understand you more easily
- Bring your network closer
- and yes of course, support your business
I’m hopefully getting better at it.

Slowly.

One article, one post, one flat white at a time.

If you’re interested in how I help organizations navigate their own transformations, you can find an overview of my work here: Linelia’s services.

And as always, I’m happy to connect.

Whether you’d like to exchange ideas or explore how we might collaborate, just drop me a note via my contact page or connect with me directly on LinkedIn.
December 3, 2025
3 small behaviors making collaboration faster & easier
Collaboration sounds simple. In reality, it’s one of the biggest challenges across almost every organization I’ve worked with, from corporates to agencies to scale-ups.

Different teams move at different speeds, goals aren’t always communicated clearly, and priorities shift faster than people can realign. With a little everyday pressure, even the most motivated teams can slow down. Over the years, I’ve noticed it’s rarely the big frameworks or complex processes that change collaboration for the better…it’s the small behaviors.

Over the years, I’ve noticed that it’s often not the big frameworks or the complex processes that change collaboration for the better. It’s the small behaviors that improve collaboration.

The ones that take almost no effort, but create a huge impact on speed, alignment, and quality of work. Here are three of them…

1. Share insights broadly, not selectively

One of the biggest reasons collaboration slows is that information gets stuck in pockets…inside teams, between agencies, or along the hierarchy.

Not because people want to hide information, but because:
- Goals aren’t communicated clearly
- Assumptions aren’t challenged
- Political dynamics get in the way
- or simply because “everyone is busy”
The result is always the same:
- Decisions get delayed
- Meetings multiply
- Teams start solving different versions of the same problem
So here’s what I’ve learned:

Transparency removes friction big time!

So switch to a “default to share” mindset!

Not the huge “knowledge-sharing initiatives” but the small things:
- Share working drafts, not only final versions
- Summarize key insights after a call
- Align on goals early and write them down
- Don’t wait for the “perfect moment” to update others
Micro-Practice:
Work with a “default to shared” mindset for early insights and drafts.
If an update, thought, or learning could help more than one person, make it visible, even if it’s not polished yet. This creates alignment early and reduces unnecessary back-and-forth.

If you want to explore this further:

Team of Teams by Stanley McChrystal offers a great perspective on why transparent information flow is often more powerful than strict hierarchy especially in fast-moving environments.

2. Provide unfiltered truth, respectfully!

Many teams avoid being completely honest. Very often not because they want to hide something, but because they don’t want to disrupt harmony or step on someone’s toes.

The problem: lack of clarity slows down decisions far more than respectful honesty.

One of the advantages of being an external partner or interim manager is that you can name things without being tied to internal agendas. And often, that’s exactly what teams need.

Unfiltered truth doesn’t mean being harsh. It means being clear.

Sometimes it’s as simple as:
- “Does this really get us where we want to go?”
- “Aren’t we just solving a symptom, not the root cause?”
- “Do you really think timeline and ambition are aligned yet?”
Clarity accelerates decisions and these are behaviors that improve collaboration.

And most people appreciate it more than expected, because clarity creates confidence.

Micro-Practice:
Before offering honest feedback or a direct observation, start with a brief intent statement like
“My goal here is alignment and clarity.”
It lowers tension immediately and makes the message easier to receive.

If you want to explore this further:

Radical Candor by Kim Scott is an established framework for giving clarity while remaining respectful and constructive. A valuable read for anyone working across teams.

3. Ask the obvious questions

This is one of the most underrated leadership behaviors.

In many meetings, people hesitate to ask simple questions because they assume someone else must know the answer or because they fear it might sound too basic.

But here’s what I’ve learned:

If you’re thinking it, someone else is thinking it too.

And if nobody asks, the misunderstanding will surface later. Usually when it’s more painful.

Asking questions helps to:
- Unblock discussions
- Clarify assumptions
- Avoid misunderstandings
- Align on next steps
- Reduce politics and interpretation
Questions like:
- “Am I the only one who doesn’t quite get this?”
- “Can we clarify the goal one more time?”
- “What does success look like here?”
- “What is the constraint we’re working with?”
- “What do we absolutely need to decide today?”
These are simple questions, but they create alignment in seconds.

Micro-Practice:
Start meetings with a quick “common ground recap”:
What are we solving? Why now? What does success look like?
It aligns everyone before the discussion even begins and prevents misunderstandings from slowing teams down later.

If you want to go deeper:

A More Beautiful Question by Warren Berger is an excellent exploration of how simple questions lead to clarity, progress, and better decision-making.

Why these behaviors matter even more in interim and cross-functional work

Interim roles mean this:
You join moving teams, with projects already in flight, priorities shifting, and multiple stakeholders in the mix.

You don’t always have the luxury of long onboarding phases.

You need clarity fast.

That’s why these behaviors matter so much:
- Sharing information openly prevents misalignment
- Honest clarity accelerates decisions
- Asking questions helps you arrive at shared understanding quickly
And the truth is:

You don’t need authority to improve collaboration.
You just need intention.

Small behaviors, big impact

Collaboration doesn’t fail because people don’t want to work together.

It fails because small behaviors compound: silence, assumptions, politeness, uncertainty.

The good news: The opposite is also true. Small positive behaviors compound too.
1. Share openly
2. Say the helpful truth
3. Ask the honest questions
If you start with one of these next week, you’ll likely notice a difference immediately: In clarity, speed, and overall momentum.

If you’re curious how I support organizations in their own transformation journeys, you can find more about my work here: Linelia’s services

And of course, I’m always happy to hear from you. If you’d like to exchange ideas or explore how we might work together, feel free to reach out via my contact page or directly connect via LinkedIn.
November 21, 2025