Hard Difficulty Questions

Report the aggregate portfolio NPV and the total number of risks across all components.

Why it fails: Aggregate NPV and total risk count are too high-level to inform governance decisions. They do not show which components contribute most to value or which risks are most significant. The board needs to understand the relationship between value and risk at a component level to make informed trade-offs. This approach lacks the granularity and context required for effective portfolio oversight.

List each component's schedule and cost performance indices in a table.

Why it fails: Schedule and cost performance indices are lagging indicators of efficiency, not measures of value delivery or risk exposure. They do not show whether components are delivering the intended benefits or how much risk they carry. The board needs forward-looking information about value and risk to make strategic decisions. This table would not provide the balanced view requested.

Summarize the portfolio's benefit realization rate and the number of issues logged this quarter.

Why it fails: Benefit realization rate is a valuable metric, but combining it with issue count does not adequately represent risk exposure. Issue count reflects problems that have already occurred, not the forward-looking risk profile of components. The board needs to see potential future risks alongside expected value to make proactive decisions. This approach is incomplete for the stated objective.

Terminate these components immediately.

Why it fails: Immediate termination discards a component delivering high ROI, forfeiting returns that could fund strategic initiatives. Termination suits components with both low strategic value and poor financial performance. Where returns remain strong, the portfolio should realign, restructure or phase the component rather than eliminate it outright.

Continue funding to capitalize on the high ROI.

Why it fails: Portfolio optimisation ranks components on strategic alignment, not financial return alone, so high ROI cannot justify retaining a component contributing nothing to strategic objectives. Continued funding suits components that advance strategy while meeting return thresholds. Low strategic value indicates realignment, reduction or exit rather than ongoing investment.

Transfer these components to a different portfolio.

Why it fails: Transferring to a different portfolio does not resolve low strategic alignment; the component still consumes investment without advancing the receiving portfolio's objectives. Transfer suits components misaligned with one portfolio but genuinely fitting another's strategy. High ROI with low strategic value calls for realignment, reduction or divestment instead.

The portfolio manager should ask the Portfolio Governance Board to replace the sponsors with more engaged executives.

Why it fails: Sponsor replacement is a governance decision with significant implications for component continuity, and the scenario provides no evidence that replacement is warranted. The immediate issue is a change in stakeholder engagement behavior, which the portfolio manager should investigate directly before proposing structural changes. Escalating to replacement prematurely skips the diagnostic engagement step.

The portfolio manager should document the attendance gap in the portfolio status report and continue with the existing engagement plan.

Why it fails: Documenting the gap without acting leaves unresolved resource conflicts and an outdated engagement approach. Status reporting is not a substitute for stakeholder engagement; the portfolio manager must respond to the behavioral change. Continuing the same plan assumes the original engagement level still applies, which the sponsors' absence directly contradicts.

The sponsors are no longer key stakeholders and should be removed from the portfolio stakeholder register.

Why it fails: Executive sponsors of portfolio components retain high influence regardless of meeting attendance, and their components are actively generating resource conflicts. Removing them from the register would discard critical engagement information and worsen the unresolved conflicts. A drop in participation signals a need to reassess engagement level, not to eliminate the stakeholder from portfolio consideration.

Reject the project outright because it does not meet the sustainability goal.

Why it fails: Rejecting outright ignores the potential value of the project and the possibility of mitigating its carbon footprint. The portfolio manager should assess whether the project can be adjusted to align with sustainability goals, such as using greener materials or offsetting emissions. A balanced approach considers both financial and strategic objectives, and outright rejection may forgo significant benefits without exploring alternatives.

Approve the project with a condition that the sponsor finds a way to offset carbon emissions later.

Why it fails: Conditional approval without a concrete plan is risky and may lead to unmet sustainability commitments. Offsetting emissions later is often uncertain and may not fully mitigate the project's impact. The portfolio manager should ensure that any conditions are specific, measurable, and aligned with strategic goals before approval. This approach avoids setting a precedent that profitability always trumps sustainability.

Recommend the project for approval because profitability is a key strategic objective.

Why it fails: While profitability is important, it must be balanced with other strategic objectives such as sustainability. Approving a project that directly contradicts the carbon reduction goal could undermine the organization's overall strategy and reputation. The portfolio manager should facilitate a discussion on trade-offs and consider whether the project can be modified to meet sustainability targets or if alternative projects better align with the strategy.

Direct each project manager to add encryption tasks to their existing project schedules without changing the portfolio

