Sailing in the digital world

Savage’s analogy of metis and the deployment of digital tools really struck a chord with me. I look back to summer evenings spent sailing with my dad on Lake DuBay, and I understand the point he was trying to make. The goal of sailing and of deploying digital tools isn’t to master anything; that isn’t possible. It is to be responsive to several factors that can change quickly and sometimes all at the same time. My Dad’s C-scow was a fun boat to sail, but it was a highly temperamental boat to race.

For those who may not know, scows are wide and flat bottomed sailboats. They are slow when sailed flat, but they become much faster when they are leaned up on edge. The waterline changes from wide and flat to very narrow and long, which drastically reduces the surface in contact with the water. When everything is going well, it is fast and exciting. Racing the boat is a matter of weighing risk and reacting quickly. You can always lean the boat less and sail it less aggressively, which will allow for more time to respond to changing conditions. Or, you can lean it far, sail very quickly, and sacrifice some of your time to react to changing conditions.

What does all of that have to do with deploying digital tools? Some of it is preparation, making sure you have done the testing needed to make sure everything works and understand how it works. Next, you need to have a team or crew that you can trust to handle their job if anything changes. The final portion is learning to pay attention to the signs in front of you. There are a lot of variables in both that can change, so paying close attention to everything around you is key to reacting to those changes. If you don’t notice a problem, it is unlikely that you will react soon enough or in the right way to be useful.

Each of us must exercise critical digital literacy to succeed in this ever changing digital world. We must understand more than just the context of our work. We must also have a strong grasp of the tools available to us and how best to use them. This was part of what prompted our switch over to HTML based documentation. The majority of employees work from home, so information needs to be accessible and able to be retrieved quickly. They also frequently have several programs open at once. HTML files are much smaller sized, and they open from a browser rather than Microsoft Word. This reduces the resources needed to open access and use the documentation.

The readings discussed single sourcing, which is another thing my team is working toward. We have established common wording guides to for frequently used portions of text or steps in processes that are program specific. This helps save time and drive consistency throughout our documentation, which can be difficult with eight different writers sharing the workload. We also have editors who help raise the quality of the documents and unify the voice.

Posted on October 27, 2013, in Literacy, Uncategorized, Workplace and tagged , , . Bookmark the permalink. 4 Comments.

  1. Thanks for sharing your ideas. You point an important point. In order for us to be able to store information electronically, we must also possess digital literary skills. Unless we know how to read, write, and analyze information coming from a digital source, the information system will be useless.

  2. Love the sailing analogy!

    You are absolutely right that one of the keys to successfully implementing digital tools is being able to adapt when the technology changes. One of my brothers teaches IT classes at a local college, but he used to work for a government contractor to train military personnel about computer security. After ten years, he got pretty burnt out because as soon as he’d learn one program or system, it quickly became obsolete and he had to learn a new program. That may be an extreme example as he worked exclusively in high-level IT, but I think it follows along with what you’re saying. In a digital world, one must be prepared for frequent, rapid change!

    I also wanted to comment on single sourcing as you brought it up in your last point. I wasn’t really familiar with this term prior to this class, but I realize now that my company does a lot of this. We don’t have an official database of documents and language that we use, but I do keep my own past communications in my email and in my personal computer files. A common mantra at our office is “don’t re-invent the wheel” and I get at least three requests a day from my co-workers if I have any language that helps explain this or that. Why, yes I do! Let me check my files and get back to you. I’m not sure if this is the exact definition of single sourcing, but I feel like I’ve become a single source! I’d like to think that they come to me because they value and respect me…but I think a lot of it has to do with the fact that I’ve been employed the longest. If they need to know if a document already exists, I am the most likely person to ask because I’ve been around long enough to know!

  3. evelynmartens13

    Enjoyed the sailing info!

    I had never heard of “single sourcing” until this semester, but I can see that the idea is in use at my university and the concept has actually been around awhile. In the old days, we called this “boilerplate” (usually in an unflattering way). In my public relations job, for instance, we would talk about small class sizes, low student-faculty ratio, etc. in identical terms on our website, in our brochures, and in press relases. It got a little boring, but it did make for consistent messaging and marketing.

  4. Excellent writing here, starting with your point, “The goal of sailing and of deploying digital tools isn’t to master anything.” I think this may be what frustrates some people in academia [particularly the humanities] and the “real world” because it not only signals resistance to change, it requires taking risks. I would hope that working in teams and having a point person [or single-sourcing] helps alleviate the stress of such risk-taking!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.