Your marketing team runs a dozen tools. Probably more. Every one of them was bought for a good reason: to understand your customer a little better, to answer their questions a little faster.

So why do more tools so often leave you with more dashboards and fewer real answers? And why, at exactly that point, is everyone reaching for AI to fix it? Sorting that out is what martech stack consolidation is really about, and it is the step most teams skip right before they make things worse.

Quick definition first, because not everyone lives in this world. Your martech stack is simply the collection of software your marketing runs on. The analytics, the email platform, the CRM, the ad tools, the dozen dashboards nobody quite remembers buying. Stitched together, that pile is your stack.

How your martech stack got away from you

Nobody sets out to run a dozen tools. It accumulates. You start with two or three that clearly earn their place, then add one for a problem that felt urgent, then another a vendor swore would tidy up the last one. Scott Brinker’s industry map now lists more than 15,000 marketing tools to choose from, so there is always a defensible next purchase.

Each decision makes sense on its own. The sum does not. Gartner has found that marketers use less than half the software they pay for. In my experience, buyers worn down by the sprawl now want fewer suppliers, not more. What you are left with is a system no single person fully understands.

Nobody buys a bloated stack on purpose.
You assemble it one reasonable yes at a time.

Why AI makes a messy stack worse, not better

Here is the uncomfortable part. Garbage in, garbage out. Sh*t in, sh*t out. You know the rule. You just never pointed it at your own tools.

AI does not clean up a fragmented stack. It runs on whatever you feed it, and if that is duplicated records, three conflicting sources of truth, and definitions nobody agreed on, the model will hand you confident nonsense, faster and at scale. AI amplifies the coherence you already have. If you do not have any, it amplifies the chaos.

AI does not fix a fragmented stack.
It just lets you be wrong faster, and at scale.

The consolidation bet I made (and the part I would reconsider)

Across my years on the corporate side, at L’Oréal and later at EnBW, I kept making a version of the same bet. We pulled as much as we could onto Google. One ecosystem, one login, one version of the numbers. And it worked. Reporting got faster. The team stopped arguing about which dashboard was telling the truth.

Would I make the exact same call today? I am genuinely not sure. Consolidation buys you coherence. It also buys you lock-in. The single source of truth that made us fast also made us dependent on one company’s roadmap and one company’s pricing. That trade is real, and anyone selling you “just simplify everything” is skipping the honest half of the conversation.

Martech stack consolidation is about coherence, not fewer logos

So the goal is not fewer tools for vanity. Ripping out six logos to feel lean is theatre. The goal is coherence: your people and your future AI working from the same clean inputs, the same definitions, the same single answer to your customer’s one question. That is the version of martech stack consolidation worth doing, and it is exactly the kind of unglamorous groundwork I end up doing with clients before anything clever gets switched on. More on how I work is on the services page.

Five checks before you let AI near your stack

Enough principle. Here is the practical part. Before I let a client bolt AI onto their marketing, we run the same five checks. None of them are glamorous. All of them decide whether AI makes you sharper or just wrong faster.

1. One source of truth for the customer. Name the single system that holds the real view of a customer. If three tools each claim that job, you have none.
2. Numbers that agree. Pull the same metric, say last month’s sales, from two different tools. If they disagree, your reporting is fiction, and AI will only scale the fiction.
3. Tools someone actually uses. For every tool, name the person who logs in each week and the decision it drives. No name and no decision means it is a subscription, not a tool.
4. Clean handoffs. Track every point where data moves by hand: export, reformat, re-import. Each manual bridge is where the truth quietly breaks.
5. A real reason for every tool. If the honest answer to “why do we have this?” is “a vendor said it would fix the last one,” you just found the first thing to cut.

Work through those five honestly and you will know what to consolidate and what to switch off, long before you spend a cent on AI. If you want a second pair of eyes on yours, that is a conversation I am happy to have.

Your customer still only has one question. Build a stack that can answer it. If this struck a nerve, let us talk, or come find me on LinkedIn, where I think out loud about this most weeks.

Common questions

The post All these tools. No answers. And now AI. So what now? appeared first on Linelia.io.

For years, most marketing leaders lived comfortably in the middle. Performance when the CEO wanted numbers. Brand when the brief called for strategy. Generalist enough to never have to pick a side.

I was never quite that comfortable with the middle. If I am honest, I have always felt more at home on the performance side. Pipeline, attribution, CAC, conversion rates. That is where my instinct goes. I can do brand work, and I have done it well, but if you ask me where I light up, it is in the numbers.

