Procuring technology well: requirements are a leadership responsibility
Many failed technology projects were lost at procurement, when requirements were copied from a vendor brochure rather than written from the organization's own work.
- Author
- Strategy & Transformation PracticeGayduo Advisory
- Published
- Reading time
- 1 min
- Topic
- Advisory

Public institutions and large organizations buy most of their technology through formal procurement. The process is designed to be fair and auditable. It is not designed to ensure that the organization buys what it needs — that depends on the requirements it publishes.
Describe the work, not the product
Strong requirements describe the organization's processes, volumes, users, constraints and outcomes. Weak requirements list features, often borrowed from a product the author has seen. The first invites solutions; the second invites the vendor whose brochure was borrowed.
Evaluate what will matter in year three
Who owns the data, and in what format can it be exported?
What does the organization need to change the system without the vendor?
What are the full costs over five years, including licences, hosting and support?
How does the system behave with the connectivity and power available on site?
These questions are rarely weighted heavily in evaluation criteria, yet they decide whether a system is still useful once the implementation team has gone. Getting them right is a leadership responsibility, not a procurement formality.


