Portfolio Stakeholder Engagement practice questions

Avoiding stakeholders to focus on fixing the problem.

Why it fails: Avoiding stakeholders during a crisis is the worst possible approach.

Only sharing good news to keep morale high.

Why it fails: Honesty is required even in a crisis.

The portfolio manager ignores all stakeholder emails to focus on work.

Why it fails: Ignoring stakeholder emails removes the communication channel engagement depends on, so it demonstrates disengagement rather than high engagement. It is tempting because focusing on delivery work looks diligent, yet portfolio stakeholder engagement requires active, two-way communication; ignoring input would be defensible only if stakeholders had no bearing on portfolio outcomes.

Stakeholders rely on the portfolio manager to make all decisions without input.

Why it fails: Concentrating all decisions in the portfolio manager removes stakeholder participation, which is the opposite of engagement. It is tempting because decisive leadership appears efficient, but engagement means involving stakeholders in decisions affecting them; unilateral decision-making would suit a command-and-control structure with no engagement objective.

Stakeholders only attend meetings when forced to by the sponsor.

Why it fails: Attendance compelled by the sponsor indicates compliance, not engagement, since stakeholders contribute nothing voluntarily. It is tempting because meetings do occur and people are present, but engagement requires willing participation and input; forced attendance would be acceptable only where the goal is merely recording attendance.

Schedule a meeting with the CFO to understand the specific reporting deficiencies, then propose a revised reporting approach to the portfolio governance board for approval.

Why it fails: While understanding the CFO's concerns is important, this option delays action by scheduling a meeting first. The question asks what to do FIRST, and the most immediate need is to address the reporting gap. However, the CFO has already expressed a clear concern, so further clarification may not be the first step. Also, proposing to the governance board is appropriate, but the action is not as direct as implementing a recognized valuation method.

Instruct the finance team to include qualitative commentary about the potential of early-stage programs in the next portfolio report, without changing the quantitative metrics.

Why it fails: Adding qualitative commentary does not address the quantitative deficiency the CFO highlighted. It may be seen as a superficial fix and does not provide a systematic way to value long-term potential. Portfolio management relies on quantitative methods to compare and prioritize components. This approach fails to incorporate risk-adjusted financial metrics, leaving the core issue unresolved.

Immediately change the reporting format to show only projected revenues for each component over a 10-year horizon, and present this to the CFO.

Why it fails: Focusing solely on projected revenues without considering costs or risks would present an overly optimistic and incomplete picture. This could mislead stakeholders and lead to poor investment decisions. The CFO's concern is about capturing long-term value, but this approach ignores the high upfront costs and risks inherent in drug development. It also bypasses governance approval and may not align with portfolio management standards.

Create a detailed communication matrix that specifies exactly what information each stakeholder will receive and when.

Why it fails: A communication matrix is a component of the stakeholder engagement plan, but it should be developed after stakeholder analysis. Creating it first would be premature because you need to know the stakeholders and their needs to determine appropriate communication. It is not the first action to take.

Immediately schedule a kickoff meeting with all potential stakeholders to announce the project and gather initial feedback.

Why it fails: While a kickoff meeting is valuable, it should occur after stakeholder analysis and planning. Calling a meeting without knowing who the key stakeholders are or their interests may result in poor attendance, miscommunication, or missing critical parties. It is more effective to analyze first, then plan, then meet.

Escalate the need for stakeholder engagement to the Portfolio Governance Board and request their guidance on which stakeholders to prioritize.

Why it fails: The portfolio manager is responsible for stakeholder identification and engagement. Escalating this to the Governance Board is unnecessary and may be seen as a lack of capability. The board's role is oversight, not operational stakeholder management. The portfolio manager should conduct the analysis and planning.

Request an immediate audit of all project management processes.

Why it fails: Auditing all project management processes examines methodology compliance, not whether the portfolio delivered the promised benefits, so it misdirects the response. It is tempting because audits are a familiar governance tool, and would be correct if process adherence itself were the concern.

Defend the portfolio by listing all completed tasks from the last quarter.

Why it fails: Listing completed tasks reports activity, not the value outcomes the board disputes; it cannot demonstrate benefit realisation against the portfolio's strategic objectives. It tempts because task tracking suits routine progress reporting, and would be correct when a sponsor simply needs delivery status, not a value defence.

Ask the board member to provide specific examples of failure.

Why it fails: Requesting examples gathers evidence but delays the immediate action of investigating the value-delivery claim against portfolio performance metrics. It is tempting because clarifying vague criticism feels prudent, yet it would be correct only after the underlying data has been reviewed.

Refuse the request immediately and inform their supervisor.

