The Satellite Imagery Feature

You're running Google Maps, which has already launched successfully and has millions of users. The core product works well - people can search for locations, get directions, and view maps. Engagement is solid and growing.

Google recently acquired Keyhole (which would become Google Earth), and your team now has access to satellite imagery of the entire planet. This is pretty cool technology - people can see aerial views of Earth from space.

Your team is debating whether to integrate satellite imagery into Google Maps. Some considerations:

Arguments for:

• It's technically impressive and novel
• Users have never seen their house from space before
• Could generate buzz and media attention
• The technology is available - why not use it?

Arguments against:

• It's not core to the job users hire Maps for (navigation, directions)
• It's a one-time novelty - after you see your house once, then what?
• Engineering resources are limited - should focus on improving core navigation
• Could distract from more important features like real-time traffic

The feature isn't strictly necessary for the product's core value proposition. It's more of a 'nice to have' than a 'must have.' Some team members worry it's a gimmick that diverts attention from real product work.