PMTales Field Guides

These are not templates.
They are not frameworks.
They are not “best practices.”

​

PMTales Field Guides exist to explain what actually happens inside real projects — the gaps, the pressure, the politics, and the quiet decisions that shape outcomes long before a post-mortem.

​

Each guide isolates one reality of project work and examines it without pretending the trench is clean.

​

How to Use These Guides

Read them in order if you’re building understanding.
Jump between them if you’re diagnosing a problem.
Revisit them when something feels off — but nobody can quite name why.

These guides are meant to:

• Clarify patterns

• Name failure modes

• Give language to experiences PMs already recognize

They don’t tell you what to do.
They explain what’s happening.

Core Fundamentals

​

• Project Management Fundamentals (From the Trench)
   

• The Project Lifecycle: How It’s Supposed to Work vs How It Actually Works
   

• Project Roles & Responsibility Gaps
   

These explain why projects behave the way they do before delivery even begins.

⚔️ Delivery & Survival

(Where theory meets pressure.)

​

• Scope Creep: How It Starts, Why It Wins, and How Projects Survive
   

• Risk Management in Real Projects (Not the Spreadsheet Version)
   

• Project Planning Myths (And Why Plans Still Matter)
   

• Status Reporting, Visibility, and Theatre
   

These explain why delivery breaks even when everyone is trying.

🏛️ Governance, Power & Decision-Making

(Where projects slow, stall, or quietly fail.)

​

• Governance vs Delivery: When Process Becomes Protection
   

• Decision-Making Failures in Projects
   

• Stakeholder Behavior Patterns (Quiet Power, Loud Influence)

These explain why projects get stuck even when they’re “well managed.”

🧰 Tools & Artifacts (Survival Gear)

(Where documents meet reality.)

​

• Project Charters: What They’re Meant to Do vs What They Actually Do
   

• Risk Registers and the Illusion of Control
   

• RAID Logs, Registers, and Rituals
   

• Meetings, Status Updates, and the Performance of Progress

These explain why artifacts feel busy but rarely decisive.

​

🧠 Meta / Philosophy

​

• Why Projects Fail Despite Good Process
   

• Why Good Plans Don’t Survive Contact With Reality
   

These guides aren’t here to replace experience.

They exist to:

• Shorten the distance between confusion and clarity

• Give language to what PMs already sense

• Make invisible forces visible

The trench doesn’t get easier. But it does get clearer.