PMP ITTOs Explained: Inputs, Tools, Techniques, Outputs

When I sat my first PMP attempt back in the PMBOK Guide Sixth Edition era, I spent roughly six weeks of my preparation period trying to memorise the ITTOs (Inputs, Tools and Techniques, Outputs) for all 49 processes. I produced flashcards, spreadsheets, colour-coded matrices, and even built a small web app that quizzed me randomly. I passed, but in hindsight I wasted half of that effort. The exam never asked me to recite a list of inputs. It asked me whether I understood the flow of work.

Today, with the PMBOK Guide Seventh Edition having moved towards principles and performance domains, and the exam content outline weighted heavily towards Agile and Hybrid scenarios, the role of ITTOs has shifted further. They are still useful as a mental scaffolding, but rote memorisation is no longer a sensible study strategy. In this article I will walk you through what ITTOs actually are, why they matter (and why they sometimes do not), the patterns that repeat across knowledge areas, the small set of ITTOs that genuinely recur, and a sensible "understand, do not memorise" approach that will save you weeks of preparation time.

The acronym ITTO stands for Inputs, Tools and Techniques, and Outputs. In the PMBOK Guide Sixth Edition every one of the 49 processes was described in this four-part structure. An input is something the process needs to begin (a document, a piece of data, a prior output). A tool is a software or template. A technique is a method or approach (brainstorming, expert judgement, decomposition). An output is what the process produces, which often becomes the input for another process.

The structure was deliberately mechanical because PMI wanted to communicate the integrated nature of project management: nothing happens in isolation. The Project Charter is an output of one process and an input to fourteen others. The Risk Register flows through almost every knowledge area. The Project Management Plan is updated by nearly every executing and monitoring process.

"I used to think of ITTOs as a parts list. They are actually a wiring diagram. The point is the connections, not the components."

That shift in mental model is what I want you to take away. Once you see ITTOs as connections, you stop asking "what are the seven inputs to Develop Schedule" and start asking "what does a scheduler need before they can begin, and what do they hand off when they are done?" The first question is impossible to answer without rote memorisation. The second is common sense.

The current PMP examination is built on a content outline that splits questions roughly 42% Process, 50% People, and 8% Business Environment, with around half of the questions drawing on Agile or Hybrid scenarios. Pure recall of an ITTO list is rare. What is common is a scenario in which you must identify the next logical step, choose the most appropriate technique, or recognise that a critical input is missing.

I have reviewed somewhere between 4,000 and 5,000 practice questions in the last few years (both my own preparation and helping mentees prepare) and the pattern is consistent: questions test whether you understand the flow, not whether you can recite a list. A typical example reads "The project manager has just completed identifying risks. What should she do next?" The correct answer is "Perform Qualitative Risk Analysis" and you only need to know that risks must be assessed before they can be quantified or responded to. You do not need to know the seven inputs to Identify Risks.

That said, knowing the major outputs (charter, plan, register, baseline, report) and which processes produce them is genuinely useful. Around 15 to 20% of process-domain questions can be solved faster if you can map an artefact back to its source process. So the answer to "do ITTOs still matter?" is yes, but selectively.

I want to share a technique I stumbled into during my second study cycle, because it turned ITTO revision from a chore into something close to enjoyable. The memory palace, or Method of Loci, is an ancient mnemonic system in which you place items you wish to remember in specific locations within a familiar mental space, such as your home or your daily commute.

Here is how I applied it. I mentally walked through my house and assigned one knowledge area to each room. Integration lived in the entrance hallway (where everything begins). Scope lived in the kitchen (where you decide what to cook). Schedule was the dining room (where you decide when to eat). Cost was the home office. Quality was the bathroom (a place of standards). Resources lived in the bedroom. Communications was the living room. Risk was the garage (full of hazards). Procurement was the front garden. Stakeholders was the patio (where you entertain).

Within each room I placed the major outputs as imaginary objects. The charter sat on the hallway table. The scope baseline was the recipe book on the kitchen counter. The risk register was a hazard log hanging in the garage. When a practice question asked me about an artefact, I mentally walked to its room and the relevant process surrounded it. Strange as it sounds, it works because spatial memory is far stronger than list memory.

