WIKI SLATEPrecision to Vision
← LibraryTailoring — Visual Knowledge MapProject Management · Managing Complexity in Projects← PrevNext →
Poster 03 · Tailoring
PMBOK® Guide — 7th Edition · Section 3 structure

Visual Knowledge Map

The whole of Section 3 on one page — four questions (why, what, how, keep improving), applied across the performance domains, with diagnostics for when to adjust.

TAILORINGSECTION 3 · PMBOK® GUIDE 7TH ED.
3.2Why Tailor
  • Suit org, environment, needs
  • Balance competing demands
  • No one-size-fits-all
  • Direct & indirect benefits
3.3What to Tailor
  • Life cycle & dev approach
  • Processes
  • Engagement
  • Tools
  • Methods & artifacts
3.4The Process
  • Select initial approach
  • Tailor for organisation
  • Tailor for project
  • Ongoing improvement
3.5Performance Domains
  • Stakeholders · Team
  • Dev approach · Planning
  • Project work · Delivery
  • Uncertainty · Measurement
3.6Diagnostics
  • Retrospectives
  • Lessons learned
  • Warning signals
  • Situation → fix table

Read it as

  • Top-down: understand context → choose → adapt → improve.
  • Bounded: governance frames every branch.
  • Cyclical: the process loops, never ends.

Driven by

  • The 12 PM principles
  • Organisational values
  • Culture & appetite for risk

Feeds into (§4)

  • Models — thinking strategies
  • Methods — means to outcomes
  • Artifacts — templates & docs