AI is closing that middle ground fast. The hiding place, the one where you could claim to be equally strong on both sides and nobody would push back hard enough to find out, is gone.

In my work at Linelia, this question comes up in almost every mandate: what kind of marketing leadership do we actually need right now? Most companies still do not have a clean answer. That is the problem.

The split was always there. Everyone just pretended otherwise.

The divide between performance marketing and brand marketing is not new. It has existed for as long as there have been marketing departments. One side runs on data, speed, and measurable outcomes. The other runs on narrative, positioning, and the slow compounding of trust. Both matter. Both require real skill. And almost every marketing leader leans more naturally toward one than the other.

The best ones knew it. They hired deliberately to cover the other side. They said it out loud in the first conversation with their CEO or board. That honesty made them faster, sharper, and far easier to work with.

The dangerous ones claimed to be both. Equally strong on brand strategy and performance operations. Visionary and data-driven. Full-stack, as every job description still likes to say. In practice, nobody is truly full-stack at senior level. You have a dominant side. Most people just hope nobody notices. And for a while, nobody did.

You have a dominant side. Most people just hope nobody notices. AI is about to make that a lot harder.

AI is not creating the split. It is exposing it.

Here is what is actually happening. AI is automating the performance side of marketing at pace. Targeting, copy testing, budget allocation, campaign optimisation, audience segmentation. Work that used to justify a team of six can now be done leaner, faster, and in many cases better with the right tools and two sharp people. The performance marketing skill set is not disappearing. But the bar is rising fast. You need to be more analytical, more technically fluent, and more comfortable at the interface of data and automation than most current job descriptions require. If you are not, you will be outrun by someone who is.

At the same time, brand work is becoming more human, not less. AI-generated content is flooding every channel. Generic messaging is everywhere. The ability to build a genuine point of view, a recognizable voice, a brand people actually trust rather than simply recognize, is getting scarcer and more valuable by the month. The brand side of marketing is not being automated. It is being elevated precisely because everything around it is becoming noise.

The comfortable middle is not a strategy anymore. It is just a delay. The two sides are moving apart faster than most marketing leaders are moving with them. Pick one. Go deep. Stop pretending the other side is equally yours.

The comfortable middle is not a strategy anymore. It is just a delay.

The hiring conversation nobody is having honestly.

When companies hire a marketing lead today, most briefs still read the same way they did five years ago. Strategic and data-driven. Brand custodian and growth engine. Visionary and executional. The brief wants everything because nobody has sat down and asked the harder question: what do we actually need in the next 18 months?

That question changes everything. If the answer is brand awareness, market positioning, and long-term equity, you need one profile. If the answer is pipeline, customer acquisition, and measurable revenue impact, you need a different one. Both are legitimate. Both require serious expertise. But they are not the same person. Hiring as if they are wastes everyone’s time and usually ends with a painful conversation six months in.

I have sat in those rooms. More than once. And I waited too long to say it clearly: I am more performance than brand. That is where I am sharpest. I will bring in someone exceptional on the brand side and work closely with them. But that is how I operate. Saying it upfront is not a weakness. It is exactly the kind of clarity that makes a mandate work from day one instead of month four.

The question both sides should have on the table before any contract is signed: are we solving for the same 18 months? If you cannot answer that together in the first conversation, the misalignment is already there. You are just not looking at it yet.

The questions worth asking before signing anything:

• For the hiring company: Are we solving for pipeline or positioning in the next 18 months? What does success actually look like, and which profile delivers it?
• For the marketing leader: Do they understand which side I naturally lead from? Have I said it clearly, or am I letting them fill in the blanks with what they hope to hear?
• For both: Where is the blind side, who covers it, and is that person already in the room or still a gap in the plan?

Hiring as if one person can be both a brand custodian and a pipeline engine wastes everyone’s time. It usually ends with a painful conversation twelve months in.

How to position yourself honestly right now.

If you are a marketing leader reading this, the question is simple: which side are you actually on? Not in your LinkedIn headline. Not in the way you answer interview questions. When things get hard and you have to make a real call under pressure, where does your instinct go? Pipeline or positioning? Conversion or culture? Attribution or narrative?

Once you know, say it. Early. Not as a disclaimer, not defensively, but as a point of clarity that builds trust fast. This is where I am exceptional. This is the blind side I hire for deliberately. Here is how I have made that work in practice. That level of specificity is rare. In a market where everyone claims to be strategic, data-driven, and brand-literate all at once, being specific is a competitive advantage, not a limitation.

