โ† Back to Cheat Sheets

๐Ÿง  PMI Mindset Decision Tree

"What would PMI want me to do?" โ€” The framework for answering every scenario question
All Domains ยท Exam Strategy ยท Most Important Cheat Sheet
โญ

The Golden Rule

Always ask: "What would PMI want me to do?" โ€” Not what you'd do in real life. Not what's fastest. What does PMI's framework say is RIGHT?

๐ŸŒณ Scenario Question Decision Tree
flowchart TD
  START["๐Ÿ“‹ Read the scenario question"]
  START --> LAST["Read the LAST sentence first
It tells you what's being asked"] LAST --> TYPE{"What type of
situation is it?"} TYPE -->|"Ethical issue"| ETHICS["๐Ÿ›ก๏ธ Ethics First
Report it. Always.
Honesty > loyalty > convenience"] TYPE -->|"Change requested"| CHANGE["๐Ÿ“ Follow Change Control
1. Assess impact
2. Submit change request
3. CCB reviews
4. Update plans if approved"] TYPE -->|"Problem discovered"| PROBLEM["๐Ÿ” Assess Before Acting
1. Identify the problem
2. Gather information
3. Find root cause
4. Evaluate options
5. THEN take action"] TYPE -->|"Team conflict"| CONFLICT["๐Ÿค Facilitate, Don't Dictate
Collaborate/Problem Solve
is almost always the answer"] TYPE -->|"Stakeholder issue"| STAKE["๐Ÿ“ก Engage & Communicate
Understand their needs
Manage expectations
Build relationships"] TYPE -->|"Risk identified"| RISK["โš ๏ธ Be Proactive
Analyze the risk
Plan a response
Update the risk register"] TYPE -->|"Methodology question"| METHOD["๐Ÿ›ค๏ธ Tailor to Context
No one-size-fits-all
Consider project characteristics
Hybrid is often valid"] ETHICS --> VERIFY{"Does your answer
reflect servant leadership?"} CHANGE --> VERIFY PROBLEM --> VERIFY CONFLICT --> VERIFY STAKE --> VERIFY RISK --> VERIFY METHOD --> VERIFY VERIFY -->|"Yes"| GOOD["โœ… Likely correct!
Facilitate > Direct
Empower > Control
Assess > React"] VERIFY -->|"No"| RETHINK["๐Ÿ”„ Reconsider
PMI prefers the answer that
serves the team and follows process"] style START fill:#dcfce7,stroke:#16a34a,color:#14532d style TYPE fill:#fef3c7,stroke:#b45309,color:#78350f style ETHICS fill:#ffe4e6,stroke:#e11d48,color:#881337 style CHANGE fill:#dbeafe,stroke:#2563eb,color:#1e3a5f style PROBLEM fill:#ede9fe,stroke:#7c3aed,color:#3b0764 style CONFLICT fill:#fef3c7,stroke:#b45309,color:#78350f style STAKE fill:#fce7f3,stroke:#c026d3,color:#701a75 style RISK fill:#fff7ed,stroke:#ea580c,color:#7c2d12 style METHOD fill:#ecfdf5,stroke:#0d9488,color:#134e4a style VERIFY fill:#f5f5f4,stroke:#78716c,color:#1c1917 style GOOD fill:#dcfce7,stroke:#16a34a,color:#14532d style RETHINK fill:#fef3c7,stroke:#b45309,color:#78350f
๐Ÿ“ Change Control Process (Memorize This Flow)
flowchart LR
  A["Change
identified"] --> B["Assess
impact"] B --> C["Submit
change request"] C --> D["CCB
reviews"] D -->|"Approved"| E["Update plans
& baselines"] D -->|"Rejected"| F["Document
decision"] D -->|"Deferred"| G["Log for
later review"] E --> H["Communicate
to stakeholders"] F --> H G --> H style A fill:#dbeafe,stroke:#2563eb style B fill:#ede9fe,stroke:#7c3aed style C fill:#fef3c7,stroke:#b45309 style D fill:#fce7f3,stroke:#c026d3 style E fill:#dcfce7,stroke:#16a34a style F fill:#ffe4e6,stroke:#e11d48 style G fill:#fff7ed,stroke:#ea580c style H fill:#dcfce7,stroke:#16a34a
๐Ÿ’ก Exam Tip

The answer is almost NEVER "make the change immediately." It's always "assess the impact" or "submit a change request." Even for small changes โ€” PMI says follow the process.

๐Ÿ“œ The 10 PMI Mindset Rules
Rule 1

๐Ÿคฒ Servant Leadership Is the Default

Tell the team what to doFacilitate a discussion
Make decisions for the teamEmpower the team to decide
Solve problems yourselfCoach the team to find solutions
Rule 2

๐Ÿ“‹ Always Follow the Process

Make the change immediatelySubmit a change request
Approve the change yourselfHave the CCB review it
Skip analysis for small changesAssess impact regardless
Rule 3

๐Ÿ” Assess Before Acting

Jump to a solutionAnalyze the situation first
Fix the symptomFind the root cause
Act on assumptionsGather data and facts
Rule 4

๐Ÿšซ Never Gold Plate

Add extra features "for free"Deliver only what's in scope
Exceed requirements to impressMeet requirements precisely
Assume the customer wants moreAsk the customer what they need
Rule 5

๐Ÿ“ข Communicate Proactively

Wait for people to askShare information proactively
Hide bad newsReport transparently
Assume people knowConfirm understanding
Rule 6

๐Ÿ“ก Engage Stakeholders Early & Often

Involve stakeholders at the endEngage from the start
Ignore resistant stakeholdersUnderstand their concerns
Communicate only when requiredMaintain continuous engagement
Rule 7

๐Ÿ›ก๏ธ Ethics First, Always

Cover up a mistakeReport it honestly
Accept a gift from a vendorDecline and report it
Falsify reports to look goodReport actual status
Rule 8

๐Ÿ“œ The Project Charter Is Sacred

Start work without a charterGet the charter signed first
Accept verbal authorizationRequire formal documentation
Let the sponsor bypass the PMReference the charter authority
Rule 9

โš ๏ธ Risk Management Is Proactive

Deal with risks when they happenIdentify and plan responses early
Ignore low-probability risksDocument all identified risks
Only think about threatsAlso identify opportunities
Rule 10

๐Ÿ“ Document Everything

Rely on verbal agreementsDocument decisions formally
Skip lessons learnedCapture lessons throughout
Trust memory for decisionsUpdate project artifacts
๐Ÿชค Common Exam Traps

๐Ÿชค The "Real World" Trap

You know what you'd do in real life โ€” but the exam tests what PMI says to do. Real-world shortcuts are wrong answers.

โ†’ Always think "What would PMI want?"

๐Ÿชค The "Escalate Immediately" Trap

Escalating to the sponsor or management is tempting but usually premature. PMI wants you to handle it first.

โ†’ Assess and attempt resolution before escalating

๐Ÿชค The "Take Action Now" Trap

Action-oriented answers feel right but skip the assessment step. PMI always wants analysis first.

โ†’ Analyze โ†’ Plan โ†’ Act (in that order)

๐Ÿชค The "Authority" Trap

Answers where the PM makes unilateral decisions sound decisive but violate servant leadership.

โ†’ Facilitate team decisions, don't dictate

๐Ÿชค The "Ignore and Continue" Trap

Ignoring a problem, risk, or stakeholder concern is never the right answer on the PMP exam.

โ†’ Address every issue through the proper process

๐Ÿชค The "Overtime" Trap

Asking the team to work overtime to absorb a change sounds practical but violates team well-being principles.

โ†’ Follow change control, adjust the plan properly
โšก Exam Day Quick Reference
flowchart LR
  subgraph timing ["โฑ๏ธ TIMING"]
    T1["180 questions
230 minutes"] T2["~76 sec
per question"] T3["Flag & move on
if > 2 min"] end subgraph breaks ["โ˜• BREAKS"] B1["Break 1
After Q60"] B2["Break 2
After Q120"] B3["Take BOTH
breaks!"] end subgraph strategy ["๐ŸŽฏ STRATEGY"] S1["Read last
sentence first"] S2["Eliminate 2
wrong answers"] S3["Choose between
remaining 2"] end style timing fill:#dbeafe,stroke:#2563eb style breaks fill:#dcfce7,stroke:#16a34a style strategy fill:#fef3c7,stroke:#b45309
๐Ÿง  The 3-Second Filter

For every answer choice, ask these three questions in order:

1. Is it ethical? If not, eliminate it.

2. Does it follow the process? If not, eliminate it.

3. Does it serve the team/stakeholders? If yes, it's probably correct.