In complex environments, budget, planning and specialist expertise remain essential. Yet even a project with clear objectives and a well-prepared team can come to a standstill when stakeholders are not aligned around the same direction.
Delayed decisions, changing requirements, conflicting priorities and continuous escalations rarely stem from technical shortcomings. They are often symptoms of relationships that are not being effectively managed. A stakeholder is more than the recipient of an outcome. A stakeholder may make decisions, enable or hinder progress, validate, use, fund or regulate a process. Overlooking the importance of this network leaves a critical part of governance unmanaged.
Time, cost and scope remain central parameters in Project Management, yet in complex environments they no longer fully define project success. Stakeholder management and quality are increasingly considered alongside them, with quality understood as the alignment between needs and the value delivered.
The traditional dimensions of Project Management remain fundamental. At the same time, project success increasingly depends on the people involved, the quality of their relationships and the clarity of decision-making.
Within this context, Stakeholder Management becomes the method for bringing different interests together around a shared objective.
The evolution of the Project Management Institute’s literature, particularly the Project Management Body of Knowledge (PMBOK), also reflects this shift in approach. In the more process-oriented framework of PMBOK 6, Stakeholder Management is primarily addressed as a set of activities to be structured: identifying stakeholders, planning their engagement, managing that engagement and monitoring its effectiveness. This is an important step because it introduces methods and operational tools into an area that can otherwise rely too heavily on individual intuition or reactive management.
Subsequent developments place greater emphasis on the quality of relationships. Stakeholders are no longer simply individuals or groups to be mapped or engaged at specific stages; they become a permanent dimension of project performance (PMBOK 7).
Collaboration, trust, satisfaction and alignment become conditions that directly influence a project’s ability to generate value.
From this perspective, processes remain useful as tools to be adapted to the context, lifecycle and stakeholders involved (PMBOK 8).
The same principle is evident in agile environments, where the relational dimension becomes even more visible. In adaptive contexts, stakeholders are involved throughout the process rather than only at the beginning to gather requirements or at the end to validate an outcome. They become continuous participants in reviews and demos, feedback sessions and recurring opportunities for discussion. Their contribution reduces uncertainty, progressively guides decisions and helps verify that the value being created remains aligned with real needs. Stakeholders therefore become active participants in shaping the solution.
In complex organisational environments, this understanding translates into operational models and practices. The objective is to make relationships clear, traceable and decision-oriented.
A concrete example is the work carried out with the Ragioneria Generale dello Stato (RGS). As DOS Design, we supported the administration in defining an Organisational Model to govern the activities of the programmes and projects within its portfolio. Time, cost, scope, quality and stakeholders are brought together within a common system of rules and responsibilities, including structured opportunities for discussion, multiple levels of governance and escalation mechanisms.
Stakeholder management therefore becomes relationship management, providing coordination, alignment, traceability of decisions, operational continuity and accurate oversight of work progress.
Within the RGS landscape, the InIt Programme provides a particularly relevant example of this approach in practice. The number of stakeholders involved, the interdependencies between working groups, the coordination of different areas of expertise and the presence of multiple decision-making levels all contribute to a highly complex environment. In this context, some of the mechanisms introduced by the Organisational Model demonstrate how Stakeholder Management can play a central role in governing a complex programme.
One critical area is the relationship between Design and Delivery. Design develops solutions aligned with users’ needs; Delivery turns those solutions into tangible outcomes. Without appropriate governance, the risk of misalignment is significant.
To manage these interactions, the Programme uses the Collaboration Management Workflow. This framework makes interactions between teams explicit and manageable: it clarifies how requests are initiated, defines engagement methods, identifies the people who need to be involved, assigns operational responsibilities and establishes the steps and expectations that need to be managed.
The Collaboration Management Workflow is therefore an example of Stakeholder Management in practice. Collaboration is structured through a shared mechanism rather than simply assumed. Interactions become visible and traceable.
A second important area concerns escalation mechanisms. In any complex environment, some issues cannot be resolved directly within working groups or operational teams. Differences in priorities may emerge, constraints may be impossible to address locally, decisions may require guidance from a higher level, or issues may have cross-cutting impacts. In these cases, escalation is neither an anomaly nor a failure. It is a necessary governance mechanism, provided that it is properly structured.
Within the InIt Programme, this mechanism also takes shape through the Board Meeting, a formalised governance ceremony whose purposes include collecting and managing escalations raised by the different working groups. The Board provides a governance forum where issues that cannot be resolved at the operational level can be brought to a higher Programme body, which is responsible for making decisions, providing direction and realigning stakeholders around shared objectives.
Managing an escalation means recognising that, where different interests, priorities and responsibilities coexist, convergence cannot always happen spontaneously. In these contexts, it is useful to establish a forum where differences can be made explicit, discussed and brought towards a decision.
In complex programmes, stakeholder management translates into the governance of relationships. This approach creates the conditions for collaboration, decision-making and structured escalation, turning relational complexity from a potential risk into a driver of coordination and value.
Stakeholder Management goes beyond simply building an organisational matrix. Its operational objective is to bring people, priorities and expectations together around a shared outcome.
Today, many areas of Project Management are supported by technological tools that help organisations plan, monitor and anticipate potential issues. Stakeholder management, however, remains a deeply human dimension. Technology can organise information and processes, while listening, trust, sensitivity and mediation continue to depend on people.
In complex environments, governing stakeholders means governing the relationships through which a project takes shape. The quality of those relationships can ultimately determine whether an initiative succeeds or fails.
(This article is an adaptation of my contribution to the ASSO PM webinar entitled “Stakeholder Management: when relationships determine project success”)

