Techs learning how to write in a group

To Democratize Your Blog, Teach Techs to Write

For two years, I was the only writer at my company. We currently have five .NET developers, three cybersecurity experts, five front-end developers, three marketing analysts… you get the idea. If you want a web app developed, a homepage designed, or any kind of user data analyzed, we have a team for that. If you wanted to actually write about any of these things, my company came to me.

On my best days, this was the greatest of power trips. I was the lead voice for a company of more than 70 experts in all kinds of digital technology. I got to decide how we describe our philosophy, ideal way of working, the kinds of customers we want, and how we bend the internet to the will of all sorts of forward-thinking companies.

On my worst days, I felt like an alien who crash-landed on a planet where the dominant language is javascript and storytelling only matters if it convinces someone to give us more money. Like when I got to the office and found an 87-page sales proposal in your inbox with the only comment “Use your writer magic to edit this!”

Is Good Writing Magic?

don draper screaming internally in frustration
After you get done screaming about editing a huge proposal, you realize your sales guys have a point about writing.

And after I got done screaming internally, I realized they have a point. Writing is magic. If I put together the right combination of words on a blog post or sales doc, I can convince someone to do something—hire us, for example. And as much as data scientists want to quantify and measure what makes writing compelling or not, good writing is more art than science. I usually feel my way through my writing rather than calculating each word or phrase.

But the problem with magic is it can’t be taught. And if I’m the only wizard capable of casting word magic in my company, I’m quickly going to get overwhelmed by how much my colleagues need my help. So what’s the answer?

You pull back the curtain on the magic and showing how the trick is done. If writing is magic, then magic is actually the product of proven techniques which can be shared, repeated, and relied on. Now all I needed to do was coach my nonwriters in how to write. Here are four tactics I found that made this teaching and coaching process work.

1. Break Down the Writing Process

Write ideas in an outline first
Emphasize how the writing process involves a series of steps by starting with an outline.

If there’s one thing technical workers love, it’s a reliable process. As a writing coach, the more I can illustrate the individual steps to writing something clear and compelling, the easier it will be for my colleagues to follow it.

At Atlantic BT, the writing process I teach involves four steps:

  • Come up with ideas and narrow them to your core topic.
  • Outline a blog post about an idea.
  • Draft this idea.
  • Revise the idea until it’s ready to publish.

I drew these steps from the writing process I learned in high school—begin with a thesis, then outline 3–5 points which prove your point of view, then draft, then revise. On each point in your outline, include additional information to explain why these points matter. It isn’t necessary to go into a ton of detail, but the more you write down in an outline, the easier the first draft will be.

Naturally, outlining isn’t the only way to write. But if you’re at all nervous about writing a blog post (and most programmers are), outlining your ideas in advance is the best way to prevent the frustration that often makes aspiring writers quit. Why? Because every time you feel unsure of what to write next, you can go back to your outline—it’s your map into the wilderness of unwritten ideas.

Once my colleagues have an outline, I encourage them to write a first draft as quickly as possible. The most important qualities in a first draft are speed and honesty—speed prevents you from making excuses why you do not finish what you started, and honesty ensures this first draft reflects all the ideas and feelings that led you to write this idea in the first place. Those things in mind, an aspiring writer’s main goal with a first draft is to finish it; her secondary goal is to make it the best reflection of her idea as possible.

2. Incentivize Writing for Everyone

Use cash to incentivize writing
Motivate your colleagues to write with a small cash bonus for each post.

Writing, even at its best, is hard work. It takes dedicated time, concentration, and the willingness to open yourself up to criticism from the entire internet. Even highly successful authors struggle with the self-confidence and discipline to write; acclaimed fantasy writer George R.R. Martin admitted that he sometimes wondered if he should quit writing and become a plumber—and this after writing numerous bestsellers and inspiring one of the most popular shows on TV.

If writing is a tough challenge for veteran authors like Martin, how daunting do you think the average PHP developer is going to feel if he wants to write a blog post? He’s got to overcome this fear before he even gets started. So how do you motivate him to try?

The most direct tactic is providing some kind of incentive. At Atlantic BT, we run a weekly writing contest in which anyone who works with me to get a post published on our blog receives a small cash reward. Every two months, the most popular post on our company blog (as measured by pageviews) wins a cash prize. By awarding the prize publicly, we gamified the writing process for our staff and gave each aspiring writer a little more motivation.

Another important incentive is to publicly recognize every single writer who carries a blog draft to publication. The simplest way to do this is by emailing or messaging the company to congratulate the new writer on his/her work getting published. However, I also like to tell my colleagues in our weekly company standup about our latest blogs so everyone can applaud the new writer to his face. The more you communicate that each person’s voice matters, the more likely you will recruit more writers for the blog.

3. Make Time for Writing in the Workday

Clock on desk to make time for writing
Your colleagues will struggle with drafts if they don’t have time in the workday to write.

However, a little cash motivation won’t cut it if you’re asking a programmer to spend his or her own time with the difficult work of writing on top of regular tasks. If you want your employees to contribute to your company blog or other writing areas, make time on your employees’ schedules for writing blog posts.

This isn’t as simple as having a “free-writing hour” every day in the style of 8th grade homeroom. After all, you still need your programmers and technical types to keep up with existing projects, and losing an hour every day can hinder progress.

Instead, check in with your employees regularly to see if they have ideas for a blog post. If someone wants to write, the best thing you can possibly do is make time for them to do so on the schedule. This is especially true if their idea will help promote the expertise and value of your organization—by showing how your programmers not only have big ideas but also know how to write and communicate about them, you’re showing off the value of your company in a way that puts your people first.

4. Coach Your Colleagues 1:1, Especially on Revisions

1:1 coach session over draft
The best way to teach good writing is in 1:1 sessions, not in front of a crowd.

If you ask anyone who has never taught how a teacher passes along knowledge, they’ll probably say something about giving a lesson in front of a class. If you ask an actual teacher, they’ll tell you the best learning happens in one-on-one conversations.

I learned this lesson the hard way. Atlantic BT gave me the opportunity to run my own writing class at lunchtimes once a week (free food included). I prepared fun presentations, came up with great GIFs, and offered the group all kinds of ways to generate ideas and blog posts. My colleagues had fun, took notes, and seemed eager to give blog writing a try. The only problem was they weren’t actually writing—weeks later, new drafts barely trickled in.

I had given my coworkers a good pep talk and some tips to get started, but my enthusiasm and advice weren’t enough to motivate my friends to do the hard work of finishing a draft. Instead, I began to approach my friends one-on-one, asking them about their ideas and how the writing was going (usually slowly). I then scheduled a meeting between me and each writer who was working on a draft.

The difference was remarkable. Once I began to meet and talk through a draft with an aspiring writer, we could quickly put together an outline on a shared Google doc. From there, it was easy to help them craft an introduction, string together paragraphs, and end on an action-oriented conclusion.

Democratize Your Blog Today

I now have another content writer on my team, and we look to add more soon (Apply here if interested!). However, we could not have gotten our company’s blog content to this point had it not been for the Account Executives, Developers, and other technologists who helped write blogs for the ABT site. Their voices are a crucial part of what make my company unique, and it’s one of the best parts of my job to help them share their ideas on our site.

If you’d like to hear more about how to democratize your company blog and give everyone a voice, I’ll be speaking at the High 5 conference in Raleigh this February. Be sure to subscribe to our Content Marketing newsletter for more information on this presentation.