Once you spend time with the Sixth Edition you notice that each knowledge area has its own personality. Patterns repeat. Recognising the pattern means you do not need to memorise every individual ITTO.

Notice how nearly every knowledge area produces register updates and consumes the project management plan. That is not coincidence. That is the integrated model PMI wants you to internalise.

If I had to compress all of ITTO study into a single list, this is the one I would memorise. These items appear in dozens of processes and recognising them instantly will save you time on the exam.

• Project Management Plan (input or update in roughly 35 of 49 processes)
• Project Documents (a catch-all input in 30+ processes)
• Enterprise Environmental Factors (EEFs)
• Organisational Process Assets (OPAs)
• Expert Judgement (technique used in 30+ processes)
• Meetings (technique used in 25+ processes)
• Data Analysis (umbrella for many specific techniques)
• Data Gathering (interviews, focus groups, checklists)
• Interpersonal and Team Skills
• Change Requests
• Work Performance Data, Information, and Reports (the data triangle)
• Project Charter
• Lessons Learned Register
• Risk Register
• Stakeholder Register

If you internalise just these 15, you will recognise around 70% of all ITTOs you encounter. The remainder are process-specific and can be reasoned out from context.

I want to be direct here, because I see candidates burn weeks of study time on this. Memorising the precise number of inputs to a given process, or trying to recite outputs in the exact order they appear in the PMBOK Guide, is wasted effort. The exam does not test that level of detail. There is no question that reads "How many inputs does the Plan Procurement Management process have?" and even if there were, the answer would not help you manage a real project.

Other wasted activities I have seen mentees attempt:

• Building giant ITTO matrices in Excel with no plan to actually use them
• Reciting ITTOs while driving (the cognitive load is too high to retain)
• Memorising tools that are clearly software categories (project management software is a tool in many processes; this tells you nothing useful)
• Trying to distinguish "expert judgement" from "meetings" in contexts where both are listed

If you find yourself doing any of the above, stop. Switch to scenario-based practice questions instead. Your exam preparation time is finite.

There are cases where ITTO knowledge directly improves your exam score. The most important is recognising when an output of one process is a required input for another. Examples I drill into mentees:

1. You cannot perform Qualitative Risk Analysis without an updated Risk Register from Identify Risks.
2. You cannot Define Activities without the Scope Baseline.
3. You cannot Estimate Activity Durations without the Activity List and Resource Requirements.
4. You cannot Control Quality without the Quality Management Plan and the deliverables themselves.
5. You cannot Close Project or Phase without Accepted Deliverables.

When a scenario question asks "what should the PM do next?" or "what is the missing input?", these sequencing rules are what get you to the right answer. Memorise these handoffs and you will catch perhaps 40 to 50 questions on the exam.
 

Here is the approach I now teach. It assumes you have around 30 hours available for ITTO study (not 100).

"If you can explain to a colleague why a process exists, what triggers it, and what it produces that the next process needs, you understand it. Lists are for software, not for you."

The five-step method:

1. Group processes by phase, not by knowledge area. Treat Initiating, Planning, Executing, Monitoring & Controlling, and Closing as the spine.
2. For each process, write a one-sentence purpose. "This process exists to..." If you cannot finish that sentence, you do not understand the process yet.
3. Identify the one or two essential inputs. Not all seven. Just the ones without which the process cannot start.
4. Identify the one or two essential outputs. The artefacts that downstream processes need.
5. Practice scenario questions. Do 30 to 50 questions per knowledge area. Each wrong answer reveals an ITTO gap to revisit.

I used this approach on my third cohort of mentees (eleven candidates) and ten passed first time, with the eleventh passing on retake. The total ITTO study time averaged about 22 hours per candidate.

Let me walk you through how I think about the Scope knowledge area without memorising lists. The five Scope processes are Plan Scope Management, Collect Requirements, Define Scope, Create WBS, Validate Scope, and Control Scope.

