Transcript
Welcome to Iconoclast Insights, the podcast where we are not afraid to slaughter the sacred cow. I'm André Daus.
Today's sacred cow? The belief that digital transformation starts with buying digital tools. We're going to dissect why this assumption kills more transformation efforts than it saves – and what actually works instead.
It is said, Einstein was once asked how he would spend his time if he had a problem that his life depended on solving, and only one hour to solve it. He said he'd spend 30 minutes analyzing the problem, 20 minutes planning the solution, and just ten minutes implementing it.
Today, I want to challenge something we see everywhere: organizations doing exactly the opposite. They choose their tools first, then spend all their thinking and planning on how to implement those tools. They never step back to understand the actual problem or whether their chosen solution can even solve it.
I'm going to tell you about a school's iPad rollout that went wrong in predictable ways. Then I'll show you how billion-dollar corporations make exactly the same mistakes. Because if we're honest about what really happens in digital transformation, we might actually start getting it right.
The School iPad Story
Eighteen months ago, I watched a school announce its big digitalization leap: "We're introducing iPads."
Why iPads? Because they support stylus input, run educational apps, and can be controlled remotely. All true. All irrelevant.
Here's what was missing: any concept of what problem these devices were supposed to solve.
The parent community split into three groups. The enthusiasts who immediately cheered, "Finally, modern education!" The resisters who wanted to maintain the status quo. And a small group of us who were interested but had questions.
My biggest question was simple: "Where's the concept?"
The answer was revealing: "We'll create one later." Spoiler alert: eighteen months later, there still isn't one.
I proposed something radical: let's think first. Create a concept, then run a six-month pilot in one classroom. Let teachers and students experiment together and learn what actually works.
The response? "That would take too much time."
Too much time to think. Too much time to plan. But apparently, unlimited time to fix problems that could have been avoided.
So they rolled out the full program. Most parents bought not the minimum configuration, but expensive, high-spec models. After all, these devices should work after graduation too, right?
Two months later, reality hit:
The devices belonged to students but were controlled by the school. Parents discovered they had less influence over their own purchases than promised.
Privacy issues emerged when administrators could access more data than anyone had disclosed.
The workload for teachers and students was significantly higher than expected.
The promised benefits – flexible learning, better home integration, modern teaching methods – proved difficult to deliver without a framework.
Many parents felt deceived because technical promises couldn't be kept.
The initial euphoria turned to disappointment.
The Pattern We Never Learn
Here's what I see happening everywhere: we treat tools as solutions.
But here's the uncomfortable truth: a tool is never a solution. It's what the name says – a tool. A means to an end.
The real work happens with people first. And not just the loud voices who dominate meetings. The quiet ones often have the best insights, but their ideas rarely make it to implementation. When we include them in designing new processes, something magical happens: they don't resist change because they helped create it.
Then comes process design. People live processes. They can describe what works and what doesn't better than any consultant.
Only then – at the very end – do you choose tools. They should support processes, not define them.
This is why thinking comes first. I say "thinking," not "analysis." Analysis sounds technical, and when things sound technical, we inevitably end up buying tools. But we don't need more tools. We need more clarity.
When Giants Fall Into the Same Trap
Let me show you how this pattern destroys value at the highest levels.
General Electric launched "GE Digital" – an ambitious program to embed Internet of Things technology across their products and processes. Instead of starting with clear pilot projects, they tried to digitalize multiple business units simultaneously.
They underestimated how different their various divisions were – different legacy systems, different processes, different cultures. The pressure for quarterly results meant long-term development got squeezed.
The result? After massive investment, GE Digital was broken up and parts were sold off. The initial transformation enthusiasm led to disappointment when reality proved more complex than the concept.
Then there's Haribo. In 2018, the candy maker wanted to modernize its supply chain management with a new ERP system. The goal was to centralize data, improve international process control, and increase efficiency.
But they didn't adequately analyze how different their regional operations were. Employees weren't properly trained, and the system wasn't sufficiently tested.
Shortly after implementation, they faced major supply chain disruptions. Inventory tracking failed, delivery delays occurred, and revenue dropped.
Both companies made the same mistake as that school: they started with the solution and worked backward.
Why This Keeps Happening
The reason is seductive simplicity. Buying iPads feels like progress. Implementing ERP systems looks like transformation. Tools are tangible, visible, measurable.
Thinking is messy. Involving stakeholders is slow. Testing requires patience. Planning doesn't photograph well for annual reports.
But here's what we've learned to ignore: every digital transformation failure follows the same script. Big announcement, enthusiastic rollout, reality check, damage control, quiet scaling back.
Meanwhile, the organizations that get it right do something different. They start boring. They think deeply about problems before shopping for solutions. They involve skeptics alongside enthusiasts. They test small before scaling big.
The Real Cost of Getting It Wrong
Let's be honest about what this pattern costs us.
There's the obvious financial waste – money spent on tools that don't solve the intended problems. But that's just the beginning.
There's the human cost. When implementations fail, people lose trust in change initiatives. They become cynical about "the next big thing" because they've seen too many big things fail.
There's the opportunity cost. While you're fixing problems that shouldn't exist, your competitors are actually solving real problems.
And there's the strategic cost. Every failed transformation makes the next one harder. Every broken promise makes stakeholders more resistant. Every shortcut makes the long-term journey longer.
What Works Instead
The alternative isn't complicated, but it requires discipline.
Start with people, especially the quiet ones. They often see problems that leaders miss and have solutions that never get heard.
Spend time understanding the actual problem, not the problem you think you're solving. Most digital transformation failures happen because organizations digitize the wrong things efficiently.
Create small experiments before big investments. A six-month pilot costs less than a failed rollout.
Design processes with the people who will live them. They'll tell you what really happens versus what officially happens.
Choose tools last, based on what you learned from people and processes.
Be ruthlessly honest about expectations. Under-promise and over-deliver beats euphoria followed by disappointment.
The Iconoclast Insight
Here's the uncomfortable truth that nobody wants to admit: most digital transformation isn't about transformation at all. It's about buying things that make us feel like we're transforming.
Real transformation is invisible at first. It happens in conversations, in understanding, in small experiments that teach us what we didn't know we didn't know.
The organizations that master this approach don't just avoid expensive failures. They discover opportunities that tool-first thinking never reveals.
But it requires something our culture struggles with: patience with the thinking phase. Comfort with questions before answers. Willingness to appear less decisive in order to be more effective.
Closing
I didn't record this episode to say "I told you so" about that school's iPad rollout. I recorded it because I believe we can do better.
When we stop confusing tools with solutions, when we start listening to quiet voices alongside loud ones, when we think before we buy – that's when digital transformation starts delivering on its promises.
The next time someone pitches you a digital solution, ask them this: "What's the problem we're solving, and how do we know these tools will solve it?"
If they can't answer clearly, you're about to repeat the same expensive mistakes that schools, candy makers, and industrial giants make every day.
But if they can answer clearly, you might be about to do something genuinely transformative.
Until next time, keep questioning everything – especially whether the solution you're being sold is actually solving the problem you think you have.
This has been Iconoclast Insights. Thanks for listening.
