Avoiding easy

When you spend all day working with the same piece of software your definition of what is easy for someone else becomes horribly skewed. Since I started jamming with the CoPress gang in 2009, I have spent thousands of hours staring at a WordPress dashboard. It means much of the WordPress interface is easy for me. That’s dangerous.

I try to minimize the number of times I use easy in a support reply. I avoid phrases like “Setting up custom menus is easy…” or “Writing a new post is easy…” There are a few reasons for this.

First, if a feature or product were legitimately easy the user would not be writing in to support about how stuck they are. Sure, some percentage of users will find questions to ask about any interface. But do you want to start the conversation by assuming the user falls into that percentage? You venture to learn much more if you assume the software is wrong, not the user.

Second, describing something as easy sets a dangerously high bar for the user when they walk away and try it for themselves. Before you characterize a feature as easy you should be certain it actually is. If you say “easy” and the user does not get it they will, at best, feel like they are wasting your time and, at worst, feel like it is not worth using your product.

Finally, the worst part about saying a product is easy is that it immediately starts the conversation by putting you in command. You are the expert. You are the one who said it was easy. In some cases that is okay. It will work out. But doing so shuts down your opportunity for learning from your users. If, instead, you think back to the days when you did not know everything, you can start the conversation on an equal ground. Help the user accomplish their goal but also learn about where the pain points are so that you can make the user’s experience, and your product, better.

The best support is a conversation. The best support happens when a user learns how to do something new and you learn about how your product can be better. This can only happen when you do not immediately think of your software as easy, intuitive, or simple. If you can remember that you too were once new to things you will end up with a better product and, most importantly, happier users.

Blogs, term papers, and a fear of what’s new

Cody Brown tweeted a link to this New York Times article earlier today about blogs and term papers. It’s a fairly shallow piece with many things I’d enjoy responding to, but I’ll pick one: the patronizing way the old guard portrays newer forms of writing.

Here are two quotes from that article. The first is from Douglas B. Reeves, a columnist for the American School Board Journal:

It doesn’t mean there aren’t interesting blogs. But nobody would conflate interesting writing with premise, evidence, argument and conclusion.

The second is from William H. Fitzhugh, founder of The Concord Review:

Writing is being murdered. But the solution isn’t blogs, the solution is more reading. We don’t pay taxes so kids can talk about themselves and their home lives.

Fitzhugh and Reeves aren’t engaging with the idea of blogs from an academic or evidence-based perspective. They seem to fearful of the new medium and seek to discredit it with all the tact of a gossip writer.

“We don’t pay taxes so kids can talk about themselves and their home lives” is a great soundbite, but it is ridiculous. First, are we so sure there is something wrong with giving kids an outlet to write about themselves and their home life? Second, what does it matter what the output is if the learning that happens in the process of getting there is substantial? I think Fitzhugh and Reeves are far too concerned with the potential output of these blogs than they are with what kids may learn by writing in a medium they enjoy.

If you want to say that blogs have, through research, been the cause of decreasing critical thinking among students that is fine. Merely asserting it does not make it so, though. You need evidence to back your claims, just like the term papers Reeves and Fitzhugh glorify.

If, instead, you are going to characterize the only benefit of blogs as the fact that some are “interesting” and imply that “premise, evidence, argument and conclusion” are only achieved through dead tree term papers, then you are full of it.

These two would be better off taking Reeves’ advice and using premise, evidence, argument, and conclusion to analyze writing on the web.

Scaling my long-form writing

Earlier Daniel asked me about starting a blog circle of sorts to help each other work on longer form writing that requires research, editing, and more careful thought. I think it’s a great idea. There’s a few things that I’d love to explore in more depth here that I don’t have a good structure in place for right now.

A benefit to attending a liberal arts school like Whitman was the sheer amount of writing I did every semester. Many classes required 4 papers a semester each of 5-7 pages. It meant I was writing something almost every week.

Since graduating the frequency of writing I’ve done has gone up drastically. Whether it’s on this blog or in my work at Automattic I’m writing far more and in far more varied contexts than I ever have before. That’s fun. What I’m not doing is the type of sustained, long-form writing that causes me to dig deeper and push my abilities. That’s also fun but is more difficult to do on a blog than as part of coursework.

There’s a few ideas that have been kicking around in my head that may fit for getting back into the swing of things with research and in-depth writing.

First, I’ve been thinking more about how news organizations need to think of themselves as crafting a product. It’s something I’ve written about before and is something I’d love to dive more deeply into. There could be an interesting line to trace here between the history of news publications and the growth of technology companies that more readily grok what it means to create a product.

Second, it’d be great to spend more time researching how WordPress can play a role in a rebooted school system. I think our current system of schooling is on its way out. Something may take its place and I think WordPress can, and in many cases probably is, playing a role here. Collecting those stories and theorizing a bit about what a more sustainable school system could look like would be fun.

We’ll see how this goes. It’d be a blast to get back into writing pieces longer than 500 words.

Pub Rules

Aside

Pub Rules. In a follow-up of sorts to the quote I posted yesterday Brent Simmons writes about what he would do if in charge of a publication. I think it will only be a matter of time before we see someone try this with a large-scale site. I bet that when they do they’ll supplant whatever the main source is for that community. The trick will be sticking to these principles as the site grows and not becoming a bloated mess of “business opportunities.”

One more thought on technology reviews

Earlier today I posted a few tweets from Dustin Curtis on mainstream technology reviews. A couple tweets from Doug Stewart made me think about one more thing worth jotting down.

Last month Matt wrote an essay titled “What’s Next for Apple.” In that he says this about Best Buy:

When I walk through Best Buy, which I try to do once every few months, it feels like it’s technology at its worst, the magic of progress used as smoke and mirrors to confuse and dupe consumers rather than make their lives better.

That’s how I feel reading a product review on the sites Dustin mentioned. It’s technology writing at its worst.

Reviews on sites like Gizmodo and Engadget prey upon gadget heads thinking that their week, month, or year-old technology is “worse.” This is what leads us to the land of 4″+ touch screens and thinking that devices with more megapixels or gigahertz are, somehow, inherently better.

Sure, normals may not be the target market of tech site product reviews. That doesn’t mean the site’s reviews can’t be thoughtful and useful pieces of text. Right now they’re drivel.