Posted in Uncategorized

What Does Knitting Have To Do With TechComm and m-Learning?

I’m so glad that this is now my 200th post on this blog! TechCommGeekMom has come a long way since it started out as a class project in grad school, now hasn’t it? For this particular post, I’d like to share my thoughts on something that I’ve been thinking about for the past two weeks or so.  It reveals one of my hobbies to you, but hopefully you’ll like the analogy.

As you’ve seen in the subject line of this post, I’m going to be talking about knitting and how it relates to tech comm and m-learning. Now, I know what you are going to say. Knitting is for grandmothers who make ugly stuff for everyone, and you are obligated to wear it when she comes over and visits. You couldn’t be wrong. Knitting has had a huge upsurge in the last ten or so years, and more and more people are adopting it as a hobby. It goes back to the 9-11 attacks, when people were trying to get back to a sense of security and home. I think with economic times, it’s also a relatively easy and inexpensive hobby to have (unless you are a true diehard like some of us).

Knitters these days make more than clothing items, accessories and toys, but it’s become an artform unto itself. (Ever hear of yarn bombing?)  I can’t remember when I started knitting exactly…but I’m guessing it was around 2004 or 2005. I know I was knitting in 2006 when I went to California for a convention for the now defunct Body Shop At Home businesses, and met Anita Roddick, as there’s photographic evidence of knitting in my hands during the event. In any case, it gave me a chance to learn something new that spoke a whole other language of its own, had a different vocabulary, and I got to work with all sorts of colors and textures in the process. For someone with sensory integration issues, it’s a great outlet for sight and touch. Even the rhythm of knitting up something has a calming effect, and following patterns forces my brain to focus.

So what does all this have to do with tech comm and m-learning? Well, as I thought about it,  there’s definitely an analogy that could be made about the benefits of knitting and how they lend themselves to these topics.  All this first came to me after I had spent the day at Adobe Day, and later took a small soujourn into the city of Portland with four fabulous technical communicators who also happen to be knitters. They had invited me to go on a yarn crawl with them (similar to a pub crawl, but in search of high quality yarn instead of libations), and I readily accepted. We only made it to one store, but we had a great time checking out all the high-end yarns and knitting notions available.

Pardon us drooling over the yarn!
Five technical communicators who
are also knitters! We know!
At KnitPurl, Portland, OR, during LavaCon
L to R: Sharon Burton, me, Sarah O’Keefe,
Marcia R. Johnston, and Val Swisher

As I reflected on Adobe Day, one of the big themes of the morning was the idea of using structured content. Without structured content, all of one’s content could fall apart and lose strength. An architecture needs to be created to make it work. Well, knitting is like that. If one doesn’t follow a pattern, and just knits in a freestyle, haphazard manner, instead of a nice jumper/sweater, one could end up with a garment with no neck hole and three sleeves. Without the structure of a pattern, and even reusing good content (or stitches, or groupings of stitches describing appropriate methods for structure), the whole thing falls apart. The beauty, too, of reusable content in content management, just as in a knitting pattern, content that is produced well, is solid, and the reader can understand clearly and concisely will produce good results, and can be recombined effectively in different instances without losing its meaning.  Take a look at a sweater or knit scarf you might have. You’ll find that each stitch makes sense, even when you look at different pattern of how the cuffs and collar differ from the sleeves and the body. But it all fits together.  In my mind, this is how reusable content can be used.  Very tight, well written content can be reused in different combinations without losing its context and form if done correctly.

The other way I thought of the analogy of knitting again had to do with how one learns how to knit, and how it relates to m-learning. Knitting fair-isle sweaters, Aran sweaters or lace shawls doesn’t come on the first day of learning how to knit. Heck, I’m even still learning how to do all these techniques! It comes with learning a foundation–namely the knit stitch and the purl stitch–and building upon that foundation. Any piece of knitting you see is all a matter of thousands of knit and purl combinations to make the item. But first, one has to master the simple knit and purl stitches by learning how to understand how to gauge the tension between the needles, the yarn and your fingers. Once that is mastered, then learning how to read the “codes” or the knitting language of K2, P2, S1 (that’s knit two, purl two, slip one), for example, then the real fun begins. Knitters have to pay attention to details in the directions, because knitting can be a long task. Except for tiny baby sweaters or sweaters for dolls or stuffed animals, I don’t know any sweater that could be hand knit in a single day, even if it was done from the time the knitter woke up until the time the knitter went to bed. It just couldn’t happen, even for a fairly experienced knitter.  So, each part of the knitted pattern must be learned or read in chunks so the knitter can understand where he or she left off.  Talk to me about lace patterns especially, and it’ll make more sense. But each technique takes time to master, and most knitters learn these techniques a little bit at a time. Whether a knitter is self-taught or taught in a conventional learning environment, nobody learns all there is to know about the most advanced knitting techniques on the first day. Just getting knitting and purling down takes a while. It’s an arduous task to learn to knit and knit well, and to be patient enough to see a pattern all the way through.

