Skip to main content
Project Intelligence

Risk manager

Who this is for​

This block is for portfolio managers: high-level oversight across projects and early warning on risks — before a slip becomes a schedule or budget failure.

On a single project, PMs use the same skills; at portfolio level the value is a shared signal method and comparable registers.

The Risk manager is the proactive risk-management skill set: risk register, probability-impact assessment, response measures, and scope-drift control.

Core competencies​

  • Proactive risk detection: documents, contracts, and tickets — dependencies, resources, failure points.
  • Risk register: structured cards (cause → effect → category → trigger → owner → source) and probability-impact assessment.
  • Response measures: three levels — prevention / mitigation / contingency — with triggers and owners; every change only after human confirmation (HITL).
  • Expert layer: the accumulated lessons-learnt base used as checklists — new risks checked against past experience and an expert view on how likely a risk is.
  • Early warning on scope: creep and material changes vs approved scope (/scope-check) — before “just a little more” erodes portfolio budget and dates.

How to use​

There is no separate role command: ask about risks, response measures, or scope drift — the agent applies /risks, /risk-mitigate, or /scope-check.

Example prompts:

  • “What risks does this contract generate? Assess them on the probability-impact matrix.”
  • “Build the response measures and triggers for the top risks.”
  • “Log a scope-creep risk: the customer wants an integration that is not in approved scope.”

Skills used​

  • Risk register (/risks): identify, assess, and review delivery risks.
  • Risk actions (/risk-mitigate): mitigation and response plan.
  • Scope check (/scope-check): assumptions baseline, signal classification, OOS/CR register — an early-warning source for the portfolio when scope starts to drift.

Mechanism​

  1. Identification — causes and effects from documents, contracts, and tickets.
  2. Assessment — probability-impact matrix + lessons-learnt checklists.
  3. Response measures — prevention / mitigation / contingency with triggers and owners (HITL).
  4. Alerting — early warning and concrete steps (including a formal CR via /scope-check notice).

That moves the portfolio from firefighting to deliberate uncertainty management.