Portfolio Stakeholder Engagement practice questions

Request an immediate audit of all project management processes.

Why wrong: This is a reactive and potentially disruptive measure without prior investigation.

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

Why wrong: Output is not the same as value; the board wants to see outcomes.

Ask the board member to provide specific examples of failure.

Why wrong: While necessary, it is better to lead with data you already have first.

Refuse the request immediately and inform their supervisor.

Why wrong: A confrontational approach is not professional or conducive to engagement.

Implement the change to keep the stakeholder happy.

Why wrong: Prioritizing individual requests over strategy undermines the portfolio's purpose.

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

Why wrong: Procrastination does not resolve the conflict.

Ignore the concern until the next quarterly update.

Why wrong: Ignoring stakeholder concern leads to a loss of trust and governance failure.

Request more staff to handle the extra scope.

Why wrong: Adding resources without evaluating the scope change violates sound portfolio management practices.

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

Why wrong: This risks project failure and does not address the underlying scope management issue.

A list of all external vendors supporting the portfolio.

Why wrong: Vendor management is separate from communication management.

The entire portfolio budget breakdown for the next three years.

Why wrong: This is data, not a communication plan strategy.

The personal contact details of all project managers.

Why wrong: This is administrative information, not a critical communication strategy element.

Portfolio Charter

Why wrong: The charter defines the portfolio authorization, not stakeholder details.

Portfolio Strategic Plan

Why wrong: This document covers the long-term vision, not stakeholder administration.

Communication Management Plan

Why wrong: This plan dictates how to communicate, not who the stakeholders are.

WBS (Work Breakdown Structure)

Why wrong: WBS is for scope decomposition.

SWOT Analysis

Why wrong: SWOT is for strategic positioning, not stakeholder analysis.

Risk Register

Why wrong: The risk register is for tracking threats and opportunities.

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

Why wrong: Regulatory changes often require timely intervention and cannot wait for the annual cycle.

Ask the component managers to handle the regulatory compliance independently.

Why wrong: Portfolio-level governance is responsible for ensuring that cross-component impacts are managed centrally.

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

Why wrong: Emails are insufficient for high-level governance decisions regarding portfolio impact.

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

Why wrong: Reducing transparency usually increases distrust and resistance.

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

Why wrong: Ignoring stakeholders does not eliminate their influence or the source of the conflict.

Escalate the resistance to the portfolio sponsor immediately.

Why wrong: Escalation should be a last resort after attempts to understand and address concerns.

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

Why wrong: This does not address the core issue of strategic alignment.

Cancel the component immediately without notifying others.

Why wrong: Unilateral cancellation without governance oversight is poor practice.

Continue as planned until the end of the fiscal year.

Why wrong: Ignoring market shifts leads to wasted investments.

A shared spreadsheet comment.

Why wrong: Too impersonal and likely to cause further misunderstanding.

A formal status report.

Why wrong: Reports are for tracking, not conflict resolution.

A mass email to the entire portfolio team.

Why wrong: Mass emails are inappropriate for sensitive, bilateral conflicts.

The number of projects the stakeholder sponsors.

Why wrong: While relevant, influence and interest are more encompassing.

The salary level of the stakeholder.

Why wrong: Salary is irrelevant to professional portfolio stakeholder management.

The stakeholder's email address.

Why wrong: Contact info is useful but not the most critical factor for engagement strategy.

To document all project meeting minutes.

Why wrong: That is a task, not the strategic purpose of a communication plan.

To increase the number of meetings held.

Why wrong: Efficiency, not quantity, is the goal.

To replace the need for direct stakeholder interaction.

Why wrong: Communication plans support, not replace, interaction.

The report is too brief.

Why wrong: Executives usually prefer concise reports.

The report is sent too frequently.

Why wrong: While possible, the content's relevance is a higher priority issue.

The sponsors are too busy to read emails.

Why wrong: This assumes a lack of interest rather than a failure in communication utility.

To report them to the board for non-compliance.

Why wrong: This is punitive and not a standard portfolio management practice.

To convince them to change their mind.

Why wrong: While you may aim to improve alignment, the primary goal is risk mitigation.

It is not necessary to include them in the register.

Why wrong: Ignoring impacted stakeholders is a significant oversight in portfolio management.

Send them a report only after all benefits are achieved.

Why wrong: Stakeholders need to be involved throughout, not just at the end.

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

Why wrong: Sign-offs are administrative; active engagement requires collaboration.

Exclude them from discussions to avoid bias in data collection.

Why wrong: Stakeholder feedback is vital for accurate benefit realization assessment.

Tell them the decision is final and non-negotiable.

Why wrong: This erodes trust and fails to explain the rationale.

Blame the governance board for the decision.

Why wrong: This shows a lack of ownership and professional integrity.

Offer to give them more budget to compensate.

Why wrong: Budget does not resolve a prioritization disagreement based on strategic value.

Sending a mass email.

Why wrong: This is push communication.

Calling a stakeholder on the phone.

Why wrong: This is also interactive.

Holding a project status meeting.

Why wrong: This is interactive communication.

Focus only on financial metrics.

Why wrong: Value is multifaceted and may include non-financial strategic benefits.

Keep the report exactly the same for everyone to ensure consistency.

Why wrong: Consistency is good, but relevance is better for engagement.

Use highly technical language to demonstrate expertise.

Why wrong: Technical jargon alienates non-technical stakeholders.

Ask the board to conduct the re-analysis for you.

Why wrong: Stakeholder management is the responsibility of the portfolio manager.

Assume the initial analysis is still good enough.

Why wrong: This leads to ineffective engagement and potential misalignment.

Wait until the next annual review to update it.

Why wrong: Waiting too long risks acting on incorrect engagement strategies.

To write the daily status reports.

Why wrong: This is an operational task for the management team.

To perform the technical work of the portfolio components.

Why wrong: The board is for governance, not execution.

To identify every individual stakeholder in the organization.

Why wrong: That is the responsibility of the portfolio manager.