How IPD Guides Stakeholder Identification in R&D Projects

The Integrated Product Development (IPD) methodology, derived from the PACE theory of the U.S. PRTM company and validated by IBM, divides product development into six phases—concept, planning, development, verification, release, and lifecycle—each with clear decision‑gate reviews that focus on business rather than pure technical criteria.

Product development projects are inherently cross‑functional; the project manager leads a team composed of members from multiple departments to deliver market‑driven solutions.

Typical project stakeholders include:

Project Sponsor : the senior individual to whom the project manager reports, providing guidance and resources.

Project Investor : the party supplying funding, often the sponsor but sometimes a separate finance stakeholder who may cut funding if concerns arise.

Project Beneficiary : the entity that gains profit from the completed project, such as shareholders in a new production‑line initiative.

Final Users of Project Deliverables : staff who operate the new product or system on a daily basis.

End‑Customers of the Product : the ultimate consumers whose acceptance determines market success.

Other Interested Parties : government agencies, community, media, competitors, partners, and even project‑team members’ families.

The stakeholder identification and analysis process consists of four steps:

Identify every potential stakeholder, recording role, department, interests, expectations, and influence. Interviews are used to expand the list until it is exhaustive.

Analyze each stakeholder’s possible impact or support, classify them, and prioritize key stakeholders for focused effort.

Evaluate likely reactions under different scenarios to plan influence tactics that gain support and mitigate negative impact.

Document the results in a stakeholder register that captures identity, assessment, and classification details.

The analysis matrix uses two dimensions—Influence (power) and Support (attitude)—to place stakeholders into four quadrants, each with a recommended management strategy:

High influence, strong support (key supporters): prioritize management, leverage resources.

High influence, weak support (key opponents): actively engage to neutralize resistance.

Low influence, strong support (active supporters): enlist to assist project progress.

Low influence, weak support (passive opponents): monitor, intervene only if influence grows.

The stakeholder register records three categories of information:

Identity: name, role, location, contact, and project responsibilities.

Assessment: primary needs, expectations, impact potential, and lifecycle phases of influence.

Classification: internal/external, level of authority, functional area, or any custom model used.

Planning stakeholder management involves evaluating participation levels (using expert judgment and meetings), identifying key stakeholders based on gaps between current and desired involvement, determining appropriate management strategies, and creating a detailed stakeholder participation plan that becomes part of the overall project management plan.

The participation matrix records current (C) and required (D) involvement levels, highlighting where additional engagement actions are needed. The participation plan outlines concrete actions, communication channels, and responsibilities to move stakeholders from their current state to the desired state.

Overall, the IPD‑based stakeholder management framework provides a repeatable, data‑driven approach to ensure that all relevant parties are identified, their influence and attitudes are understood, and appropriate engagement strategies are executed throughout the project lifecycle.