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 V – Mark Lewis and DITA Metrics

After Val Swisher spoke about being global ready in today’s tech comm market, the final speaker of the morning, Mark Lewis, took the stage to speak about DITA Metrics.

Mark literally wrote the book about how DITA metrics are done, titled, DITA Metrics 101. Mark explained that ROI (return on investment) and business value are being talked about a lot right now in the business and tech comm worlds, so it’s worth having a basic understanding of how DITA metrics work.

Now, I have to admit, I know NOTHING about how any tech comm metrics are done, let alone how DITA metrics are done, so I listened and interpreted the information as best as I could. (Mark, if you are reading this, please feel free to correct any information below in the comments!)

Mark began by explaining that content strategy applies to the entire ENTERPRISE of a business, not just the technical publications. There are lots of ways to measure tracking through various means, including XML. Traditional metrics involved measing the cost of page, and the type of topic would be gauged by guideline hours. For example, a document outlining step by step procedures would equal four to five hours per write up of this type of procedure. Traditional metrics looked at the cost of the project through the measure of an author or a team’s output of pages, publications per month. It doesn’t measure the quality of the documents, but it concerned more with quantity instead of quality.

Mark referenced several studies which he based the information in his book, especially a paper done by the Center for Information-Development Management, titled, “Developing Metrics to Justify Resources,” that helped to explain how XML-based metrics are more comprehensive. (Thanks, Scott Abel, for retweeting the link to the study!)

XML-based metrics, Mark pointed out, uses just enough DITA information, concerning itself instead with task, concept and reference within documentation. XML-based metrics can now track the cost of a DITA task topic, showing the relationship between occurrences, cost per element, and total number of hours. The cost of a DITA task topic is lower because referenced topics can be reused, up to 50%!  For comparision, Mark said that you can look at the measurement of an author by measuring the number of pages versus the amount of reusable content of a referenced component. The shift is now in the percentage of reused content rather than how many pages are being used. Good reuse of content saves money, and ROI goes up as a result!

Mark introduced another metric-based measurement, namely through the perceived value of documents as a percentage of the price of a product or R&D (research and development), as well as looking at the number of page views per visit.  Marked warned the audience to be careful of “metrics in isolation” as it can be an opportunity loss, a marketing window. He clarified that page hits are hard to determine, because hit statistics could either mean the reader found what they wanted, or didn’t want that information. We have no way of knowing for sure. If technical communicators are not reusing content, this can make projects actually last longer, hence producing more cost.

Mark emphasized that through metrics, we can see that reuse of content equals saving money and time. Productivity measures include looking at future needs, comparing to industry standards, how it affects costs, etc. He suggested looking at the Content Development Life Cycle of a project, and how using metrics can help to determine how reuse or new topics cost in this process. By doing this, the value of technical communications become much more clear and proves its value to a company or client.

I have to admit, as I said before, I don’t know or understand a lot about the analytical part of technical communication, but what Mark talked about made sense to me. I always thought that measuring the value of an author based on page output rather than the quality of the writing didn’t make sense. Part of that is because as a newer technical communicator, I might take a little longer to provide the same quality output as someone who is more experienced, but that doesn’t mean that the quality is any less. So measuring pages per hour didn’t make sense. However, if consistency in reusing content is measured instead throughout all documentation, then the quality, in a sense, is being analyzed and it can be measured on how often information is referred or used outside that particular use. Using DITA makes a lot of sense in that respect.

More information about DITA metrics can be found on Mark’s website, DITA Metrics 101.

I hope you’ve enjoyed this series of all the Adobe Day presenters. They all contributed a lot of food for thought, and provided great information about how we as technical communicators should start framing our thought processes to product better quality content and provide value for the work that we do. I gained so much knowledge just in those few hours, and I’m glad that I could share it with you here on TechCommGeekMom.

Posted in Uncategorized

Upgrade Time! PREVIEW of the NEW Adobe Technical Communications Suite 4!

I’m very excited as this is my 100th post here on techcommgeekmom.com, and with this 100th post, I am able to present all of my readers with a special preview.

Adobe’s Technical Communications Suite 4.0 (TCS4) is now out!

Woo hoo! It’s great to see that along with upgrades to the Adobe Creative Suite and e-Learning Suite, now the Technical Communications Suite is getting a major update as well.

Now, you may be wondering, like most technical communicators, what changes have been made between the 3.5 version and the 4.0 version. Good question! There have been several upgrades to the software package, thank you very much. How do I know? Adobe was kind enough to invite me to a preview a little while ago, and even as a newbie to this software package, I can say that I could see that the company is trying very hard to keep up with the needs of technical communicators, and they are taking the necessary steps to embrace mobile technology, which is highly evident in this upgrade.

Now, I took as many notes as I could, considering the presentation went by faster than I could take the notes, but I know that there are a few major highlights that are important to cover.

As the speakers from Adobe started the presentation, they concentrated on identifying key trends they felt were happening in technical communications, namely a movement to structured authoring, rapid mobile growth in smartphones and tablets, the need to make content more interactive, the concern of technical communicators having to do more with less resources, and the need to provide searchable, personalized and socially enabled content. It sounded to me like they were on the right track, especially if the improvements they were about to present fulfilled these needs.

