Project Mechanics
The Art & Science of Delivering Projects That Matter
In 2002 I founded Project Mechanics as my consulting practice, to codify what I'd learned about delivering complex projects. The practice wound down when I joined CEC Entertainment in 2015, but the methodology didn't. Decades of iteration — through client engagements, partnerships, and thousands of project hours — and across consulting, enterprise, and healthcare environments, these principles have been refined into a practical, complete methodology.
This is that methodology, documented in full and written for teams that deliver in sprints and releases. Each page names the problem it solves, the steps, the decision aids and who owns each decision, and links to the essays its lessons came from.
Project Mechanics is how I manage the work: one part of how I solve business problems, alongside DevSpark for building the software.
Project Mechanics: The Overview
A 60-second walkthrough of the Project Mechanics framework — the origin, the art and science, the seven-state project life cycle, core disciplines, and where to start.
The Core Duality
Successful project management is part art, part science. Understanding the difference determines whether a methodology becomes a bureaucratic checklist or a genuine force multiplier.
The Art
The subjective dimension — the human layer that drives project success. It cannot be fully templated, only cultivated.
- Building trust with clients, staff, and management
- Reading the room in difficult conversations
- Knowing when to push and when to adapt
- Inspiring a team when the plan hits friction
- Communicating context, not just status
The Science
The objective mechanics — repeatable processes that create consistency, transparency, and accountability across every project.
- Seven-state project life cycle from Future to Complete
- Portfolio governance and project selection criteria
- Formal change control and scope management
- Chargeability, utilization, and realization tracking
- Structured kick-off, status reports, and closure procedures
The Project Life Cycle
Every project passes through a defined series of states. By making these states explicit, teams can plan, track, and communicate progress with precision — and portfolio managers can see across the entire organization at a glance.
The Practices
8 practices, grouped from the framework down to the people doing the work. Each page stands on its own and links to the essays its lessons came from.
Framework
The life cycle, the three failure modes and who owns each decision.
Product
Deciding what to build and finding out whether it worked.
Portfolio & Program
Choosing among projects and running related ones together.
Project & Release
Running the work and deciding what ships, and when.
Project Management
10 minRun the work between approval and close: estimate in ranges, plan slices that each ship value, hold the scope boundary, and keep risks visible.
Read articleSprint & Release
10 minCount the sprint back from release, freeze scope at D−5, gate every fix, and give the business owner a real choice of release paths while options exist.
Read articlePeople
Leading the team, changing how people work and handling conflict.
Leadership
9 minKeep ownership where the work is: define before delegating, tell blocked from stopped, help without rescuing, and absorb pressure from above.
Read articleChange Management
8 minChange how people work by naming the pressure, attaching a sponsor first, changing in steps, treating resistance as information, and measuring use.
Read articleConflict Management
8 minFind the structural cause of project conflict first, choose a strategy on purpose, say what yes means, and escalate with evidence and a record.
Read articleReference Library
Supporting materials for terminology and historical context.
Glossary
Essential Project Mechanics terminology, from accountability and authority to the release clock, scope freeze, fast follow and fix readiness gate.
OpenHistory
How Project Mechanics went from a 2002 consulting practice to a website that outlived it, and then to a delivery practice reworked for iterative teams.
OpenWhere to Start
Your best entry point depends on where you sit in the organization. Choose the path that fits your role.
For Project Managers
Start with the foundational framework, then execution, release decisions, and leading your team.
For Product Owners
Anchor the backlog to outcomes, then learn the release decisions you will be asked to make.
For Portfolio, Program & PMO Leaders
Choose and measure the portfolio, then the framework every project shares and how change lands.
For Engineering & Delivery Leads
Run the release clock, hold the scope boundary, and settle risk disagreements with the business.
For Team Leaders
Keep ownership where the work is, handle conflict by its cause, and change how people work deliberately.
For Training & Development
Work through every article in order for a complete curriculum-ready foundation.