The marketing leaders who will build the strongest positions over the next three years are not the ones who claim to do everything. They are the ones who are ruthlessly honest about what they are built for, deliberate about covering their blind side, and done pretending the gap does not exist. AI is not the threat here. The self-deception that existed long before AI is the threat. AI just turned the lights on.

Know your side. Own it loudly. Build your team around the rest. That is not a limitation. That is how the best marketing organisations actually work. Always has been. Now it just matters more.

1. Name your dominant side explicitly. Not in a footnote. In the first real conversation. Performance or brand. Say which one.
2. Identify your blind side and hire for it deliberately. Not accidentally, not hopefully. Build it into the mandate from day one.
3. Stop writing or accepting briefs that ask for both equally. That brief is not ambitious. It is just unresolved. Push back on it before you sign anything.

If you are working through a question like this, whether you are a marketing leader figuring out your own positioning or a founder trying to hire the right profile, I am happy to think it through. Get in touch via linelia.io or connect with me directly on LinkedIn.

Common questions

The post Performance or Brand. AI is removing the hiding place. appeared first on Linelia.io.

You’ve heard of “garbage in, garbage out.” It applies to AI, to data pipelines, and to every consulting engagement I have ever seen go sideways.

Brief badly. Get bad work. It is that simple.

I know this from every angle. I have been the agency account manager trying to decode a three-line brief from a brand that expected magic.

I have been the brand-side marketing director handing over exactly that kind of brief, convinced it was fine.

I have been the consultant brought in to salvage a project where nobody could quite remember what the original brief said.

And I have spent years trying to bridge the gap between supplier and client, watching both sides frustrate each other in completely avoidable ways.

The problem is almost never the talent. It is almost always the brief.

Specifically: whether the client wrote it for a supplier, or for a partner. This post is about the second kind.

What a brief is actually for

Most people think a brief is a document that describes what they want. It is not. A brief is an act of thinking out loud. The process of writing it forces you to:

• clarify what you actually need,
• what you already know,
• and where your own uncertainty sits.

A brief that does that well is worth more than any subsequent meeting.

The external partner reads a brief and forms a picture. Not just of the project, but of the organization. Of the leadership team. Of how decisions get made. Of what has already been tried and quietly abandoned. A thin brief produces a thin picture. And a partner working from a thin picture will spend the first four weeks building the context they should have walked in with.

That is four weeks of your budget used for orientation instead of output.

A brief is not a document that describes what you want.

It is an act of thinking out loud.

The clearer the thinking, the faster the work.

The gap between the stated problem and the real one

The most consistent pattern I see: the stated problem and the real problem are not the same thing.

A company says: we need a new marketing strategy. What they mean is: the last three initiatives failed and we don’t understand why, we are under pressure from the board, the team is exhausted, and we need someone to help us see clearly again.

A company says: we need support with our digital transformation. What they mean is: we bought a platform eighteen months ago, adoption is at eleven percent, the internal champion has left, and we need someone to salvage this without making leadership look bad.

Neither version is dishonest. Both versions are incomplete. And a consultant working from the incomplete version will optimise for the wrong thing.

I have been on the receiving end of both. As an agency, you learn to read between the lines, often incorrectly. As a brand, you sometimes don’t even know what the real problem is until someone from outside names it.

The best briefs I have ever received were the ones where the client had done that naming themselves before I arrived. Those engagements moved at a completely different pace.

What to include that most people leave out

There are four things that almost never appear in a brief but consistently determine whether an engagement succeeds.

The internal politics. Who is behind this project, and who is not. Where the resistance sits, and why. Which stakeholder needs to be brought along carefully, and which one has already made up their mind. This is not gossip. It is navigation data. Without it, the external partner walks into rooms without a map.

The real deadline. Not the official one. The one behind the official one. The board presentation. The budget cycle. The moment when someone senior runs out of patience. External partners can work to a deadline they understand. They cannot protect a deadline they don’t know exists.

What has already been tried. Every organisation that hires external support has usually attempted something internally first. Knowing what was tried, and why it didn’t stick, is some of the most valuable context a consultant can have. It saves weeks of re-covering ground. It also prevents the embarrassment of proposing exactly what was already rejected six months ago.

Who actually has to say yes. Not who commissioned the project. Who has the authority to block it, delay it, or quietly de-prioritise it once the external partner is on board. In my work at Linelia, the most productive first conversation I can have with a new client is the one where they draw the actual decision map, not the org chart, but the map of who influences what.

The real deadline, the internal politics, what has already been tried, who actually has to say yes.

