---
title: "Writing as a Holy Calling"
date: 2012-07-09
description: "$( document ).ready(function() { // Handler for .ready() called. $("
canonical_url: https://idratherbewriting.com/2012/07/09/writing-as-a-holy-calling/
---
# Writing as a Holy Calling
Perhaps because of my blog's title, "I'd Rather Be Writing," many people think this blog deals with creative writing. As a result, I frequently get asked if I want to review books about writing. Sometimes I say yes.

Recently someone sent me*[A Year of Writing Dangerously: 365 Days of inspiration and Encouragement](https://www.amazon.com/Year-Writing-Dangerously-Inspiration-Encouragement/dp/1608680517),* by Barbara Abercrombie. So far I like the book. I'm not sure if "dangerously" accurately describes it, but each page contains short encouragement about writing. I welcome this quick, daily encouragement because it usually motivates me to write.

I know that in the field of tech comm, "writing" has been somewhat commoditized, so there's always a tension that rears its head when I start mentioning writing as a worthwhile activity. But in other contexts, "writing" can be just the opposite: a holy calling. This brings me to entry #3 in *Writing Dangerously*:

> 3. The Holy Calling
> You may find that your friends and family are somewhat less than respectful of your sitting there in your sacred space. They might even refer to what you're up to as "typing" or "your new hobby." Writing is not a hobby. Collecting stamps or coins is a hobby. Writing is a calling.
> ----------
> *I believe that -- if you are serious about a life of writing, or indeed about any creative form of expression -- you should take on this work like a holy calling. I became a writer the way other people become monks or nuns.... I was writing's most devotional hand-maiden. I built my entire life around writing. -- Elizabeth Gilbert.*

Perhaps it's this sense of the writer's holy calling that binds us together. It's a kind of secret order. As a college student majoring in English, I once joined a group that was banded together like this. The group was called "Writing Fellows." We acted as writing tutors for classes across the disciplines. In our training to become writing fellows, we had to write an essay describing how we knew we were writers, essentially telling the conversion story about our "holy calling."

As a writing fellow looking at my future, I didn't care what my exact career title would be, so long as I could spend all day immersed in words -- shaping ideas, organizing content, styling sentences with rhythm and flow.

The reality is that most technical writing jobs fail to engage any sense of a holy calling. A few weeks of writing dry, step-by-step procedures can suck the writing zeal out of the most passionate writing devotee. As one embarks on a career in technical writing, it becomes clear that not all writing endeavors have the same fulfillment. In fact, many don't consider technical writing to be *writing* at all.

In a presentation at the last STC Summit on [Exploring the Information Ecosystem](http://www.slideshare.net/rhanna/exploring-the-information-ecosystem), Rob Hanna explained that persuasive writing and informational writing rely on two different mindsets altogether, such that a person skilled in persuasive writing (blogs, essays, articles, stories, fiction, letters) might perform below average with informational writing (help topics, reports, proposals, interface text, reference manuals), and vice versa.

Informational writing requires you to structure your content into concepts, tasks, and references. You strip out all the extraneous words and focus on the bare essentials to complete a task. You focus on clear, accurate information -- not on persuading or arguing for an idea of any kind. You add indexes, meta properties, glossaries, related topics, and other navigational aids.

Few people find technical writing a holy calling in the same way creative writers find writing to be a holy calling. For example, in [Is Technical Writing Your Calling?](http://www.stc-carolina.org/newsletter/tiki-index.php?page=Pith+and+Vinegar%3A+Is+Technical+Writing+Your+Calling%3F), Michael Harvey writes,

> Personally, I don't think that writing installation manuals, product guides, or help panels is a calling. It's a job — an enjoyable career if you're good at it. The underlying activity — clearly communicating complex concepts or procedures to help someone get work done — feels close to a calling. Clear communication makes a connection between human beings or between ideas, creates understanding, and promotes efficiency and order. Those are inherently good, if imprecise, goals to pursue.

I think Michael's assessment expresses the perspective most technical writers hold: technical writing provides a worthwhile career but does not connect with its practitioners as a calling. But why can't it be a calling? Technical writers still, in fact, work with words. Why does the activity not summon one's creative energies?

Perhaps the lack of the muse constitutes the real difference between technical writing and creative writing. With creative writing, you may feel an inner muse guiding and styling your words, whispering to you the twists and turns of the plot. You may have periodic epiphanies that give you a glimpse of an aesthetic vision -- something beautiful and true that you can see in your mind and try to reach with words. That aesthetic vision motivates you.

In contrast, technical writers forego the muse. Instead, the subject matter expert plays a kind of pseudo muse and deigns to give you table scraps of information whenever it's convenient for him or her. You gather up these scraps and cobble them together into a seamless patchwork of information that you're sort of proud of, except that no one else sees much value in it.

Perhaps so many people find technical writing careers boring because we forget that users need more than information. Users also need the persuasive / language arts side communication as well, as Rob Hanna described in his dichotomy of writing. You can find ample opportunities to write in this more persuasive mode. For example, the other day I wrote an article for our technology blog on [How to Update Your LDS.org Directory Photo](http://tech.lds.org/blog/511-how-to-update-your-directory-photo).

Granted, this article seems like a topic in a help system. Still, I elaborated in places, added more images, and included more of an introduction. I made it an article instead of a help topic. A while ago I wrote another technology-related article titled [From Local Unit Websites to a Suite of Tools](https://tech.lds.org/blog/486-from-local-unit-websites-to-a-suite-of-tools). It provides less how-to information and answers more "what" and "why."

For a non-personal example, look at [Inside Google Search.](https://www.google.com/insidesearch/) You'll see that the top navigation has much more than a list of how-to articles. There's a tips and tricks section, a stories section, a blog, a playground, and more.

![Inside Google Search has more than just how-to information.](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/google_search_how_to1.png)

Many software companies have technology blogs, and if so, articles about the software products and their uses can provide you with a steady stream of content. As you engage in technology blogging for your organization, you can call forth your creative talents and escape the hum-drum world of procedural writing.

If you have a personal blog on the side, like I do, you have even more opportunities to let down your creative hair and "write dangerously."

Although I don't feel technical writing to be a holy calling, I do still feel the writer's calling from time to time. The more I write, the more energy I feel to write, and I don't much care exactly what the form is. I know that my creative energy will push me toward certain directions at times, and perhaps pull me back at others.