Why it fails: While project managers can add tasks, this ad hoc approach lacks portfolio-level oversight and may lead to inconsistent solutions, resource conflicts, and missed dependencies. It also does not address the need to re-prioritize the portfolio to reflect the new regulatory mandate, potentially causing delays and non-compliance.

Outsource all patient data handling to a third-party vendor that already has encryption in place

Why it fails: Outsourcing may be a viable long-term strategy, but it is a major portfolio change that requires due diligence and may not meet the 12-month deadline. It also does not address existing projects that handle data. The portfolio manager should first ensure compliance within the current portfolio before considering such a drastic shift.

Request an extension to the regulatory deadline to allow the current portfolio to continue unchanged

Why it fails: Regulatory deadlines are typically non-negotiable, and requesting an extension is not a proactive portfolio management action. The portfolio manager must adapt the portfolio to meet the compliance requirement, not avoid it. This option fails to address the risk of non-compliance and could result in penalties.

Delegate the review to the component manager to save time.

Why it fails: The benefit realization review should be conducted objectively, often by the portfolio management office or an independent party. Delegating to the component manager could introduce bias and compromise the review's integrity. The portfolio manager is responsible for ensuring that reviews are conducted properly and reported to the governance board.

Grant the extension because the component manager is responsible for benefit realization.

Why it fails: The portfolio manager does not have the authority to unilaterally grant extensions to governance policies. The governance board sets policies and should approve any exceptions. Granting an extension without board approval undermines governance and could set a precedent for non-compliance. The portfolio manager should escalate the request to the board.

Close the component without a review since the benefits are still being realized.

Why it fails: Closing without a review violates the governance policy and forgoes the opportunity to validate benefits. The review is essential to ensure that the component delivered the expected value and to capture lessons learned. The portfolio manager should not bypass governance requirements; instead, the review should be conducted.

An external audit finding.

Why it fails: An external audit finding is an auditor's compliance observation, not the classification of a realised portfolio risk. It tempts because both arise from oversight activity, but a risk that occurs and impacts strategy is an issue, regardless of audit involvement.

A project failure.

Why it fails: A realised portfolio risk affecting strategic goals is an issue, not a project failure; failure denotes a project unable to deliver its objectives. It tempts because strategic impact may cascade to projects, but the risk event itself is classified as an issue.

A new risk.

Why it fails: A risk that has occurred and affected strategic goals is a realised risk (issue), not a new risk; new risks are unidentified potential events. It tempts because the event originated from the risk register, but occurrence converts it into an actual issue requiring response.

Immediately cancel all store expansion projects to reallocate funding to e-commerce.

Why it fails: Immediately canceling all store expansion projects is a drastic action that may not be necessary and could harm the business if physical stores still play a role in the omnichannel strategy. The portfolio manager should first assess the strategic fit and contribution of each component, including how store expansions might support online sales (e.g., as fulfillment hubs). A measured rebalancing is better than blanket cancellation.

Increase the budget for all existing e-commerce initiatives proportionally to their current spend.

Why it fails: Increasing budgets proportionally without assessing their potential impact or alignment may waste resources on small initiatives that cannot scale to meet the 40% target. The portfolio manager must first understand which e-commerce initiatives have the highest potential and what additional capabilities are needed. A blanket increase ignores strategic prioritization and could leave critical gaps unfilled.

Ask the e-commerce project managers to revise their business cases to show they can deliver the 40% target.

Why it fails: Asking project managers to revise business cases to meet a top-down target can lead to unrealistic projections and optimism bias. The portfolio manager should instead conduct an independent assessment of what is achievable and what portfolio changes are required. The target should drive analysis, not be retrofitted into existing business cases. This action could result in poor decisions based on inflated benefits.

Ignore their concerns as they are not experts.

Why it fails: Dismissing stakeholders because they lack technical expertise breaches the PfMP expectation of proactive engagement and leaves the perceived benefits overstatement unexamined, so any genuine forecasting error persists. Ignoring dissent would only be defensible where the group has no legitimate stake in the portfolio's outcomes.

Remove them from the list of stakeholders who receive reports.

Why it fails: Withholding reports from the sceptical group removes their visibility rather than resolving the disagreement, escalating suspicion and breaching the transparency PfMP requires for benefits governance. Restricting distribution is legitimate only for stakeholders who have formally delegated their interest or left the portfolio's sphere.

Update the benefits document to reflect lower expectations immediately.

Why it fails: Lowering the documented benefit forecasts before validating the underlying data concedes an unverified claim and corrupts the benefits register that governs portfolio decisions. Immediate revision would be right only once analysis has confirmed the original estimates were genuinely overstated.

Support the sponsor's decision and proceed, but document the community concerns in the risk register.