Leave any of these out and the engagement starts with a disadvantage it may never recover from.

On working at eye level

Here is what I learned from sitting on both sides: the dynamic in a briefing room reveals everything about how the engagement will go.

When I was agency-side, I could feel within twenty minutes whether a client saw us as a thinking partner or a production house. The brief was the first signal. A brief written with care, with context, with honest acknowledgment of what the client didn’t know, that brief said: we respect your expertise. Let’s figure this out together.

A brief that was vague, rushed, or basically a rephrased internal memo said something different. It said: deliver the thing and don’t ask too many questions.

Eye level does not mean equal authority. The client makes the decisions. That is how it should be.

Eye level means equal respect.

It means the external partner is hired to think, not just to execute. It means their honest assessment is more valuable than their agreement.

The best consulting relationships I have been part of shared one thing: the client treated the engagement as a collaboration, not a transaction. They shared the uncomfortable context. They pushed back when something didn’t feel right. They expected honest challenge in return, and they created space for it.

That starts with the brief. Before a single meeting. Before a proposal. The brief is the first signal of what kind of client you are going to be.

If your consultant always agrees with you, you have hired the wrong person.

A good brief creates the conditions for honest challenge from day one.

A practical starting point

If you are putting together a brief for an external partner right now, here is a simple structure that covers what actually matters. Not a template. Templates produce template answers. These are questions worth sitting with honestly before you write a word.

What is the real problem? Not the presenting issue. The one underneath it. If you had to explain this to someone with no stake in the outcome, what would you say?

What does success actually look like? In concrete terms, six months from now. Not the aspiration. The observable change.

What have you already tried? And what stopped it? Even a partial answer here is enormously useful.

Who needs to be on board? Name them. Include the ones who are currently not.

What is the deadline behind the deadline? What external or internal pressure makes this urgent right now?

What is the one thing you are not sure you want to hear? Write it down. Then make sure the brief creates space for the external partner to say it anyway.

And one final test, from someone who has been on both sides of this table:

Before you send the brief, ask yourself if you would be happy receiving it.

That question alone filters out about half the problems before they start.

You can find more on how Linelia approaches project setup and consulting partnerships on the services page. If you are currently putting together a brief for an upcoming project and want a second perspective before you send it, the fastest way is a short conversation.

Reach out via linelia.io/contact or connect with me directly on LinkedIn.

Common questions

The post Stop briefing suppliers. Start briefing partners. appeared first on Linelia.io.

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

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.

The post The reason your team isn’t using AI has nothing to do with AI appeared first on Linelia.io.

I’m writing this from the sideline of a field hockey pitch.

Laptop open. Travel espresso cooling next to me. One eye on the screen, one on the pitch. Technically working. Completely where I need to be.

This is the setup I built when I started Linelia. Not a fixed office with fixed hours. A structure that moves with me, as far as client meetings and mandates allow it. That sounds like a lifestyle statement. It isn’t. It is an operational decision with real constraints and real discipline behind it.

My daughters both play field hockey. The elder one trains and plays several times a week, the younger a bit less. I try to be there as much as I can. Sometimes I am on a call at the edge of the pitch. Sometimes I am finishing a draft while they run their warmup drills. But I am there, I check in regularly, and they know where to find me. I would not trade this for anything.

Does this mean working fewer hours? Honestly, no. Running my own company probably means more hours than many of my corporate years. The difference is in how those hours are distributed, and who decides where they go. An evening at the desk after both girls are in bed feels entirely different from the same evening dictated by a calendar someone else built. One is a choice. The other was a condition.

The founder work-life integration setup that actually works

Founder work-life integration sounds great on paper. In practice, without a few firm rules, it becomes neither good work nor good presence. Here is what makes it functional rather than just aspirational.

“The flexibility to work from anywhere is only worth something if you also know when not to.”

1. Know the difference between sideline presence and full presence

Training sessions, games, school pickups, meals, bedtime. All of those are in the calendar and protected. But the level of presence varies by moment, and being honest about that is the whole point.

During training, the approach is more fluid. A call at the edge of the pitch, a voice memo during a drill break, a quick reply between exercises. I am on the sideline. I am checking in. That counts. Games are different — more present, less screen. And when both of them are playing on the same day, that is a different category altogether. Laptop stays in the bag. No exceptions.

2. Voice memos and offline drafts

An idea doesn’t wait for a desk. During warmup of my eldest daughter today, something clicked about a client challenge I’ve been turning over for days. Thirty seconds into the voice memo app, the thought was captured. Then I put the phone away and watched the warm-up drills.

