Posted in Uncategorized

Adobe Day@STC Summit 2014 – We Went Back to The Future

We definitely didn't hear this panel say to any of us, "I'm afraid you're just too darn loud!"
We definitely didn’t hear this panel say to any of us, “I’m afraid you’re just too darn loud!”

I apologize for my blog coverage of the 2014 STC Summit edition of Adobe Day being delayed–it’s been a busy month! But hopefully, you’ll feel it’s been worth the wait, and you had a chance to see my live Twitter feed as it happened.

The STC’14 Adobe Day felt a little bit different this year. One of the things I noticed was that as much as Adobe says that these Adobe Day events are Adobe-product free, lately, they haven’t been. HOWEVER, they are still not one big, in-person infomercial either. Adobe products are not brought up much, but if they are, it’s to show that they can be tools to use to create solutions to common tech comm issues. So, it might be an inadvertant infomercial in that respect, but it’s not done in a blatant way that screams, “YOU NEED TO BUY ME!!!!!! PLEASE BUY OUR PRODUCTS!!!” Adobe continues to do a good job in showing what tech comm issues are out there, and as leaders in the software field, they are tuned into these issues and are creating products that benefit the technical communicator. I think that’s fair enough. The talks, overall, were broader topics that in some instances used Adobe Tech Comm Suite tools to provide solutions. And you have to remember, while these talks are aimed to be product-free for the most part, it’d probably look pretty bad if you had someone declaring all the glories of a competitive product when Adobe is hosting the event. Y’know?

With that out of the way, I observed some other things that made this a little bit different. First, there were fewer speakers this year. I felt that was a good thing, because in the past with more speakers, each speaker would be racing to get his/her presentation completed in a very short amount of time, and there would be little time for questions or discussion. Since there were fewer speakers this year, each one could elaborate more on their topic, which allowed for more time for questions and discussion. More networking time during the breaks was also a benefit from having less speakers.

The other difference I saw dealt with the speakers themselves. While they were all familiar, established voices in the tech comm world, it wasn’t the same crowd that one usually sees at Adobe Day events. All of them have participated in Adobe events or other tech comm events before, but in the past, it usually is most of the same speakers up on the podium. While I like all the “usual suspects” very much, and consider them my mentors and have become friends with several of them, seeing these new “players” was actually refreshing to me. I hope that Adobe continues to change up the speaker lineups with future Adobe Days, as all the speakers I’ve heard have a clear voice that’s worth listening to, and hearing as many of those voices as possible provides both variety and fresh perspectives going forward. As I go through each presentation in forthcoming blog posts, hopefully you’ll see what I mean.

But as tradition in this blog dictates, I always start with the panel that capped off the Adobe Day event. I find that these panel talks bring an umbrella perspective to where we are as a profession through several points of view, and seeing where there are agreements and disagreements in the issues at hand.

This year, the panel was moderated by Matt Sullivan, who has been an Adobe Day speaker in the past. He did a great job, as this was the first time I’d seen him as the moderator of an Adobe Day panel. The panel consisted of Adobe Day speakers Marcia Riefer Johnston, Bernard Aschwanden, Kevin Siegel, and past Adobe Day speaker, Joe Welinske. The theme for the panel was looking ahead to the future of where tech comm seems to be going.

The Adobe Day Panel L to R: Matt Sullivan, Bernard Aschwanden, Joe Welinske, Marcia Riefer Johnston, and Kevin Siegel
The Adobe Day Panel
L to R: Matt Sullivan, Bernard Aschwanden, Joe Welinske, Marcia Riefer Johnston, and Kevin Siegel

Matt started with the point that tech comm is more than tech writing now, so what do we need to improve short-term and long-term? Kevin responded first, saying that we need to do more with less on smaller displays and adapting the content appropriately for mobile. Marcia added to that, saying that using less can mean writing tighter as well. (She has a technique she taught during the STC Summit, in fact!) Joe agreed with Marcia, adding that technical communicators need to put in the time to make concise content meaningful, and to look at simplified English as part of that objective. Bernard felt that attending workshops and demonstrations were important, because technical communicators need to continually learn and adapt in this industry! He added that SMEs (Subject Matter Experts) should contribute to content, but technical communicators should control it. Kevin also agreed with Bernard, saying that SMEs are writing content more often now, so teaching them to write tighter will help. Marcia chimed in that many people are now being required to write, but don’t have the skills. We need to help with that.

Moving onto topics about how technology affects technical communication, Kevin said that new technology, like Google Glass and other wearables, is emerging, and we need to understand how these work. Joe pointed out that the Pebble watch now is starting to have user docs now, and more will be emerging. Bernard added that gesture based technology similar to the Xbox Kinect will need documentation.

