The case for easter eggs (and other clever user treats)

My previous post on user treats drew some arguments both for--and passionately against easter eggs in software. But in each of the arguments against easter eggs, the reason is virtually the same: "Why the hell are you spending your time creating these "surprises" when you haven't even bothered to fix the glaring bugs?"

So let's get this out of the way right now...

* Until you've nailed the fundamentals--the things users want, need, and expect--don't bother trying to "surprise and delight" users. That just pisses 'em off.

* A good easter egg is a playful, hidden or disguised feature that, when discovered, can offer surprise, delight, entertainment, humor, novelty, or an "I Rule" experience. (Via Creating Passionate Users)