Why it fails: Refusing outright and escalating to a supervisor bypasses portfolio governance and damages the stakeholder relationship. Escalation is correct when the stakeholder breaches agreed governance processes or the conflict cannot be resolved through the portfolio board.

Implement the change to keep the stakeholder happy.

Why it fails: Implementing the change subordinates portfolio strategy to stakeholder pressure, misallocating resources and undermining governance. Accommodating stakeholders is correct when the change aligns with strategic objectives and passes portfolio change control, not when it contradicts them.

Tell the stakeholder that you need more time to study the request.

Why it fails: Deferring to study the request delays a decision the portfolio's strategic direction already answers, and signals indecision to an influential stakeholder. Analysis is correct when the request's strategic alignment is genuinely unclear, which is why it appears reasonable here.

Ignore the concern until the next quarterly update.

Why it fails: Deferring the concern leaves scope uncontrolled until the quarterly review, allowing cost and schedule drift to compound. It is tempting because it avoids confrontation and fits existing reporting cycles, and would be correct where the variance is trivial and already covered by agreed tolerance thresholds in the portfolio plan.

Request more staff to handle the extra scope.

Why it fails: Adding staff expands capacity to deliver the extra scope, accepting the creep rather than controlling it, and leaves the portfolio's strategic alignment unexamined. It is tempting because resourcing feels decisive and addresses stakeholder delivery pressure, and would be correct where scope is legitimately approved and the constraint is genuinely insufficient personnel.

Arbitrarily reduce the budget for the project to force scope reduction.

Why it fails: Cutting budget arbitrarily does not remove scope; it forces cuts unrelated to strategic value and damages delivery capability. It is tempting because it appears to restore cost control quickly, and would be correct only where a formally approved funding reduction has already been agreed through portfolio governance and change control.

A list of all external vendors supporting the portfolio.

Why it fails: A vendor list is portfolio inventory, not a communication specification; the plan requires defined stakeholders, information needs, cadence and channels for performance reporting. It tempts because vendors are stakeholders who receive updates, but listing them omits what is reported, to whom, how often and through which channel.

The entire portfolio budget breakdown for the next three years.

Why it fails: Performance reporting needs agreed metrics, reporting frequency, audiences and escalation paths; a three-year budget breakdown is financial planning data, not a communication element. It tempts because budget figures appear in portfolio reports, but the plan must define how performance information flows, not forecast costs.

The personal contact details of all project managers.

Why it fails: Contact details are directory data, not a communication plan; effective performance reporting requires defined metrics, audiences, frequency, format and escalation routes. It tempts because project managers are reporting participants, but recording their personal details does not specify how portfolio performance information is distributed or acted upon.

Portfolio Charter

Why it fails: A portfolio charter authorises the portfolio and defines its scope, objectives and governance structure; it does not record stakeholder expectations, roles or influence levels. It is tempting because charters do establish high-level authority and sponsor relationships, but stakeholder registers and analysis grids serve that tracking purpose.

Portfolio Strategic Plan

Why it fails: The portfolio strategic plan aligns components with organisational strategy, defining vision, objectives and prioritisation; it does not track individual stakeholder expectations, roles or influence. It is tempting because strategy work involves senior stakeholders, but a stakeholder register captures those per-person attributes.

Communication Management Plan

Why it fails: A communication management plan defines how, when and to whom information is distributed; it does not catalogue stakeholder expectations, roles or influence. It is tempting because communication planning follows stakeholder analysis, yet the register itself, not the plan, records those attributes.

WBS (Work Breakdown Structure)

Why it fails: A WBS decomposes scope into deliverables and work packages; it contains no stakeholder attributes at all. It is tempting because it is a core PfMP planning artefact, and it would be correct when defining and organising the programme's deliverables into manageable components.

SWOT Analysis

Why it fails: SWOT maps internal strengths and weaknesses against external opportunities and threats; it never plots stakeholders on interest and influence axes. It is tempting because it is a familiar strategic-analysis grid, and it would be correct when assessing an organisation's strategic position before selecting initiatives.

Risk Register

Why it fails: A risk register catalogues threats with probability, impact, owner and response; it holds no interest or influence ratings for stakeholders. It is tempting because it also tracks people and issues, and it would be correct when logging, prioritising and monitoring programme risks through their lifecycle.

Wait for the annual portfolio review meeting to discuss the change.

Why it fails: Waiting until the annual review delays governance action on a live regulatory obligation, so affected components proceed without approved direction or funding. It is tempting because the review is the established forum, and deferring would be acceptable for a low-priority change with no compliance deadline or immediate portfolio impact.