Matt then asked, “What should we look forward to in the next five years?” Bernard felt that less specialization will be needed so that the right people write the right content, such as an engineer who can write. Specialized writing will be very important. Joe added that we need to agree on taxonomy and terminology, and use style sheets more often for consistency. Marcia believed that topic-based writing will be emerging more as a growth area. Kevin explained that in e-learning, there is a need to develop learning for new devices that responds to user displays, thus accomodating multiple screens.

The next question asked about how to help educate and help with adapting certain generations adjust between print and digital writing/designing. The consenus was that we just need to adapt. The panel encouraged the audience to get to know your UX/UI people, as they will help you learn to adapt, especially if you aren’t as tech-adaptive.

The last question centered on customers customizing their content–is this a trend? Bernard leapt into a response with, “GOOD! DO IT!” He encouraged us to help customers to start doing personalized help, or personalizing any information, for that matter! Moderator Matt closed by saying that rich media that engages users is going to be about content strategy, but it will also be about content marketing. The group agreed that personalized, concise information going forward will be best!

"I guess you guys aren't ready for that yet--but your kids are going to love it!"
“I guess you guys aren’t ready for that yet–but your kids are going to love it!”

And that was it! The session went by quickly, but as you can see, there was a lot of great information that many technical communicators can take and use going forward in their own work.  While it might take some time to adapt, sure enough, it will bring the field forward as technology and the way we access it moves ahead.

Coming soon: The individual presentations at Adobe Day #STC14 Edition!

Posted in Uncategorized

Plain language always wins. Always.

Businessman Midair in a Business MeetingI love it when I’m inspired to write a blog post due to something that I read through social media. In this case, this morning I saw a Facebook post written by Jack Molisani, author of Be The Captain of Your Career, executive director of the Lavacon Conference, and technical recruiter that intrigued me. His post is listed below with his permission. It stated:

Just read this in a resume:

“Sophisticated, results-driven Program Management professional with a demonstrated ability to successfully lead business or technical initiatives with demonstrated experience in IT Governance, cost and schedule management, leadership, cost estimating, and infrastructure management covering full life-cycle application development & integration, data management, strategy & IT architecture implementations/roll-outs.”

First thought: Sophisticated? He wears shirts with frilly cuffs and drinks tea with his pinky up?

Second thought: Run-on sentence. Can’t communicate well in writing.

Oh candidates, why must thou shootest thouselfs in thine own feet?**

I definitely agree with Jack’s assessment. The run-on sentence is particularly bad.

The thing that caught my eye even more was the language used. As Jack alluded, it initially implies some sort of sophistication or high-intelligence level.  But in the end, couldn’t this candidate have simply said, “I am a successful and reliable project manager with experience in X, Y and Z”?   I mentioned to Jack that I would not be surprised that the candidate wrote this way because many job descriptions for openings are written similarly.

One of my greatest frustrations when I did job searches in the past was getting through wordy job descriptions, as they were written in the same gobbledy-gook language used by this candidate. WHY? Is this done for the purpose of weeding out candidates from the get-go, as if to say, “If you can’t read this, then you must be too stupid for this job”? I’ve often gotten that feeling.  Or, I’ve read many job descriptions that sound much grander than they are–again, much like this candidate’s description of himself–only to find that it’s a basic job with several steps, and it’s not that hard to do. The job description was only made to sound like more than what it really is, which is what this candidate was trying to achieve, I’m sure.

This made me think about plain language use, and how it’s starting to take hold in technical communications. I’m really glad about this shift. Why? To be honest, I’m an idiot. While I have a solid education, and can speak and write fairly well, how often will you hear me using the $10 words? Rarely. The use of “fancy” language alienates people, and in my case, it overwhelms me. My brain can’t always process it sufficiently. I find that technical writing is similar to translating complicated English into simplified or plain-language English.  Since I’ve learned how to do that over many years, it’s become a little bit easier for me to process. But, most people don’t have that internal filter. They hear or read, “Blah, blah, blah,” as Jack implied in his reaction above.

A follow-up comment to Jack’s post by one individual pointed out that this is how business people are taught to write. That’s a good point. I would also point out that legal professionals have the same issue. Have you ever tried to read “legal-ese”? It’s just crazy. I remember an early assignment in grad school required us to look up the local legal codes in our towns, and “translate” the legal mumbo-jumbo into plain language. I remember mine clearly, as it directly related to my house. Put into plain English, the particular housing code from my town stated that if you have a pool in your backyard, you have to have a fence around it for legal and insurance purposes; if you didn’t, you’d be fined. Simple enough, right? Not if you read the original language.

