Why bother advertising a meeting if it's not open to the public? That's like me issuing a press release saying "Family meeting, 7.30, around the dinner table. We're going to talk about the state of the bathroom." Of course, Wednesday's papers will follow up the story with photos of Hessa al-Jaber shaking some guy's hand. There won't be any details of what was discussed - just a photo and a repeat of the purposes of the meeting. Grr.
Given that I'm not invited, here are my suggestions. The important ones are non-technical.
- Scatter the money around. Don't spend millions on a single project to do everything - it will fail, and all your money will have been wasted.
- All initial projects should be finished within three months. A two-year project will fail, and you will be two years behind schedule.
- After three months, see who's got something working - give them more money and more responsibility. Stop funding the projects that haven't achieved anything; look for new small projects instead.
- Replace the leaders of failed projects. Publicise the successful projects.
- Insist on compliance to internet standards. If someone is using an ActiveX control, Macromedia Flash, or non-validating HTML, take away their money. They don't understand the web, and eventually you will be embarrassed if people believe their solution is representative of the State of Qatar.
- Insist that people use a free database in their solutions. It saves on costly licenses for still-born projects, and the database code will be cleaner if programmers believe they need to swap from MySQL to Oracle at a later date.
- Apart from following internet standards, and using free databases, don't enforce any other standards. In particular, enforcing Microsoft products will halve your pool of talented programmers; enforcing project management and system analysis methodologies will double the bureaucratic overhead. Both of these will encourage failure.