Ask the component managers to handle the regulatory compliance independently.

Why it fails: Delegating to component managers fragments the response, leaving no portfolio-level view of cross-component dependencies, conflicts or consolidated risk for the board to govern. It is tempting because component managers own their delivery, and it would be correct for a requirement confined to a single component with no portfolio-wide effect.

Send an email to the board members with the full regulatory text.

Why it fails: Dumping the full regulatory text gives the board raw legal wording with no portfolio impact analysis, dependencies or recommended response, so it cannot support a governance decision. It is tempting because it is fast and complete, and would be right for distributing reference material after the board has already received an impact assessment.

Limit the group's access to portfolio performance reports to reduce friction.

Why it fails: Withholding performance reports removes the transparency that lets stakeholders evaluate and align with strategic shifts, which typically deepens resistance rather than resolving it. Restricting access is tempting as a friction-reduction tactic, and it would be defensible only where a stakeholder has no authorisation to view confidential portfolio data.

Update the portfolio management plan to remove the stakeholder from the engagement list.

Why it fails: Removing a resistant stakeholder from the engagement list suppresses the symptom rather than addressing the root cause of resistance, and it breaches the portfolio manager's duty to maintain stakeholder engagement across the portfolio. It is tempting because reducing the audience appears to simplify communication, and disengagement would be valid only where a stakeholder has no legitimate interest or influence.

Escalate the resistance to the portfolio sponsor immediately.

Why it fails: Escalation transfers the decision upward without addressing the stakeholder group's concerns, leaving resistance intact and eroding trust. Escalation suits a blocked decision requiring sponsor authority. Improving engagement here requires structured dialogue and influence mapping to surface and resolve the underlying objections directly.

Ask the component team to absorb the cost of the change.

Why it fails: Charging the component team for the change addresses cost recovery, not the portfolio-level decision to rebalance, reprioritise or retire the component whose value proposition has shifted. It is tempting because cost absorption preserves the portfolio budget, and would be correct where the change is minor and the component's strategic value remains intact.

Cancel the component immediately without notifying others.

Why it fails: Cancelling unilaterally bypasses portfolio governance, skipping the impact analysis and stakeholder consultation that a value-proposition change requires before rebalancing or terminating a component. It is tempting because swift cancellation stops further investment, and would be correct only after governance review confirms the component no longer aligns with strategy.

Continue as planned until the end of the fiscal year.

Why it fails: Deferring review until the fiscal year ends leaves the portfolio misaligned with the shifted market, forfeiting reallocation or termination decisions that governance demands now. It is tempting because annual planning cycles provide stability and budget predictability, and would be correct where value propositions remain stable and no trigger for reassessment exists.

A shared spreadsheet comment.

Why it fails: A shared spreadsheet comment is asynchronous, visible to all with access, and too narrow to carry the nuance a sensitive conflict demands. It tempts because comments keep discussion attached to the relevant artefact, and would suit routine collaborative review, but resolving conflict requires private real-time dialogue.

A formal status report.

Why it fails: A formal status report is one-way, broadcast communication that cannot surface the underlying positions or emotions a sensitive conflict requires. It tempts because reports document decisions and progress, and would suit routine portfolio governance updates, but conflict resolution demands direct two-way dialogue between the parties.

A mass email to the entire portfolio team.

Why it fails: A mass email exposes a sensitive interpersonal dispute to the whole portfolio team and cannot support the private two-way exchange needed to resolve it. It tempts because email reaches everyone quickly, and would suit announcing a settled decision, but conflict resolution requires confidential direct discussion.

The number of projects the stakeholder sponsors.

Why it fails: Sponsorship counts describe a stakeholder's portfolio footprint, not the engagement data the register governs. The register's purpose is recording influence, interest and engagement strategy, so the decisive factor is each stakeholder's current power and interest position. Counting sponsored projects would fit capacity or investment-balance analysis instead.

The salary level of the stakeholder.

Why it fails: Salary level has no bearing on a stakeholder register, which records identification, influence, interest and engagement classification for portfolio decisions. Compensation data belongs in HR or resource-management records, not the register. It would only be relevant when analysing remuneration for budgeting or resource-cost planning, not when verifying stakeholder information.

The stakeholder's email address.

Why it fails: An email address is a contact detail, not the engagement attribute the register exists to capture. The register's critical field is each stakeholder's influence, interest and alignment with portfolio objectives, which drives communication and engagement planning. Contact data would be the focus when maintaining a distribution list or notification channel, not the Portfolio Stakeholder Register.

To document all project meeting minutes.

