Intelligence is more useful when it has some idea where the world is.
Ask an AI where to have dinner and it can write a lovely paragraph.
Ask it where to have dinner near your hotel, before a concert, with parking, outdoor seating and a kitchen still open at 9:30, and geography suddenly becomes part of the intelligence problem.
The useful version of that question is rarely generic. It has a location, a time, a budget, a route, an opening hour and often one person in the group who has veto power over seafood.
Once those constraints appear, “intelligence” needs live information about the physical world—not just a talent for adjectives.
Maps gives information a place.
Weather gives that place conditions. Search gives it outside knowledge. Personal context can add preferences when a person chooses to share them. The useful experience is what happens when those capabilities cooperate.
That place can connect to weather, traffic, business information, events and the route between them. If a person chooses to add personal context, it can also incorporate preferences without requiring those preferences to become public facts.
The design challenge is making these layers cooperate without turning every local question into an excuse to collect more information than the task needs.
This is why we do not think of Maps as a side product.
Place becomes context for travel, local businesses, events, logistics, weather and eventually machine navigation.
Place is one of the basic coordinates of ordinary life. It shapes what “nearby,” “open,” “on the way,” “safe to drive,” “deliverable,” and eventually “navigable by a machine” actually mean.
Maps is useful today as a destination in its own right. It becomes more interesting as a shared capability underneath other experiences.
None of this requires the user to know which division answered which part.
In fact, if they have to know, we probably designed it wrong.
If someone asks for a coffee shop near the train station before rain starts, the system can combine place and weather without asking the person to perform a small organizational merger first.
That is the larger eFind idea in miniature: different capabilities, one objective.
The destination is the objective.
The products should know when to get out of the way.