{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigoymtck6d6tvhalowauevhvb4zraskewocyra5x6zy3wiezlrxwe",
    "uri": "at://did:plc:dwfz7or64ad5te6ds2oveka5/app.bsky.feed.post/3mnbnie354xf2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihlevsrkogee2bzchm6wuikr6ib2ztqj6lic5w7ashim2ys3f66s4"
    },
    "mimeType": "image/png",
    "size": 2209156
  },
  "description": "The PMI Visual Wall compresses into a clear, high‑signal layout that shows how strategy, governance, delivery, and value connect in real project environments. It turns a dense standard into a fast, visual reference engineers and project leaders can use for daily decisions and exam‑level mastery.",
  "path": "/pmi-visual-wall-kevos/",
  "publishedAt": "2026-06-02T03:25:12.000Z",
  "site": "https://kevos.com",
  "textContent": "PMI Visual Wall — Batch 1: Foundation & PMBOK 7\n\n# PMI VISUAL WALL · BATCH 1\n\nFoundation + PMBOK 7 core · Posters 1–6 🖨 Print / Save as PDF — A3 landscape Tip: in the print dialog set paper = A3, layout = Landscape, margins = None, \"Background graphics\" ON.\n\n## How to use this wall\n\nEach sheet is a self-contained **A3 landscape poster**. On screen, scroll to review; to print, use the button above (set paper to A3, landscape, no margins, background graphics on). Each poster keeps the same anatomy — **Purpose → Visual Map → Key Concepts → Relationships → Exam Concepts → Executive View → Industry Example → Memory Hooks → 60-second Daily Review** — and a **colour spine** coded by domain so the wall is navigable at a glance.\n\n**Colour code:** ■ Master/Strategy ■ Project / PMBOK ■ Program ■ Portfolio ■ Business Analysis / Value ■ Risk ■ EVM\n\nPOSTER 01\n\nSection 1 · The Whole System on One Page\n\n## The PMI Ecosystem — Master Map\n\nShows how **strategy cascades down** into delivery and how **value flows back up** ; which of the seven standards governs each layer; and **who holds decision authority**. This is the index to the whole wall.\n\n### Visual Map — Strategy → Delivery → Value\n\nRisk Standard\n\nA **single risk lens** spans every level — Enterprise → Portfolio → Program → Project. Same language, scaled.\n\nGovernance\n\nAuthority, funding & decisions move **down ▼**. Reporting, benefits & learning move **up ▲**.\n\nDrives all\n\nOrganisational Strategy\n\nVision, mission, objectives — the \"why\" everything must serve.\n\n▼ aligns / funds\n\nPortfolio Std\n\nPortfolio — do the RIGHT things\n\nThe org's programs, projects & operations chosen to meet strategy. Components need **not be related**.\n\n▼\n\nProgram Std\n\nProgram — coordinate for BENEFITS\n\nRelated projects + sub-programs + ops managed together to deliver benefits **unattainable separately**.\n\n▼\n\nPMBOK Guide\n\nProject — do things RIGHT\n\nA temporary effort creating a **unique output** (product, service, result).\n\n▼ produces\n\nOutputs\n(deliverables)▶ Outcomes\n(change)▶ Benefits\n(gains)▶ VALUE\n\n▼\n\nOperations → Customer\n\nRun & sustain the output so benefits keep flowing. Value is realised **here** , often after the project closes.\n\nOPM Standard\n\nThe **container** : aligns portfolio + program + project management to strategy via governance, methods & culture.\n\nBusiness Analysis\n\n**Cross-cutting.** Defines the **right needs & requirements** so the right thing gets built at every level.\n\nEVM Standard\n\nA **performance lens** integrating scope + schedule + cost to answer \"are we on track & what will it cost?\"\n\n__Portfolio __Program __Project __Value\n\n### Key Concepts\n\nPortfolio\n    Doing the **right** work — strategic selection & balance.\nProgram\n    Coordinated delivery of **benefits** across components.\nProject\n    Doing work **right** — a unique, temporary endeavour.\nOutput\n    The deliverable a project hands over.\nOutcome\n    The change/result the output enables.\nBenefit\n    The measurable gain to the organisation.\nValue\n    Worth to stakeholders — financial _or_ not.\nGovernance\n    Authority, decisions, oversight (the \"rules\").\nManagement\n    Day-to-day execution within those rules.\n\n### Relationships — How the layers connect\n\n  * **Money & mandate flow down;** benefits, status & lessons flow up.\n  * A **program** groups related projects to unlock benefits no single project could.\n  * A **portfolio** groups programs/projects/ops — related or not — to meet strategy.\n  * **OPM** is the system that keeps all three aligned to strategy.\n  * **BA** feeds every level the right requirements; **Risk** gives every level one risk language; **EVM** gives every level one performance language.\n\n\n\n### Exam Concepts\n\n  * Portfolio components are **not necessarily related** ; program components **are**.\n  * Output ≠ outcome ≠ benefit ≠ value — know the ladder.\n  * \"Tactical vs strategic\": project=tactical, portfolio=strategic.\n  * Governance **≠** management.\n\n\n\n### Executive View\n\n  * Allocate **capital** to the highest-value mix, not the loudest sponsor.\n  * **Kill, pause or continue** investments at gates.\n  * Steer by **value & benefits**, not just on-time/on-budget.\n  * Confirm strategy is actually being **executed**.\n\n\n\n### Industry Example — Defence shipbuilding\n\nDefence\n\n  * **Portfolio:** naval capability investments.\n  * **Program:** a frigate class program.\n  * **Projects:** hull, combat system, integration.\n  * **Benefit→Value:** in-service readiness → security.\n\n\n\n### Memory Hooks\n\n  * **\"Right things → right way → done right\"** = Portfolio → Program → Project.\n  * **Money goes DOWN ▼, Value comes UP ▲.**\n  * **P-P-P:** _Pick · Pace · Produce._\n\n\n\n60-sec Review Name the 5 layers, top to bottom Who governs each layer? Match each layer to its standard Output→Outcome→Benefit→Value Where do Risk, OPM & EVM sit?\n\nPMI Visual Wall · Poster 01 of the system · original instructional design · A3 landscape\n\nPOSTER 02\n\nSection 2 · PMBOK 7 — The \"Why / Ought\"\n\n## The 12 Project Management Principles\n\nPrinciples are **guides for behaviour & decisions**, not steps. They are outcome-oriented and apply to _any_ approach. The 12 sit beneath the 8 Performance Domains (Poster 3) and tell you **how to act** when the playbook runs out.\n\n### Visual Map & Key Concepts — All 12, clustered\n\n__**People** __**Outcome & Value** __**System & Uncertainty** __**Adaptation & Change**\n\n01StewardshipBe diligent, respectful & caring — for the organisation _and_ society/environment.\n\n**Cue:** accountable to all affected, not just the sponsor.\n\n02TeamBuild a collaborative, safe, shared-ownership team culture.\n\n**Cue:** optimise the team, not the hero.\n\n03StakeholdersEngage proactively, to the depth needed to deliver value.\n\n**Cue:** engage early, often, at the right depth.\n\n06LeadershipShow leadership behaviours — influence & direction beyond authority.\n\n**Cue:** lead the behaviour you want to see.\n\n04ValueContinually evaluate & adjust to maximise benefits & worth.\n\n**Cue:** ask \"so what's the value?\" at every gate.\n\n08QualityBuild quality into processes & deliverables — fitness for purpose.\n\n**Cue:** prevent defects, don't just detect.\n\n12ChangeEnable people to adopt the change & reach the future state.\n\n**Cue:** no adoption = no benefits.\n\n11Adaptability & ResiliencyBuild capacity to flex and to recover from setbacks.\n\n**Cue:** plan to flex; design to bounce back.\n\n05Systems ThinkingSee interacting wholes; anticipate ripple effects.\n\n**Cue:** trace the ripple before you change.\n\n09ComplexityRecognise complexity (systems, behaviour, ambiguity) & adapt.\n\n**Cue:** probe–sense–respond when cause/effect is unclear.\n\n10RiskAddress uncertainty — chase opportunity, limit threat — cost-effectively.\n\n**Cue:** spend on response only where it pays.\n\n07TailoringDesign the approach to fit the unique context; maximise value, minimise waste.\n\n**Cue:** fit the method to the work, never the reverse.\n\n### Relationships\n\n  * Principles rest on the **PMI Code of Ethics** : Responsibility, Respect, Fairness, Honesty.\n  * The 12 **enable the 8 Performance Domains** — principles = mindset, domains = activity.\n  * **Uncertainty cluster:** Risk + Complexity + Adaptability work together.\n  * **People cluster** (Stewardship, Team, Stakeholders, Leadership) underpins all the rest.\n\n\n\n### Exam Concepts\n\n  * Principles are **not prescriptive** and are **not processes**.\n  * Stewardship covers **internal + external** (society, environment).\n  * Leadership ≠ positional **authority** — anyone can lead.\n  * Tailoring appears as both a **principle** and a recurring theme.\n\n\n\n### Executive View\n\n  * The 12 are a **leadership operating system** for delivery culture.\n  * **Stewardship + Value** map directly to board & ESG conversations.\n  * Promote **leadership at all levels** , not just at the top.\n  * Use as **decision tie-breakers** when rules conflict.\n\n\n\n### Industry Example — Manufacturing line upgrade\n\nManufacturing\n\n  * **Systems thinking:** a faster cell starves the next station — model the whole line first.\n  * **Quality built-in:** poka-yoke & in-process checks beat end-of-line inspection.\n  * **Optimise risk:** spend on a pilot cell before committing the full retrofit.\n  * **Change:** operator training & buy-in decide whether throughput actually rises.\n\n\n\n### Memory Hooks\n\n**Sentence mnemonic (in order 1–12):**\n\n**S** tewards **T** end **S** takeholders' **V** alue · **S** ystems **L** ead **T** ailored **Q** uality · **C** omplexity, **R** isk, **A** daptability, **C** hange\n\n  * 4 **People** , 2 **Outcome** , 3 **System** , 3 **Adaptation** — recite by colour.\n\n\n\n60-sec Review Recite all 12 by cluster colour Run the sentence mnemonic Name the 4 ethics values Principle vs process — the difference Pick one cue to use today\n\nPMI Visual Wall · Poster 02 · PMBOK 7 Principles · original instructional design · A3 landscape\n\nPOSTER 03\n\nSection 2 · PMBOK 7 — The \"What / Where It Shows Up\"\n\n## The 8 Performance Domains\n\nDomains are **interacting areas of focus** that run _concurrently_ across the whole effort — **not phases** and not the old knowledge areas. You steer each one by its **outcomes & checks**. The 12 Principles (Poster 2) are the mindset behind them.\n\n### Visual Map & Key Concepts — the 8 domains, their outcomes, signals & traps\n\nStakeholders↔ Team↔ Dev Approach↔ Planning↔ Project Work↔ Delivery + cross-cutting → Measurement· Uncertainty\n\nDomain| Intent| Target outcomes| Measures / indicators| Watch-out\n---|---|---|---|---\n**1 · Stakeholders**|  Build productive relationships & the right level of engagement.| Stakeholders aware, engaged & supportive; conflicts surfaced & managed.| Engagement level (unaware→leading); satisfaction; open issues.| A hidden or under-engaged stakeholder.\n**2 · Team**|  Grow a high-performing, shared-ownership team & distributed leadership.| Trust, safety, shared ownership, capability growth.| Stable velocity; retention; morale / safety pulse.| Hero culture & burnout.\n**3 · Development Approach & Life Cycle**| Choose predictive / iterative / incremental / adaptive / hybrid & a fitting life cycle & cadence.| Approach matches the deliverable & context; delivery cadence set.| Fit-for-context check; release cadence.| Forcing one approach onto every deliverable.\n**4 · Planning**|  Organise & coordinate the work progressively & proportionately.| Coordinated, \"just-enough\" plan; estimates that evolve.| Forecast accuracy; plan/baseline stability.| Over-planning & big-bang plans.\n**5 · Project Work**|  Run efficient processes — resources, procurement, communications, learning.| Smooth flow; informed stakeholders; capable, supplied team.| Throughput; WIP; lead / cycle time.| Invisible work & bottlenecks.\n**6 · Delivery**|  Deliver the scope & quality that achieve the intended outcomes.| Requirements met; acceptance & quality criteria satisfied; value delivered.| Acceptance %; defect/escape rate; scope completion.| Shipping output that produces no outcome.\n**7 · Measurement** cross-cutting| Assess performance vs plan/value & act on it.| Reliable information; timely, evidence-based decisions.| EV · CPI · SPI; leading vs lagging KPIs; dashboards.| Vanity metrics & gamed numbers.\n**8 · Uncertainty** cross-cutting| Navigate risk, ambiguity, complexity & volatility.| Threats reduced; opportunities captured; resilience built.| Risk exposure (EMV); reserve burn; variability.| Ignoring opportunity; false precision.\n\n### Relationships\n\n  * All 8 run **simultaneously & continuously** — they are not a sequence.\n  * **Dev Approach** shapes **Planning** & **Project Work** ; **Delivery** realises **Stakeholder** value.\n  * **Measurement** feeds decisions in every other domain.\n  * **Uncertainty** overlays all — risk lives everywhere.\n\n\n\n### Exam Concepts\n\n  * Domains are **concurrent** , not phases.\n  * They are the **lens that replaced the 10 knowledge areas**.\n  * Steer by **outcomes & checks**, not activities.\n  * **Leading** indicators predict; **lagging** confirm.\n  * You **tailor the system** of domains to context.\n\n\n\n### Executive View\n\n  * Exec dashboards = the **Measurement** domain made visible.\n  * Watch **flow metrics** (lead time, throughput) beside Earned Value.\n  * Reward **outcomes over outputs**.\n  * Treat **Uncertainty** as a standing board topic.\n\n\n\n### Industry Example — Rail station build\n\nInfrastructure\n\n  * **Dev Approach:** predictive civils, agile for the passenger-info software → **hybrid**.\n  * **Project Work:** manage interfaces between contractors as flow & WIP.\n  * **Delivery:** \"trains stop & passengers flow safely,\" not just \"platform poured.\"\n  * **Uncertainty:** weather, utilities & possessions are the live risk drivers.\n\n\n\n### Memory Hooks\n\n**Order mnemonic (1–8):**\n\n**S** ome **T** eams **D** evelop **P** lans, **P** roducing **D** eliverables **M** easured (under) **U** ncertainty\n\n  * **M & U** are the two **cross-cutting** domains — picture them as a frame around the other six.\n\n\n\n60-sec Review Name all 8 in order (mnemonic) Which 2 are cross-cutting? \"Domains run concurrently\" — say why One outcome + one trap per domain Leading vs lagging indicator\n\nPMI Visual Wall · Poster 03 · PMBOK 7 Performance Domains · original instructional design · A3 landscape\n\nPOSTER 04\n\nSection 2 · PMBOK 7 — Why Projects Exist\n\n## The Value Delivery System\n\nPMBOK 7 reframes projects as part of a **system that creates value**. Effort moves **down** as funding & direction; **worth** moves **up** as outcomes, benefits and value. The job is not \"deliver the thing\" — it's **realise the value**.\n\n### Visual Map — the system, end to end\n\n▲ VALUE · BENEFITS · INFORMATION & FEEDBACK flow UP ▲\n\nOrganisational\nStrategy▶ Portfolio\nright work▶ Program\nbenefits▶ Project\noutputs▶ Product\nthing of value▶ Operations\nsustain▶ Customer\nrealises value\n\n▼ STRATEGIC DIRECTION · FUNDING · DECISIONS & MANDATE flow DOWN ▼\n\nThe system is governed as **a whole**. **Feedback loops** from operations & customers continually re-shape strategy and the portfolio — value delivery is **circular** , not a one-way pipeline.\n\n### The Value Ladder\n\nOutput\n\nThe deliverable produced (e.g. an app, a bridge).\n\n▼\n\nOutcome\n\nThe change the output enables (people use it).\n\n▼\n\nBenefit\n\nThe measurable gain (cost down, revenue up).\n\n▼\n\nValue\n\nWorth to stakeholders — financial _or_ not.\n\n### Key Concepts\n\nValue\n    Worth/importance to stakeholders.\nBusiness value\n    Net quantifiable benefit to the org.\nInternal value\n    Capability, IP, morale, readiness.\nExternal value\n    Customer & market worth.\nValue stream\n    The flow that turns need → value.\nSystem view\n    Optimise the whole, not a part.\n\n### Relationships\n\n  * Each component **feeds the next** ; operations **sustain** the value over time.\n  * Portfolio governance **steers** the whole toward strategy.\n  * Benefits are often realised **after the project closes** — programs/operations own realisation.\n  * Customer feedback **loops back** to reshape strategy.\n\n\n\n### Exam Concepts\n\n  * Output ≠ outcome ≠ benefit ≠ value.\n  * Value can be **non-financial**.\n  * Benefit realisation may sit **past closure**.\n  * Know the term \"**value delivery system**.\"\n\n\n\n### Executive View\n\n  * Steer the portfolio by **value** , not activity.\n  * Maintain a **benefits dependency network**.\n  * Ask: \"value created — or just deliverables shipped?\"\n  * Fund **realisation** , not only build.\n\n\n\n### Industry Example — Enterprise SaaS\n\nIT\n\n  * **Output:** a new billing feature ships.\n  * **Outcome:** finance teams adopt it.\n  * **Benefit:** churn down, ARPU up.\n  * **Value:** higher enterprise valuation.\n\n\n\n### Memory Hooks\n\n  * **Build → Use → Gain → Worth** = the value ladder.\n  * **\"OO-BV\"** : Output, Outcome, Benefit, Value.\n  * **Money down ▼, value up ▲** — and it **loops**.\n\n\n\n60-sec Review Draw the system left→right Climb the value ladder aloud Internal vs external value When are benefits realised? Name one feedback loop\n\nPMI Visual Wall · Poster 04 · PMBOK 7 Value Delivery System · original instructional design · A3 landscape\n\nPOSTER 05\n\nSection 2 · PMBOK 7 — Fit the Approach to the Context\n\n## Tailoring\n\nTailoring is the **deliberate adaptation** of approach, governance and processes to suit the unique context of the work. The aim is to **maximise value and minimise waste** — never to cut corners. It is _iterative_ : you tailor at the start and keep adjusting as you learn.\n\n### Visual Map — The Tailoring Funnel\n\n__**Predictive** — plan-driven, fixed scope, single delivery __**Hybrid** — predictive shell, adaptive core __**Adaptive** — iterative, evolving scope, frequent delivery\n\n**1 · Select**\ninitial development approach ▸ **2 · Tailor for the Organisation**\ngovernance, methodology, policy, culture ▸ **3 · Tailor for the Project**\nproduct, team & the specific context ▸ **4 · Implement & Improve**\ninspect, adapt, refine continuously ↺\n\nThe funnel **narrows** from a broad starting point to a precise fit, then **loops** — step 4 feeds learning back into steps 1–3 throughout delivery. You tailor the **life cycle, processes, engagement (people), tools, methods & artifacts** — but the 12 **principles always apply**.\n\n### What Drives the Decision? — Read the Context\n\nDimension| Pushes toward Predictive ▸| ◂ Pushes toward Adaptive\n---|---|---\n**Requirements**|  Stable, clear, well understood| Emerging, uncertain, fast-changing\n**Risk & regulation**| Safety-critical, heavily regulated| Low regulatory burden\n**Cost of change**|  Expensive to change late| Cheap & easy to change\n**Delivery cadence**|  One large, integrated delivery| Frequent small increments\n**Customer involvement**|  Limited / milestone-based| Continuous & collaborative\n**Size & duration**| Large, long, many interfaces| Small-to-medium, shorter\n**Team & culture**| Distributed, low agile maturity| Co-located/empowered, agile-fluent\n\n### What You Can Tailor\n\n  * **Life cycle & development approach** — phases, gates, cadence.\n  * **Processes** — add, remove, blend or align to fit value.\n  * **Engagement** — how people & stakeholders interact.\n  * **Tools** — methods of delivery, software, infrastructure.\n  * **Methods & artifacts** — which models, methods & documents you actually use (Poster 6).\n\n\n\n### Relationships\n\n  * Tailoring is **Principle #7** and a theme across all 8 domains.\n  * **Organisational governance / the PMO** sets the guardrails you tailor within.\n  * Feeds **Development Approach & Life Cycle** domain directly.\n\n\n\n### Exam Concepts\n\n  * Goal = **maximise value, minimise waste** — _not_ reduce rigour.\n  * Tailoring is **iterative & ongoing**, not a one-time setup.\n  * **Over-tailoring** (too much process) and **under-tailoring** (too little) are both risks.\n  * You tailor **methods** , never the **principles**.\n  * Tailoring decisions should be **justified & documented**.\n\n\n\n### Executive View\n\n  * **Right-sized governance** = speed without losing control.\n  * Avoid **one-size-fits-all** mandates that burden small work.\n  * A documented **tailoring framework** signals organisational maturity.\n  * Frees senior attention for **high-risk, high-value** projects.\n\n\n\n### Industry Example — Defence vs Start-up\n\nDefence\n\n  * **Shipbuilding:** fixed config baselines, stage gates, safety regs → strongly **predictive** , minimal agile tailoring.\n\nIT\n\n  * **Internal tooling team:** backlog, 2-week sprints, continuous release → **adaptive**.\n\nHybrid\n\n  * **Regulated SaaS:** agile build _inside_ a predictive compliance & assurance wrapper.\n\n\n\n### Memory Hooks\n\n  * **\"Tailor the suit to the person\"** — fit the method to the work, never the reverse.\n  * **A·O·P·I** = **A** pproach → **O** rganisation → **P** roject → **I** mprove (the 4 funnel steps).\n  * **More tailoring ≠ less rigour** — it means _appropriate_ rigour.\n  * Stable + regulated → **predictive** ; uncertain + fast → **adaptive** ; both → **hybrid**.\n\n\n\n60-sec Review Draw the 4-step funnel + loop Predictive vs Adaptive drivers Name the 5 things you tailor Over- vs under-tailoring Why principles never tailor\n\nPMI Visual Wall · Poster 05 · PMBOK 7 Tailoring · original instructional design · A3 landscape\n\nPOSTER 06\n\nSection 2 · PMBOK 7 — The Practitioner's Toolkit\n\n## Models, Methods & Artifacts\n\nPMBOK 7 stops prescribing process and instead gives a **toolkit** you tailor (Poster 5). Three families: **Models** are thinking frameworks that explain a situation; **Methods** are the means to produce an output; **Artifacts** are the templates, documents & deliverables you create.\n\n### MODELS — ways to _think_\n\n  * **Situational leadership:** flex style (direct → coach → support → delegate) to follower readiness.\n  * **Communication:** sender–receiver, channels = n(n−1)/2, cross-cultural & effectiveness models.\n  * **Motivation:** Maslow (hierarchy) · Herzberg (hygiene vs motivators) · McGregor (Theory X / Y) · intrinsic vs extrinsic · Pink (Autonomy·Mastery·Purpose).\n  * **Change:** ADKAR · Kotter 8-Step · Bridges Transition (ending→neutral→beginning) · Satir curve.\n  * **Complexity:** Cynefin (clear / complicated / complex / chaotic) · Stacey matrix.\n  * **Team development:** Tuckman (Forming·Storming·Norming·Performing·Adjourning) · Drexler–Sibbet.\n  * **Conflict:** Thomas–Kilmann — Compete · Collaborate · Compromise · Avoid · Accommodate.\n  * **Stakeholders:** Salience (Power·Legitimacy·Urgency) · Power/Interest grid.\n  * **Process / planning:** PDCA · OODA · escalation & negotiation models.\n\n\n\n### METHODS — ways to _do_\n\n  * **Data gathering:** brainstorming · interviews · focus groups · benchmarking · surveys · checklists.\n  * **Data analysis:** alternatives · cost-benefit · earned value · forecasting · root-cause · variance · trend · what-if · SWOT · regression · reserve · assumption/constraint.\n  * **Estimating:** analogous (top-down) · parametric · three-point / **PERT** · bottom-up · affinity (story points, t-shirt sizing).\n  * **Decision-making:** voting / fist-of-five · multicriteria (MCDA) · weighted scoring.\n  * **Data representation:** see Artifacts → \"visual data & information\".\n  * **Meetings & events:** stand-ups · reviews · retrospectives · planning · kick-offs.\n\n\n\n### ARTIFACTS — things you _show_\n\n  * **Strategy:** business case · project brief · **charter** · roadmap.\n  * **Logs & registers:** assumption · backlog · change · issue · lessons-learned · risk · stakeholder (RAID).\n  * **Plans:** PM plan + subsidiary plans (scope, schedule, cost, quality, comms, risk, etc.).\n  * **Baselines:** scope · schedule · cost · the integrated **performance measurement baseline (PMB)**.\n  * **Hierarchy charts:** WBS · OBS · RBS (risk & resource breakdown).\n  * **Visual data & info:** Gantt · burn-up/down · cumulative flow (CFD) · S-curve · RACI · dashboard · story map · value stream map.\n  * **Reports:** status · progress · quality · risk reports.\n  * **Agreements / contracts:** FFP · T&M · CPFF · CPIF.\n\n\n\n### High-Yield Exam Concepts\n\n  * **Contract risk:** **FFP** = most risk on _seller_ ; **CPFF / cost-plus** = most risk on _buyer_ ; **T &M** = shared.\n  * **PERT** (expected) = (O + 4M + P) / 6 · **PERT σ** = (P − O) / 6.\n  * **Communication channels** = n(n − 1) / 2.\n\n\n  * **Baseline** = approved version + approved changes; measure actuals against it.\n  * Know cold: **Tuckman** stages · **Cynefin** domains · **Thomas-Kilmann** modes · **Salience** · **ADKAR vs Kotter**.\n  * Match the **tool to the context** — there is no single \"right\" set.\n\n\n\n### Executive View\n\n  * Standardise a **core toolkit** ; let teams tailor the rest.\n  * Dashboards & S-curves are the **artifacts that reach the board**.\n  * Contract type = a **strategic risk-allocation** lever, not an admin detail.\n\n\n\n### Industry Example — Manufacturing Transformation (Lean Cell)\n\nManufacturing\n\n  * **Models:** Cynefin to classify the change · Kotter + ADKAR to drive shop-floor adoption · Tuckman to read the new cell team.\n\n\n  * **Methods:** cost-benefit + parametric estimate to justify the cell · root-cause (5 Whys) on defects · what-if for capacity.\n\n\n  * **Artifacts:** business case · WBS · risk register · S-curve · RACI · value stream map of the line.\n\n\n\n### Memory Hooks\n\n  * **\"Models think · Methods do · Artifacts show.\"**\n  * Tuckman: **\"Form a Storm, Normally Perform, then Adjourn.\"**\n  * Artifacts = the PM's **paper trail** (logs record, baselines compare, reports communicate).\n\n\n\n60-sec Review Define model / method / artifact Recite PERT + channels formulas Who holds risk: FFP vs CPFF List Tuckman's 5 stages Name 3 visual-data artifacts\n\nPMI Visual Wall · Poster 06 · PMBOK 7 Models, Methods & Artifacts · original instructional design · A3 landscape",
  "title": "PMI VISUAL WALL · BATCH 1",
  "updatedAt": "2026-06-02T06:45:40.855Z"
}