One of the main anchors of Technical Communications Suite is Framemaker, and here in the TCS 4 Suite, Framemaker has been upgraded to Framemaker 11. From what I’ve been able to gather from my observations, Framemaker had its heyday, then it lost favor, and now it’s starting to regain steam again. Framemaker (FM) 11 seems to be taking the improvements make from FM 10 another step forward. Structured authoring was the main focus of the improvements with this product, including multi-view editing environments providing WYSIWYG (What You See Is What You Get) of XML and author sources as well as getting WYSIWYG output as well. Content creators can edit XML documents in any view, and the changes are reflected in all views without manual changes. This bodes well for working towards single-source creation! DITA and XML support has been enhanced as well, and performance using these has been enhanced as well.

A big addition to FM 11 is ability to include rich media objects like vector images with hotspots, video, and 3D modeling. One of the features I liked that was demonstrated was one where play, pause, and jump buttons were created around a video/animation presentation within the content. Nice! The 3D model imaging that can now be used will be great for how-to manuals, so there is better context at looking or training on physical objects, like looking at a machinery part from all angles. From a productivity standpoint, SmartPaste and SmartInsert features have been added to help auto-format pasted or inserted text or content into a new document, but one can still retain the old formatting as well. Another appealing feature is the ability to create your own Framemaker set-up. Adobe’s goal was to enable content creators to be able to author content faster by allowing the creators to customize navigation and workspaces. That sounds great! Of course, what got me most excited was to hear that FM 11 has been oriented to now enable mobile output, including multi-screen HTML5 content as well as ePub 3.0 and Kindle formats. That’s definitely a step in the right direction!

The second main anchor of Adobe’s Technical Communications Suite is RoboHelp (RH), now available in version 10. RH 10 works seamlessly with Framemaker, as it always has, but again Adobe has focused on streamlining the workflow process as well as improving the product’s output. That output includes new outputs for mobile devices. RH 10 can deliver content to iPad as well as other tablets, smartphones, and desktops now—there are 17 output formats now! It is set up so that authors can work in a multi-author, multi-reviewer environment, where it’s easier to personalize and optimize content relevance. Content can be rich media—again, like FM11, and includes various HTML5 outputs that include mobile apps, ePub 3.0 and Kindle now.

The HTML5 output has also been made to be modern looking, frameless and SEO-friendly. The output is responsive design that works well with fluid layouts like CSS 3 and media queries. Like FM 11, RH 10 can customize and optimize the appearance of the content on each screen as needed. Socially enable documentation can be produced using RH 10, which means that creative native and web mobile apps can now be produced from RoboHelp. This is a big boost for making apps for iOS and Android mobile apps. The workflow view is easier as multi-layout options are available, and there is a preview tool that allows the author to see how the output will look on different devices and subsequently, there is the ability to assign different styles to different devices, including the output publishing settings for each device. One of the other features that caught my attention was that now there is also out of the box integration with MS Sharepoint, so it provides end-to-end workflow. Being someone who’s used SharePoint at my last job extensively, that would make things flow really well for output, and I’m sure that would provide a better product for the end user as well!

TCS 4 has several new features about it. While it includes Framemaker 11 and RoboHelp 10 as mentioned, it will also include the updated Captivate 6, Acrobat X Pro, and now Illustrator has been added (most likely to accommodate vector images better) and Adobe Presenter. I think I’m most excited that not only the newly updated Captivate has been included, but that Presenter has been included as well. I think this is a really smart move on the part of Adobe, because between Captivate and Presenter, more interactive content can be created and put out for mobile. And yes, as I mentioned before, the big push for TCS 4 is being able to provide technical communicators with tools to produce output for mobile devices. To use their words, they are “embracing the mobile revolution” with the multi-screen outputs that are in HTML5 and other mobile formats like ePub 3.0, but also providing tools to make the content context sensitive, providing socially enabled apps, and support for optimizing indexes, glossaries, custom metadata and other content features.

Adobe even made sure that it was understood how TCS 4 would work very well for those in the e-Learning world, saying that TCS 4 provides “new workflows to bridge technical communication with e-Learning” by providing tools that can create m-Learning opportunities and rapid step-by-step authoring. Keeping up with other major trends, cloud-based computing is integrated into the product, as review workflows can now be done using the cloud with TCS 4.

One of the new pricing features also includes using the same cloud pricing model. There will be monthly rates as well as a reduced rate that monthly is cheaper than a month-to-month rate. Due to a lot of these new features–especially the ones that help enable publishing content for HTML5 and other mobile content, I would especially upgrade if I had an older version of TCS or older version of Framemaker and Robohelp. The fact that both FM 11 and RB 10 have customizable views is a big bonus, as well as having the capabilities to produce mobile-friendly content is a big boost. Having more efficient single-source authoring, and cloud capabilities—there are a lot of good things that are added to this.
Now granted, like I said, I’m still a newbie to using the product and using it, but from this reviewer’s standpoint based on the preview, it’s good to see significant upgrades to a product making a strong comeback in the technical communications field. I do hope that as time goes on, Adobe continues to keep up with updates to the product, especially considering the “Creative Cloud”-like option with obtaining the product.

It’s an exciting product, from what I can see, if you are just starting out, or need to revamp your technical communications software.

I hope this review has proven to be helpful. Have you downloaded your copy yet? If so, do you think these changes are big improvements or is there still something missing? Please leave a comment below on what you think about TCS 4 so far.

Adobe notified me just as I was writing this post (before I posted it) that I will have a chance to test-drive the product itself very shortly, and once I have it installed, I’m hoping that I can give my techcommgeekmom readers more information about this product–from my newbie perspective, and see if the preview information holds up to the real deal. Stay tuned!