More on Destination, Identity, and the Future of Content

Thanks no doubt to a helpful boost from Alexis Madrigal, my November 8 post, “The Future of Content Is Not Destination but Identity,” found a passel of new readers this week. One of them was constructively skeptical of my argument.

What does it really mean, he asked, to say the future of content is in its identity? Or that content must be imbued with the brand? However people find content, he argued, they “always wind up back at the brand to read it.” He also took issue with my suggestion that the container—the original site of publication—doesn’t matter anymore. As he pointed out, it does matter “if you want to keep people hanging around on your site reading more beyond the link that brought them there.”

Because his objections are too good to leave in the obscurity of a comment on a week-old entry, and because my MUD obligations limit the amount of time I can spend on this blog, I’m addressing his comment in today’s post.

It’s possible, of course, that I overstated my case considerably, which one is wont to do when blogging. But people don’t always wind up back at the brand to read content. Like my commenter, I read a lot of content in my RSS reader. But unlike him, I don’t go back to the source to read most of it. Thus, for me, the experience not only divorces the content from its original container, but also strips away much of its original formatting. Others may read content through Instapaper or Flipbook, which can similarly deracinate content. And I think this way of reading will only grow more common with time. (UPDATE: That should be Flipboard. And reading through it just now, I realized it actually does a good job of preserving original branding.)

It was certainly rhetoric more than conviction that prompted me to say that containers don’t matter anymore. Done well, they can still lure readers in and keep them hanging around. But containers are not nearly as good at containment in the digital era as they were in the analog. Because it is so easily copied and transmitted, content (not to mention readers) now can much more readily drift away.

When I suggested that, in response, content must be imbued with brand, I was again, no doubt, overstating. Publishers are obviously free to let their content wander off like wayward dogies without any identifying brand on their flanks. But a publisher concerned with promoting and propagating its brand would be wise to ensure that the content carries some form of brand identity. That can be done in a variety of ways: instilling a brand voice into the content (The Atlantic was once superb at this—you could always recognize its voice, no matter the author), incorporating brand references (Wired‘s Wired vs. Tired, for instance), or employing an identifiably distinctive point of view (Reason, perhaps?).

It used to be that publishers and their editors didn’t have to worry so much about this problem. When an article was contained within a print magazine, the context was enough to brand the content. But online, that context is much weaker. To me, at least, infusing your brand directly into your content seems like a smart response.

3 Traits of Editorial Success

MUD day 7:

Editors should be pleased by Malcolm Gladwell’s review in the latest New Yorker of Walter Isaccson’s Steve Jobs biography. In it, Gladwell argues that Jobs’s peculiar genius was not so much creative in nature as editorial. His sensibility, Gladwell writes, “was editorial, not inventive. His gift lay in taking what was in front of him . . . and ruthlessly refining it.”

As I thought about the characteristics of Jobs’s genius after reading Gladwell’s review, I realized that in fact some of them are shared by successful editors. Though there may be more, here are three that came to mind immediately.

1. Trusting your own intuition more than user research. As noted in The New York Times obituary, Jobs preferred his own research and gut instinct to focus groups: “When asked what market research went into the iPad, Mr. Jobs replied: ‘None. It’s not the consumers’ job to know what they want.’”

I learned the same lesson early in my editorial career in a seminar given by the estimable Pierce Hollingsworth. There’s no point in asking readers what they want, he said. They don’t know. It’s the editor’s job to figure that out on their behalf. Research might get you part way there, but in the end, it’s an editor’s intuition and judgment that finish the job.

2. Changing your mind. Like Emerson, Jobs believed that a foolish consistency is the hobgoblin of little minds. He was famous for making blanket statements like “no one wants to watch video on an iPod” only to reverse himself later. His flexibility was one reason Apple was able to dominate its industries for so long. Likewise, to be great at their craft, editors not only need strong opinions, but need to alter them when the facts prove them wrong.

3. Knowing but not worshipping the rules. In his review, Gladwell quotes Steve Jobs on the genesis of the Apple slogan, Think different:

“We discussed whether it was correct before we ran it. It’s grammatical, if you think about what we’re trying to say. It’s not think the same, it’s think different. Think a little different, think a lot different, think different. ‘Think differently’ wouldn’t hit the meaning for me.”

