Lesson 1: Stakeholders Change. Requirements Must Not.
In a 3-year government project, the minister changes, the secretary changes, and the project champion retires. We learned to document requirements so rigorously that any new stakeholder can be onboarded within a day — and cannot unilaterally redefine the project scope.
Lesson 2: Security Is a First-Class Feature
Government systems are high-value targets. Every deployment we make includes penetration testing, vulnerability scanning, and a formal security audit. We have turned down projects where we could not meet our own security standards.
Lesson 3: Training Is Half the Project
The most sophisticated system is worthless if staff cannot use it. We budget 20% of every government project for training, documentation, and change management. This number was learned the hard way.
Lesson 4: Build for the worst connection, the oldest browser, the slowest laptop. Government procurement cycles mean the hardware is always older than you expect.
Written by Nadeem Moeen
COO at BesTel Communications
