Hard Difficulty Questions

The total budget allocated to the project office.

Why wrong: Budget is a constraint, not a risk factor.

The average experience level of the project managers.

Why wrong: This affects execution but not the inherent risk of the portfolio.

The number of projects currently active.

Why wrong: Quantity does not equal risk exposure.

Force the under-allocated department to take on the other's work without training.

Why wrong: This would lead to project failure.

Let the departments resolve it themselves.

Why wrong: Portfolio-level intervention is needed to balance capacity.

Cut the projects in the over-allocated department.

Why wrong: This may cut high-value projects; resource leveling is preferred first.

Sanction the project managers for non-compliance.

Why wrong: Punitive action is rarely the first step in effective governance.

Manually update all reports to comply with the standard.

Why wrong: This does not address the systemic process failure.

Ignore the finding if the projects are still achieving their KPIs.

Why wrong: Governance requires adherence to processes regardless of short-term outcomes.

An external audit finding.

Why wrong: Audit findings are different from realized risks.

A project failure.

Why wrong: Not necessarily a failure; it is an issue requiring management.

A new risk.

Why wrong: It was already a risk; now it is an issue.

Double the project budget.

Why wrong: Throwing money at a problem without understanding the cause is ineffective.

Abandon the strategy.

Why wrong: Abandonment is premature without proper analysis.

Fire the project managers.

Why wrong: Personnel changes should be based on data, not immediate reaction.

By authorizing the next year's budget.

Why wrong: Budgeting is a planning function.

By enforcing project management compliance with technical standards.

Why wrong: Audits cover the entire portfolio, not just technical standards.

By selecting new projects for the portfolio.

Why wrong: Selection is part of the authorization process.

To prevent project managers from speaking to the executive committee.

Why wrong: Transparency and communication are key to effective governance.

To reduce the number of employees required in the PMO.

Why wrong: This is not the primary purpose of tiered governance.

To comply with outdated regulatory requirements.

Why wrong: Governance models should follow current best practices.

Delegate the risk to the strongest program manager.

Why wrong: The portfolio manager retains responsibility for risks affecting multiple programs.

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

Why wrong: Proactive management is required for all identified risks.

Tell each program manager to manage the risk independently.

Why wrong: This leads to inconsistent responses and inefficiencies.

Bypass the governance steps to speed up delivery.

Why wrong: Bypassing governance creates risk.

Add more staff to the governance committee to speed up decisions.

Why wrong: Larger committees usually slow down decisions.

Accept the delays as part of the price of governance.

Why wrong: Effective governance should not unnecessarily impede progress.

Flip a coin to be fair.

Why wrong: Governance should be based on data, not chance.

Give the resource to the project with the longest timeline.

Why wrong: Timeline is not a strategic prioritization factor.

Ask the resource manager to decide.

Why wrong: Resource managers follow portfolio-level prioritization decisions.

Ignore the non-compliance as the project is near completion.

Why wrong: Compliance is non-negotiable.

Issue a formal warning to the project team.

Why wrong: A warning alone does not remediate the risk.

Report the project team to the HR department.

Why wrong: This is a governance process issue, not an HR issue.

The complete internal chat history of the team.

Why wrong: This violates privacy and is not a governance report.

The personal opinions of the auditor about the staff.

Why wrong: Audits must be objective and data-driven.

A project manager taking a one-day vacation.

Why wrong: Minor project events do not trigger roadmap reviews.

The lunch menu in the cafeteria changing.

Why wrong: Irrelevant.

Project team hiring.

Why wrong: This is resource management.

Office cleaning.

Why wrong: Not related.

Annual holiday planning.

Why wrong: Not related.

Create a new Portfolio Management Plan.

Why wrong: The plan should be updated if necessary, but action must be approved first.

Inform the project managers that they are failing.

Why wrong: This is unproductive and does not solve the portfolio-level problem.

Immediately cut the budget of all low-performing projects.

Why wrong: This is an overreaction without board approval.

Ask the technical team to change the vision.

Why wrong: The portfolio manager follows the strategy, they don't change it based on technical success.

Keep the project because it is technically successful.

Why wrong: Technical success does not equal portfolio value.

Continue the project but reduce its budget.

Why wrong: This is a compromise that does not fix the misalignment.

The ones that are closest to completion.

Why wrong: Completion status is not the primary factor in strategic prioritization.

The ones managed by the most experienced managers.

Why wrong: Manager seniority does not dictate project priority.

The ones that have the highest number of team members.

Why wrong: Size is not a proxy for strategic value.

Request a revision of the organization's corporate strategy.

Why wrong: Portfolio management must align with the existing strategy, not dictate it.

Increase the frequency of status reporting from project managers.

Why wrong: More reporting does not solve the fundamental misalignment of objectives.

Change the KPI definitions to show better alignment.

Why wrong: Changing metrics is unethical and masks the problem.

Ignore the delay until the project completes.

Why wrong: This is a failure of responsibility.

Speed up the project work by reducing quality.

Why wrong: Reducing quality is not an acceptable solution.

Change the expected benefit date in the system.

Why wrong: Changing dates without justification is misleading.

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.