Why it fails: Meeting minutes are project-level artefacts produced by the project manager; a portfolio communication plan addresses strategic messaging across the portfolio to executives and governance bodies. Documenting minutes would be correct only when the requirement is a project record-keeping procedure, not portfolio-wide stakeholder engagement.

To increase the number of meetings held.

Why it fails: The plan governs message content, timing and audience, not meeting volume; increasing meetings adds overhead without improving communication quality. It would be the right aim only if the diagnosed problem were genuinely insufficient stakeholder contact, which the plan itself does not mandate.

To replace the need for direct stakeholder interaction.

Why it fails: A communication plan defines audiences, messages, channels and cadence; it coordinates engagement rather than substituting for it. Direct interaction remains essential for portfolio decisions, escalations and stakeholder alignment. Replacing interaction would be the goal only if stakeholders were purely passive recipients, which portfolio governance never assumes.

The report is too brief.

Why it fails: Silence from sponsors signals the report lacks decision-relevant content, such as strategic alignment, benefits realisation and exceptions requiring action; brevity alone does not cause non-response. It is tempting because trimming length feels efficient, and a brief report would be correct for a routine status update to a delivery team, not executives.

The report is sent too frequently.

Why it fails: Frequency does not explain silence; a report lacking strategic insight, benefit forecasts or escalation points generates no response regardless of cadence. It is tempting because over-communication is a recognised anti-pattern, and reducing frequency would be correct if sponsors had complained about volume, not ignored content.

The sponsors are too busy to read emails.

Why it fails: Sponsor silence reflects the report's content failing to demand a decision or surface strategic risk, not their workload; busy executives still respond to reports requiring governance action. It is tempting because workload is an easy external explanation, and it would be correct if sponsors had explicitly delegated portfolio decisions elsewhere.

To report them to the board for non-compliance.

Why it fails: Stakeholder identification gathers and analyses interests and influence; it is not an enforcement mechanism, and the board is not a compliance body for portfolio stakeholders. Reporting them is tempting when opposition feels like obstruction, but the register exists to understand impact and plan engagement, not to escalate non-compliance.

To convince them to change their mind.

Why it fails: Including negatively impacted stakeholders is to understand their interests, influence and potential resistance so engagement can be planned; persuasion is an engagement outcome, not the identification purpose. It is tempting because opposition often needs addressing, but the register captures impact and expectations, not predetermined attempts to change minds.

It is not necessary to include them in the register.

Why it fails: Excluding negatively impacted stakeholders from the register leaves their interests, resistance and requirements unanalysed, so the portfolio cannot manage risks or expectations arising from them. It is tempting when such stakeholders appear obstructive, but identification is about capturing influence and impact, not filtering out inconvenient parties.

Send them a report only after all benefits are achieved.

Why it fails: Reporting only after benefits are achieved gives stakeholders no opportunity to influence realisation while it is still underway, so involvement is retrospective rather than continuous. It is tempting because post-implementation reporting is genuinely useful for governance closure and benefits confirmation, but that belongs at the end of the cycle, not as the engagement mechanism.

Ask them to sign a document stating they support the benefits.

Why it fails: A signed support document captures a one-off declaration rather than ongoing participation in benefit measurement, review and adjustment. It is tempting because formal endorsement is genuinely valuable for securing sponsorship and commitment at approval gates, but sign-off is a governance artefact, not a mechanism for continuous stakeholder involvement in realisation.

Exclude them from discussions to avoid bias in data collection.

Why it fails: Deliberately excluding stakeholders removes the very input the process needs, and bias is mitigated through facilitation techniques, not exclusion. It is tempting because controlled data collection does reduce skewed responses in narrow analytical contexts, yet portfolio benefit realisation depends on stakeholder contribution, so exclusion directly contradicts the requirement.

Tell them the decision is final and non-negotiable.

Why it fails: Declaring the decision final and non-negotiable shuts down dialogue, so the stakeholder's perception of unfairness is never examined against portfolio prioritisation criteria. It is tempting when governance decisions are settled, but transparent re-scoring against strategic alignment and balancing is what resolves perceived inequity.

Blame the governance board for the decision.

Why it fails: Blaming the governance board deflects accountability and inflames the stakeholder rather than resolving the perceived unfairness. It is tempting because governance boards do set prioritisation, so escalating there can feel legitimate; however, the portfolio manager's role is to facilitate transparent re-evaluation against strategic criteria, not to assign fault.

Offer to give them more budget to compensate.

Why it fails: Offering extra budget bypasses the portfolio prioritisation criteria and misallocates funding, since the stakeholder's concern is ranking, not resourcing. It is tempting as a goodwill gesture, but re-examining scoring against strategic alignment and balancing addresses the perceived unfairness directly.