Skip to main content

Easter Eggs

Want to get people talking about your product? One way to get people talking is to include "Easter eggs" in your product. An Easter egg is a hidden feature that surprises and delights, but isn't necessarily useful or consistent with the core purpose of the product.

When someone discovers an Easter egg, they are likely to spread word about it to their friends. "Hey, look what I found."

An Easter egg that my friend Sonia recently passed along is in Google Maps:
  1. Go to
  2. Click 'Maps'.
  3. Click 'Get Directions'.
  4. Enter 'New York, New York' to 'Paris, France'.
  5. Read line #23.
Sometimes developers include Easter eggs as a private joke, unbeknownst to you or your product manager. In other cases, Easter eggs are a deliberate means of generating word of mouth.


AlanAJ said…
You'll note that the journey takes "about" 29 days 7 hours. Just swimming the Atlantic in that time, non-stop, gives you an average speed of 5 miles an hour.

By the way, Google Maps UK has this "Easter Egg" at step 15. The Brits are advised to take a slightly longer (47 miles), slightly simpler (?) route.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware