Archive for the 'google' Category

Positioning real-time web platforms

Like many people, I’ve been thinking a lot about the live nature of the web more and more recently.

The startup world has gone mad for it. And though I think Microsoft’s Chief Software Architect Ray Ozzie played down the depth of Microsoft’s commitment to it in his recent interview with Steve Gillmor, it’s apparent that it’s at the very least a top-of-mind subject for the people at the highest levels of the biggest companies in the Internet world. As it should be.

The live web started to feel more tangible in shape and clearer for me to see because of Google Wave. Two of the Guardian developers here, Lisa van Gelder and Martyn Inglis, recently shared the results of a DevLab they did on Wave.

My brain has been spinning on the idea ever since.

(A DevLab is an internal research project where an individual or team pull out of the development cycle for a week and study an idea or a technology. There’s a grant associated with the study. They then share their findings with the entire team, and they share the grant with the individual who writes the most insightful peer review of the research.)

Many before me have noted the ambition and tremendous scale of the Wave effort. But I also find it fascinating how Google is approaching the development of the platform as a service.

The tendency when designing a platform is to create the rules and restrictions that prevent worst-case scenario behavior from ruining everything for you and your key partners. You release capability gradually as you understand its impact.

You then have to manage the constant demand from customers to release more and more capability.

Google turned this upside down and enabled a wide breadth of capability with no apologies for the unknowns. Developers won’t complain about lack of functionality. Instead it will probably have the opposite effect and invite the developers to tell Google how to close down the risks so their work won’t get damaged by the lawlessness of the ecosystem.

That’s a very exciting proposition, as if new land has been found where gold might be discovered.

But on the other hand, is it also a bit lazy or even irresponsible to put the task of creating the rules of the world that your service defines on the customers of your service? And do those partners then get a false sense of security because of that, as if they could influence the evolution of the platform in their favor when really it’s all about Google?

Google takes no responsibility for the bad things that may happen in the world they’ve created, yet they have retained full authority on their own for decisions about the service.

They’ve mitigated much of their risk by releasing the code as “open source” and allowing Wave to run in your own hosted environment as you choose. It’s a good PR move, but it may not have the effect they want it to have if they aren’t also sharing the way contributions to the code are managed and sharing in the governance.

They list the principles for the project on the site:

  • Wave is an open network: anyone should be able to become a wave provider and interoperate with the public network
  • Wave is a distributed network model: traffic is routed peer-to-peer, not through a central server
  • Make rapid progress, together: a shared commitment to contribute to the evolution and timely deployment of protocol improvements
  • Community contributions are fundamental: everyone is invited to participate in the public development process
  • Decisions are made in public: all protocol specification discussions are recorded in a public archive

Those are definitions, not principles. Interestingly, there’s no commitment to opening decision-making itself, only sharing the results of decisions. Contrast that with Apache Foundation projects which have different layers of engagement and specific responsibilities for the different roles in a project. For example,

“a Project Management Committee member is a developer or a committer that was elected due to merit for the evolution of the project and demonstration of commitment. They have write access to the code repository, an apache.org mail address, the right to vote for the community-related decisions and the right to propose an active user for committership.”

That model may be too open for Google, but it would help a lot to have a team of self-interested supporters when things go wrong, particularly as there are so many security risks with Wave. If they are still the sole sponsor of the platform when the first damage appears then they will have to take responsibility for the problem. They can only use the “we don’t control the apps, only the platform” excuse for so long before it starts to look like a cop out.

Maybe they should’ve chosen a market they thought would run with it and offer it in preview exclusively for key partners in that market until Google understood how to position it. With a team of launch partners they would have seemed less autocratic and more trustworthy.

Shared ownership of the launch might also have resulted in a better first use-case app than the Wave client they invented for the platform. The Google Wave client may take a long time to catch on, if ever.

As Ray Ozzie noted,

“When you create something that people don’t know what it is, when they can’t describe it exactly, and you have to teach them, it’s hard…all of the systems, as long as I’ve been working in this area, the picture that I’ve always had in my mind is kind of three overlapping circles of technology, social dynamics, and organizational dynamics. And any two of those is relatively straightforward and understandable.”

I might even argue that perhaps Google actually made a very bad decision to offer a client at all. This was likely the result of failing to have a home for OpenSocial when it launched. Plus, it’s never a good idea to launch a platform without a principle customer app that can drive the initial requirements.

In my opinion, open conference-style IM and email or live collaborative editing within docs is just not groundbreaking enough as an end-user offering.

