Perspective: situating the initiative in its organisational context
What this domain is really testing
Perspective is the 'why and where' of an initiative. It checks whether you can place a project, programme or portfolio inside its wider setting and let that setting shape your decisions. The competence elements are: strategy (how the initiative delivers organisational goals and benefits), governance, structures and processes (who decides what, in which forum), compliance, standards and regulations, power and interest (informal influence, coalitions, agendas) and culture and values (norms, taboos, risk appetite).
Concepts to name precisely
Distinguish governance from management: governance sets direction, boundaries and decision rights; management executes inside them. A business case is a living document linking strategy to spend, and benefits are realised after handover - output, outcome and benefit are not synonyms. Separate formal authority from informal power, and be ready to explain why a resistant functional head or a 'shadow' sponsor matters even when the org chart ignores them.
Traps
The commonest trap smuggles a Practice answer into a Perspective question: organisational politics and power mapping sit here, not in the stakeholder-engagement element of Practice. Second, compliance is treated as paperwork rather than a design constraint. Third, culture is dismissed as 'soft', although it decides whether an escalation reads as normal or as betrayal. Fourth, strategy is mistaken for a one-off document instead of a source of trade-offs when scope and budget collide.
Rule of thumb
Ask: can the delivery team change it? If no, it is context - Perspective: analyse, align, navigate. If yes, it is Practice: plan, control, adjust.
Worked example
A regulator publishes new reporting rules mid-project. Perspective thinking asks first whether the rules apply to this deliverable, who inside the organisation owns compliance, and what the sponsor's risk appetite is - before anyone re-plans the schedule.