Select Two (Multi-Select) Questions

Portfolio performance reports

Why it fails: Portfolio performance reports provide data on progress and variances, which can inform risk identification, but they are not a foundational input to the risk management process itself. The process inputs typically include the portfolio management plan and risk register. Performance reports are more of an output or monitoring tool.

Individual project schedules

Why it fails: While project schedules can provide context, they are not a direct input to the portfolio risk management process. Portfolio risk management focuses on aggregated risks and strategic alignment, not detailed project timelines. Using schedules as a primary input could distract from portfolio-level risk assessment.

Resource breakdown structure

Why it fails: A resource breakdown structure organizes resources by category, but it is not a primary input to portfolio risk management. While resource availability can influence risks, the portfolio risk management process relies more on risk registers, plans, and performance reports. Using it as a key input would be a misapplication of tools.

The frequency of office social events.

Why it fails: Social-event frequency does not feed portfolio risk assessment, which weighs component-level probability and impact against strategic objectives. It is tempting because staff-engagement metrics genuinely belong in organisational-health reporting, where such data would be the right input.

The color of the project office wallpaper.

Why it fails: Wallpaper colour has no bearing on portfolio risk, which aggregates probability and impact across components. It is tempting because office environment factors can appear in workplace-satisfaction or facilities surveys, where such details would legitimately be recorded.

Delegate the alignment assessment to the CRM project manager.

Why it fails: Delegating the alignment assessment to the project manager is inappropriate because strategic alignment is a portfolio-level responsibility. The project manager focuses on tactical execution, while the portfolio manager ensures the component fits the broader strategy. Delegation could lead to a narrow view that misses portfolio-wide implications. The portfolio manager must retain ownership of strategic alignment assessments.

Reject the CRM upgrade because it does not directly support 5G expansion.

Why it fails: Rejecting solely because it does not support one goal is short-sighted. The CRM upgrade may strongly support customer satisfaction and operational efficiency, which are also strategic goals. A portfolio manager should evaluate the component's contribution to the overall strategy, not just one aspect. This approach avoids missing opportunities that enhance multiple strategic objectives.

Approve the CRM upgrade immediately because it supports customer satisfaction.

Why it fails: Immediate approval without thorough evaluation ignores other strategic goals and potential trade-offs. The upgrade might not address operational efficiency or could conflict with 5G expansion priorities. The portfolio manager must assess alignment across all relevant goals and consider portfolio balance before approval. This action ensures that resources are allocated to components that maximize overall strategic value.

The office cleaning staff.

Why it fails: Cleaning staff hold no portfolio decision rights, funding authority or governance accountability, so they cannot participate in committee decisions. The committee requires executives and portfolio managers who own strategy, investment and benefit realisation. Cleaning staff would be relevant only to facility-related operational matters, not portfolio governance.

The entire company's sales force.

Why it fails: The whole sales force lacks the decision rights, funding authority and strategic oversight the committee exercises; including everyone destroys quorum and confidentiality. Governance requires a small group of executives and portfolio managers accountable for investment selection and benefits. The sales force would be relevant only as stakeholders consulted during demand intake.

The local newspaper reporter.

Why it fails: A newspaper reporter has no portfolio accountability, decision rights or investment authority, and external media presence would breach confidentiality of strategic and financial data. Governance committees comprise executives and portfolio managers who own strategy and benefits. A reporter would be appropriate only for public-relations announcements, not governance decisions.

Employee names.

Why it fails: Individual employee names are resource-assignment detail, not a roadmap input; the roadmap needs aggregated capacity and skill availability, not named personnel. It is tempting because staffing feels central to delivery planning, yet names belong in resource schedules after components are prioritised, not in the strategic roadmap itself.

The local cafeteria menu.

Why it fails: A cafeteria menu holds no portfolio data, so it cannot inform roadmap sequencing or investment decisions. It is tempting because stakeholder refreshments appear in some programme communications, yet menus belong to facilities planning, not to the strategic inputs — strategic objectives, resource capacity and prioritised component list — that a roadmap is built from.

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.

A detailed list of all project-level tasks

Why it fails: A detailed list of project-level tasks is not part of a portfolio risk management plan; it belongs in project schedules. The portfolio plan focuses on strategic risk management across the portfolio, not on operational task details. Including such lists would overwhelm the plan and detract from its purpose of managing aggregate risk.