Why are business and legal professionals still writing as they did a century ago? Who are they trying to impress? In our current digital age, it’s a pointless endeavour.  We are a society of instant gratification. We need people to get straight to the point. This is most evident with the proliferation of mobile devices. We need information to be short, fast, and quickly comprehensive.  Writing in the “sophisticated” language used by that the job candidate above isn’t going to help anyone anymore.  We need to be able to communicate with customers and citizens in a way that everyone can understand. This is not the dumbing down of language as we know it, necessarily. As I said earlier, using grandiose language alienates the reader, especially if the reader is trying to find out basic facts. All Jack wanted to know was whether this person qualified for the job.  Instead, he had to translate what the person was saying before he could determine that, and that act in itself turned Jack off to this candidate. It’s not a good reaction to have.

Plain language is not simplifying language for the less-educated. It’s a simplification of content at its best. Technical communicators and universities (and yes, I’ll even say it, all schools in general) have to start teaching their students to have a full understanding of rich vocabularies, yet choose words wisely to communicate the best message possible. Tech comm does that in aces. We need to get the business schools and law schools (among others) on board with this concept.

So, Candidate, if you want to get in Jack’s good graces (or anyone’s good graces for that matter), you’d be better off writing in plain language. If you pick up a copy of Jack’s book, too, you’ll get some other hints that will make you a more viable candidate. Get to work!

**Update: a few hours after I originally posted this, it appears the either Facebook is hiding the post, or Jack took it down. I know that some of the comments he got showed that people misinterpreted his intention and purpose of the post, and perhaps it got too heated to keep the post up, which is a shame. I definitely did get his permission first before I “reprinted” it here.  I support Jack’s intention in sharing the information, because I know that he didn’t publically humiliate a specific person by name or inference, and his purpose was to show how a recruiter really does react to a poorly written resume. Jack’s business, and by extension his recent book, are meant to be guides to helping anyone get a good job. Jack has continually pointed out that many of the steps needed are so basic. This is what he was trying to point out in the post he wrote above. I suppose I understand his position because I’ve been the candidate enough times that I actually know that the smallest things–like what Jack pointed out with this candidate–have made the difference as to whether I got an interview or not. The other perspective I understand is that as a recruiter. While I’m not a recruiter, my mother owned her own agency for years, so I learned a lot from her about what that business entails, and it’s not an easy job. So for that, I understand where Jack was coming from. He wasn’t being antagonistic, but rather it was a remark of frustration. –techcommgeekmom

Posted in Uncategorized

A new milestone for TechCommGeekMom!

20Ktoday

Yes, you are reading that correctly. Today, I crossed the 20,000 all-time hits mark on my blog. And no, it wasn’t my husband going to my page and hitting the refresh key several times either. (I made sure to tell him not to do that!) I’m thrilled!

I still realize this is small potatoes compared to many tech comm blogs out there. I think I would’ve hit this mark earlier if this past February hadn’t been so slow and bogged down from everyone dealing with the worst winter in recent memory. Nonetheless, I’m finally here in the 20K club!

Whenever I get to this point, I always feel like someone who just won an award on one of those shows like the Academy Awards, the BAFTAs, the Grammys, etc. I want to thank everyone who has supported me so far with my little blog, and have encouraged me to keep going with it. I will always think of this blog as a work-in-progress. Hopefully, it will grow not only with more readers, but that I grow in the process, and the quality of the content grows as well. I honestly appreciate my readers!

Thank you! Onwards to the 25, 000 mark!

Posted in Uncategorized

One Morning with Google Glass Was Enough for Me!

Here I am with my Google Glass package, sad that the experience wasn't more, and the price was significantly less.
Here I am with my Google Glass package, sad that the experience wasn’t more, and the price was significantly less.

As disappointed as I was that I’d have to return my Google Glass because it really wasn’t in the budget, I knew there was a 30-day trial to use Glass, so my husband suggested that perhaps I should give the trial a whirl, and if I still liked it, I could purchase it again later when the price goes down. I wasn’t keen on the idea because I was afraid that if I liked the product enough, I’d be reluctant to return it. Despite his encouragement to try Glass first, my husband didn’t help the cause, as he’d constantly be emailing me negative articles about Glass.

Nonetheless, I decided that I’d forge ahead and give Glass a try. I didn’t even last one morning.

