Navigation Section
Executing Process ITTOs
References
Plans don’t deliver projects — people do.
Executing Process Group – Where the Work Gets Real
Executing is where all the planning finally gets to stretch its legs. The processes in this group exist to coordinate people, manage Delivery, and keep things moving. The ITTOs you’ll find here aren’t abstract or theoretical — they’re tactical, practical, and deeply human.
This process group is where schedules meet reality, stakeholders start watching closely, and issues surface faster than Risk registers can keep up. But the ITTOs in Executing are ready for this. They’re about guiding the team, communicating across boundaries, and making mid-Flight decisions that still align with the original charter.
Each process below serves as a container for ITTOs that help translate intent into outcomes. We won’t walk through the process mechanics — just the ITTOs they hold, and why they matter when the real work begins.
Direct and Manage Project Work
This is the central engine of execution. It’s the process where the plan turns into deliverables — the actual doing of the work.
Inputs here include everything you’d expect: the Project management plan, approved Change requests, EEFs, OPAs, and Performance data. What makes this process powerful is its toolset: expert judgment, Meetings, project management information systems (PMIS), and [[3-glossary#Issue management|Issue management]].
Outputs are what you’d hope for — deliverables, work Performance data, and new Change requests. But the real story is that every input in this process can be dynamic. Plans shift. Issues emerge. The PM’s job is to keep action aligned with intent — even when things are messy.
This process produces the raw materials for monitoring and controlling. If it’s not logged or communicated here, it probably doesn’t exist.
Manage Project Knowledge
While Direct and Manage is about Delivery, Manage Project Knowledge is about learning while delivering. The ITTOs here Support creating and sharing knowledge in real time — especially lessons that future teams can reuse.
Inputs include the project team’s experience, deliverables in progress, and organizational knowledge bases. Techniques like knowledge management, information-sharing tools, and Feedback systems help capture insights before they vanish into Slack threads and hallway conversations.
The key output — [[3-glossary#Lessons learned register|Lessons learned register]] — isn’t just an after-action Artifact. It lives during execution. It helps shape better outcomes as you go, not just when you look back.
Acquire, Develop, and Manage Team
These three processes are the people operations heart of Executing. Planning told you who you’d need. Now you go get them, grow them, and lead them.
In Acquire Resources, inputs include resource calendars, Availability, and organizational Policies. Outputs include assigned Resources and physical assets. Tools include Negotiation, internal hiring systems, and procurement interfaces.
Develop Team uses Coaching, Training, Feedback, and team-building activities to move the group from a collection of names into a functioning unit. Outputs include Performance assessments, skill improvements, and strengthened team Cohesion.
Finally, Manage Team handles ongoing Engagement, [[3-glossary#Conflict Resolution|Conflict Resolution]], Performance tracking, and Adaptation. It’s where Emotional intelligence meets organizational policy — and where many projects either thrive or unravel.
Across all three, the ITTOs Lean heavily on interpersonal skills, Communication tools, and real-time Feedback loops. These processes keep the humans aligned while the work accelerates.
Manage Communications
If you’re managing work and people, you’d better be managing Communication. This process ensures that the right people get the right information, in the right format, at the right time.
The inputs are wide-ranging — from project plans to Stakeholder registers to actual Performance data. Techniques include Communication models, Information distribution systems, and Active listening (yes, that’s an ITTO-adjacent concept). Meetings, status updates, dashboards, and impromptu syncs all live here.
The output? Information that flows — not just exists. If your comms are delayed, misunderstood, or overly complex, this is the process that helps untangle it.
Implement Risk Responses
You planned for Risk earlier. This is where those plans get triggered. Implement Risk Responses connects planning to action — it’s the moment where a Mitigation or Contingency plan stops being hypothetical.
Inputs include the [[3-glossary#Risk register|Risk register]], Risk response plan, and Change requests. Execution tools include expert judgment, PMIS, and interpersonal skills (because not every Risk response lands gently).
Outputs are clear: work Performance data, Issue logs, and updates to documents reflecting how Risk response played out in real time.
This is where proactive work becomes reactive Readiness — and where the exam often tests your ability to recognize intentional vs. improvised responses.
Conduct Procurements
Working with vendors isn’t just about Contracts — it’s about managing relationships, timelines, and Expectations once the work begins. This process activates procurement agreements, oversees deliverables, and navigates issues or claims.
Inputs include bid documents, selected sellers, and agreements. Tools may include Negotiation, [[3-glossary#Performance reviews|Performance reviews]], inspections, and claims administration systems.
Key outputs include procurement Performance Reports, updates to agreements, and occasionally Change requests if Scope, price, or timelines shift.
Effective execution here means staying ahead of Vendor issues — not reacting once a Delivery goes sideways.
Manage Stakeholder Engagement
This process is where Influence is maintained, Expectations are managed, and relationships are protected. You already identified stakeholders and planned how to engage them — now you carry it out.
Inputs include the [[3-glossary#Stakeholder Engagement plan|Stakeholder Engagement Plan]], project documents, communications plans, and the current mood of your stakeholders (harder to quantify, but just as important).
Tools here are strategic and emotional: Communication, Negotiation, [[3-glossary#Conflict Resolution|Conflict Resolution]], Facilitation, and Cultural awareness.
When this process works, stakeholders stay Informed and invested. When it’s skipped, even a perfect deliverable can feel like a failure.
What You Should Take Away
Executing ITTOs are active. They move, shift, and adapt in real time. They aren’t about Governance — they’re about getting the job done, while staying aligned with plans, people, and purpose.
On the exam, watch for signals like:
- The work has begun
- Stakeholders are reacting to deliverables
- Risks are being addressed
- Teams are Forming, Storming, or Norming
You’re not in setup anymore — you’re in motion. Executing ITTOs help you keep that motion on track.
Questions Worth Exploring
- What signals that a Communication breakdown is an execution Issue, not a planning miss?
- How do Issue logs and Change requests evolve in Executing?
- What distinguishes effective Stakeholder Engagement during execution?
- How do Lessons learned get captured while the work is still in progress?