But the live web is fractionally about the client app.

The live web that matters, in my mind, harnesses real-time message interplay via multiple open networks between people and machines.

There’s not one app that runs on top of it. I can imagine there could be millions of client apps.

The Wave idea, whether it’s most potent incarnation is Wave itself or some combination of a Twitter/RabbitMQ mesh or an open XML P2P server or some other new approach to sharing data, is going to blow open the Internet for people once again.

I remember trying very hard to convince people that RSS was going to change the Internet and how publishing works several years ago. But the killer RSS app never happened.

It’s obvious why it feels like RSS didn’t take off. RSS is fabric. Most people won’t get that, nor should they have to.

In hindsight, I think I overvalued RSS but undervalued the importance of the idea…lubricating the path for data to get wherever it is needed.

I suspect Wave will suffer from many of the same issues.

Wave is fabric, too.

When people and things create data on a network that machines can do stuff with, the world gets really interesting. It gets particularly interesting when those machines unlock connections between people.

And while the race is on to come up with the next Twitter-like service, I just hope that the frantic Silicon Valley Internet platform architects don’t forget that it’s about people in the end.

One of the things many technology innovators forget to do is to talk to people. More developers should ask people about their day and watch them work. You may be able to breakthrough by solving real problems that real people have.

That’s a much better place to start than by inventing strategic points of leverage in order to challenge your real and perceived competitors.

Building markets out of data

I’m intrigued by the various ways people view ‘value’. There seem to be 2 camps: 1) people who view the world in terms of competition for finite resources and 2) people who see ways to create new forms of value and to grow the entire pie.

Umair Haque talks about choices companies make that push them into one of those 2 camps. He often argues that the market needs more builders than winners. He clarifies his position in his post The Economics of Evil:

“When you’re evil, your ability to co-create value implodes: because you make moves which are focused on shifting costs and extracting value, rather than creating it. …when you’re evil, the only game you want to – or can play – is domination.”

I really like the idea that the future of the media business is in the way we build value for all constituencies rather than the way we extract value from various parts of a system. It’s not about how you secure marketshare, control distribution, mitigate risk or reduce costs. It’s about how you enable the creation of value for all.

He goes on to explain how media companies often make the mistake of focusing on data ownership:

“Data isn’t the value. In fact, data’s a commodity…What is valuable are the things that create data: markets, networks, and communities.

Google isn’t revolutionizing media because it “owns the data”. Rather, it’s because Google uses markets and networks to massively amplify the flow of data relative to competitors.”

I would add that it’s not just the creation of valuable data that matters but also in the way people interface with existing data. Scott Karp’s excellent post on the guidelines for transforming media companies shares a similar view:

“The most successful media companies will be those that learn to how build networks and harness network effects. This requires a mindset that completely contradicts traditional media business practices. Remember, Google doesn’t own the web. It doesn’t control the web. Google harnesses the power of the web by analyzing how websites link to each other.”

Ad networks vs ad exchanges

I spent yesterday at the Right Media Open event in Half Moon Bay at the Ritz Carlton Hotel.


Right Media assembled an impressive list of executives and innovators including John Battelle of Federated Media, David Rosenblatt of DoubleClick, Scott Howe of Microsoft, entrepreneur Steve Jenkins, Jonathan Shapiro of MediaWhiz, Ellen Siminoff of Efficient Frontiers, and Yahoo!’s own Bill Wise and the Right Media team including Pat McCarthy to name a few.

It was an intimate gathering of maybe 120 people.

Much of the dialog at the event revolved around ad exchange market dynamics and how ad networks differ from exchanges. DoubleClick’s Roseblatt described the 2 as analagous to stock exchanges and hedge funds…there are a few large exchanges where everyone can participate and then there are many specialized networks that serve a particular market or customer segment. That seemed to resonate with people.

The day opened with a very candid dialog between Jerry Yang and IAB President Randall Rothenberg where Jerry talked about his approach to refocusing the company and his experiences at Yahoo! to date.

Battelle’s panel later in the afternoon was very engaging, as well. The respective leaders of the ad technology divisions at Yahoo! (Mike Walrath of Right Media), Miscrosoft (Scott Howe of Drivepm and Atlas) and Google (David Rosenblatt of DoubleClick) shared the stage and took questions from John who, as usual, didn’t hold back.

The panelists seemed to have similar approaches to the exchange market, though it seems clear that Right Media has a more mature approach, ironically due in large part to the company’s youth. Microsoft was touting its technology “arsenal”. And DoubleClick wasn’t afraid to admit that they were still testing the waters.

