Skip to main content

Rumors of the death of newspapers have been greatly exaggerated

A lot has been said lately about the decline and fall of the newspaper industry. In the last week I've seen at least two TV interviews with newspaper publishers moaning that blogs (ahem) can't provide the same quality of reporting as they can. Yet, they give newspapers away for free, online, which seems to me to be a race to the bottom. If everything is free, how are readers supposed to value the reporting provided by newspapers over what they can get from the Huffington Post or (God forbid) Digg?

Look, if newspapers want to stay in business, they have to start charging money for online access. It's as simple as that. The trick is balancing revenue from subscriptions with revenue for online ads driven by "free" access. The NY Times ran an experiment a couple of years ago where they started charging for "prime" content such as the editorial pages. In the end they pulled the plug since they were losing hits. But the question is not how many hits - it's dollars per hit that matter. With web browsers like Firefox making it trivial to block online ads, a site can't continue to rely on ads alone to keep the business afloat.

This is going to require some creative pricing models. Personally I'd like to see newspapers make the current day's stories free, but require that you be a subscriber to access the archives. If I email a link to a story and the recipient doesn't read it that very day, well, too bad, they need to sign up to get access. A (generous) free trial period will lure people in. This model can work. I pay something like $5 a month for Angie's List yet I access the site only a couple of times a year. Mostly it's because the opportunity cost of not having access to the site is high when I need it (i.e., to find a good plumber when my dishwasher explodes). Same goes for sites like the NY Times. If someone emailed me a link to Bittman's latest recipe for chocolate chip waffles and I couldn't read it, I would just have to subscribe, now wouldn't I?

Another model would be to bundle access to a wide range of online publications together, much like you get when you sign up for cable or satellite TV. The NY Times, Boston Globe, WSJ, Wired, Salon, etc. should form subscription packages where you get access to all of the sites for "one low monthly payment." Just like I can't watch anywhere near all of the 200+ channels I get with my DirecTV subscription, most people can't consume all of this content, so it gives consumers the appearance of getting a lot more than they are paying for.

Newspapers aren't going anywhere fast. But they do need to get with the times and reset readers' expectations that you get what you pay for.

Comments

Popular posts from this blog

Why I'm leaving Harvard

The word is out that I have decided to resign my tenured faculty job at Harvard to remain at Google. Obviously this will be a big change in my career, and one that I have spent a tremendous amount of time mulling over the last few months.

Rather than let rumors spread about the reasons for my move, I think I should be pretty direct in explaining my thinking here.

I should say first of all that I'm not leaving because of any problems with Harvard. On the contrary, I love Harvard, and will miss it a lot. The computer science faculty are absolutely top-notch, and the students are the best a professor could ever hope to work with. It is a fantastic environment, very supportive, and full of great people. They were crazy enough to give me tenure, and I feel no small pang of guilt for leaving now. I joined Harvard because it offered the opportunity to make a big impact on a great department at an important school, and I have no regrets about my decision to go there eight years ago. But m…

Rewriting a large production system in Go

My team at Google is wrapping up an effort to rewrite a large production system (almost) entirely in Go. I say "almost" because one component of the system -- a library for transcoding between image formats -- works perfectly well in C++, so we decided to leave it as-is. But the rest of the system is 100% Go, not just wrappers to existing modules in C++ or another language. It's been a fun experience and I thought I'd share some lessons learned.

Why rewrite?

The first question we must answer is why we considered a rewrite in the first place. When we started this project, we adopted an existing C++ based system, which had been developed over the course of a couple of years by two of our sister teams at Google. It's a good system and does its job remarkably well. However, it has been used in several different projects with vastly different goals, leading to a nontrivial accretion of cruft. Over time, it became apparent that for us to continue to innovate rapidly wo…

Running a software team at Google

I'm often asked what my job is like at Google since I left academia. I guess going from tenured professor to software engineer sounds like a big step down. Job titles aside, I'm much happier and more productive in my new role than I was in the 8 years at Harvard, though there are actually a lot of similarities between being a professor and running a software team.

I lead a team at Google's Seattle office which is responsible for a range of projects in the mobile web performance area (for more background on my team's work see my earlier blog post on the topic). One of our projects is the recently-announced data compression proxy support in Chrome Mobile. We also work on the PageSpeed suite of technologies, specifically focusing on mobile web optimization, as well as a bunch of other cool stuff that I can't talk about just yet.

My official job title is just "software engineer," which is the most common (and coveted) role at Google. (I say "coveted&quo…