Just like in m-learning, things need to be learned in small chunks for comprehension. Information has to be short and to the point so that the reader, just like the knitting pattern reader, can take that information, mentally digest it, and then work out how to use the information. There is definitely trial and error in both m-learning and knitting; if one doesn’t succeed, then it’s possible to go back and try to re-learn the information and correct it, and in doing so, retains the information better.

Now, if one happens to be BOTH a technical communicator AND a knitter, then these are easy concepts. Reusing content, breaking down information into smaller portions for better learning retention, structuring the content appropriately and consistency comes both with our words and our stitches.

A variety of tools can be used in either case to create the content. For technical communicators, it’s the use of different software tools that help us achieve our goal. For knitters, different sized needles, different kinds of yarns and other tools can be used in the process. Is there only one way of doing things? Of course not. Is there any single tool that will do the job? Generally, no. This is the beauty of both technical communication and knitting. In the end, the most important tool is the mind, because without the individual mind, creativity and intellect cannot be expressed. When all of these tools and factors work together, it is possible to create a fantastic piece of work. When this combination of factors aren’t followed, it can look pretty disastrous.

So, next time you see someone with a pair of knitting needles in their hands, look carefully at the workflow that person is following. You might learn something from it.

Posted in Uncategorized

Adobe Day at LavaCon 2012 Roundup!

This post is just a quick summary of the Adobe Day at LavaCon 2012 series from this past week. As you see, there was so much information that it took six posts to try to summarize the event!

Being in Portland, Oregon was great. It was my first trip there, and being a native Easterner, my thoughts pushed me to that pioneer spirit of moving westward in this country. Once there, I saw a hip, young, modern city, continuing to look towards the future.  The information I gathered at Adobe Day was general information that was endorsement-free, and practical information that I can use going forward as a technical communicator, and that by sharing it, I hope that others in the field will equally take on that pioneering spirit to advance what technical communications is all about, and bring the field to the next level.

To roundup the series, please go to these posts to get the full story of this great event. I hope to go to more events like this in the future!

As I said, I really enjoyed the event, and learned so much, and enjoyed not only listening to all the speakers, but also enjoyed so many people who are renowned enthusiasts and specialists in the technical communications field and talking “shop”. I rarely get to do that at home (although it does help to have an e-learning developer in the house who understands me), so this was a chance for me to learn from those who have been doing this for a while and not only have seen the changes, but are part of the movement to make changes going forward.

I hope you’ve enjoyed this series of blog posts. I still have many more to come–at least one more that is inspired by my trip out to Portland, and I look forward to bringing more curated content and commentary to you!

The autograph from my copy of
Sarah O’Keefe’s book,
Content Strategy 101.
Awesome!
Posted in Uncategorized

Adobe Day Presentations: Part IV – Val Swisher asks, “Are You Global Ready?”

Val Swisher
of Content Rules, Inc.

Following a short break after Joe Welinske’s talk about Multi-screen Help Authoring, Val Swisher took to the stage.

Val is the founder of Content Rules, Inc., and she spoke about eight simple rules for technical communicators to follow to make content global-ready–now! Her specialty is doing translation work, so she knows a thing or two about making content ready for a global market. As she went through each rule, she would explain the impact of the rules and why the rules were in place, although some were self-explanatory.

The rule she listed were as follows:

Rule 1: Not all errors are created equal. Some can cost you thousands of dollars!
This is one of those obvious rules. Taking the time to write content carefully as well as making sure proper editing is done is a necessity. Even one small typo can make a difference.

Rule 2: Creative Writing is a myth. Standardize.
Val’s point with this rule is that superfluous writing is not necessary. Keeping content clear, concise, cogent and correct is especially important in translation, and allows for better reuse of content.

