Skip to main content

Google's Category Confusion

In my last entry, I wrote about Donald Norman's contention that Google is more "complex" than Yahoo, and that users like complexity. While I mostly disagree with Norman, I think his arguments raise some interesting questions about categories and some challenges for Google.

The crux of the issues is whether Google is a web search engine or a portal. Yahoo is a portal. Its primary business is as a central starting point to provide access to various content and services. As such, its front page is "busy" and contains many links in addition to a search engine.

As a search engine, Google is the market leader and a powerful brand. But Google is not the market leader as a portal.

Portals and search engines are different categories of products. Google as a brand can't be as successful straddling both categories as it can by focusing its brand on one category. To be most successful in search, it needs to keep the clean, search-oriented look of its front page. To be most successful as a portal, it would have to clutter its front page with links and addtional services.

Google does offer various services that don't fall squarely into the search category. Gmail, though it provides excellent search capabilities, is an e-mail client. Google Calendar is an impressive on-line application, but it's more of an organization tool than a search tool.

Some of these services are diluting Google's brand. They by no means cause people to view Google negatively, but they do have an effect on the extent to which people equate "Google" with "search".

Comments

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

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem