Key Takeaways
- Meaningful digitalization starts with the problem, not the tool.
- The order decides: clarify processes first, then digitize – otherwise chaos just gets faster.
- Technology must serve people: what the team does not adopt yields no return.
- My compass from over 35 years of IT and business practice: benefit before features, routine before revolution.
“Meaningful digitalization” is more than a keynote title – it is an attitude. Over more than three decades I have experienced IT projects as a salesperson, managing director and consultant, and found one constant: failed digitalization almost never fails because of the software.
How Do You Recognize Pointless Digitalization?
- A tool is introduced because the competitor has it – not because a problem hurts.
- The paper process is digitized one-to-one instead of rethought: forms become PDFs.
- Users hear about the solution for the first time at rollout.
- Success is measured in installed licenses instead of saved time.
How Is It Done Right?
With three questions, in exactly this order: Which problem costs us the most time or nerves today? What would the process look like if we were allowed to reinvent it? And only then: which tool supports this process most simply? Those who proceed this way digitize less – and achieve more. That is the core of my keynote “Meaningful Digitalization”, which I have delivered on big stages including Greator.
Why Is the Human Being the Yardstick?
Every digital solution competes with a well-rehearsed habit – and habits win if the new is even a touch more complicated. Therefore: better a simple solution everyone uses than a perfect one everyone bypasses. That is exactly what my motto “making technology simply work” stands for.
Which Four Questions Show Whether a Project Is Worth It?
Before you invest money and energy, answer these four questions – in writing, in full sentences. Anyone who cannot answer them does not have a digitalization project but an idea:
- Who exactly benefits – the customer, the employees, or only the statistics?
- How often does the case occur? One transaction per month does not justify automation.
- What gets removed in return? Digitalization without a deletion list only creates extra work.
- Who decides whether it worked – and what will that person look at?
In my keynotes the third question is regularly the uncomfortable one. It is exactly the question that separates meaningful digitalization from digital busywork: a new tool is progress only when an old procedure really disappears.
How Do You Prioritise Among Ten Good Ideas?
The typical situation in mid-sized companies is not a lack of ideas but a surplus. My approach is deliberately simple: every idea gets two numbers from one to five – effort and impact. Everything with low effort and high impact is done immediately, everything with high effort and low impact is deleted, not postponed.
For the rest one rule saves a lot of arguing: one running project per unit. Not three half-finished ones, but one that gets completed. Visible wins buy the patience for the bigger undertakings – organisationally and emotionally.
How Do You Recognise Progress After Six Months?
Progress becomes measurable once you agree on a few honest figures. These four work in almost any company:
- Hours saved per week in the process you actually touched.
- Number of systems in which the same information is maintained – it should go down.
- Follow-up questions per transaction: fewer questions mean clearer procedures.
- One question to your workforce: does the work feel lighter than six months ago?
Planning an event? As a keynote speaker for artificial intelligence, digitalization and Microsoft 365, I bring technology topics to the stage in a way that sticks – hands-on, entertaining and immediately actionable. Book a digital transformation keynote: content, formats and fee at a glance.
Frequently Asked Questions (FAQ)
For which occasions is this topic suitable?
From the annual kick-off to association conventions to leadership retreats – wherever orientation in the digitalization jungle is needed.
Is the keynote industry-specific?
The compass is universal, the examples are not: they are tailored to the audience's industry – from trades to banking to manufacturing.
What do participants take away concretely?
A three-step for every digitalization decision, an honest checklist for running projects – and typically two or three immediate actions that can be implemented within the same week.
Should we start with artificial intelligence or with processes?
With the processes – but not for months. Understand the workflow well enough to explain it, then put technology next to it. An unclear process only becomes unclear faster with AI.
How do we keep the topic alive after the keynote?
With a fixed date: 30 days after the event, three teams report for ten minutes each on what they tried. That small format works more reliably than any glossy roadmap.
