Stakeholders & coordination

The term "stakeholder", popularized by Edward Freeman in his 1984 book *Strategic Management: A Stakeholder Approach*, refers to any actor who influences the project or bears its consequences. This very broad definition is useful in strategic framing, but it becomes misleading at the operational level: it suggests that a single stakeholder management plan covers all cases. In practice, on a project, four distinct types coexist, and confusing their nature creates blind spots that cost dearly. **The client.** The main contractual counterpart, the client holds the power to validate, refuse, or evolve the scope. Their implicit game is twofold. On one hand, they naturally push for broad and often ill-defined scopes, with specifications peppered with placeholders to be clarified later (the famous TBDs, To Be Defined). On the other hand, they maintain competitive pressure: the explicit or implicit threat of going to competitors is common currency in negotiations. This configuration fuels what could be called a market bluffing game, where several competitors display commitments they know are difficult to keep, each betting that others will fail first. **Internal management.** Often the most complex actor to handle, particularly when the project is strategic for the organization. Their implicit game consists in multiplying requests for justification and reporting, while remaining unavailable to make the arbitrations the project manager requests. The higher the stakes, the more the project manager risks being drowned in solicitations that pull them away from real steering activities. The power asymmetry here is vertical : the project manager must obtain decisions from actors who have neither the time nor sometimes the appetite to take them. **Partners.** In temporary consortium (or joint venture) configurations, or any form of operational partnership, partners are both indispensable and often near-competitors on other markets. The fluidity of communication suffers: each party protects its sensitive areas, its methods, its commercial relationships. The configuration becomes particularly delicate when the partner owns the client relationship, which deprives the project manager of direct access to contractual information and to decision shifts. **Critical suppliers.** This category groups suppliers without whom the project cannot be delivered: suppliers imposed contractually by the client, suppliers for whom no alternative exists due to a lack of expertise on the market, or single-source suppliers on patented components. Their power asymmetry is inverted compared to classical suppliers: they know the project depends on them, and they have no contractual responsibility to the final client. In some sectors, notably at national defense procurement agencies (such as the DGA in France), it even happens that the final client has contracted directly with the critical supplier, leaving the project manager without a direct lever on their own supply chain. This typology is not exhaustive and can be refined by sector (end users distinct from the buying client, regulators, riparian communities on infrastructure projects). But it covers the four categories that call, on most projects, for a differentiated management discipline. A project manager who handles these four categories with the same generic tool sets themselves up to fail on at least one of them.

Each type of stakeholder calls for a coordination discipline of its own. The levers effective on one category are inoperative or counterproductive on another. Mastering coordination consists in mobilizing the right lever at the right place, without confusing the registers. **On the client side: investigation, progressive freeze, assured stance.** The right response to a client pushing fuzzy scopes with many TBDs is neither to refuse the contract, nor to accept everything. It is to conduct active upstream scope investigation, then to propose a progressive freeze plan or an incremental development, rather than a raw model where everything is unrolled at once with a single PDR (Preliminary Design Review) and a single CDR (Critical Design Review). The incremental approach makes it possible to freeze scope areas one after another, providing the client, at the end of each cycle, with a clear view of the impacts of the decisions taken. This dynamic progressively clarifies grey areas, including for a client who does not have all the answers at start. This discipline is developed in depth in the Scope & requirements hub. Faced with competitive pressure and threats of departure, the project manager gains from knowing precisely the value of their own company and that of competitors. A confident posture ("we deliver on our commitments at a competitive price") defuses the threat better than an anxious counter-offer. A client who perceives that they cannot play on the project manager's fear often reconsiders their negotiation strategy. **On the internal management side: lean steering system, frank disclosure, negotiation of levers.** The key when facing management that multiplies reporting requests is not to produce more tables, it is to produce fewer indicators but better targeted on real impact points. A lean and meaningful steering system progressively reduces reporting pressure without giving the impression of evasion. This discipline is developed in depth in the Steering & reporting hub. On the nature of what is escalated, the posture that best protects the project manager over time is one of lucidity: displaying real difficulties, but always accompanied by a mitigation plan. Management that discovers problems at the same time as the project manager has already handled them reinforces its trust; management that discovers problems late and without a plan stops trusting. Regarding arbitrations slow to come, the best protection is to negotiate alternative levers upstream. If internal resources are unavailable at the critical moment, having obtained beforehand the right to go find external resources avoids the deadlock. **On the partner side: partnership management plan, interest mapping.** The good practice when facing an operational partnership is to formalize from the start a project management plan at the partnership level, distinct from each company's internal management plan. This document defines the roles and responsibilities of each party, the shared steering bodies, the communication rules, the calendar of shared milestones, the escalation modalities. Without this framework, each partner operates by its own rules, and friction points accumulate silently until they become open blockers. The project manager must also explicitly identify each partner's own interests beyond the current contract: positioning on other markets, technological ambitions, internal constraints. This mapping transforms coordination into an ongoing but informed negotiation, rather than a succession of surprises. **On the critical supplier side: contractual securing and long-term levers.** When possible, securing goes through a firm contractual commitment from the supplier, with penalties and continuity clauses that align the supplier's interests with the project's. This is not always feasible: a supplier in a position of strength may refuse this type of clauses, and contracting may have been done by the final client directly, outside the project manager's field of action. In this last case, one avenue is to strengthen the clauses relating to coordination with critical suppliers in the contract between the final client and the company, to create an indirect lever. This negotiation is often difficult because the client contract is already signed before the project manager arrives on the project. Another lever, more subtle, consists in mobilizing the perspective of future business relationships: what will there be after the current contract between the company and this supplier? This dimension exceeds the project manager's scope and falls under an action at the company level, but it can unlock situations that were blocked at project level. A misidentified or poorly managed stakeholder is also a first-order risk, to be treated as such in the risk register (see the Risk & opportunity management hub).