Why it fails: Simply documenting concerns does not address the potential risk. If the community opposition escalates, it could lead to delays, legal challenges, or reputational damage. The portfolio manager has a duty to ensure that stakeholder engagement is adequate and that significant risks are managed. Proceeding without mitigation ignores the portfolio's responsibility to balance competing stakeholder interests and could violate organizational policies.

Organize a public hearing to allow the community to voice their concerns directly to the project team.

Why it fails: A public hearing may be premature and could inflame tensions without a clear plan for addressing concerns. It also may not be the most effective way to resolve the conflict, as it can become confrontational. The portfolio manager should first assess the concerns and determine the appropriate engagement approach, which might include facilitated discussions rather than a public forum. Escalation to governance ensures a strategic view.

Commission an independent environmental impact assessment and share the results with the community.

Why it fails: An independent assessment is a good step, but it alone does not resolve the conflict or address the sponsor's insistence. The portfolio manager still needs to ensure that the governance board is aware of the situation and can make a decision on how to proceed. The assessment could be part of the information presented to the board, but it is not the immediate action to take without escalation.

Focus only on financial metrics.

Why it fails: Financial metrics alone omit the strategic, risk and non-financial benefit components that diverse stakeholders need to judge portfolio value. Financial-only reporting fits a narrow finance or investment-committee audience, not a mixed group whose interests span capability, compliance and outcomes.

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

Why it fails: A single identical report ignores differing stakeholder information needs, so executives, delivery teams and finance each receive irrelevant detail. Uniform reporting works when the audience is homogeneous with a common interest, not for a deliberately diverse stakeholder group.

Use highly technical language to demonstrate expertise.

Why it fails: Technical jargon excludes non-technical stakeholders and obscures value delivery. Technical depth is appropriate when reporting to engineering or architecture audiences who need implementation detail, not to a diverse group requiring shared understanding of portfolio outcomes.

Double the project budget.

Why it fails: Doubling the budget adds spend without diagnosing why benefits fell short, potentially worsening the portfolio's value ratio. The first step is analysing variance against the benefits realisation plan to find the cause. Extra funding suits a validated capacity or resource constraint, not an unexplained shortfall.

Abandon the strategy.

Why it fails: Abandoning the strategy pre-empts the diagnosis the stem requires first. The portfolio manager should quantify the benefits variance and trace its drivers before any strategic pivot. Strategy abandonment is a deliberate portfolio rebalancing decision, appropriate once analysis confirms the strategic objectives are unachievable.

Fire the project managers.

Why it fails: Dismissing project managers addresses personnel, not the benefits shortfall's root cause. The first step is measuring variance against the benefits realisation plan to identify whether scope, quality or adoption drove the gap. Termination is a later governance decision, appropriate only once analysis proves a manager's performance caused the failure.

Flip a coin to be fair.

Why it fails: Flipping a coin ignores the portfolio's strategic alignment, failing to weigh each component's contribution against organisational priorities. It is tempting because random selection appears impartial when components seem equal. Coin-tossing suits trivial, reversible decisions with no strategic consequence; here, the portfolio manager must apply prioritisation criteria to allocate the constrained resource deliberately.

Give the resource to the project with the longest timeline.

Why it fails: Longest timeline is not a portfolio prioritisation criterion; it ignores strategic alignment, value and risk scoring that governance uses to arbitrate contention. It is tempting because duration feels objective, and would suit scheduling levelling within a single programme, not cross-portfolio resource arbitration between competing components.

Ask the resource manager to decide.

Why it fails: Delegating to the resource manager transfers the decision away from portfolio governance, which owns prioritisation across components competing for shared capacity. It tempts because resource managers control day-to-day allocation, but that operational role cannot arbitrate strategic portfolio trade-offs between competing components.

Return on Investment (ROI) calculation.

Why it fails: ROI compares an investment's financial return against its cost, so it ranks initiatives by value rather than by probability and impact. It is tempting because portfolio managers do use ROI to prioritise funding, but that is portfolio selection, not qualitative risk ranking.

Monte Carlo analysis.

Why it fails: Monte Carlo analysis runs thousands of simulated iterations over probability distributions to produce quantitative output ranges, so it cannot perform the ordinal probability-impact ranking qualitative analysis requires. It is tempting because it is the standard portfolio risk-modelling technique, but it answers quantitative, not qualitative, questions.

Sensitivity Analysis.

Why it fails: Sensitivity analysis ranks risks by how much each one moves a quantitative model's output, so it needs numeric ranges and simulation rather than the ordinal probability-impact scoring of qualitative analysis. It is tempting because it genuinely identifies which variables most influence outcomes, but that belongs to quantitative risk analysis.