Rule 3: Real copy editors don’t do it without a terminology manager. 
It is vital to use the same terms for certain words, especially for translation purposes. For example, the words “puppy”, “dog”, and “canine” all refer to the same animal, but are clearly different words, even though they essentially mean the same thing. In translation, there are times that this much word variation for a single item isn’t available in a different language, so choosing one word as the referential term is recommended. It keeps terminology within the content–especially if reusing content–consistent.  Style guides are, unfortunately, not followed as often as they can be. A system is needed to manage terminology and help prevent problems like this example from occurring.

Rule 4: Have you got translation memory (a translation database)? Your vendors do. Use it. It keeps content standardized and saves money.
This is another fairly self-explanatory rule. I was not aware, since I’m not in the translation business, that there are such things as translation databases. From what I could understand how it works (and someone please correct me if I’m wrong), a translation database has features that when a specific turn-of-phrase is used on one language, there is a specific translation for that combination of words into another language. When a translation is done, the database looks for that word combination and translates it accordingly. This, again, allows for consistency in translations between the different language editions of content.  As a technical communicator who does translations, Val is saying that if you don’t have such a database in place, you should have one because in the long run, it will standardized content and save money.

Rule 5: Don’t complain about quality of your tech writers. You agreed to outsource docs to ___ in the 1st place.
Val pointed out that while there are good outsource resources for writing and translation out there, sometimes the quality is not as good as keeping it in house or closer to home, especially if the content is written by someone whose first language is not English. Good quality source material is key! Having good quality source material helps control costs, especially with translation!

Rule 6: If you write flabby copy, even the nicest vendors will email you a bill for localization that will astound you.
Again, this comes back to having quality content in place. Val’s point was that if you do write weak content that is difficult to translate because it is not quality content, even one’s best clients will send you a bill for the translation for localization purposes, and the bill will be VERY HIGH. Again, having quality content saves money!

Rule 7: Get rid of extra adjectives and superlative words! Delay this product launch, and there’s no next product launch.
This rule is a strong recommendation related again to how content should be written. The use of extra adjectives, adverbs and other superlative words do not enhance the content. Using such words that have to be rewritten or translated can delay a product going out, and for a client, that can be a deal-breaking move. By delaying the product due to not meeting a deadline due to overdue time for translation, and there will be no next time being able to help with a product launch. Obviously, that would be bad business.

Rule 8: Translation is a team sport. You want to work alone? Become an accountant.
While this rule elicited a laugh from the audience, it was a point well taken. Teamwork is KEY! A better source of English content will result between source writers and translators if they work together.

Val was asked the question at the end of her presentation, “What alternative tools for style guides are on the market?” She responded that there are lots of software tools out there, but to be careful about push technology within those software items.

More information can be found at Val’s website, http://www.contentrules.com  and her free e-book is available by e-mailing her at vals@contentrules.com.

I found this presentation rather fascinating, especially since Val presented it with a sense of humor. But her point was clear. Content needs to be as precise as possible when it will be reused and especially when used in translation for consistency. By following her basic rules, costs can be controlled, and the quality of the content can only get better.

I thought about what it takes to do translation, searching my own memory banks from when I almost minored in French during my undergrad years and had to do translations, to the present day watching my husband translate literature written in German to Spanish for a group he’s been involved with for years, to my own struggles to translate what I want to say to my in-laws into my broken Spanish. Translation is not an easy task, but when thinking about translating my English thoughts into another language, it can get tricky because of the turn of phrase or colloquialisms used from area to area. Even in talking to my husband about the topic, he will say that there are different idioms used between Spanish speaking countries, although Spanish will still be relatively “standard.” Being from Ecuador, he can still understand someone from Spain, Mexico or Argentina as much as an American can understand someone from the UK, Canada, or the Australia. But I’ve even found in my own teaching of a business and technical writing course to a corporate group in Asia is that English taught globally is not consistent due to the source English being from different countries, so I have to go and set the record straight.  I can certainly appreciate where consistency and choice of words can lead to better quality content and communication in the long term.

The next presentation, and the last in this series: Adobe Day Presentations: Part V – Mark Lewis and DITA Metrics.

Posted in Uncategorized

Missed Adobe Day at LavaCon2012? Here’s the scoop…

One of the “Three Sisters” mountains
outside Portland
(don’t know which one–took this from
my airplane seat coming home!)

As I write this, I am still recovering from quite the whirlwind of a weekend! I flew out to the West Coast on Friday night, and returned to the East Coast on Sunday.  I met SO many people who are not only leaders in the technical communications field in one capacity or another, but they are also nice and SMART people in the field. You couldn’t help but be inspired or feel smarter once you walked out!