No half-present scrolling. No “let me just quickly check.” The thought is safe. I can be here now. This post started as three bullet points in a Notes app, written while she was doing stretches on the far side of the pitch. The full draft came later. The thinking happened at the pitch.

“The thought is safe. I can be here now!”

3. Hockey sessions in the calendar with the same weight as a client call

Hockey sessions do not move. They are in my calendar with the same weight as a board presentation. Non-negotiable. Non-moveable.

What gets scheduled gets protected. Everything else finds its place around it. This is not a new productivity principle. It is just one that most founders fail to apply to their personal commitments with the same rigour they apply to professional ones. Your daughter’s training session is a commitment. Treat it like one.

4. AI tools that make compact work actually possible

One thing that has quietly made the whole setup more workable: AI tools. Research, first drafts, briefing summaries, client prep, follow-up emails. Work that once required two uninterrupted hours at a desk can now happen in focused twenty-minute slots between warmup and kickoff. I am not using AI to work less. I use it to work in smaller, sharper intervals, which is exactly what a setup like this demands. A voice memo captured on the pitch becomes a finished document by the time I am back at the desk.

The line that doesn’t move

All of this works because I know where the hard line is.

The line is clearest when both of them are playing. Those days, the laptop stays in the bag. Not because I scheduled it that way. Because some things are not a blend, and a day with both girls on the pitch at the same time is one of them.

But even on a regular training session, there is a version of the same line. When one of them looks up from the pitch to find me, I am looking back. Not at a screen. That is the only thing that actually matters about being there.

Founder work-life integration doesn’t mean always blending. It means knowing which moments belong entirely to one thing. The freedom to work from anywhere only means something if you also have the discipline to be somewhere fully when it matters.

In my work at Linelia, I spend a lot of time with leaders who are building something sustainable. Organizations and ways of working that don’t depend on one person being permanently available. The same principle applies to how you run your own day. Build the structure once. Then trust it.

“Build the structure once. Then trust it.”

One more honest note. Every rule has its exceptions. Real urgency happens, and a client in a crisis on a hockey day doesn’t wait for the final whistle. But these moments are rarer than you’d expect. And when they do happen, I’m genuinely lucky that my wife has the same kind of flexible setup. She can step in, be fully present at the pitch, and I can deal with what needs dealing with. That shared flexibility is not a footnote to the system. It is what makes the whole thing hold.

If you’re thinking about how to build a working setup that fits both your clients and your life, I’d be glad to compare notes. Reach out via the Linelia contact page or connect with me directly on LinkedIn.

Common questions

The post Founder Dad Mode: Why I Work From the Field Hockey Pitch appeared first on Linelia.io.

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

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.

The post Why most digital transformations fail before they start appeared first on Linelia.io.

This week is my last at RheinEnergie.

Not dramatic. Not surprising. It was agreed from day one. And yet here I am, sitting in a meeting room in Cologne, looking at an agenda I built myself, thinking: what actually remains?

Not for the company. That’s documented, handed over, carried forward.

For me. And honestly, it’s a good feeling.

Interim management isn’t a sprint. It just feels like one.

When I started the mandate, the brief was clear: accelerate digital transformation, build structures, enable a team, gain marketing and sales growth. All with an end date attached.

What I underestimated: how deeply a fixed-term mandate changes the way you work.

There’s no time for long warm-up phases. You can’t defer things to “later.” Every meeting counts, every decision carries weight. That sharpens your focus on what truly matters, faster than any permanent role ever could.

And yet that’s also the beauty of it: you build something you won’t finish yourself. You create the foundation, and then you trust the team to take it further. That trust – and seeing them do exactly that – is one of the most rewarding parts of this work.

Building structures is one thing.
Building a team and a system that others can take forward and scale…that’s always been my definition of success.

What energy companies actually need — versus what they think they need

RheinEnergie is not a startup. It’s a company with history, with grown structures, with people who have been doing their jobs well for years, while operating in an industry that’s changing faster than ever before.

What I encounter again and again in organisations like this: the desire for transformation is genuine. The willingness to truly disrupt existing processes to get there, often isn’t.

That’s not a weakness, it’s human. People who have spent years building a system will defend it. People who carry responsibility protect themselves against failure. And people who are accountable for daily delivery simply don’t have the bandwidth to simultaneously reinvent everything.

That’s precisely where outside perspective creates value. Not because external consultants are smarter.

But because we have nothing internal to protect and everything to prove through results.

The uncomfortable conversation and why it matters