Upon receipt of my Google Glass, the Glass didn’t have enough charge to even set up my account on the device out of the box, so I had to charge it overnight. Even with an overnight charge, it was only at 88%. Something’s not right with that. You’d think that with such a small device that a) there would be just enough charge in it to set it up, at least, and b) that charging it overnight would put it at 100%. So, not a good start, but by the next morning, 88% was enough power to be able to set the device up.

Now, I hate to compare apples to oranges, but I couldn’t help but make mental notes of how much the experience was nothing like dealing with an Apple mobile device. Yes, I know that Glass is not a smartphone, but it does connect to one’s smartphone, after all. I’ve done the set-up of my son’s Android smartphone (and I will admit, I’m no Android expert) and set-up 4 iPhones and 2 iPads over the years, so I think I have a good idea of what a good out-of-the box experience should be.  I’m also fairly adept at figuring out new technology, and have been the “tech person” in my family for decades, even before digital technology was mainstream. Add to those credentials that I am a technical communicator, so figuring out how to set a digital wearable device should be par for the course.

When I used an iPhone for the first time, I could figure out everything instantly. Apple walks you through set-up directly on the device, and nothing extra has to be done on another device paired up to it. Google Glass had some directions in the viewing screen (for lack of a better term), but it took me a while to set the device up so that it could connect to my phone and read the QR code that the app had to read to connect and activate the account. I had also read the Google Glass online help files on my laptop as I was doing this. It’s not a good sign, to me, if I have to read the website simultaneously while setting the device up. Even then, the directions weren’t that great. It assumed that everything would go smoothly, so set-up would be a snap. However, mine was not, and I couldn’t find any answers to problems I had.

Eventually, I did figure out how to get Glass set-up. I was connected to my Google account, and ready to go. It was early in the morning, and I decided to try it out, let me son see how it worked, and my husband was curious to see how it worked, too, even if he was the naysayer against it.  Because I didn’t want to accumulate too much personal content on the device, I tried to be careful about not taking video or photos, as I needed to learn how to download apps and manuever the device first.  My son liked what he saw, and I had him do the instruction, “OK, Glass, Google Minecraft,” and it did. He liked it. But, being that he is a rambunctious 12 year old boy, I didn’t want him wearing this expensive device for long. It was then my husband’s turn.

polish-chicken-11
This is a Polish chicken. And this is what my hair looked like that morning (more or less).

Before I could try to instruct him on how to manuever the device, my husband decided that he already knew how to use it based on viewing the Saturday Night Live skit from a while back. I scolded him for just trying to do things randomly, and I wanted him to give them back to me if he wasn’t going to give me a chance to explain how to use them properly–based on my limited knowledge at that point. The next thing I know, he proclaims, “OK, Glass, take a picture.”  In full glory, in my rumpled NJIT pajamas, angry face, and Polish chicken hair because I had not gotten ready for the day, he had a photo of me. I was not happy about that. He then asked, “If I wanted to send this, what would I do?” At this point in the story, he and I differ on the account, but since it’s my blog, I’m telling it my way.  He started to say, “Would you say, ‘OK, Glass, send an email…’?” and when he realized that he’d actually be sending an email, it opened up to THAT PHOTO.  “Oops!” he claimed, and tried to back out of it. He did say, “Cancel,” a few times, but nothing happened. But somehow, the photo did get sent, and it was sent to the first person listed on my Google + list, whom I don’t know personally! How embarrassing! I had to get on my laptop later, and send a note to her in Google+ explaining the situation, that I wasn’t sending a photo of a crazy, angry bag lady on purpose, etc.  By that time the Glass was confiscated,  that was enough to get me on the wrong foot with the device even further.

After everyone had left for school and gone off to the office, I had a little time to myself to try to figure more about this. One of the biggest flaws I saw with this device is that it’s not intuitive. As I mentioned, the set-up was not smooth at all. I found that I couldn’t figure out for the life of me how to delete the photo or the Google search from the Glass unless I reset the device back to factory settings. That can’t be right.  Additionally, I couldn’t figure out how to get to a screen to add apps. Again, that doesn’t make sense. So, I went back to the Google Glass Help online to try to figure that out. I couldn’t find any instructions on how to add apps. Additionally, I saw that there were less than two dozen apps available at all! Geez, that doesn’t seem like a lot. I know that this is a product that’s still in development, but you’d think that after a year, Google would have more apps than what I saw.

So, when I took into account how the product wasn’t intuitive, had very few apps, had no ability to delete things (I was able to delete the photo in my Google account via my laptop, but shouldn’t be), plus the exorbitant price, I succumbed to what my husband had been telling me all along. It wasn’t right for me.  So, I called Google to ask for the return labels so I could send it back and get my full refund.

