Project management

Contents

1. The Processes & Methods axis: fit beats purity
2. The Technologies & Tools axis: the tool is the last decision, not the first
3. How this interacts with the soft axes
4. A tool check for what you already have
5. Conclusion

The Processes & Methods axis: fit beats purity

The methodological debate of the past fifteen years, agile against traditional, has consumed a lot of energy and improved few projects. The more productive question is not “which method is better?” but “what kind of task is this?”. Initiatives with stable requirements and high costs of change (plant engineering, construction, regulated environments) benefit from a plan-based approach. Initiatives with unclear requirements and cheap iterations (software, product development) benefit from an empirical, agile approach. The reality in most organizations is adaptive, and that is not a lazy compromise but professionalism, provided the interfaces are designed deliberately: how does an agile subproject synchronize with an overall stage-gate plan? Who decides what, when and on which data? Three design principles have proved themselves. As much standard as possible, as much adaptation as necessary: a shared minimum standard of phases, roles and reporting creates comparability across projects, while room to maneuver below it preserves the fit. Scale by risk: a 50,000 euro project needs different governance from a 50 million program, and uniform maximum processes for everything create exactly the bureaucracy that gives methods a bad name. And methods live on ability, not on documents: a lean, well-trained approach beats any comprehensive handbook nobody knows.

The Technologies & Tools axis: the tool is the last decision, not the first

Hardly any investment decision is made back to front as often as the tool question. The pattern: a tool is selected because it was demonstrated impressively, and then the organization tries to adapt its way of working to the tool. The right order is the reverse: first the process, then the requirements, then the tool. Four important questions before any tool decision. Which concrete process is the tool meant to support, and is that process defined and accepted? Who has to work with the tool, and what can reasonably be asked of those people, the question of adoption? Which data flows to neighboring systems (ERP, resource planning, controlling) are needed? And how high are the follow-on costs for maintenance, administration and training, not just the license? An honest finding from practice: a mediocre tool on a good process works. An excellent tool on a missing process never does.

How this interacts with the soft axes

Here too the logic of the axis cross applies: methods and tools only work in combination with people and organization. A new reporting system (process) needs managers who read reports and act on them (organization). A collaboration tool (technology) needs teams who want to communicate openly (people). Anyone who introduces tools without checking the foundation is building on sand, and will later wrongly blame the tool for the failure.

A tool check for what you already have

It is not only new purchases that deserve scrutiny, but the existing landscape too. Three questions for a short internal audit. Which tools in the project management environment are actually used, by whom and for what, and which are only filled in because somebody demands it? Where do employees enter the same data more than once in different systems? Every duplicate entry points to an unresolved question of process or interface. And which decisions are actually made using the data from these tools? A system whose data never appears in a decision meeting is not infrastructure, it is a ritual. In most organizations the answers reveal clear potential for consolidation, and often the most effective tool project of the year is a shutdown.

Conclusion: processes, methods and tools are the visible backbone of professional project work, but they are means, not ends. The art lies in the fit, to the task, to the risk, to the organization and to the people who work with them. That closes our series on methods. Anyone who wants to learn the craft from the ground up or anchor it in their team will find a concrete format in the next article: the project management fundamentals course with a TÜV certificate.

Would you like to check your project management processes and tool landscape for fit? We offer a compact, free live webinar on September 18, 2026 at 10:00 CEST, held in German. Subscribe now Register here: https://event.webinarjam.com/4o8q9v/register/n5l6y7h5