Now granted, this was the first time I ever attended a conference-type event within the tech comm field, so I was excited to be there and soak everything in as much as I could. This is not to say that I’ve never been to a professional conference or travelled to this type of event; I just never have done it with the tech comm crowd.

Like I said, for me, at least, as the “new kid on the block”, I didn’t know exactly what to expect of the event, the topics, or the people I would encounter, and I’m glad to say that everyone was very welcoming to me, and I felt included as a fellow technical communicator very quickly. It was a little surreal in some instances, because many of the people I met were those whom I had only met online through Twitter or Facebook–Twitter mostly, so to be among such a collection of established tech comm thought leaders could have been a lot more intimidating, but it was not that way at all.

There was so much great information that came out from the morning that I will be splitting up my report over the next few days. Each day going forward will have my summary about each speaker at the event. And I have some photos as well!

So, let me get started into the Adobe Day event itself –with some photos!

Saibal Bhattacharjee (@saibalb79) from Adobe setting up.

The Adobe Day event started with an introduction from LavaCon organizer Jack Molisani welcoming everyone to the event. Jack, thanks for organizing and running LavaCon! Although I’m missing the main conference, I’m hearing awesome stuff about the speakers on Twitter, so I think you deserve some kudos for helping to assemble all of it!

Jack Molisani

Jack was followed by a short introduction and welcome by Maxwell Hoffmann, who is one of the key players of Adobe’s Technical Communications marketing team. If you’ve ever attended any Adobe Tech Comm webinars, more than likely you’ve heard Maxwell moderating the webinars. He is also one of the bloggers for Adobe’s Tech Comm blog. Having worked with him while creating my own webinar for Adobe, I can say that he does a fantastic job at what he does.

Maxwell Hoffmann of Adobe

One thing I’d like to mention, before continuing, is that the nice thing about Adobe Day was that is wasn’t actually about Adobe or promoting Adobe products. I don’t recall during the entire duration that any speaker promoted any Adobe product or the brand other than possibly to thank the company for the opportunity to speak. All the speakers spoke broadly about technical communications as a whole, so whether one supported Adobe products or not, everyone could benefit from the information being provided.  This really was a collective presentation of the best and brightest in thought leadership, and an opportunity to network and learn from those who are considered top in the technical communications field.

Now, for this post, I’m actually going to start this Adobe Day series going backwards in the day’s event, starting with the panel discussion that was at the end of the morning.

The panel topic at the end of the Adobe Day event was titled, “The Decade Ahead: Opportunities and Challenges for Technical Communications Professionals.” Scott Abel, who is also known as “The Content Wrangler,” moderated the panel.  The panel included several of the leading thought leaders in the tech comm industry. The panel consisted of Joe Gollner, Beth GerberBernard Aschwanden, Joe Welinske, Val Swisher,  Sharon Burton and Joe Ganci.

Adobe Day Panel.
L to R: Joe Gollner, Beth Gerber, Bernard Aschwanden, Joe Welinske,
Val Swisher, Sharon Burton, and Joe Ganci

As far as the opportunities in tech comm right now, Sharon Burton said it best when she exclaimed, “We are in the Wild West!” meaning that the field is still so very wide open that anything done right now would be in the pioneering spirit. Another point that Sharon summarized was that 99% of the content consumers are not happy with the tech comm content they are receiving, and so a revolution is brewing. It was agreed by all that so many new ways to deliver content are out, such as using audio, video, shared content, personalized content and mobile content. The choices are limitless and there is so much to explore that there is room so that we can all contribute! Interactivity and structured content will be key to communicating information as well.

That said, the group presented the challenges ahead, which included providing technical communicators with an education on understanding all the available possibilities, combating management’s misperception of cost, the general resistance to progressive change, business models still tied to old metrics, and too many tech comm specialists instead of tech comm generalists. An additional challenge mentioned dealt with the relationship that technical communicators have among themselves as well as to the rest of the world. It was suggested that technical communicators are not creating appropriate relationships with other business departments, and need to be proactive in business affairs to prove the value of tech comm as a whole and how it integrates with other business needs, thus providing a good ROI (return on investment). When the panelists were asked what skills were needed to go forward, they replied that the need to create communities to support each other and learn from each other was key, which could be done through such activities like participation in branding and discussion on the Twitter website with other technical communicators.  Bernard Aschwanden did comment, “People are not lazy enough!” which elicited a laugh. However, his point was that in this day and age, people just want more direct route to complete tasks, and community building was part of that.

