Most procurement failures begin before the tender is written. The requirement was wrong. The problem was misunderstood. The specification described a solution rather than a need. By the time anyone noticed, the contract was signed and the wrong thing was being delivered efficiently.
Define the Requirement covers the work that happens before procurement begins - the questions most professionals skip, the data that gets assumed rather than verified, and the conversations that should happen before a single requirement is written down.
At its centre is the Requirement Blueprint - a five-question framework that structures the requirement conversation and keeps the procurement anchored to what the organisation actually needs.
Every chapter includes war stories with imperfect endings and practical tools you can apply immediately.
Independently Published
979-8-1913-3137-9