When I look back at the moments where I genuinely moved something, they were rarely the big presentations.

They were the uncomfortable conversations.

The one where I told the leadership team that a particular process wouldn’t scale — even though it had just been proudly showcased.
The moment I openly challenged a priority that seemed settled.
The room where I said, as an outsider, what nobody inside was willing to say.

None of that feels comfortable in the moment. But when the team is open to that kind of honesty – and this team definitely was – it becomes genuinely energizing. That openness is what makes transformation actually happen.

You’re not brought in for validation.
You’re brought in for clarity.

And when the team embraces that, remarkable things happen.

What remains

A mandate ends. But what was built stays.

Structures that keep working without you.
Decisions that got made because someone created the space for them.
A team that is now ready to take full ownership and continue scaling. I’m genuinely excited to see where they take it.

That’s the goal of good interim management:
not to create dependency, but to leave capability behind.

What I can say: I’m leaving this mandate with more than I brought. A deeper understanding of an industry in transition.

Real respect for the people inside large organizations who push for change every day. And the confidence that comes from building something that continues on its own.

The question that stays with me

How do you hand over something that isn’t finished?

Transformation isn’t a project with a sign-off sheet. It’s an ongoing process. And yet there’s always this moment where someone from the outside passes the baton and says: from here, this is yours.

I don’t have a clean answer to that. But I believe it’s not about finishing everything. It’s about taking the right things far enough that they continue on their own.

That’s the most honest goal an interim manager can have. And in this case, I’m proud of what we built together.

If you’re curious how I support organisations through digital transformation and interim leadership, you can find more about my work here: Linelia’s services.

And as always, I’m 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 connect with me directly on LinkedIn.

The post What remains when the mandate ends appeared first on Linelia.io.

Lately, I’ve had a few moments in projects where I caught myself thinking:

This would have taken a full team a few years ago.

Now it’s a conversation, a few iterations… and we’re already moving. Not because we’re cutting corners.

But because AI is removing a lot of the “busy work” that used to justify large teams.

This shift is already changing AI consulting vs traditional consulting in a very practical way.

And that changes something fundamental:

What companies actually need from consultants.

5 things that are shifting right now

1. More people doesn’t mean more progress anymore

For a long time, adding people was the default answer.

• More analysts.
• More slides.
• More capacity.

Today, a lot of that work is simply… gone.
Or at least massively compressed.

Which leads to a slightly uncomfortable truth:
More people often just means more coordination.

And coordination rarely moves things forward.

2. “Having seen many companies” is not the same as having run one

This is probably the biggest gap I see.

You can work on dozens of projects…
and still never experience what it actually means to carry responsibility inside an organization.

Because inside, things look different.

Decisions are not clean.
Trade-offs are real.
Politics are part of the game.
And once something goes wrong, you don’t move on to the next project.

You stay with it.

That changes how you think.

And it shows very quickly in the kind of recommendations you make.

3. Speed no longer comes from capacity. It comes from clarity.

The old way of consulting:
→ more (junior) people = faster progress

The reality:
→ more people = more alignment loops
→ AI removes a lot of the heavy lifting.

What’s left now is:
• understanding the problem
• making decisions
• moving forward

And that doesn’t scale well with team size.

4. A lot of “consulting work” was never really about solving the problem

If we’re honest, a big part of traditional project work goes into things like:

• internal alignment
• status updates
• formatting slides
• preparing the next steering

Necessary? Often yes.
Directly solving the problem? Not really.

In lean setups, most of this disappears.

And suddenly, you see very clearly what actually matters.

5. Impact becomes visible much faster

In the end, the question is simple:

Is anything actually changing?

Not:
• how impressive the deck looks
• how structured the framework is

But:
• are decisions made
• are things moving
• does the organization feel it

With fewer layers and faster cycles, that becomes visible very quickly.

And it’s much harder to hide behind process.

This is where the difference between AI consulting vs traditional consulting becomes very visible in real projects.

Where AI really comes into play

AI is not replacing consulting.

But it is removing a lot of what used to justify large structures and massive costs.

AI can:
• structure messy topics in minutes
• create first versions instantly
• explore scenarios without long preparation

Which means:

Less production, more judgment.

And that’s exactly where experience matters.

Tools that make this possible in practice

All of this sounds abstract until you actually use it in your day-to-day work.

A few tools I rely on quite heavily right now:

n8n
For automating workflows that used to take manual effort.
Connecting tools, triggering processes, moving data around without thinking about it twice.

