ambiguity

A condition where meaning or causes are not clear, making it hard to determine why events occur or which of several plausible choices to take.

Key Points

  • PMI definition: A state of being unclear, having difficulty in identifying the cause of events, or having multiple options from which to choose.
  • Ambiguity is about multiple interpretations or hard-to-trace causes; it is different from simple uncertainty about probabilities.
  • It appears often in novel, complex, or rapidly changing work, especially early in discovery and design.
  • Manage it by sensemaking: collaborate with stakeholders, run time-boxed research spikes and prototypes, and progressively refine requirements and acceptance criteria.

Example

A product team is told to "improve customer engagement" but receives no metric or specific outcome. Several paths exist (personalized content, chatbot, notifications). The project manager schedules stakeholder workshops to define measurable outcomes and leads short spikes to test the riskiest assumptions before selecting a direction.

PMP Example Question

A team receives vague requirements and sees multiple viable solutions. What should the project manager do first?

  1. Freeze scope until the sponsor chooses one option.
  2. Start building the most popular option to maintain momentum.
  3. Facilitate stakeholder sessions and run short experiments/prototypes to clarify needs and reduce uncertainty.
  4. Update the risk register and proceed without changes.

Correct Answer: C — Facilitate experiments and stakeholder clarification

Explanation: When facing ambiguity, the best first step is sensemaking: engage stakeholders and use spikes/prototypes to learn and refine requirements before committing to a solution.

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 Agile career!

HK School of Management and Technology helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More