The names of all project team members

Why it fails: Listing all project team members is not relevant to a portfolio risk management plan. Team composition is managed at the project level. The portfolio plan should focus on risk-related roles and responsibilities, such as the risk owner or risk review board, rather than enumerating every individual team member.

A copy of the organization's marketing strategy

Why it fails: The marketing strategy is not an essential element of a portfolio risk management plan. While alignment with organizational strategy is important, the plan itself should contain risk-specific components like thresholds, review processes, and roles. Including unrelated strategic documents would dilute the plan's focus and utility.

Immediately escalate the integration requirements to the Portfolio Governance Board for approval before any discussions.

Why it fails: Escalating before engaging the component teams may bypass necessary groundwork and delay progress. The governance board should be involved for strategic decisions, but the integration details are best handled by the component teams. Early escalation without stakeholder input can lead to resistance and lack of ownership.

Create a detailed RACI chart for the new component and distribute it to all stakeholders without consultation.

Why it fails: Creating a RACI chart without consultation may result in incorrect assumptions about roles and responsibilities. Stakeholders need to be involved in defining their own roles to ensure buy-in and accuracy. Unilateral distribution can cause confusion and resistance, undermining integration efforts.

Assign a liaison from the portfolio management office to each component team to relay messages between them.

Why it fails: While a liaison can facilitate communication, relying solely on intermediaries may slow down information flow and create bottlenecks. It can also lead to miscommunication if messages are not accurately conveyed. Direct engagement between component teams is preferable for building relationships and resolving issues quickly. This action alone does not ensure effective integration.

Daily office cleaning tasks.

Why it fails: Daily office cleaning is recurring operational work sustaining the status quo, so it cannot be a strategic component, which must be a programme, project or sub-portfolio delivering strategic benefits. It tempts because cleaning supports the workplace, but that is business-as-usual operations, not portfolio management.

Monthly team birthday parties.

Why it fails: Birthday parties are operational, recurring team-engagement activities with no strategic objective, so they belong in business operations rather than the portfolio's strategic components. The option tempts because staff morale genuinely supports delivery, but that belongs under resource or team management, not portfolio strategy.

Replacing a lightbulb in the hallway.

Why it fails: Replacing a lightbulb is routine facilities maintenance, not a strategic component, because it delivers no change aligned to organisational objectives. It tempts as a tangible task, yet such operational upkeep sits in business-as-usual; strategic components are programmes, projects or sub-portfolios delivering intended benefits.

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.

Office lunch menu.

Why it fails: An office lunch menu has no bearing on portfolio components, investment decisions or benefit realisation. It would be the correct document for facilities catering arrangements, but portfolio governance relies on the portfolio register, strategic roadmap and performance reports.

Personal diary of the portfolio manager.

Why it fails: A personal diary captures one manager's private notes and is neither authoritative nor shared, so it cannot evidence portfolio decisions or benefits. It would be the right artefact for individual time management, whereas governance requires the portfolio register, charter and performance reports.

Employee vacation calendar.

Why it fails: A vacation calendar tracks staff absence, giving no view of portfolio components, investment alignment or benefit delivery. It would be relevant to resource-capacity planning within a programme, but portfolio governance depends on the portfolio register, roadmap and performance reports.

Average project schedule variance, expressed as a percentage of baseline duration.

Why it fails: Schedule variance is a project-level metric that measures time performance, not portfolio strategic value. While it can be aggregated, it does not reflect benefits delivery or strategic alignment. Portfolio performance management emphasizes outcomes over outputs, so this metric alone is insufficient for the governance board's strategic view.

Resource utilization rate, calculated as the percentage of available staff hours billed to portfolio components.

Why it fails: Resource utilization is an efficiency metric that focuses on operational capacity, not strategic value delivery. High utilization does not necessarily mean the portfolio is achieving its objectives; it could indicate overwork or misallocation. Portfolio performance management prioritizes benefits and strategic alignment over resource efficiency.

Number of change requests approved per project, tracked monthly.

