Part Three: Making It Stick

A framework that works on paper but fails in practice is not a framework. It is a proposal.

Part Two described the structural elements of Firmitas - the governance model, the estimation approach, the risk and issues treatment, the delivery model, the quality and compliance practices, the team design principles, and the rest. Those elements are coherent. They are grounded in the failure diagnosis of Part One. They are designed to address the specific conditions that produce the specific failures this book is built around.

But coherence on paper and function in a real organisation are different things. Real organisations have history, politics, inertia, and incentive structures that were not designed with this framework in mind. Leaders who will need to change their behaviour to make the framework work may not yet know they need to change. Adoption attempts will go wrong in predictable ways. And the framework itself has limits - contexts in which it will not work, conditions under which it will be misused, and honest acknowledgements of what it cannot fix.

Part Three addresses all of this directly.

Chapter 24 is the hardest chapter in the book. It is addressed to the leader who recognises their own behaviour in what Part One described - the one who set the committed date, who noted the risk register, who applied the pressure that converted an honest estimate into a convenient one. It does not accuse. It diagnoses. And it describes, specifically, what changing that behaviour requires.

Chapter 25 provides the Firmitas Delivery Diagnostic - twenty-six questions that assess how a real programme compares to what the framework requires. The diagnostic is designed to be uncomfortable to answer honestly. That discomfort is useful. It points directly at where to start.

Chapter 26 catalogues the failure modes that occur when Firmitas is adopted without the philosophy behind it - when the process layer is installed while the system that produces the failure remains unchanged. These are the patterns to watch for in the first six months of any adoption attempt.

Chapter 27 addresses measurement - what to track, what to avoid tracking, and how to measure system health without creating the perverse incentives that most measurement systems generate.

Chapter 28 is the honest limits chapter. What Firmitas cannot fix. Who it is not for. The conditions under which it will fail even when applied sincerely and competently. A framework that cannot name its own failure modes is not credible.

Chapter 29 closes the book with the long view - what sustainable delivery looks like over years rather than programmes, and what it means to build an engineering organisation that can deliver well not just once but repeatedly, through personnel changes, market shifts, and the accumulated pressure of an industry that will always find new ways to ask for the impossible by Friday.

Part Three does not soften what Part One and Part Two have argued. It extends the argument into the territory that most frameworks avoid - adoption failure, honest limits, and the specific human and organisational reality of trying to change a system from inside it.

Read it with the same honesty that Part One asked for.