Updated below the fold…

Still didn’t see it…

Poor Shatner, stop hitting yourself!

I think I have a new avatar, so get used to it! Or, hate me for it

1. Lock the features. QA can’t be done on a moving target. And while a live website is “never done” like a print edition, establishing and meeting defined goals produce better results than just throwing things at a server and seeing if they stick!

2. Load up the content. Pretty self-explanatory.

3. Launch. Establish the protocols for delivering and/or deploying the site in the proposal. Waiting until the end to find hosting or get DNS registrar credentials will only delay the result!

Why, oh why? I ask.

And, here is my prayer: make it stop.

Click on the link if you are semi-comatose and the sheer overload of pointless bouncing and blinking transitions will perk you right up!

Otherwise, you can learn a lot about what not to do with Flash by trying to watch the monstrosity that is the intro movie at that site. It’s not like I have anything against Flash, as I really like programming in ActionScript. And 10 years ago, I started animating in Flash (Terry Gilliam has nothing to fear, but I was definitely inspired by Monty Python).

Back in 2000, Jakob Nielsen wrote how bad Flash could be for web content, but in less than two years, Macromedia paid him off hired him as an information architectural consultant in an effort to turn things around. Unfortunately, that whole effort seems wasted on the developers of iccm.org.

Here, then, this is the usability sermon that the counter-reformation developers ICCM might understand:

Did ya catch that? Raymond Scott’s famous Powerhouse motif?

Yep. That’s the theme for me! Five guys playing harmonicas — that poor man at the end playing a chromatic arrangement of, what, like 12 harmonicas? That’s just icing on the cake!