Single Loop Learning

A way of solving problems that applies preset methods to correct errors inside the existing process, avoiding reconsideration of the underlying goals, rules, or assumptions even when feedback or experience suggests change.

Key Points

  • Focuses on fixing deviations using current policies, tools, and procedures.
  • Does not question or revise the underlying goals, assumptions, or rules.
  • Efficient for routine, well-understood issues where speed is important.
  • Can mask root causes and hinder improvement when conditions or requirements change.

Example

After several escaped defects, a Scrum team adds extra steps to its existing test checklist and reassigns tasks to hit the next sprint goal, but it does not examine whether the definition of done, coding standards, or architecture should be updated. They correct errors within the current approach rather than rethinking the approach itself.

PMP Example Question

During retrospectives, a team adds more checks to the current workflow to address recurring issues but avoids discussing whether the workflow or policies should change. What type of learning is occurring?

  1. Single Loop Learning
  2. Double Loop Learning
  3. Root cause analysis leading to process redesign
  4. Exploratory experimentation

Correct Answer: A — sticking to preset methods without questioning them

Explanation: The team is correcting errors within existing rules and methods, not reevaluating the rules or assumptions themselves, which is characteristic of single loop learning.

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


Launch your career!

HK School of Management and Technology offers training in project management, job-search strategies, and career growth. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More