Jobs, of course, was right. People who let the rules master them would say, oh no, it should be “Think differently.” But those, like great editors, who master the rules, know better.

The parallels between the basis of Jobs’s success and that of great editors can only be taken so far. But there is, well, one more thing. As Gladwell implies, Jobs was ruthless. Though it’s not a personality trait that serves editors well, in their work, a touch of ruthlessness, a soupçon of Jobs-like jerkiness, is sometimes a necessity. Editors who aren’t willing to offend will never achieve their potential.

Embrace Your Errors

MUD day 5:

When I embarked on this month of daily, rapidly written blog posts, I knew my tolerance for typos and other errors would be sorely tested. And indeed, yesterday I committed one of the homophonically confused errors I’ve made since the beginning of my publishing career, writing “died-in-the-wool” rather than “dyed.”  Once I might have been upset by the discovery of my mistake, but my recent reading has persuaded me that a few errors now and then, once recognized, can be good for both readers and writers.

In this morning’s Los Angeles Times, the editors published a note under the headline “Didn’t anyone edit this?” As the paper’s “reader representative” Dierdre Edgar wrote, “When readers write in about errors, it shows they care, and that’s a good thing.” While there are other ways of getting readers to interact with you, the occasional mistake can be good for a writer’s engagement with readers.

But there’s a better reason for writers not to feel too bad when realized they’ve goofed: It’s a valuable learning experience. I’ll leave the last word on this to Kathryn Schulz, a writer I discovered only yesterday through a wonderfully written New York Times review of Haruki Marukami’s new novel 1Q84.  In her book, On Being Wrong, Schulz eloquently explains why the occasional error is not only tolerable, but beneficial:

Far from being a sign of intellectual inferiority, the capacity to err is crucial to human cognition. Far from being a moral flaw, it is inextricable from some of our most humane and honorable qualities: empathy, optimism, imagination, conviction, and courage. And far from being a mark of indifference or intolerance, wrongness is a vital part of how we learn and change.

Innocent and Malignant Typos and the Case of Filloux v. Jarvis

Picture of a fainting heroine

Overdosed on typos?

As one who cares more than he should about such things, I’ve been spending way too much time today mulling over Rob O’Regan’s recent post on eMedia Vitals, “Can you spare 15 minutes in the battle against typos?”.

Like O’Regan, I suspect, I have an unhealthy sensitivity to typographical errors. To this day, I’m still suffering post-typographic stress from the discovery 27 years ago that in my first published book review, for the Nashville Tennessean, I asserted that the novel’s protagonist died from an overdose of “heroine.”

Much of the pain of that error came from the fact that it was permanent. That day’s press run was done forever. The only comfort I could take was in the knowledge that few people would read the review, fewer would notice the mistake, and all would throw the paper out a few days later.

In today’s online media, of course,  it’s easy to repair such mistakes (as I’ve done in my archived version of that fateful book review). What’s odd is how few people bother. Though O’Regan is too nice to name the writers or publications, he notes that three of the four errors he cites have yet to be corrected, several days after publication. (Me, I’m not so nice: Come on, Stefanie Botelho and Folio: magazineSilicone Valley is almost as embarrassing as heroine.)

In those rare moments when I can look at them dispassionately, I can see that most typos are innocent. Some people will be amused by Silicone Valley; no one is hurt by it.

But there’s another class of typos that, left uncorrected, suggest a subtle malignity. For the reader, they are indications that the writer’s argument might not be trustworthy. A recent example, for me, is Frédéric Filloux’s critique earlier this month of a Jeff Jarvis blog post on the status of the article in journalism.

In my opinion, Filloux simply gets it wrong. I could respect his view, however, if I thought he was actually trying to get it right. But a critical typo, uncorrected now for nearly two weeks, suggests that he isn’t trying, and worse, that he doesn’t care to. “To support his position,” Filloux writes, “Jarvis mentions Brian Settler’s coverage of the Joplin tornado.”

Settler? Nope. The New York Times reporter’s last name, of course, is Stelter.

Is failing to spell Stelter’s name correctly an innocent mistake? Maybe at first (though even then it’s a sign of carelessness). But after two weeks, it starts to fester. It would undercut even the most thoughtful argument, not just Filloux’s impulsive rant.

