The Risk Attitude

It represents the level of risk the business stakeholders are willing to accept and shapes their choices about if and when to take actions to reduce potential negative impacts.

Key Points

  • Defines how much uncertainty or potential loss stakeholders are comfortable accepting.
  • Directly influences the selection, timing, and intensity of risk response actions.
  • Can differ across stakeholders, so it should be elicited, aligned, and documented.
  • Driven by factors such as strategy, regulations, culture, benefits sought, and prior experience.

Example

In an agile program, the business sponsor is risk-averse about performance issues. When a performance risk is identified in sprint planning, they push to create a technical spike and add performance tests early, accepting reduced scope this sprint to lower the chance of production slowdowns.

PMP Example Question

Which statement best describes the business stakeholders' risk attitude and its impact on project decisions?

  1. It measures the probability of risk events and dictates the risk register format.
  2. It indicates how much risk stakeholders are willing to accept and informs when to implement mitigation actions.
  3. It identifies all project threats and opportunities using qualitative methods only.
  4. It requires the project manager to avoid all risks by adding contingency reserves.

Correct Answer: B — Stakeholders' willingness to accept risk guides mitigation timing and selection

Explanation: Risk attitude reflects acceptable risk levels and drives choices about if and when to act to reduce potential negative impacts; it does not mandate avoiding all risks or define register formats.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More