By Eugene le Roux, FSAIRAC and Eamonn Ryan
Project management is often spoken about as though it were a simple matter of scheduling tasks, overseeing resources and updating a Gantt chart.
Anyone who has grappled with a significant undertaking knows that this perception dramatically underestimates the discipline. Would you not agree that no major activity – be it constructing a bridge, launching a new cooling-IT system or developing an aircraft – can succeed without the rigorous application of project management?
True project management is not a clerical function. It is a strategic, technical, legal, human and organisational endeavour requiring both breadth and depth of knowledge. Far from merely co-ordinating timelines, a project manager must understand the product, the processes and the ecosystem of stakeholders that define the project’s success.
MORE THAN A PLANNING EXERCISE
Consider the development of an aircraft. Even if a highly competent main contractor is appointed to integrate the final system, the project manager cannot operate at arm’s length. Before the contractor can begin, the project manager must ensure that the requirement analysis is properly executed across all system levels, aligned with the intended timelines, and consistent with other interfacing projects. This goes beyond administrative oversight – it demands a detailed understanding of the product items themselves.
Requirements form the backbone of the entire project. If they are flawed or incomplete, every subsequent phase becomes compromised. Therefore, the project manager must be conversant not only with the high-level objectives, but also with the technical language, constraints, risks and interdependencies that govern the product’s development.
Contract management is frequently underestimated. Too often, project managers focus on reporting poor vendor performance rather than preventing it. But a good project manager does not simply relay that Contractor A or Subcontractor B delivered late. Instead, they ensure – well before issues arise – that the contract has the necessary enforcement mechanisms and that they themselves have fulfilled all obligations under the agreement.
Contracts must have teeth. They must be unambiguous, enforceable and aligned with the project’s Work Breakdown Structure (WBS), which identifies the deliverables at every level. Here, Statements of Work (SOWs) play a critical role. They serve as the bridge between contractual expectations and practical execution by outlining the inputs, activities and outputs required for each work package. To draft or negotiate these effectively, the project manager must again draw upon deep knowledge of the product and its development processes.
TECHNICAL DEFINITION, SPECIFICATIONS AND THE HUMAN DIMENSION
No complex project is complete without a robust technical definition of what is to be delivered. Detailed specifications – supported by clear acceptance criteria and test plans – form the contractually measurable baseline for performance. Yet one must ask: where does this information come from? Who is responsible for identifying and defining these specifications?
The project manager cannot rely solely on external specialists. While they may collaborate with engineers, designers or analysts, the manager must possess enough technical competence to guide, challenge and validate the work. Unfortunately, people with this combination of managerial, contractual and technical skills are not always readily available, yet the success of high-stakes projects depends on precisely this blend of expertise.
Beyond the mechanics of planning and contracting lies another significant layer of complexity: people. Internal and external communication is not merely a courtesy – it is an essential risk-control mechanism. Stakeholders may be unpredictable, resistant or even powerful enough to halt a project. Managing expectations, resolving conflicts and cultivating alignment require diplomacy, emotional intelligence and strategic communication. A project may be perfectly defined on paper yet fail due to interpersonal breakdowns.
Fundamentally, project management exists to reduce risk. All risks – technical, financial, legal, human, organisational – ultimately influence whether a project defaults on its scope, schedule, budget or stakeholder relationships. Legal requirements often add another layer of constraints, from regulatory compliance to intellectual property clauses to health and safety obligations.
To navigate these, the project manager must integrate multiple, sometimes conflicting requirements. Trade-offs become inevitable. Solutions may not always satisfy every party. This, truly, is complexity ‘on steroids’ – a dynamic environment where decisions must balance technical realities, strategic priorities, contractual terms and human behaviour.
ARE WE TRAINING PROJECT MANAGERS ADEQUATELY?
Having touched on only a fraction of the real complexity embedded in project management, one must confront an uncomfortable question:
Are we training our new project managers sufficiently before assigning them major responsibilities?
Too often, technical specialists are promoted into project roles without proper training, or managers are expected to perform in high-risk environments with only superficial exposure to the discipline. Yet the stakes of poor project management are enormous: delays, cost overruns, product failures and reputational damage.
If organisations recognise the true breadth and complexity of the discipline, they must invest in comprehensive training that integrates:
• technical literacy
• requirement analysis
• contract and commercial skills
• systems engineering principles
• human and stakeholder management, and
• risk and compliance
Project management is not merely a support function, it is a central pillar of organisational success. And only by treating it as such can organisations hope to deliver consistently and confidently in an increasingly complex world.