Onepage
For getting from idea to something tangible very quickly.
Landing pages, MVPs, simple setups that help you test and move instead of overthinking.

LeChat, Claude and ChatGPT (incl. custom GPTs)
For structuring thoughts, drafting first versions, exploring options, and pressure-testing ideas.
Custom GPTs especially help me to reuse patterns, frameworks and ways of thinking across projects.

Notion
As a central place to structure ideas, notes, and ongoing work.
Less about documentation, more about keeping things connected and accessible.

PopAi (or beautiful.ai, if you prefer)
For turning rough ideas into clean, structured presentations quickly.
Not to create “perfect slides”, but to get to a point where you can discuss something real.

None of these tools are magic.
But combined with experience, they remove a lot of friction.

And that’s exactly what changes how fast you can move.

P.S.: If you’re interested in learning more about my tech setup, you might want to check out this post as well: The first 150 days

Why this matters to me

Because this is exactly why I enjoy my current setup so much.

A lean structure.
Real experience from inside organizations.
And tools that remove a lot of overhead.

It creates a way of working that feels much closer to reality.

And, to be honest, much harder to fake.

If you’re looking for a more direct, hands-on way to move topics forward, you can find more about how I work here: Linelia’s services.

And if you’d like to exchange thoughts or explore a potential collaboration, feel free to reach out via my contact page or connect with me on LinkedIn.

The post Why Small, Senior Teams Are Winning in the Age of AI appeared first on Linelia.io.

In my last post, I wrote about a question that often changes the direction of a discussion:

“What now?”

Once people move from explaining what’s wrong to thinking about the next step, the whole energy in a room usually shifts.

But there’s another small question that often matters even more for ownership in meetings:

“Who owns this?”

And interestingly, that question decides whether ideas actually turn into action.

The moment after the good discussion

IIf you’ve spent enough time in meetings, workshops or steering committees, you probably know the situation.

The conversation was productive.
Everyone agrees on the direction.
The next step seems clear.

Someone says something like:
“We should probably move this forward.”
“We should look into this.”
“We should align on that.”

Everyone nods.

And then the meeting ends.

Because while “we” sounds collaborative, it’s also wonderfully vague.

A small reminder from a recent project

I was reminded of this again recently in a project I’m currently involved in. We had just wrapped up a discussion about the next steps. The topic was clear, the direction made sense, and we were already moving toward the next agenda item.

Then one of the managers in the room asked a very simple question:

“Okay, but who owns this?”

No big speech.
No finger pointing.
Just a calm question.

Within seconds, the topic had a name attached to it and suddenly everything felt clearer.

It’s one of those small moments that stick with you.

And honestly, it’s also one of the reasons I enjoy working as a consultant so much.

People sometimes think consulting is about bringing all the answers into a room.

In reality it’s much more of a two-way game.

Of course I bring experience, perspectives and ideas to the table.

But I constantly learn from other leaders and experts as well.

Often through small moments like this that remind you how powerful simple leadership habits can be.

Why ownership changes the dynamic

Once ownership in meetings becomes clear, something interesting usually happens:

• Follow-ups become easier.
• Priorities become clearer.
• Decisions move faster.

Not because the owner suddenly does everything alone.

But because everyone knows where the topic lives.And that alone creates momentum.

The slightly uncomfortable part

But taking ownership is not always comfortable.

It creates visibility.
And visibility usually comes with expectations.

So it’s understandable why many topics stay in the safe territory of “we”.

But in my experience the opposite is often true.

Once ownership is clear, pressure actually decreases.
Because the uncertainty disappears.

One small habit I’ve started to appreciate

So, a simple question before leaving a meeting can make a big difference:

“Who takes this?”

Not as a control mechanism.

More as a service to the group.

Because once a topic has a name attached to it, the chances that it actually moves forward increase dramatically.

Closing the loop

In my last post I wrote about moving from

“No” → “What now?”

Maybe the next step is simply:

“What now?” → “Who owns it?”

Because momentum doesn’t just need ideas.
Sometimes it just needs a name.

If you’re curious how I support organizations in turning challenges into concrete next steps and building positive momentum along the way, you can find more about my work here: Linelia’s services

And as always, I’m 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 connect with me directly on LinkedIn.

The post From “What Now?” to “Who Owns This?” appeared first on Linelia.io.

I’ve been thinking about something lately, mostly because I keep running into it again and again in my day-to-day work.

We’re actually very good at saying no…

Especially here in Germany, and honestly across Europe as well.