I also learned about an interesting market of middlemen that I didn’t know existed. For example, I spoke with a guy from a company called exeLate that serves as a user behavior data provider between a publisher and an exchange.

There were also ad services providers like Text Link Ads and publishers like Jim Mansfield’s PhoneZoo all discussing the tricky aspects of managing the mixture of inventory, rates and yield, relationships with ad networks, and the advantages of using exchanges.

I’ve been mostly out of touch with the ad technology world for too long.

Our advanced advertising technology experiments at InfoWorld such as behavioral targeting with Tacoda, O & O contextual targeting services like CheckM8, our own RSS advertising, lead generation and rich media experiences were under development about 3 years ago now.

This event was a great way to reacquaint myself with what’s going on out in the market starting at the top from the strategic business perspective. I knew ad exchanges were going to be hot when I learned about Right Media a year ago, but I’m even more bullish on the concept now.

Gatekeepers need to stop calling themselves gatekeepers

Time business columnist Justin Fox questioned the success of the new media methods in a recent post “The reign of the enthusiasts“.

He suggests the algorithms that proudly surface the deep dark corners of the Internet are actually just self-referential popularity contests. When searching for his name Justin found that the articles he’s written that are likely most influential in the real world fail to rank higher than the articles he’s written which attracted the most link love from media-obsessed blogger types, like myself.

“There are web2topians out there–Battelle and my friend Matt McAlister immediately spring to mind–who are convinced that the Googles (and Diggs and del.icio.uses and Amazons and Last.fms) of the future will do a vastly better job of steering people to what they want, such a good job that most of the gatekeepers of the current media universe will prove wholly extraneous.”

This isn’t the first time someone has accused me of being a Web 2.0 blogger. Coincidentally, the same day Justin posted this, I was mocked by a local construction worker waiting for the bus with his buddies as I passed on my way to the office. He shouted to nobody in particular,

“Man, you know what I hate? Dotcommers.” He watched me walk by stonefaced and waited for a response. The guys standing around him turned to look. Unsure still, he blurted out, “Architects, too. Hate all of them.” He got the laugh he was looking for.

Jeez, am I that boring? Or that obvious and annoying? (Please don’t say anything. I think I know the answer.)

Anyhow, Justin’s question is top-of-mind for a lot of people in the media business. Where I disagree with him and the wisdom of the media industry crowd is on the notion of “gatekeepers” or rather the need for them at all.

Perhaps the most important part of being successful in media is distribution, and the reason we’re asking what the role of the gatekeeper is today is because the Internet has disintermediated the media distribution models that helped them become gatekeepers in the first place.

Online search changed the way people access relevant information, and those who once thought of themselves as gatekeepers suddenly found themselves at the mercy of the link police, the new gatekeepers, the search engines.

Yet, Justin’s explanation of the weakness of Google’s algorithm is exactly what I think many people who get mocked for their trendy glasses, old man sport coats, carefully orchestrated facial hair events, designer shoes and man purses (I don’t have a man purse) all see improving with the introduction of explicit and implicit human data into the media distribution model. The act of hyperlinking to a web page is not a strong enough currency to hold together a market of information as big as the Internet has become in recent years. It’s a false economy.

But the link currency opened the door to the idea of using behavior to help people find things. I love Last.fm not just for the music it recommends to me but because it proves this to be true. The Internet is made of people, people with a wide range of knowledge, tastes, and interests.

Now, there will always be a role for experts, and there are many cases where being an expert is not just subjective. Experts are hugely influential on the Internet as they are in other media. But I don’t see that a gatekeeper is an expert by definition.

There will also always be a role for enablers. Good enablers are often community builders who understand the rhythms of human psychology and emotion. Henry Luce was such a man, and I think he might have been a very successful web2topian today.

If those who call themselves “gatekeepers” want to share their expertise in valuable ways, then they will need to understand how the role of human data helps with distribution of that expertise. If those who aim to be enablers of communities want to be relevant, they will find ways to do that in many of the social technologies that have proven successful in this new world.

Similarly, if the people Justin affectionately refers to as web2topians appear smug, glib or arrogant when talking about media, then they are only doing themselves and everyone in the business a disservice. Gatekeepers know better than anyone that expertise does not by definition make you important. That’s a lesson the Internet generation will learn the hard way when someday they become irrelevant, too, I’m sure.

Friday fun: The Daily Show on the Viacom vs YouTube dispute