You invested in project management software. Your projects still run too long and too expensive. The problem doesn’t sit in the system.
I have seen this picture repeatedly across assessments — from manufacturing to IT. The starting point is always the same: a capable software has been rolled out, at considerable expense. And the results still fall short.
The Quiet Fallacy in Leadership
Buying a tool gets unconsciously equated with building project management capability. The two have little to do with each other.
A tool manages data. It replaces neither trained project managers, nor binding processes, nor clarified roles and accountabilities. Without these three elements, the software remains an expensive data-entry mask — with the added risk of inconsistent use creating new sources of error.
However, a powerful Project Management tool is not yet project management, which would be necessary for replicable project success:
- There is a lack of trained project managers who (can) use the tools sensibly.
- There is a lack of processes / specifications that sensibly control and standardize tool use.
- There is a lack of processes / specifications that define clear roles and responsibilities.
What I Find in Practice
In a recent assessment, the pattern was textbook: templates existed, processes were in preparation — but project managers had barely been trained on them. Many were technically excellent, yet without formal project management training, running projects alongside their day job.
The result: project management gets done “on the side,” with minimal effort. Too much data, too little substance, little intrinsic motivation for disciplined use. Leadership was initially unhappy with this finding — but not, at bottom, surprised.
The Real Constraint
The constraint is not technology — it is leadership accountability for projects. Project management is not a methodological discipline you delegate to a system. It is a leadership task, internal and external — with governance, clear mandates and developed capability.
Where that leadership task is missing, every further tool investment will manage the symptoms, not the cause. That is the uncomfortable but consistently confirmed lesson from more than 30 years in project and programme accountability.
What Actually Works
The actual investment begins after the software purchase. A reliable pattern has emerged from comparable situations:
- Close process and template gaps fast, agile — usable, not perfect
- Simplify forms and information, with users, not for them
- Invest in training, internal and external — capability, not clickpaths
- Deploy workflows and automation only where they genuinely relieve project managers
- Build consistency and routine through a central project office that removes administrative load from projects
The outcome is not another tool, but rising schedule and target reliability, better project results, and measurable cost savings.
A Question for You:
If your projects, despite good tools, are not delivering the expected results — is that a tool problem, or a governance issue no one has openly named yet?
I am glad to discuss this with you, confidentially and at eye level.
Learn more about Operational Excellence in Project Management an read my book “Erfolg und Wachstum in projektorientierten Unternehmen” (AMAZON: https://buff.ly/3xKz4Lb)