In fact, sometimes implementation details affect the original objectives. Take the Iraq “war” for example. Apparantly there were objectives now, as it’s being implemented, those objectives shifted. Maybe that’s a bad example. But, in programming, if someone says they want an “animation” that is actually an implementation detail–before you even get to Flash. An objective’s are more general goals and messages. An animation might solve the task to communicate a particular message.

Quite often I get clients who’ve jumped to the implementation way to early. Similarly, whenever someone begins to explain a project by telling me the opening animation sequence I know we’re in trouble. Actually, the best way to tell a story is to write the first part last. That way, you know where you’re headed.

Thanks,
Phillip

P.S. There you go again with the “old” thing.

If you talk technology…they lose control of the situation. If they can keep you talking abstract process concepts they feel safer and less threatened.

The best applications out there are designed and developed by the peeps who have a solid grasp of the technology and can leverage the intricacies against the business objective they understand.

Fuckin bollox.