Perspective: Context, Governance, Strategy, Compliance, Power and Culture
What Perspective covers
The Perspective area asks whether a project manager can read and shape the environment in which a project sits. Key concepts: the project context (internal and external factors, PESTLE-style scanning), governance (decision rights, stage gates, escalation paths, separation of sponsor and manager roles), strategy alignment (how the project contributes to organisational objectives and benefits), compliance (legal, regulatory, standards, ethics), power and interest (stakeholder mapping, influence without authority), and culture (organisational, national, and team norms).
Traps in questions
Questions often present a situation where the manager has authority only over delivery, yet the problem is a governance or strategy problem. The tempting answer is to "fix it in the team"; the correct answer is usually to escalate, engage the sponsor, or realign with strategy. Watch for:
- Confusing sponsor accountability with project manager responsibility.
- Treating compliance as a checklist rather than a design constraint.
- Ignoring informal power: a high-interest, low-authority stakeholder can still block acceptance.
- Assuming one culture fits all: high-context versus low-context communication changes what "clear" means.
Worked example
A regulator issues a new data rule mid-project. A candidate may pick "update the risk register and continue." The stronger answer: assess compliance impact, inform the sponsor and governance board, re-baseline scope or schedule through the change process, and document the decision. Rule of thumb: when the environment changes, the governance route changes with it - never absorb a compliance shift silently.
Rule of thumb
Before choosing any action, ask: Whose decision is this? If it is not the manager's decision right, the answer involves the governance path.