Irritations at the Start of a Telecommunications Project (Mini-Case Study: 3.2)

This mini-case study examines stakeholder conflict at the beginning of a telecommunications project. It considers how competing technical priorities, unclear responsibilities, and different expectations can complicate project initiation.

Q1. What went wrong in terms of stakeholder management?

The stakeholder concept is an important contribution to business management. Concern for stakeholder interests is a recognized feature of ethical management and conflict resolution. Stakeholders are people, groups, or organizations that have interests in a project, may influence it, or may be affected by its planning, implementation, and use.

From the beginning, it is important to identify potential conflicts between stakeholders. This supports anticipation and conflict management. The next step is to assess stakeholder expectations and identify where their interests or priorities might differ.

In this case, both teams needed sufficient authority and the necessary competencies to meet the project's specifications and requirements. Conflict emerged over whether to choose a cost-competitive, non-platform solution or a solution considered to offer advantages for future requirements.

This disagreement should have been addressed early through clear responsibilities, agreed decision-making arrangements, and adequate communication channels.

Different Priorities Needed a Shared Basis for Comparison

The original analysis identifies a trade-off between immediate cost competitiveness and longer-term suitability. Neither priority is inherently unreasonable. Frustration can arise when participants evaluate the same options using different assumptions or success measures.

A lower initial price does not establish the lowest overall cost. Equally, describing a solution as “future-proof” does not demonstrate that it will meet every future requirement. Both claims need evidence and an agreed time horizon.

APM recommends early and continuing consultation to clarify requirements, working relationships, and measures of success.[1] Applied here, that would mean agreeing how the alternatives would be assessed before committing to a preferred solution.

Authority and Representation Also Matter

Technical competence alone is insufficient if participants cannot approve decisions or obtain timely approval. The team should know who can recommend an option, who must be consulted, and who can authorize the commitment.

Disagreement can be useful when it exposes a genuine trade-off. The management problem is allowing that disagreement to remain unresolved without a clear decision process.

Illustrative Option-Comparison Framework

The following table proposes questions for evaluating the alternatives described in the original answer. It does not assign scores or establish that either option was technically superior.

Questions for Comparing the Telecommunications Solutions
Criterion Question for both options Evidence to seek
Initial cost What is included in the quoted price? Comparable estimates covering equipment, implementation, and necessary services.
Requirements fit Does the option meet the agreed essential requirements? Documented requirements and demonstrable technical capability.
Future adaptability Which anticipated changes can the solution accommodate? Specific upgrade assumptions, dependencies, and limitations.
Integration How will the solution connect with relevant systems? Interface specifications and appropriate test results.
Whole-life cost What operating, maintenance, and replacement costs are expected? Cost estimates over an agreed evaluation period.
Delivery risk What could prevent successful implementation? Dependencies, resource needs, and identified uncertainties.

APM describes a business case as evaluating the benefits, costs, and risks of alternatives and explaining the rationale for the preferred solution.[2] This provides a useful basis for resolving the competing priorities in the case.

Q2. Compare project initiation tasks with the activities in the case. What should the organization improve?

Initiation is a critical phase in the project life cycle. It establishes the foundation for deciding whether and how the project should proceed. Developing a business case and conducting proportionate feasibility work can help clarify that decision.

In this case, the organization should have examined feasibility and decided which party would carry out the project. Both parties could also have been involved, depending on the capabilities and support each could provide.

The project leader should have prepared a proposal clearly describing the intended approach. When organizations enter a temporary working relationship, different expectations may arise concerning the results. Agreement about whether the work is a prototype is particularly important because it shapes the objectives and acceptance expectations.

In my opinion, unclear communication can be a major contributor to project failure. Communication should therefore remain relevant, understandable, and directed toward the appropriate stakeholders.

Clarify What a Prototype Is Expected to Demonstrate

If the project involves a prototype, the parties should agree which questions it is intended to answer. They should also distinguish prototype acceptance from authorization of a production solution.

A prototype may provide evidence for a later decision; its existence does not guarantee the suitability of the final product. The supplied account does not establish the exact prototype arrangements, so these are proposed improvements rather than additional case facts.

Proposed Initiation Checklist

Initiation Tasks and Recommended Improvements
Task Improvement Expected output
Define the need Agree the business problem and intended outcomes. A shared statement of purpose.
Identify stakeholders Confirm relevant participants and decision authority. Documented consultation and approval responsibilities.
Assess feasibility Review capabilities, constraints, dependencies, and uncertainty. Evidence supporting or challenging the proposed approach.
Compare options Assess alternatives against agreed criteria. A justified recommendation and recorded trade-offs.
Define delivery arrangements Agree which organization performs and approves each part of the work. Clear responsibilities and escalation routes.
Confirm prototype expectations Specify learning objectives, limitations, and acceptance criteria. An agreed basis for evaluating the prototype.
Authorize the next stage Review outstanding questions before committing further resources. A documented decision and conditions for proceeding.

The European Commission's PM² resources include a business case, project charter, stakeholder matrix, and communications management plan. These offer practical templates for documenting the proposed arrangements.[3]

Illustrative Example: Making the Trade-Off Explicit

Suppose one team favors a less expensive solution while another anticipates a later expansion. Rather than debating broad claims about cost and future readiness, the teams could identify the expected expansion, assess whether each option can support it, and estimate the consequences.

The resulting evidence would not remove every uncertainty, but it would make the decision more transparent. This example is illustrative and is not an additional event reported in the case.

Conclusion

The disagreement reflected competing priorities that needed a shared decision framework. Earlier consultation, clearer authority, proportionate feasibility work, and explicit delivery expectations could have improved initiation. The goal is to turn stakeholder disagreement into an informed choice with understood responsibilities and trade-offs.

Sources and Further Reading

These sources support the expanded management guidance rather than independently document the original case. The tables and example are proposed analytical additions.

  1. Association for Project Management. Consult Early and Often.
  2. Association for Project Management. What Is a Business Case?
  3. European Commission. PM² Artefacts.