What:
Why:
In VanillaPM: · walk it in the tutorial →
In the app: Project → the whole workspace; each process is a tab you already use
Reference. Not a lesson with an ECO task number — the thing you read before the ITTO cheat sheet makes any sense. If you already know what the columns mean and just need to look a process up, go straight to the cheat sheet.
Most people meet ITTO as a wall: forty processes, each with three lists, and an instruction to memorise them. It is the single most common reason people decide PMBOK is bureaucratic nonsense and go back to their issue tracker.
The wall is an artefact of how ITTO is usually presented, not what it is. This page reframes it and lets you explore all 40 processes; its companion, the ITTO chain, walks a single thread through one real project — the Coral Ridge Resort build — so you can watch one process's output become the next one's input.
Inputs · Tools & Techniques · Outputs. Every process takes some things, does something to them, and produces some things.
That is the entire idea. A process is a function:
| Means | |
|---|---|
| Input | What must already exist before you can start |
| Tool / Technique | What you do to it |
| Output | What exists afterwards that did not before |
If you have ever written a function signature, you already have the concept. inputs →
transform → outputs. The PMBOK Guide applies it to 40 processes across 7 performance
domains in the 8th edition.
The part nobody tells you: the lists are illustrative, not exhaustive. The 8th edition marks them so explicitly. They are examples of what a competent PM would reach for — not a checklist to tick, and not a set to recite.
Two honest things that most ITTO material will not tell you.
First: ITTO-per-process is a PMBOK 6 structure. The 6th edition organised the whole guide around 49 processes, each with its own ITTO block. The 7th edition moved to principles and performance domains and stopped presenting it that way. The 8th edition keeps the processes but is explicit that the lists are illustrative.
So if ITTO feels like it belongs to an older, more clerical way of thinking about projects — that is because it partly does.
Second: the exam tests it far less literally than the study material implies. Since the 2021 ECO the PMP is scenario-based. You will not be asked to recite the seven inputs to Develop Schedule. You will be asked what a project manager should do next — and answering that requires knowing what must already exist and what you are trying to produce.
Which is ITTO. Just not as a memorisation exercise.
The reframe: ITTO is not forty lists. It is a dependency graph. One process's output is the next one's input. Learn the chain and the lists mostly derive themselves.
All 40 PMBOK-8e processes, one at a time — what it's for, why it matters, its inputs → tools → outputs, and where you do it in VanillaPM. Pick one from the dropdown, or step through with Prev / Next. (Clicking a process on the cheat sheet lands you right here.)
What:
Why:
In VanillaPM: · walk it in the tutorial →
What it is —
When it's overkill —
The techniques the processes reach for — what each one is, how and when to run it, where it shines, and when it's overkill. A growing reference (the core set first); pick one from the dropdown or step through with Prev / Next.
What it is —
When it's overkill —
Once the dependency idea clicks — walked step by step on the ITTO chain — the ITTO cheat sheet stops being a wall. All 40 processes, 7 performance domains, with the VanillaPM tab for each — use it as a lookup, not a reading list.
The pages do different jobs:
| This page | Cheat sheet | |
|---|---|---|
| Answers | "What is an ITTO, and why?" | "What are Develop Schedule's outputs?" |
| Shape | Concept + a 40-process explorer | A lookup grid |
| Read it | First | Whenever you need an answer |
Then drill it: PMP Reps turns the grid into spaced-repetition flashcards with a coach and a glossary. No login.
Not "list the inputs to Develop Schedule." It asks things like:
The environmental clearance a project depends on has not been granted, and the superstructure phase is due to start. What should the project manager do first?
Answering that needs no recall. It needs you to know the clearance is an input that does not yet exist, that proceeding without it manufactures a far worse problem, and that the correct move is to work the dependency and the schedule impact — not to escalate blindly, and not to start and hope.
That is ITTO doing its real job: telling you what must exist before a thing can begin, and what you are accountable for producing. The lists are the footnotes.
When you are ready for the walked tasks, start at P1 · Develop a common vision — the same Coral Ridge project, one ECO task at a time.