Put a few smart people in a room and it usually doesn’t take long until someone points out why something won’t work. Too risky. Too dependent. Too complex. Too early. Too late. You name it.

And to be fair: most of the time, those concerns are absolutely valid.

But what often happens next is the part I find more interesting.

The conversation slows down.
Everyone agrees that “this is difficult”.
And then… nothing really follows.

At that point, I often catch myself thinking:

Okay, agreed. But what now?

Seeing what’s wrong is only the first step

I don’t see problem awareness as a weakness. Quite the opposite.
It’s a strength. It keeps standards high and prevents naïve decisions.

But I’ve learned that identifying what doesn’t work is really only half the job.

The more useful part usually starts with the next question:

If we don’t want to do this, what’s the alternative?

Not the perfect one.
Not the final answer.
Just a better option than standing still.

I hear variations of this in many contexts:

• If we want to reduce dependencies, where do we start pragmatically?
• If certain platforms don’t align with our values, what do we actively build instead?
• If something feels wrong long-term, what’s the next reasonable step today?

Those conversations tend to feel very different. More constructive. More forward-looking.

And usually a bit more energizing as well.

That’s pretty much my daily reality

In my work, I’m constantly surrounded by challenges.

• Ambiguous situations.
• Conflicting priorities.
• Limited time.
• High expectations.

Honestly, there would be plenty of reasons to complain every single day. And sometimes, yes, that happens as well.

But what I’ve seen over time is that progress rarely comes from listing everything that’s broken.

It usually comes from asking a simpler question:

What’s the next step that actually helps?

Not the big transformation.
Not the perfect target picture.
Just something that moves things forward.

Mini-Hack: A small habit that helps me here, when someone says “this won’t work”, I try to follow up with one simple question: “Okay, so what would you do instead?”

Not in an aggressive way. More out of curiosity.
It often shifts the conversation faster than any framework.

Why I care so much about momentum

I’ve become a big believer in momentum.

Not because it solves everything, but because it changes how people feel about a situation.

Once teams see that something is moving, discussions shift.

Energy comes back.
Ideas get bolder.
And suddenly, bigger change doesn’t feel quite as scary anymore.

That’s also why I’m a fan of quick solutions – and by “quick” I don’t mean careless.

I mean fast enough to show progress.
Concrete enough to reduce uncertainty.
Small enough to actually happen.

Those small steps often do more than perfectly crafted plans that never leave the slide deck.

Positivity is not naïve, it’s practical

Being solution-oriented doesn’t mean ignoring reality. It’s closely tied to how openly and honestly we communicate progress and challenges. Something I’ve written about before when reflecting on visibility without cringe.

For me, it’s more about deciding where to put attention.

I was lucky to learn early in my career how important it is to make progress visible.
Especially at L’Oréal, this was done extremely well.
Not as empty celebration, but as honest acknowledgment of what moved forward.

It sounds simple, but it changes a lot.

Teams feel seen.
Work feels meaningful.
And motivation doesn’t have to be forced.

The interesting part is that this doesn’t stop at team level.

I notice the same pattern on a broader scale as well. In organizations, in industries, and often in how we talk about change more generally.

Zooming out: a European angle I strongly believe in

When I zoom out, this mindset feels just as relevant beyond individual teams.

I see myself very much as European. Germany is a big part of that, of course, but I’m convinced that our real strength lies in what we can build together across Europe.

There are so many strong ideas, talented people, and solid capabilities here. We just don’t always talk about them that way.

And when you look at initiatives like the European Innovation Council, it becomes pretty clear how much potential already exists if we choose to build on it.

Especially in times like these, I think it helps to focus a bit more on what’s possible.

Less “why this won’t work”.

More “how could we make this work, together?”

That shift alone can already change the tone of many conversations.

And yes, sometimes you need to let off steam

Just to be clear: I don’t believe in forced positivity.

I also need valves.
Good talks.
Honest feedback.
Sometimes even a bit of ranting to get things out of the system.

I’ve written openly about struggles before, and I know that can sometimes sound negative. For me, it’s the opposite. Once things are said out loud, you can actually start working with them.

Transparency creates the foundation for change.
Momentum builds on top of that.

The mindset I try to bring into organizations

For me, it usually comes down to this:

See the issue.
Acknowledge it honestly.
Then ask: What now?

Not because everything is easy.
But because staying stuck rarely helps.

Momentum does.

If you’re curious how I support organizations in turning challenges into concrete next steps and positive momentum, you can find more about my work here: Linelia’s services

And as always, I’m 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.

The post From “No” to “What Now?” appeared first on Linelia.io.