Believe me, I was really frustrated with this product. Although my family thought it was cool, they also felt that it wasn’t so easy to figure out how to use it seamlessly, and we’re all fairly technical–even my son. But for something that was the price of two new iPad Air devices or laptops that had much more functionality, I had one funny pair of electronic eyeglasses that didn’t do a whole lot.  The experience was disappointing, and I didn’t want to pursue it further–that’s how frustrating it was in one morning.  To quote my husband, “If Apple had come out with these instead of Google, it would be cheaper and it would be a completely different experience.” This is coming from a guy who’s very reluctant to use Apple products in the first place, and he even came to this conclusion. The sad thing is, he’s right. When watching that SNL skit again after this experience, my experience wasn’t too different, except the character in the skit got apps on his Glass, at least. The scary thing is, that skit was done a year ago, and nothing has changed since that time!

Despite this less than stellar experience with emerging technology, I think if the price came down significantly, the intuitiveness of the product was better–including understanding how to delete content and add apps, and there were more apps to use, then I’d definitely reconsider getting Glass again in the future. The product isn’t ready for primetime, in my opinion. Even the iPhone had more features on it when it first came out in the first year than this has.  I initially got interested in Glass after seeing my friend, Marta Rauch of Oracle, using them, and seeing her presentations about the product’s many capabilities. I wouldn’t have rushed to purchase the product and have a chance to use them if I didn’t believe that there was a true potential in the product. I think Marta has more of a chance to play with them and see the potential because she uses them professionally as well as personally. Part of her job is seeing how Glass can be integrated in projects and products that she’s working on at Oracle. I don’t have any such projects or products I’m trying to develop.  And as I said, I do think there is potential for a wearable smart device.

I don’t think Google Glass in its current state, however, is the product for me right now. Once some of these issues are fixed, I’ll see about giving it another try. Believe me, I’m really disappointed, but at least I can get my money back, and Google is being fairly cool about me returning it. And yes, I’ve given them this feedback–twice.

Do you think I didn’t give it a chance? Do you think I was crazy to even try it in the first place? What do you think about such devices? You can put your response in the comments section below.

 

Posted in Uncategorized

Adobe Day at #STC14 Will Be Looking Towards the Future!

Doc and Marty McFly can't believe the fabulous information they are getting at Adobe Day @STC Summit 2014 . (They already went, and said it was fantastic--not to be missed!)
Doc Brown and Marty McFly can’t believe the fabulous information they got at Adobe Day at the STC Summit 2014. (They already went, and said it was fantastic–not to be missed!)

With each big conference that I attend, I always look forward to Adobe Day, and Adobe Day at the 2014 STC Summit is no exception.  You’ve probably read my past posts about Adobe Day from other conferences, so you know how rich in information they are. I’ve learned an enormous amount of information FOR FREE that would otherwise cost thousands of dollars from the leading experts in the field. It’s hard to find that anywhere else.

On Sunday morning, May 18th, 2014, Adobe is once again putting together a stellar group of technical communications luminaries to set our imaginations on fire! This year’s theme appears to be, “Vision 2020: The Demanding Job of a Technical Communicator.”  Based on the descriptions of each speaker’s talk during this morning session, each will be providing advice and tools–free of any product promotion–that can help make our demanding jobs easier and more productive.  I’ve heard all the speakers before in one way or another, and I can tell you that all of them are top rate. Most of them have spoken at previous Adobe Day events, and they are invited back time and time again because they have valuable information to share.

Kapil Verma of Adobe will be speaking about who he thinks are today’s technical communicators (hint: there’s more than one type!). Marcia Riefer Johnston will be talking about single-sourcing techniques she used to save her company USD$16,000! I’ve taken Marcia’s writing workshop and read her book, so I can tell you she have some marvelous tips. Kevin Siegel will be talking about how to combine something I love–e-learning–with technical documentation to make the documentation more dynamic and valuable! I’m looking forward to that.  Bernard Aschwanden–the STC’s newly elected vice-president–will be speaking about using content strategy to help promote revenue growth. And last, but not least, a panel including all the speakers plus Tom Aldous of Acrolinx, moderated by Matt Sullivan, looks like it will be quite the lively talk.

Did I mention that breakfast, snacks, and lunch are included, too? And it’s FREE?

I know–you are saying, “Great! I want to go! I don’t want to miss out on this!” Great! But you do have to register so that Adobe knows you are coming! Make sure you register by 11:59 PM PDT on May 16th, because you don’t want to miss out!

Register for Adobe Day @ STC Summit 2014

I will be covering the event LIVE on Twitter from my @techcommgeekmom account, so make sure to follow along, even if you are attending!

See you there!