I tell people how they should fix their information products. When I do, I follow some obvious rules, and them some less obvious one. These tips are to enable customers (readers, clients, whatever) to more easily use one’s information product (book, web site, whatever). For example, this farm (where we’re celebrating a family member’s birthday; it’s his big 3.0.!) uses a clunky, slow and inaccessible Flash animation as a banner. That’s one of the biggest no-nos among web developers! But they’re not paying me to tell them that.
The tips and tricks that I’ve taught software developers over the years are as just as relevant to people who create publications such as print or digital books. Today, I’m writing specifically for writers.
Writing is complicated, and good writing is hard. When I write, I use dictionaries, thesauruses, search engines and all kinds of tools unrelated to me physically typing or scribbling. Assuming that tools such as these are part of the process of writing, then software should make it natural and effortless to use those tools, too.
So how do I decide what software to recommend to writers? My desire to work naturally and effortlessly when writing, is the basis of my list of rules for writing software. My list of ten heuristics will help me evaluate the usability of the software you can use to make books.
So, here’s the first heuristic:
- Does the tool support effortless writing*?
More to follow once I actually try out PubCoder. The Windows installer is 168 MB, so we’ll see how this goes on my mobile connection.
* I chose the term effortless instead of the word natural because that leaves space for innovation in writing, such as speech-to-text technology, which might enable me to write while I’m moving around. Dictation-to-text, really. Such novel, unnatural ways of writing are welcome, but their utility shouldn’t make writing an effort.