Nolwenn Kerzreho, another attendee at Adobe Day, noted on Twitter during the discussion  that “[T]ech writers need to change, have to get an education in structured writing and writing for a global audience…Key is that needs to be promoted…everywhere!” Good point that I missed noting on Twitter myself, Nolwenn!

In other words, the panel felt that while this is a time with a lot of changes due to technological advances with plenty of opportunity to use different kinds of content to deliver information, there are still obstacles in the way that prevent those opportunities from coming to fruition. However, those obstacles aren’t anything that can’t be conquered over time. A big part of making these opportunities happen will be adopting the use of structured content and community building.

Now, if this was the caliber of the discussion just for the panel at the end of the Adobe Day event, then you can only imagine that each of the presentations before this were equally great as well, and why I’ve come back with renewed enthusiasm.

I’ll also just add here that I had the chance to meet SO people that I had only met through social media or featured in various technical communications media. It was like a parade of tech comm stars to me, and I was a little in awe to be among them! I enjoyed meeting so many people who really enjoy what they are doing and trying to make a difference in this field.

Waiting for Adobe Day to start!
Me and Kyle Johnson of Rocket Software
(photo courtesy of @barriebyron, also of Rocket Software)

I also have to say that in addition to Maxwell Hoffmann, I met others from the Adobe team as well, including Saibal Bhattacharjee, Ankur Jain (the Robo(Help) Cop!) and Tom Aldous. They did an excellent job putting this event together, and I appreciated their kindness and support in having me there to attend. I felt so welcomed! I was really happy to meet them in person after so many months of corresponding through Twitter or email.

I’ll be going through each presentation given prior to this panel in the next several posts over the next week, and I know you will find the information as educational as I did.

Next post: Adobe Day Presentations: Part I – Scott Abel and Structured Content.

PS– To anyone featured in this post or who attended this event, please let me know if I need to append or correct anything featured in this summary or in the future posts on the presentations. I am working off my “notes” that I tweeted during the event, so my recollection may need some tweaking. 😉

Posted in Uncategorized

Who says you can’t have a PDF book and print it too?

I’m in the process of recovering from a great weekend I had at the pre-conference of Lavacon hosted by the Adobe TCS team this weekend. There is so much to tell, but I’m working on a separate post for that, so stay tuned–it should be up in a day or so.

In the meantime, I just wanted to share something that I thought was pretty cool. Lavacon is taking place in Portland, Oregon, which is the home of the world famous Powell’s Bookstore. It is one of those landmarks that anyone who visits Portland has to visit, even if it’s just for a few minutes. The store occupies an entire city block, and includes both used books and new in print books. I was told by multiple sources that one should not think that an hour is enough time to spend in the store, as an hour easily turns into a whole day there. It’s THAT cool.

Marcia leads Val and I to Powell’s!

Well, I had a very limited window where I was going to be able to check out the city before returning home from the Adobe Day event, and my new friend, author Marcia Riefer Johnson who writes the blog, “How to Write Everything,” took me and Val Swisher, who is an Adobe Day and Lavacon speaker as well as the CEO of Content Rules, to Powell’s just for a quick visit, so that a) we could say that we had been to Powells, even if it was just a brief visit, and b) to show us this neat machine that prints books for customers on the spot! It’s called the “Espresso Book Machine“, and it prints out digital publications that are in the Powell’s catalog, and will print the book for you right on the spot.

Powell’s Espresso Book Machine!

Yes, while you wait!  Marcia goes into more details about how it works, and how she is using it for pre-publication purposes of her upcoming book coming out in April 2013 called, Word Up! How to Write Powerful Sentences and Paragraphs (And Everything You Build from Them.  Read about how she’s doing this in her blog.

In the meantime, as one of the things Marcia posted on her blog, she shared a YouTube video of how Powell’s Espresso Book Machine (EBM) works. I think this is pretty cool:

Now…imagine writing the user manual for this gadget? That would be quite the interesting and exciting task, now wouldn’t it be?

Val Swisher and I at Powell’s!

Val and I both felt that if we had the chance to go back to Powell’s, we definitely would. Thanks for taking us, Marcia! This looks like a great tool, not only as a consumer (this way, we can find lots of great tech comm resources and have them specially printed for us), but also as creators, allowing us to print our content as needed. Print is not dead! It has gone digital in more than one way!