I liked a lot alorza’s commandment for eGov 2.0: “don’t create web2 applications in vain”
I would suggest another one: “never present and eGov project in a public meeting without mentioning its COST and its TAKE-UP”
I am fed up with presentation of idea and projects, indicating objectives and potential benefits.
Cost and usage are two essential data, which are ALWAYS available to the project manager – no data collection required. And they address the 2 critical points of eGovernment (high cost and low take-up).
Of course data on real impact would be more important, but they require additional effort for data collection and analysis.