In a subsequent attack on Jarvis’s advocacy of process journalism, Filloux says, “personally, I’d rather stick to the quest for perfection rather than embrace the celebration of the ‘process.’” I would suggest to M. Filloux that the quest for perfection begins at home.

Fortunately, it’s not too late. As Jarvis says in a comment on Filloux’s post, “publish first and correct later has *always* been the rule, except now we can publish earlier and correct sooner.”

Should you care as much as I do about typos? I don’t recommend it. To be a productive writer, you need a tolerance for innocent slip-ups. But if you care about the truth—not to mention perfection—you’ll make sure they don’t turn into malignant ones.

Should You Edit Guest Posts? 5 Tips for Better Copy

There’s wide agreement in the blogging world about the benefits of guest posts, both for the guest blogger and the blog owner. There seems to be less consensus, however, about the logical next question: If you use guest posts, should you edit them?

In a way, I’m asking a trick question. As I explain below, the moment you accept an article, you’ve already started to edit it. Not to finish the job would do a disservice both to your guest blogger and to yourself.

The real question, then, is just how much editing you should do. To judge by the quality of many guest posts I read, the answer too often seems to be: little or none. Publishing a guest post exactly as it comes to you might seem the easiest way to proceed, but it’s a false economy. By following the five editorial principles below, you can maximize the appeal and impact of guest posts while minimizing your effort.

Give fair warning. If you plan to use guest posts on your blog, you should publish submission guidelines. If nothing else, it’s a great way of signaling that you welcome contributions.  But more importantly, by setting the ground rules and expectations clearly in advance, guidelines serve an important editorial function. When you let writers know what you need, they’ll do some of the editing for you.

It’s important, though, to keep the tone of your guidelines positive. The point isn’t to scare contributors off but to give them a helping hand. Good examples of clear but encouraging guidelines can be found on Copyblogger and ProBlogger; sound advice on how to write them is offered by One Stop Blog and Men with Pens.

If you only use guest posts on rare occasions, you don’t need published guidelines. But you should agree in advance with a guest blogger about how you will handle the copy, what publishing rights you are acquiring, and so on. The last thing you want is an unhappy guest blogger.

Choose wisely. Of all editorial activities, the most important is the decision whether to accept or reject a submission. When you publish a blog post, you are taking on legal and ethical responsibility for it. You don’t need to agree with your guest blogger’s point of view—in fact, it’s a good idea to look for a point of view that challenges yours. But you do need to make sure that it comports with the editorial mission of your blog.

Even if a guest post suits your mission, it may not warrant publication. If it seems too obvious, simply repeats other posts you’ve published, or will require too much work to make publishable, you may want to turn it down.

Above all, don’t agree to publish something before seeing it. Allow yourself leeway to turn something down once you’ve read it. It’s possible to reject a guest post gracefully and without creating hard feelings, but only if you haven’t already promised to use it.

Tidy up. At the very least, you must look for and fix typos and grammatical errors in guest posts. It’s one thing not to do this for your own writing: you have only yourself to blame. But you owe it to guest bloggers to show off their work in the best possible light by cleaning up obvious writing goofs. If your own grammar ain’t so hot, find a proofreader. There are plenty of good ones looking for work.

Avoid salvage operations. Once you’ve made the obvious fixes, you may see other changes that could improve the post. If they are relatively simple, you can suggest them to the author. But beware attempting too much reconstruction. I know from many years of rescuing submissions for B2B publications that with enough work you can make almost anything publishable. But the cost is high, and most of the time, you should avoid the effort. You’ll generally do better finding another author or writing your own post.

Ask for approval, not forgiveness. Editing is a collaborative art. No matter what changes you make to a guest post, whether it involves a single punctuation mark or a total makeover, you should allow your contributor to review the edited copy before publication. Most of the time, your contributors will be thankful for the fixes. But when they’re not, it’s better to find out before you click the “publish” button.

When you publish a guest post, you’re hoping to benefit yourself, your reader, and your contributor alike. A little thoughtful editing will help make sure you succeed.


Are you looking for a guest blogger? Or would you like to write for B2B Memes? Let me know.