Ghostwriting by content teams saves subject matter experts time and anxiety when faced with writing about their work. This writing sample highlights an internal blog post that uses an analogy to build understanding about an IT project. I ghostwrote this blog post for my client’s artificial intelligence (AI) expert.
How the post started
The purpose of the post was to explain to the IT services department what his team was working on. I approached the expert by giving him three writing options:
- He could write the post himself, and I’d polish it.
- He could put thoughts down about the topic, and I’d build a post around it.
- I could interview him about the topic and write it up for him.
His eyes and ears perked up when I mentioned I could do the writing for him. I assured him that he’d have full ownership of the content and final sign-off before it was published. He chose the interview option but leveraged some initial thoughts he’d jotted down about the topic. He relished using analogies to describe his work, so it made sense to use this format for his post.
How the writing went
At the time I wrote the post, Ground Hog Day had just past and the Kansas City Chiefs just became Super Bowl Champs. Seeing how the NFL uses AI in predicting scores, I found this example a relevant and relatable lead-in to the post. From there, I set up the analogy based on our conversation. Feeling confident about what I had written for about two-thirds of the draft, I made sure these parts were in more of a “ready-for-publication” state. When I found myself struggling with the last third, more technical part of the draft, I realized it was time to get more input from my expert.
Before returning the draft to him, I outlined my questions and gave suggestions for the items I was struggling with. Whether my comments were on track or completely off track with my comments, the purpose was to help guide him in his review and let him decide the best direction. He noted quite a few changes on the area I had in question, which was a good sign that it really needed some work. After a few emails between us about the last changes and some polishing on my side, the draft was ready for publication.
How the post turned out
In the end, the expert was satisfied with the post and was glad he didn’t have to write it. He light-heartedly said his wife–an English major–would be proud of his work.
Because the post was for an internal audience, I posted it to the IT employee newsletter site and socially promoted it to the IT team group on Yammer. I also sent a link to the newsletter by email to the project team. Of the posts I had written for the IT newsletter site, this one gained the most likes in terms of vanity metrics and lots of praise by IT colleagues.
See the post in the PDF below. Parts of the post have been scratched out as noted by the blue scratch marks.