I start with the trigger: the Project Charter is approved. That is the entry point. The PM now needs to plan how scope will be managed (Plan Scope Management), producing a Scope Management Plan and Requirements Management Plan. These are subsidiary plans, so they feed into the Project Management Plan.

Next, the PM gathers requirements from stakeholders (Collect Requirements). The essential input is the Stakeholder Register. The essential outputs are the Requirements Documentation and the Requirements Traceability Matrix. Now the PM can write a Project Scope Statement (Define Scope), which is then decomposed into a Work Breakdown Structure (Create WBS). Together, the Scope Statement, WBS, and WBS Dictionary form the Scope Baseline.

During execution, the PM uses Inspection to Validate Scope (formal customer acceptance) and Variance Analysis to Control Scope. That is the entire knowledge area, traced as a story rather than as a list. If a question asks "the customer has rejected a deliverable, what process is the PM in?", you can answer Validate Scope without having memorised any ITTO list.

Risk is where ITTO sequencing matters most because PMI loves to test the order. The Sixth Edition lists seven risk processes: Plan Risk Management, Identify Risks, Perform Qualitative Risk Analysis, Perform Quantitative Risk Analysis, Plan Risk Responses, Implement Risk Responses, and Monitor Risks.

The Risk Register is the central artefact. It is created in Identify Risks and updated by every subsequent process. If a question describes a project where the PM has just listed risks but not yet prioritised them, the next process is Qualitative, not Quantitative. Quantitative is optional and is used only when the project is large enough to justify Monte Carlo or EMV analysis.

Plan Risk Responses produces specific response strategies (avoid, transfer, mitigate, accept for threats; exploit, share, enhance, accept for opportunities), which are documented in the Risk Register. Implement Risk Responses (added in the Sixth Edition) is where those strategies actually get carried out. Monitor Risks tracks identified risks, identifies new ones, and evaluates response effectiveness.

The ITTO insight here: every risk process takes the Risk Register as input and produces an updated Risk Register as output. The register is the thread.

Question writers love to plant ITTO-related traps. Here are the patterns I have seen most often:

• Listing a valid tool that belongs to a different process (e.g., "Earned Value Management" as an option for a quality question)
• Listing the correct output but pairing it with the wrong process
• Asking "what should the PM do next?" when the scenario describes a process that has just completed (you need to know what comes next, not what just happened)
• Listing four valid actions but only one is correct given the sequence
• Using PMBOK Guide Seventh Edition language ("performance domains") in a question that expects Sixth Edition process knowledge

The defence against all of these is sequencing fluency. If you know which process comes next and what it requires, the trap reveals itself.

A practical exercise I recommend is to draw your own ITTO flow diagram on a single A3 sheet. I have done this three times now and each time my understanding deepened. The exercise:

1. Draw 49 boxes, one per process, arranged in five columns (the process groups).
2. Draw arrows from each output to the processes that consume it as input.
3. Use colour coding for the ten knowledge areas.
4. Highlight the five most-used artefacts (charter, plan, register, baseline, report).
5. Step back and look at the density of arrows.

What you will see is that Integration sits in the centre, with arrows radiating in every direction. Stakeholder and Risk are surprisingly dense. Procurement is more isolated. This visual gestalt teaches you more about project flow than any list could.

I am cautious about recommending specific products because what worked for me may not suit your learning style. That said, here is what I have used and found genuinely helpful:

• A printed Sixth Edition PMBOK Guide for the ITTO appendix (the digital version is harder to scan)
• A single-page ITTO summary sheet (many free versions exist online; I built my own)
• A flashcard app for the 15 recurring ITTOs only (not for every process)
• A whiteboard or large sheet of paper for the flow diagram exercise
• A small notebook for sequencing rules I keep forgetting

What I would not recommend: paid ITTO memorisation courses, ITTO songs (yes, these exist), or apps that gamify memorisation of process inputs. The opportunity cost is too high.

If you have one week before your exam and ITTOs are a weak area, here is a focused plan.

Total: roughly 12 hours of focused work. That is enough to lift a weak ITTO score to a solid one without consuming your final week.