Haunted Project Survival Guide
summary
Frames projects as haunted mansions and offers three concrete responses: confront (change the system), accept (reframe stress) or escape (leave). Calls out specific monsters — a revenue-driving monolith tied to everything, micromanaging puppeteers, and a bureaucratic mummy — and gives tactics: use Microsoft Excel to show value (example: 3-day build fix saves ~40 developer days/year), run quarterly 5–10% tech-improvement slots, use a supporter of the week role to shield teams, escalate smartly and create early tasks to prefetch approvals.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 3:19What do we truly want in projects
- 7:33Handling stress
- 10:43Miscommunication tech vs business
- 13:12Monolith resistance
- 17:26Micromanaging
- 20:58Bureaucracy
- 23:46Lack of growth
- 27:15Purpose beyond project
- 28:38Focused work
- 29:41Closing
related talks
37mHaunted Projects Survival Guide
30mDealing With A Project's Complexity In A Changing Environment
40mImproving Software Architecture Through Murder
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
24mFrom Startup to Scale Up Designing for Growth from Day One
01h 02mTools for simplified large scale systems
55mFactory, Workshop, Stage
25mThinking Architecturally