Interview with Julia Wertl on why software alone doesn’t guarantee efficiency and how the right strategy works.
Efficiency projects fail not because of technology, but due to unclear requirements and poor process clarity. Julia Wertl presents her four-phase BA-R-T methodology: analyze needs before selection. Often, the problem isn’t the software itself – it’s that processes were never adapted to the tool’s evolution or data was never maintained.
Key insight: team resistance is valuable experience. When you involve employees from the start, you embed solutions sustainably.
Dr. Renate Mayer explores a parallel concept in the Zebra-Stripes column: “Decluttering Safety” – sometimes eliminating unnecessary rules matters more than building new ones. Clarity and purpose, whether in processes or rulebooks, are the key to lasting efficiency gains.