Why it fails: This metric is operational and project-focused, not portfolio-level strategic performance. It does not indicate whether the portfolio is delivering value or aligned with strategy. While change request volume can signal scope instability, it is not a direct measure of portfolio strategic performance.

Asking the IT help desk for everyone's password.

Why it fails: Requesting passwords from the IT help desk is a security and privacy violation that yields credentials, not stakeholder information. It is tempting because the help desk holds user records, but legitimate identification uses organisational charts, sponsor input and role-based analysis instead.

Listing people randomly from the corporate directory.

Why it fails: Random selection from the corporate directory produces an arbitrary sample with no link to the portfolio's objectives, so it cannot reliably surface affected parties. It is tempting as a quick way to broaden coverage, but it is legitimate only for sampling populations, not identifying stakeholders.

Ignoring stakeholders outside the finance department.

Why it fails: Excluding stakeholders outside finance omits parties affected by or able to influence the portfolio, such as operations, compliance and end users. It is tempting when finance owns funding, but scope-based exclusion is legitimate only after analysis shows a group has no stake.

Ordering stationery for the PMO office.

Why it fails: Ordering stationery is an administrative procurement task, not portfolio governance. The Portfolio Governance Plan defines decision rights, escalation paths, stage-gate criteria and audit requirements, so the portfolio manager owns its creation, maintenance and enforcement. Stationery purchasing would sit with PMO administration, not the governance responsibilities tested here.

Creating all the individual project code.

Why it fails: Writing project code is a delivery-team activity, not portfolio governance. The portfolio manager defines the governance framework, decision rights and stage-gate criteria within the Portfolio Governance Plan, then ensures component projects comply. Coding individual projects would fall to development staff, and would breach the portfolio manager's oversight role.

The component has a duration of less than six months.

Why it fails: Duration alone is not a reliable criterion for portfolio governance inclusion. Short-duration components can still be strategically critical or high-risk, while long-duration components might be operational. Governance should focus on strategic impact and risk rather than timeline. Using duration as a criterion could exclude important initiatives or include trivial ones, leading to misaligned oversight.

The component is executed by an external vendor under a fixed-price contract.

Why it fails: Contract type or execution method does not determine portfolio governance inclusion. While external vendors introduce risk, governance scope should be based on the component's strategic contribution and risk profile, not solely on contractual arrangements. A fixed-price contract might reduce financial risk but does not negate the need for strategic oversight if the component is critical to portfolio objectives.

The component is managed by a project manager who reports directly to the PMO.

Why it fails: Reporting structure alone does not determine portfolio governance inclusion. While PMO involvement can be relevant, governance scope is typically based on strategic, financial, or risk factors rather than reporting lines. A component might report to the PMO but still be outside portfolio governance if it is operational or low-risk. PfMP emphasizes that governance scope should be driven by value and risk, not organizational hierarchy.

Delegate the realignment decision to each component's project manager to speed up the process.

Why it fails: Component managers lack the portfolio-wide view of strategy, dependencies, capacity, and benefits trade-offs needed for realignment. Delegating realignment to them would produce fragmented, locally optimized decisions that may conflict with revised strategic priorities and undermine portfolio-level governance authority.

Wait until the next fiscal year to realign the portfolio so that budgeting cycles remain undisturbed.

Why it fails: Delaying realignment until the next fiscal year leaves resources committed to components that may no longer support revised strategy, wasting investment and missing the opportunity created by the disruption. Portfolio alignment must respond to significant strategic shifts as they occur, not wait for administrative budgeting cycles.

Immediately suspend all components that were approved before the market disruption.

Why it fails: Suspending all pre-disruption components indiscriminately would halt work that may still strongly support revised objectives and could damage benefits realization, contracts, and stakeholder confidence. Realignment requires evidence-based assessment and governance decisions, not blanket suspension based only on approval timing.

Mandate that all existing components incorporate an emerging market component into their scope, regardless of relevance.

Why it fails: Forcing every component to add emerging market scope is a blanket approach that can dilute focus and waste resources. Strategic alignment requires selective fit, not universal inclusion. Components that have no logical connection to emerging markets would become less efficient and could jeopardize their original objectives. Alignment is about prioritizing the right work, not adding irrelevant work to everything.

Increase the portfolio budget by 50% to accommodate both existing components and new emerging market initiatives without trade-offs.