Resource leveling.

Why it fails: This is a scheduling technique.

Checklist analysis.

Why it fails: Checklists only capture known-knowns.

Variance analysis.

Why it fails: This compares planned vs. actual results.

Wait for the annual budget cycle to propose changes.

Why it fails: Strategic alignment is continuous, not tied to annual cycles.

multiple_choice

Why it fails: ...

Continue all projects until completion to avoid sunk costs.

Why it fails: Completion of misaligned projects wastes capital.

Reduce the portfolio budget by 10% across all projects.

Why it fails: Arbitrary cuts don't ensure strategic alignment.

Delegate the risk to the strongest program manager.

Why it fails: Correlated risks span programmes, so delegating to one program manager leaves cross-programme exposure unowned at portfolio level; the portfolio manager must aggregate and own it. Delegation suits single-programme risks within one manager's authority, where escalation to the portfolio is unnecessary.

Ignore the risk until it becomes an issue for one of the programs.

Why it fails: Portfolio-level risks spanning programmes require coordinated response through the portfolio risk register, not deferral; waiting lets the correlated impact materialise across several programmes simultaneously. It is tempting because programme-level issue management handles single-programme risks, which is where this risk would eventually surface.

Tell each program manager to manage the risk independently.

Why it fails: Independent management cannot address a correlated risk, since each programme sees only its own slice and duplicated mitigations conflict or overlap; the portfolio must treat it once, centrally. Independent handling is correct for programme-specific risks with no shared cause or dependency.

Eliminate the governance board and rely solely on the portfolio manager for all decisions.

Why it fails: Eliminating the governance board removes essential oversight and strategic decision-making, leading to potential misalignment with organizational objectives. The board provides accountability and ensures that portfolio decisions consider broader strategic and risk factors. While the portfolio manager plays a key role, the board's collective judgment and authority are necessary for effective governance. This action would undermine governance rather than streamline it.

Require all component managers to present detailed status reports at every board meeting.

Why it fails: Requiring all component managers to present detailed reports at every meeting is time-consuming and shifts the board's focus to operational details. It does not streamline governance; it creates a reporting burden and reduces the board's ability to focus on strategic decisions. Instead, the board should receive consolidated reports and only invite component managers for specific issues that require discussion.

Increase the frequency of governance board meetings to weekly to review all component details.

Why it fails: Increasing meeting frequency to weekly for all component details would overwhelm the board and reduce time for strategic decision-making. It is inefficient and does not streamline governance; instead, it adds bureaucracy. Efficient governance relies on exception reporting and delegated authority, not on more frequent detailed reviews. The board should focus on strategic matters, not operational minutiae.

Rename the document to 'Agile Governance Plan' without changing content.

Why it fails: Renaming the document leaves decision rights, funding gates and review cadences unchanged, so governance still operates hierarchically despite the agile shift. A rename is adequate only when the underlying governance model already matches the new operating model and merely needs relabelling.

Maintain the old plan until the next fiscal year.

Why it fails: Deferring the update until the next fiscal year leaves portfolio governance misaligned with the agile model throughout the transition, so funding and review decisions still follow hierarchical gates. Deferral is valid only when the governance change is scheduled to take effect at that later date.

Delegate all governance to the scrum masters.

Why it fails: Scrum masters govern team-level delivery, not portfolio investment decisions, so delegating all governance removes the portfolio-level decision rights, funding gates and risk oversight the plan must retain. Delegation fits when governance is genuinely devolved to delivery teams within agreed portfolio guardrails.

The number of resources currently assigned to the component.

Why it fails: Resource count is an operational detail, not a strategic decision factor. A component with many resources may still be underperforming or misaligned, while one with few resources could be highly strategic. The portfolio manager should focus on value and alignment, not headcount. Resource reallocation is a consequence of the decision, not a primary criterion.

The component manager's tenure with the organization.

Why it fails: Tenure is irrelevant to portfolio performance decisions. Decisions should be based on objective criteria such as strategic alignment, financial return, risk, and value delivery. Using tenure as a factor would introduce bias and could lead to poor portfolio outcomes. The portfolio manager must maintain objectivity and focus on data-driven analysis.

The component's historical cost performance index (CPI).

Why it fails: While CPI indicates cost efficiency, it is a lagging indicator and does not alone determine strategic fit. A component with a low CPI might still be strategically vital, while one with a high CPI might no longer align with strategy. Historical CPI is useful for performance assessment but is not a primary factor for termination decisions compared to strategic alignment and future value.