Inside this issue:
I’m Julia Southwick: your new editor! I introduced myself in my first article about how to use some of the Google suite products, but I’ll tell you a bit about myself here too. My family has a lot of engineers and engineering types in it (my grandfather, my dad, my brothers, my mom), so technical communication comes as naturally to me as breathing. I have had two jobs in the Tech Comm space so far: one at Lockheed Martin and one at Siemens.
While at Lockheed Martin, I used my writing, editing, and design skills to update company documentation including onboarding, policies, and organizational materials. At Siemens, I edited and formatted power generator outage reports to meet internal writing standards for publication.
I’m currently looking for a new job and if you know of any opportunities opening up, please let me know.
If you need to contact me for any reason, feel free to reach out to me at firstname.lastname@example.org.
Have you been looking for an opportunity to develop your leadership skills and get more involved with the STC Florida chapter? We want to invite you to our annual Leadership Retreat, where the STC Florida Chapter plans for the upcoming chapter year.
This event is free for STC Florida members and volunteers who are looking to take an active role in the chapter for the coming year.
Event Timing: July 25, 10:00am-2:00pm
Location: Online through Zoom
The STC Florida Chapter’s annual summer Leadership Retreat provides a “post-mortem” on the previous year’s activities and serves as a kick-off meeting for the upcoming chapter year. At the annual summer Leadership Retreat, the STC Florida Chapter sets its strategic goals and objectives for the upcoming chapter year and identifies the projects and activities we must execute to achieve those goals.
We are eager to engage with student members, recent graduates, and veteran chapter members alike. The summer Leadership Retreat serves as a time to review our previous year’s activities to see what we can improve. We hope this event will be fun, interactive, and productive for everyone who attends. In addition to our planned chapter business, we have time for discussion, brainstorming, and leadership development activity.
At this free event, we welcome anyone who is looking to take an active role in the chapter for the coming year and develop leadership skills!
The skills Technical Communicators use in their profession make them excellent Dungeons and Dragons players, as well as game runners (a.k.a “Dungeon Masters”). From writing to collaboration, the core skills that lead to success on the job can be developed and honed in this fun, fantasy setting. While fighting evil monsters as an Elven fighter might not seem to relate to work in Information Technology, both challenges require thoughtful communication, working with a team, doing research, and applying critical thinking skills.
Dungeons and Dragons is a fantasy role-playing game that got its start in 1974 and is often abbreviated to DnD or D&D — we will be using D&D here. Each player creates a character that they will play as during the game. The players then act out scenarios as their character, like actors in a play. However, unlike in a play, there is no script or stage. The script is improvised, and the acting takes place in the imagination. Actions are spoken such as: “I look around the cave, searching for the monster said to live there.”
The straightforward way to explain D&D is by saying it’s play-pretend for all ages. Games can focus on exploring a fantasy world, combat in a fantasy world, the interactions between characters, or some combination of the three. If you want to learn more, here’s a 5-minute video explanation from The Dungeoncast on YouTube.
The world of the game is created and run by the Dungeon Master (DM) or Gamemaster (GM). While each player is responsible for playing a single character in the game, the DM runs the entire game world, everything from describing scenery to playing the Non-Playable Characters (NPCs) that their characters meet.
Each player character has a character sheet that defines the skills and abilities that player has developed. This includes skills like stealth (how good is your character at being sneaky?) or perception (how observant is your character?) and abilities like the power to fly or casting magical spells. Following the rules of the game, each player gets to define all their abilities and write a story for who their character is.
Below is my character sheet from the first game I played as Linea Faenane, the High Elf Wizard, and her “familiar” (a magical animal companion), Lunara the cat.
Developing the narrative is a collaborative experience between all participants, with dice facilitating the gameplay. When a player wants to take an action in the game that requires a challenge, they will roll a die to determine the outcome. For most rolls, they roll a twenty-sided die called a “d20”. If the die lands on a 20, the action is always successful; if the die lands on a 1, the action always fails. There is also a myriad of results in-between.
Based on a combination of the number on the die, the character’s skills, and the difficulty of the action, the DM will describe the outcome.
To start learning to play the game, the best thing you can do is to watch others play (in person or online), to or jump in and start playing.
In my first session, we had mostly new players with some more experienced players, so we started by introducing ourselves. We then went over how to use Roll20.net, which makes it possible to play D&D online. Our next step was to create our characters and their backstories. Once our characters were created, we introduced our characters to the other players and told their backstories. The final two steps were to learn the scenario we would be playing and then to play it (while taking any necessary snack or bathroom breaks).
Technical communicators possess skills that apply to playing and running a game of Dungeons and Dragons. For instance, running an entire D&D adventure across multiple sessions requires project management skills. While the game itself is played for fun, a good DM must manage scheduling and storylines, tracking the players’ progress through the story and noting key milestones.
The table below illustrates the correlation I identified between skills many technical communicators use on the job and the tasks in D&D that applies those skills.
|Tech Comm Skill||D&D Application|
|Clear writing, tone||Backstory, DM description|
|SME interviews||NPC conversations and roleplaying|
|Project management||Manage long-term campaigns|
|Research and exploration||Imaginative storytelling and roleplaying|
|Collaboration||Teamwork with fellow players|
|Critical thinking||Creative problem-solving|
|Graphic design||Maps, illustrations|
|Adept with technology||Playing online through systems like Roll20|
Most veteran DMs spend time preparing before a session with their players. They create descriptions for the world the players will explore. Drafting these descriptions is an exercise in creativity, but also in conservation of detail.
In our game, Bethany as the DM provided the scenario. Our characters were a group of acolytes who had left our temple to go work for the Harpers, an organization that seeks to do good while working in the shadows of the port city of Waterdeep. Our Harper contact, Renaer, would assign us jobs, and in exchange for efficient, speedy work, our characters would receive handsome compensation.
At the start of the adventure, he provided the details on our latest job:
Uza Solizeph is an old woman who sells books out of her small shop in the Trades Ward of the vast city of Waterdeep. She claims to have trapped a monster in her shop and fears for the welfare of her books and her cat. The City Watch isn’t likely to lend a hand, given Uza’s propensity for tall tales, but the Harpers owe her a favor. You’ll find her sobbing at the tavern on the corner of Sort Street and Salabar Street. Make haste!
Like technical writing, you give your players the information they need to complete their task, without overloading them with unnecessary or distracting details.
In D&D, you often engage with characters who provide crucial information to aid your player characters on their quest.
We received our assignment and went to the tavern to interview Uza. We listened carefully to her story and asked questions like: “Did you see the monster clearly?” “Can you describe it?” “What does your cat look like, and what’s your cat’s name?” “Can you describe the interior of your shop for us, please?” These questions were designed to help us gain an understanding of what we were up against.
While we were talking, a bard recognized a member of our group as the person who previously swindled them and tried to pick a fight. Our bard convinced them to back down using superior barding skills, and the other bard moved on. Once we established all necessary details, we asked Uza to take us to her store and to wait outside it for us while we took care of the monster and found her cat.
Gathering information on the job often presents challenges for technical communicators. While a SME can become your greatest ally in learning the product you need to document, determining what questions to ask can be tricky.
Dungeons and dragons gameplay provides a series of challenges for the players to overcome. While some players may expect to resolve conflicts with combat, many obstacles can be resolved with creative problem-solving.
We went into her shop. Linea asked Lunara telepathically to look for Uza’s cat and let her know if she finds the cat. The group started looking for the cat and the monster. While exploring the shelves looking for clues, the group noticed some scorch marks and identified some books about monsters. The monster found us, so we rolled for initiative (turn order) and started fighting the monster.
During the fight, Lunara concentrated on staying out of the fight and kept searching for Uza’s cat. Lunara found Uza’s cat towards the end of the fight and worked on calming her. We defeated the monster and Linea used a spell to identify how the monster arrived in the shop — it was through an enchanted book about the monster. There were two similar books that could summon other monsters. One of us called Uza in, and Linea explained her findings and asked if they could take the other two books to turn in to the Harpers. Uza agreed and thanked the group for their help.
By nature, all tabletop roleplaying is collaborative. The game and story evolve through the input of the DM and the players, with dice rolls determining how things play out. As a party, the players each contribute their ideas to influence the direction for every scene.
At the end of the session, we talked about how we thought the session went, alternative paths, how we liked D&D, if we would like to continue playing D&D, and if we would like to continue the story of these characters.
As technical communicators, collaboration drives our work. Even solo writers must learn to work with subject matters experts and consider the response of stakeholders in developing documentation.
As technical communicators, our skills make us the ideal party members, both in Dungeons and Dragons and on the job. We shine in a collaborative environment where our work can enhance the effectiveness of those around us. With that in mind, why should you give a tabletop game like Dungeons and Dragons a try?
First off, it’s enjoyable! Gathering together with friends to develop a compelling narrative gives you a chance to stretch your creative muscles. Whether you roll dice around a physical table or play online through Roll20, gathering together and tackling challenges with friends provides a chance to relax and have fun.
Second, you can practice many technical communication skills in the creative safe space of a tabletop role-playing campaign. While the decisions in the game do not have real world consequences, the DM and the narrative still define the stakes. Telling a story in a game provides you a chance to hone your skills, such as telling stories through your documentation to your users.
Why not give it a try?
My name is Mia Stephens, and I am a second-year student at the University of Central Florida. I am currently a member of both the Society for Technical Communication and the Future Technical Communicators at UCF. Over the past semester with the guidance of my mentor, Rachael Swertfeger, I have worked on curating a website that displays the aspects of Technical Communication that individuals interested in the industry should know as part of my mentoring project for the STC.
For this project, I developed a survey that asked industry professionals about their experiences in the field, as well as what advice they would give to those that are either currently studying Technical Communication or are interested in the field. If you are interested in viewing the website, it can be found at https://techcom.crd.co/ (or https://itechcom.crd.co/ for mobile users).
There are four types of editing: line editing, copy editing, developmental editing, and proofreading.
Would you like a series on editing? High-level overview, tips/tricks, editing tools, best practices, etc. Let me know!