Why it fails: Increasing the budget without trade-offs assumes unlimited resources, which is unrealistic and undermines the portfolio manager's role in balancing investments. Strategic alignment often requires reallocating from lower-value to higher-value components. Simply adding funds can perpetuate misalignment by keeping non-strategic components alive. It also bypasses the need for prioritization, which is a core portfolio management responsibility.

Delegate all realignment decisions to the individual component managers, as they best understand their projects.

Why it fails: Delegating realignment entirely to component managers fragments strategic decision-making. Component managers naturally focus on their own projects and may lack the portfolio-wide view needed to balance investments against the emerging market strategy. The portfolio manager must retain responsibility for alignment, using component managers as input sources but not as sole decision-makers. This ensures enterprise-level optimization.

Delegate all alignment responsibilities to the project management office (PMO) to centralize control.

Why it fails: Delegating all alignment responsibilities to the PMO can distance strategic decision-making from executive leadership and component managers. While the PMO can support alignment processes, ultimate accountability for strategic alignment rests with the portfolio manager and governance board. Centralizing control may reduce agility and fail to engage key stakeholders needed to drive the digital transformation.

Create a portfolio dashboard that tracks only financial metrics such as ROI and NPV for each component.

Why it fails: Tracking only financial metrics ignores strategic alignment indicators like contribution to digital capabilities, customer experience improvements, or innovation. While financial health is important, a dashboard focused solely on ROI and NPV may lead to prioritizing financially attractive but strategically misaligned components. Alignment requires metrics that directly measure progress toward the digital transformation objectives.

Focus on completing all in-flight components before initiating any new digital transformation initiatives.

Why it fails: Completing all in-flight components before starting new digital initiatives can delay the transformation and allow the portfolio to become misaligned with urgent strategic priorities. The portfolio manager should re-evaluate in-flight components against the new strategy and may terminate or pause those that no longer fit, freeing resources for digital transformation. A rigid completion-first approach ignores strategic agility.

Replace the portfolio stakeholder register with a component-level communications matrix for each affected product line.

Why it fails: Component-level communications matrices support execution but do not replace the portfolio stakeholder register, which provides the portfolio-wide view of stakeholder interests, influence, and engagement levels. Substituting one for the other fragments engagement and loses cross-component perspective. The register should be updated, not replaced, so portfolio-level engagement decisions remain grounded in a complete stakeholder picture.

Limit engagement to the executive sponsors of the emerging-market initiatives, since they are the primary beneficiaries of the rebalancing.

Why it fails: Focusing only on beneficiaries ignores stakeholders tied to the mature product lines, whose cooperation is essential for winding down or transitioning those components. Portfolio stakeholder engagement must consider all affected parties, including those who may lose investment. Excluding them risks resistance, knowledge loss, and transition delays that can jeopardize the rebalancing's expected value.

Withhold details of the rebalancing until the Portfolio Governance Board formally approves the final investment allocations.

Why it fails: Withholding information until final approval excludes stakeholders from shaping transition plans and can amplify resistance once the change is announced. While sensitive financial details may be restricted, the strategic direction and implications for affected groups should be communicated early enough for stakeholders to prepare. Late disclosure undermines the trust and ownership that effective portfolio engagement depends on.

The daily technical code commits of developers.

Why it fails: Daily code commits are operational engineering activity, outside portfolio governance scope. The Governance Plan shapes portfolio-level components like investment selection, prioritisation criteria, and benefits tracking, not developers' day-to-day technical work. It is tempting because projects deliver code, but governance operates at portfolio level, not within team-level development practise.

The individual vacation schedule of project team members.

Why it fails: Vacation schedules are an HR and resource-management concern, not a portfolio governance artefact. The Governance Plan influences portfolio components such as strategic alignment, investment decisions, and benefits realisation, not individual leave bookings. It is tempting because team availability affects delivery, but that is handled through resource management, not governance.

The cafeteria menu at the office.

Why it fails: A cafeteria menu is a facilities matter with no portfolio governance linkage. The Governance Plan influences portfolio components such as strategic alignment, investment decisions, and benefits realisation, not office amenities. It is tempting because governance touches organisational life broadly, but its scope is portfolio decision-making, not workplace catering.