How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

Critical thinking

A disciplined way to question information, test assumptions, and draw reasoned conclusions. It helps leaders and teams choose options based on evidence and logic, not bias. Use it to resolve issues, justify decisions, and guide team actions.

Key Points

  • Focuses on clarifying the problem, separating facts from opinions, and probing for evidence.
  • Uses structured questioning to surface assumptions, risks, and trade-offs.
  • Facilitated by the leader through open dialogue, psychological safety, and time-boxed analysis.
  • Results are documented so the team can explain why a decision was made and revisit it if needed.

Purpose of Analysis

Apply rigorous thinking to choose the best course of action under constraints, uncertainty, and diverse viewpoints. It improves decision quality, reduces cognitive bias, and builds team alignment.

  • Resolve conflicts by comparing options against explicit criteria.
  • Prioritize work by linking choices to objectives, value, and risk.
  • Detect hidden dependencies and unintended consequences before committing.

Method Steps

  • Frame the issue: State the problem, desired outcome, constraints, and decision deadline.
  • Gather relevant evidence: Pull data, policies, prior lessons, and stakeholder perspectives.
  • Surface assumptions: List what is believed to be true and validate the riskiest items.
  • Generate options: Create multiple feasible alternatives, including doing nothing.
  • Define criteria: Agree on measurable criteria such as value, cost, risk, time, and compliance.
  • Evaluate trade-offs: Compare options against criteria; consider second-order effects and risks.
  • Check biases: Look for anchoring, confirmation bias, groupthink, and sunk-cost fallacy.
  • Decide and document: Select the option with rationale, assumptions, and expected outcomes.
  • Communicate and follow up: Share the reasoning, assign actions, monitor results, and adjust.

Inputs Needed

  • Problem statement, objectives, and decision deadline.
  • Constraints and policies, including budget, schedule, quality, and compliance rules.
  • Performance data, metrics, and relevant benchmarks or experiments.
  • Stakeholder inputs, team expertise, and customer feedback.
  • Risk register, issue log, assumptions log, and lessons learned.
  • Requirements, acceptance criteria, and definition of done or success criteria.

Outputs Produced

  • Decision log entries with rationale, criteria used, and selected option.
  • Action items, owners, and time-bound follow-ups.
  • Updated assumptions, risks, and issues based on the analysis.
  • Change requests or backlog adjustments where needed.
  • Communication updates to align the team and stakeholders.
  • Facilitation notes and lessons captured for future decisions.

Interpretation Tips

  • When time is tight, time-box analysis and use simple tools like pros and cons, 5 Whys, or decision matrices.
  • Invite diverse viewpoints, then converge using agreed criteria to avoid endless debate.
  • Ask for evidence and ranges rather than absolutes; prefer repeatable data over opinions.
  • Document assumptions and plan a quick validation if uncertainty is high.
  • Escalate only when criteria conflict with organizational policy or risks exceed authority limits.

Example

A team must choose between building a custom API or buying a connector. The lead gathers cost and cycle-time data, lists assumptions about maintenance and security, and defines criteria: time-to-value, total cost of ownership, risk, and supportability. A quick spike reduces uncertainty, revealing higher integration risk for custom work. The team selects the connector, records the rationale and assumptions, and creates a follow-up task to monitor vendor performance.

Pitfalls

  • Analysis paralysis from unclear decision criteria or no time-box.
  • Confirmation bias or anchoring on the first idea or senior opinion.
  • Groupthink due to lack of psychological safety or missing dissenting voices.
  • Ignoring second-order effects, dependencies, or downstream risks.
  • Poor documentation that makes decisions hard to defend or revisit.

PMP Example Question

Two senior engineers disagree on a design approach, and stakeholders want a quick decision. To apply critical thinking, what should the project manager do first?

  1. Ask the team to vote and go with the majority.
  2. Define evaluation criteria and surface key assumptions before comparing options with data.
  3. Escalate the disagreement to the sponsor for direction.
  4. Select the lowest-cost option to meet budget constraints.

Correct Answer: B — Define evaluation criteria and surface key assumptions before comparing options with data.

Explanation: Critical thinking starts by clarifying criteria and assumptions, then using evidence to evaluate options. Voting or escalating skips analysis; choosing by cost alone ignores value and risk.

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.

Seven 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


Advance your Lean Six Sigma expertise!

HK School of Management helps you take Lean Six Sigma to the next level without the overwhelm. Master advanced statistical tools, Excel-based analysis, and real-world improvement techniques to solve complex problems with confidence. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More