PMP
- Scope and deliverables
- Schedule and dependencies
- Cost and resources
- Risk and quality
- Stakeholders and communication
- Governance and accountability
PMP, Agile and The Tools®-informed practices are not substitutes. They operate at different levels of the same transformation challenge: governance, adaptation and human response.
The Tools® are a set of brief, action-oriented psychological exercises associated with psychotherapist Phil Stutz and writer and psychotherapist Barry Michels. They were developed in a therapeutic context, but this framework does not bring psychotherapy into project management. It asks a narrower question: can selected ideas be translated into safe self-leadership prompts that help project professionals act constructively when pressure, fear, avoidance or resistance appears?
The Tools® do not replace PMP practices, Agile ways of working, change management, coaching, HR processes or professional mental-health support.
Here they serve as short reflection prompts used primarily by the project leader on their own reactions and choices.
Purpose: move from automatic reaction to deliberate, constructive action.
A name for the internal resistance that encourages avoidance, delay, defensiveness or retreat into the comfort zone. PM prompt: What story am I telling myself so I can postpone the necessary action?
A practice of moving toward necessary discomfort instead of organizing behaviour around avoiding it. PM prompt: Which difficult conversation or decision would create the most value if addressed now?
A way to interrupt resentment and emotional reactivity so that the leader can respond constructively. PM prompt: How can I challenge the behaviour without reducing the person to the problem?
A focus on the next meaningful action rather than waiting for motivation, certainty or a perfect transformation plan. PM prompt: What is the next useful pearl we can complete and make visible?
Useful reminders to acknowledge perceived loss and face current facts without denial. PM prompts: What does this change threaten? and What truth must we accept before we can adapt?
Governance creates stability. Agile practices create learning. Psychological tools support adoption. When these layers reinforce each other, the result is sustainable transformation.
A new process does not move directly from implementation to usage. Between them lie fear, resistance, politics, perceived loss, experimentation, acceptance and finally ownership. This middle path is frequently under-managed, even though it determines whether the technical solution becomes working practice.
The same issue can be treated structurally, adaptively and psychologically. Effective leadership combines all three rather than overusing only one.
This map translates psychological tools into practical PM use. It is a leadership aid, not psychotherapy or a clinical model.
| Tool or concept | PM situation | Agile connection | Managerial practice |
|---|---|---|---|
| Reversal of Desire | Avoided conflict, escalation or decision | Expose impediments early | Schedule the difficult conversation and define its constructive objective. |
| Part X | Resistance, delay, passive opposition | Make blockers visible | Name the resistance pattern without labelling or attacking the person. |
| Active Love | Anger, blame or damaged trust | Psychological safety and collaboration | Regulate the reaction, separate behaviour from identity and respond constructively. |
| String of Pearls | Overwhelm and transformation fatigue | Iterations and incremental value | Define the next useful action or deliverable and complete it visibly. |
| Loss Processing | Change threatens status, habits or autonomy | Change readiness and feedback | Ask what is perceived as being lost and design transition support. |
| Radical Reality | Optimistic reporting or hidden performance issues | Transparency and inspect-adapt | Use verified data, describe gaps neutrally and convert facts into action. |
Do not use a psychological concept to diagnose or manipulate stakeholders. Use it first as a self-leadership prompt, then as a respectful lens for curiosity, listening and facilitation. Formal performance, HR, safety and contractual matters still require the appropriate organizational processes.
Why governance and adaptation are insufficient without human adoption.
How structure, visibility and accountability create the foundation.
How feedback, experimentation and iterations enable adaptation.
A practical psychological lens for avoidance, fear and ownership.
Recognizing resistance patterns without blaming individuals.
Reversal of Desire and the discipline of difficult conversations.
Positioning adoption as a critical dimension of project success.
Examples from fabrication, installation, QA/QC and organizational development.
Connecting control, adaptation, adoption and sustainable results.
Assessment questions, facilitation prompts and practical routines.
Development note: the framework should distinguish clearly between original synthesis, established PMP/Agile practices and concepts attributed to Phil Stutz. Any publication should use accurate references, avoid clinical claims and present the The Tools® component as a leadership and self-reflection lens.
The examples below are not conclusions. They are conversation starters. The aim is to collect real experiences, examine whether a Tools-informed reflection adds practical value and identify situations where it does not.
Choose a real, anonymized project situation. Apply the questions below and tell the community whether the Tools-informed reflection was useful, partly useful or not applicable.
Community question: Where does this perspective improve PM practice, and where does it oversimplify the situation?
The Tools® refers to practical psychological exercises associated with Phil Stutz and Barry Michels, including Part X, Reversal of Desire, Active Love and String of Pearls. In this framework, they are used only as a non-clinical self-leadership and facilitation lens for understanding resistance, encouraging constructive dialogue and supporting human adoption. This is an independent project-management synthesis and does not imply endorsement by the authors, trademark owner, PMI or any Agile organization.