Well, the 2011 conference is officially underway. Joe's speaking now, thanking sponsors and exhibitors and taking care of conference details.
For the first time, computer lab with all sorts of installed software for attendees to experiment with, plus guided lab sessions by vendors.
This is a session of polls, many of the questions submitted in the conference online community. The poll results will be posted to the community later.
Which skills are most important in career? Of the 5 choices, the ability to learn quickly got 45%, followed by writing and interpersonal skills at 21% each. Tool knowledge had 9% and understanding IT had 5%.
Favorite way to learn a new authoring tool? Trial & error overwhelming favorite at 42%, with classroom training at 21% and eLearning at 15%.
Improving skills in what area will best prepare you for the future? Delivering information viz handheld devices was tops at 35%, with eLearing development second at 25%. Social media and usability testing had 13% and 11%.
When asked at a party what you do for a living, you respond? Tops was writer, with 42%, then technical communicator at 33% and "I work with computers" at 14%. Unemployed and user assistance pro tied for last with 6%.
Which help controls do you use? "What the hell are A links and K links?" got 66%. A l;inks got 15% and A and K links got 10%.
What;s the biggest challenge to adopting a new tool or process? Enough time got 45% with resistance from personnel second at 29%. Lack of funds was third at 15% and infrastructure complaints had 11%.
Where do you think AIR Help will be 5 years from now? "What the hell is AIR Help?" got 37% with used in isolated cases a close second with 36%. Not sure was a distant third with 19% and widespread had just 8%.
Have you considered using a wiki for SMEs to review content? Yes, but not doing it had a bit of an edge with 33%, and "no, we don't want the SMEs fooling around with our content" was second with 25% and "No, but that's worth looking into" had 25%. Using one now was 15%, and "Wha the hell is a wiki?" had just 2%.
How do you keep your users up-to-date on software changes? "Other" won going away with 56%. A newsletter/bulletin came in second with 19%, and "we can't keep up" was third with 13%. Blog (7%) and webinars (6%) trailed.
How often do you telecommute? Never had 31% and less than 1 day/week had 30%. 1-2 days a week was at 19%, and full time came in at 12%. Interesting that 40% telecommute a day or more a week.
In the past year, what has been your primary method of non-sales contact with users? No contact came in first with 30%, and other had 25%. Email was third with 23% and in-person had 13%. Tony noted that a lot of the "no contact" comes from outsourcing, when we get contracts, we don't know who our users will be.
What type of smartphone do you have? No smartphone came in first at 40%. iPhone was next with 23% and Android trailed a bit with 16%. BlackBerry had 13%, Other had 6%, Windows Phone came it with 3% and Nokia had 0%.
Monday, March 14, 2011
Sunday, March 13, 2011
Sunday Sessioning
After spending some time in the embedded user assistance session with Rob Houser (a subject very near and dear to my heart, where he was riffing on some themes that I've been advocating for for quite a while), I'm now in Saul Carliner's session on eLearing.
Saul is energetic and engaging, just the type of person you want to listen to. I entered when he was talking about the notion of completion and acceptable performance of tasks. If you're writing eLearing questions and answers, what's acceptable for task completion? It's different if the task is, say, installing a pacemaker compared to installing software.
He also talked about creating objectives. Using words such as "know" and :understand" aren't acceptable because the goal is not observable or measurable.
Prerequisites. Objective or course? If you make it a course, you can say that you took the course. If you make it an objective, then you have something measurable that they should know how to do beforehand.
Don't write course materials before you write the test.
You just need to test the main objective, not the supporting objectives. If students have learned the main objective, they have by default also learned the supporting objectives. That said, testing the supporting objectives as you go along help make surte you're on track.
The number of questions you write depends on the situation.
Finally, I'm spending a bit of time in Linda Urban;s session on topic types. Of course, I enter right in the middle of an exercise, so it'll be a few minuts before she gets back to talking about session content.
What's interesting is the notion of design patterns for topic types. Also, topics can be broken down into elements, and different types of topics use different sets of elements.
Design patterns are useful, and their development is iterative, but their usefulness can't be ascertained without adding actual content. And adding content lets you know if the design works.
"Awesome" website recommended: usability.gov.
Interesting notion: links are a distraction. If you want people to read your topic, dont' add links.
Saul is energetic and engaging, just the type of person you want to listen to. I entered when he was talking about the notion of completion and acceptable performance of tasks. If you're writing eLearing questions and answers, what's acceptable for task completion? It's different if the task is, say, installing a pacemaker compared to installing software.
He also talked about creating objectives. Using words such as "know" and :understand" aren't acceptable because the goal is not observable or measurable.
Prerequisites. Objective or course? If you make it a course, you can say that you took the course. If you make it an objective, then you have something measurable that they should know how to do beforehand.
Don't write course materials before you write the test.
You just need to test the main objective, not the supporting objectives. If students have learned the main objective, they have by default also learned the supporting objectives. That said, testing the supporting objectives as you go along help make surte you're on track.
The number of questions you write depends on the situation.
Finally, I'm spending a bit of time in Linda Urban;s session on topic types. Of course, I enter right in the middle of an exercise, so it'll be a few minuts before she gets back to talking about session content.
What's interesting is the notion of design patterns for topic types. Also, topics can be broken down into elements, and different types of topics use different sets of elements.
Design patterns are useful, and their development is iterative, but their usefulness can't be ascertained without adding actual content. And adding content lets you know if the design works.
"Awesome" website recommended: usability.gov.
Interesting notion: links are a distraction. If you want people to read your topic, dont' add links.
Job hunting
The conference introduces a new feature this year, a career rune-up morning session by ProSpring's Jack Molisani. Jack has been a long-time fixture at the WritersUA conferences, as a vendor and as a speaker.
Part of his morning session is a presentation called "Job Hunting Secrets That Might Surprise You." It focused largely on resumes and interview tactics.
"Official" definition of resume is wrong. If not a summary of what you've done & can do, what is it? It's whether you match what the reader is looking for. Includes a short account of your career and experience. But it has to help the reader find what they are looking for.
No one will read your resume. They'll scan it.
You'll never be hired because of your resume. You wil be rejected because if it. But interview because you weren't rejected.
Never rejected anyone because their resume was too short.
Recruiters automatically assume you're not qualified until you prove otherwise.
What are some of the mistakes job hunters make? Well, not following job submission directions is tops.
You can see the presentations on the ProSpring website.
Part of his morning session is a presentation called "Job Hunting Secrets That Might Surprise You." It focused largely on resumes and interview tactics.
"Official" definition of resume is wrong. If not a summary of what you've done & can do, what is it? It's whether you match what the reader is looking for. Includes a short account of your career and experience. But it has to help the reader find what they are looking for.
No one will read your resume. They'll scan it.
You'll never be hired because of your resume. You wil be rejected because if it. But interview because you weren't rejected.
Never rejected anyone because their resume was too short.
Recruiters automatically assume you're not qualified until you prove otherwise.
What are some of the mistakes job hunters make? Well, not following job submission directions is tops.
You can see the presentations on the ProSpring website.
Starting Sunday @ Adobe
Sunday starts early this year. Two vendors at the conference are having morning-long product presentations. I'm starting the morning in the Adobe session.
Ankur Jain, RoboHelp's product manager in India, is opening the morning talking about how he sees the direction of documentation, including that users want documentation that's more collaborative and interactive.
He describes RoboHelp 9's output as providing a wide range of user collaboration, from topic forums to the ability of add user tips.
He talked also about outputs. One of the pieces of exciting news is that RoboHelp 9 will now output EPUB output. eBooks are going to be a next wave of content output.
Rick Stone then talked about how RoboHelp enables content finadability.
The Adobe session got a good turnout too; it looks like close to two dozen folks got themselves up early on a Sunday morning for this training. (Author-IT had less than half that, and the career tune-up got about 10.)
Ankur Jain, RoboHelp's product manager in India, is opening the morning talking about how he sees the direction of documentation, including that users want documentation that's more collaborative and interactive.
He describes RoboHelp 9's output as providing a wide range of user collaboration, from topic forums to the ability of add user tips.
He talked also about outputs. One of the pieces of exciting news is that RoboHelp 9 will now output EPUB output. eBooks are going to be a next wave of content output.
Rick Stone then talked about how RoboHelp enables content finadability.
The Adobe session got a good turnout too; it looks like close to two dozen folks got themselves up early on a Sunday morning for this training. (Author-IT had less than half that, and the career tune-up got about 10.)
Saturday, March 12, 2011
Joe's hard at work
Most of you see conference founder and president Joe Welinske on stage introducing speakers or presenting himself. But he works hard behind the scenes to make sure the conference experience is aces for everyone. And he's not above pitching in on the "grunt" work, as pictured here collating and stuffing the conference bags everyone receives when they register.
Monday, February 28, 2011
The insanity of WritersUA
Don't get me wrong, the WritersUA Conference for Software User Assistance is by far THE best industry gathering I've ever attended. (To be fair, I've not attended many non-WritersUA conferences, but I have evaluated the session lineup of others, including past STC conferences, and WritersUA easily tops the others.) But for me it is an absolutely crazy week.
For me, it begins before the conference does. Not like organizer Joe Welinske and his crew, who have been working long hours for weeks on end to culminate in this day. But my conference week has always begun on Saturday, when I volunteer to help Joe put together the bags you all get when you register. It's tedious, labor-intensive work that can't be automated (and it was much more a chore in the heady days of the mid-90s, when the conference drew more than a thousand attendees), but it's also enjoyable in many ways. I get to catch up with Joe and Shannon and Sharon and often Joe's parents, most of whom I have not seen since the previous year. It also enables me to find out late changes, see what things Joe needs, and other odds and ends.
Saturday night, I'm prepping for Sunday. I already have picked out and designed the template for the year;s daily newsletter. I'm checking my email and making final plans for Sunday.
Ah Sunday. What used to be basically a half day has this year morphed into a full, multitasking day. It began with Jack Molisani, of ProSpring and who runs LavaCon, offering a full-morning job-seeker presentation, free for all attendees. Add to that both Adobe and Author-It offering information and training on their products, all of which I want to be in, and the morning is suddenly packed.
A few years ago, Joe began offering the Sunday Supplemental session, sessions that lasted a full Sunday afternoon where presenters could dive deep into useful topics as add-ons to the three-day conference. I usually spend a short time in all three, writing up brief summaries for the Monday newsletter. In the evening is the LaunchPad and conference orientation sessions. I don't spend time in them to get information , but just to take a few photos, again for the newsletter.
Exhibitors are also setting up their booths for Monday and Tuesday, and I spend time going around to all of them, reminding them of the newsletter, asking about any items them might have, news they might want spread, and again taking photos.
And then, once again this year, Joe has an informal mixer scheduled at the lobby bar, where I'll catch up with more old friends and take a bunch more photos. Then it's off to produce the Monday newsletter. With luck, I'll have had good chunks of it written, and it'll be about adding some more items, selecting, editing, and laying out photos, checking with Joe about last-minute changes for Monday, having it edited by Sue Heim, and printing out a couple hundred copies before I can head off to bed.
So officially, the conference hasn't even started and I have one very long day under my belt.
And one the conference sessions start, I'm once again faced with the same problem I find at WritersUA every year: Which sessions to attend.
I have found, in the nearly 20-year history of this conference, that during many, if not most, of the time periods, there are at least two sessions I want to attend. Unfortunately, cloning technology has not advanced to the point where I can be in two or three places at once, so I'm forced to make hard choices. Let me explain.
Monday morning begins with a session open to everyone. After that, the breakout sessions begin. This year, I have 2 that I want to attend: "Research-Validated Practices for Designing Effective ELearning," by Saul Carliner, and "Designing Content for Mobile Devices," by Scott DeLoach. I'm also thinking about "A Pattern Library for User Assistance," by Rob Houser.
But that's nothing compared to the afternoon. In the 12:45 and 2:05 time slots, I've found 4 sessions of interest, and in the 3:25, "only" 3.
To start with, 12:45 brings "Leveraging Social: User-Generated Content, " by Doug Bolin, "Comparison of Current Help Authoring Tools," by Matthew Ellison, "Global User Assistance Requirements and Guidelines," by Pam Noreault, and ""Trends in Usability Testing," by Kyle Soucy. The latter two probably are the ones I lean toward the most.
But then at 2:05, there's the Adobe Lab, "Crating a Strategy for Video to Attract Users and market Your Help Content," by Harry Miller, "Using Personas to Improve the Customer Experience," by Joan Lasselle, and "Developing for the Unknown - Using CSS, Other Control Files, and More," by Neil Perlin. I'm a huge personas advocate, but I'd love to get some hands-on time with the latest Adobe products, and Neil looks like he's going to have some interesting stuff.
To round out yet another busy day, at 3:25, I find "Determining the Best eLearning Design Approaches and Development Tools," by Joseph Ganci, "Techniques for Embedded User Assistance," by Tony Self, and the Madcap software lab. Again, I want to get some hands-on time with the latest tools, but Tony Self always puts on an interesting presentation.
The day ends with a networking mixer, where I'll also be taking photos, and then I'm off to produce Tuesday's newsletter. with luck, I'll be done well before midnight.
Tuesday begins earlier than Monday. Fortunately, I (currently) have just one session penciled in for the 8:30 time slot: the DITA lab. At 9:50, I found just one also: "HTML5 to the Point," by Scott DeLoach. The challenge here is going to be staying awake with the early start. I've said it before; Scott is an absolutely charming person, smart, engaging, and just plain nice, but is speaking style is, shall we say, less than enthusiastic. Oh, he knows his stuff all right. Let's just say not everyone can be a Dave Gash.
Meanwhile, at 11:10, we're back to making tough choices, once again, between four different options: "60 Minutes to an HTML5 Web Page," by Char James-Tanny, "Improving Online Help with Google Analytics, WebTrends, and SurveyMonkey," by Lisa Saunders, "The Value of UX," by Kyle Soucy, and "Using Web Analytics for Improving Content," by Robert Desprez. It's interesting that two sessions discussing similar topics, how to collect and analyze feedback about online help from various sources for improvement. And I most definitely know how valuable UX is, although I can always learn more about this topic that I'm very passionate about. But Char's presentations are always fabulous, so it'd have to be something tremendously compelling to keep me away.
After lunch, the 1:25 sessions hold two attractions for me: "Creating a Wiki-Based Help System," by C. Rand McKinney, and "How Microsoft SharePoint Gives You a Realistic Approach to Content Management," by Dan Beall. While a lot more companies are looking at CMS systems for their user assistance content, even more seem to be moving toward wikis as a documentation solution. This seems like the more useful skill to pick up, at least immediately.
Finally, the day slows down a bit. At 2:45, the only one I found for me is "Making Your UA Accessible to All," by Shawn Henry. And at 4:05, I hope to split time between the MadCap and Adobe product demos. At 6 is the Geek Trivia Quiz Show, always entertaining, always fun, and always not well enough attended. Make your plans to be there.
Finally, the past two years I've attempted to take part in the very first part of a very unofficial conference event, the Australian Cultural Evening, or ACE. I've managed to get the Wednesday newsletter to the point the past couple of years where I can make the first stop with the gang, the dinner stop, before I head back and finish up. Whether or not I'll be in the same state this year remains to be seen. However, the Wednesday newsletter is usually the easiest. The vendors have gone, most any big news has already happened, and the issue is a bit of a roundup for the year, with more photos than text. (Not to say that selecting a few good photos from hundreds, then editing and laying them out is a quick task.)
Wednesday is no less a crazy day. Again an early day, three session make for a very difficult decision: "A Style Guide for DITA Authoring," by Tony Self, "Making 'Expando-Magic' Glossaries with XSLT," by Dave Gash, and the Help Authoring Tool Lab, hosted by several good friends and stars. Now to begin with, Tony leads the ACE, so seeing him start early the next day should be...interesting. But it's good stuff too. I never like to miss a Dave Gash presentation, and this is about as high-end techie as it gets at WritersUA, and very useful stuff. And going to either of these means I miss out on potentially useful tool information from people such as Char James-Tanny, Sue Heim, and more. A really, really tough choice to start the day.
At 9:50, the "Designing Out of Box and First-Time User Experiences to Delight Your Customers," by Catherine Moya. I am all about great user experiences, but this is the same time as the Microsoft lab, led my more friends and stars. Some might say that Microsoft long ago gave up its position at the top of the Help heap, but they still have influence in the desktop world, and they do drive a lot of leading-edge ideas.
At 10:50, we break for the peer showcase. It's often interesting to see what others are doing. For me, I'm taking a lot of photos, listening to a few short presentations, and then trying to squeeze in a quick lunch.
At 1:05, I'm again looking at three different sessions: "A Second Look at Culture and Help Usage," by Leah Guren, "What They Won't Tell You About DITA," by Alan Houser, and "Language in Software User Interfaces," by Laura Bergstrom. I'm most torn between more DITA information and more information about how to best create UI content.
Things finally slow down a bit at 2:25. While "Interaction Design for DOOH (Digital Out of Home)," by Doug Bolin, is right up my alley, I don't see how I can miss Dave Gash's second presentation of the day, "Automated Customized Documents with DITA."
The conference closes with a keynote, "Tickling the Brain: Sharing Ideas in Memorable Ways," by Adam Rubin. While we miss out again on a Jared Spool closer, Joe often finds some real diamonds in the rough for intriguing, challenging keynote topics, and this looks like one you don't want to miss because you have to catch a plane.
So there you have it. Yet another insane WritersUA schedule. It's subject to change, of course, but the decisions I'm going to have to make, all day every day, show just how important and useful this conference is.
For me, it begins before the conference does. Not like organizer Joe Welinske and his crew, who have been working long hours for weeks on end to culminate in this day. But my conference week has always begun on Saturday, when I volunteer to help Joe put together the bags you all get when you register. It's tedious, labor-intensive work that can't be automated (and it was much more a chore in the heady days of the mid-90s, when the conference drew more than a thousand attendees), but it's also enjoyable in many ways. I get to catch up with Joe and Shannon and Sharon and often Joe's parents, most of whom I have not seen since the previous year. It also enables me to find out late changes, see what things Joe needs, and other odds and ends.
Saturday night, I'm prepping for Sunday. I already have picked out and designed the template for the year;s daily newsletter. I'm checking my email and making final plans for Sunday.
Ah Sunday. What used to be basically a half day has this year morphed into a full, multitasking day. It began with Jack Molisani, of ProSpring and who runs LavaCon, offering a full-morning job-seeker presentation, free for all attendees. Add to that both Adobe and Author-It offering information and training on their products, all of which I want to be in, and the morning is suddenly packed.
A few years ago, Joe began offering the Sunday Supplemental session, sessions that lasted a full Sunday afternoon where presenters could dive deep into useful topics as add-ons to the three-day conference. I usually spend a short time in all three, writing up brief summaries for the Monday newsletter. In the evening is the LaunchPad and conference orientation sessions. I don't spend time in them to get information , but just to take a few photos, again for the newsletter.
Exhibitors are also setting up their booths for Monday and Tuesday, and I spend time going around to all of them, reminding them of the newsletter, asking about any items them might have, news they might want spread, and again taking photos.
And then, once again this year, Joe has an informal mixer scheduled at the lobby bar, where I'll catch up with more old friends and take a bunch more photos. Then it's off to produce the Monday newsletter. With luck, I'll have had good chunks of it written, and it'll be about adding some more items, selecting, editing, and laying out photos, checking with Joe about last-minute changes for Monday, having it edited by Sue Heim, and printing out a couple hundred copies before I can head off to bed.
So officially, the conference hasn't even started and I have one very long day under my belt.
And one the conference sessions start, I'm once again faced with the same problem I find at WritersUA every year: Which sessions to attend.
I have found, in the nearly 20-year history of this conference, that during many, if not most, of the time periods, there are at least two sessions I want to attend. Unfortunately, cloning technology has not advanced to the point where I can be in two or three places at once, so I'm forced to make hard choices. Let me explain.
Monday morning begins with a session open to everyone. After that, the breakout sessions begin. This year, I have 2 that I want to attend: "Research-Validated Practices for Designing Effective ELearning," by Saul Carliner, and "Designing Content for Mobile Devices," by Scott DeLoach. I'm also thinking about "A Pattern Library for User Assistance," by Rob Houser.
But that's nothing compared to the afternoon. In the 12:45 and 2:05 time slots, I've found 4 sessions of interest, and in the 3:25, "only" 3.
To start with, 12:45 brings "Leveraging Social: User-Generated Content, " by Doug Bolin, "Comparison of Current Help Authoring Tools," by Matthew Ellison, "Global User Assistance Requirements and Guidelines," by Pam Noreault, and ""Trends in Usability Testing," by Kyle Soucy. The latter two probably are the ones I lean toward the most.
But then at 2:05, there's the Adobe Lab, "Crating a Strategy for Video to Attract Users and market Your Help Content," by Harry Miller, "Using Personas to Improve the Customer Experience," by Joan Lasselle, and "Developing for the Unknown - Using CSS, Other Control Files, and More," by Neil Perlin. I'm a huge personas advocate, but I'd love to get some hands-on time with the latest Adobe products, and Neil looks like he's going to have some interesting stuff.
To round out yet another busy day, at 3:25, I find "Determining the Best eLearning Design Approaches and Development Tools," by Joseph Ganci, "Techniques for Embedded User Assistance," by Tony Self, and the Madcap software lab. Again, I want to get some hands-on time with the latest tools, but Tony Self always puts on an interesting presentation.
The day ends with a networking mixer, where I'll also be taking photos, and then I'm off to produce Tuesday's newsletter. with luck, I'll be done well before midnight.
Tuesday begins earlier than Monday. Fortunately, I (currently) have just one session penciled in for the 8:30 time slot: the DITA lab. At 9:50, I found just one also: "HTML5 to the Point," by Scott DeLoach. The challenge here is going to be staying awake with the early start. I've said it before; Scott is an absolutely charming person, smart, engaging, and just plain nice, but is speaking style is, shall we say, less than enthusiastic. Oh, he knows his stuff all right. Let's just say not everyone can be a Dave Gash.
Meanwhile, at 11:10, we're back to making tough choices, once again, between four different options: "60 Minutes to an HTML5 Web Page," by Char James-Tanny, "Improving Online Help with Google Analytics, WebTrends, and SurveyMonkey," by Lisa Saunders, "The Value of UX," by Kyle Soucy, and "Using Web Analytics for Improving Content," by Robert Desprez. It's interesting that two sessions discussing similar topics, how to collect and analyze feedback about online help from various sources for improvement. And I most definitely know how valuable UX is, although I can always learn more about this topic that I'm very passionate about. But Char's presentations are always fabulous, so it'd have to be something tremendously compelling to keep me away.
After lunch, the 1:25 sessions hold two attractions for me: "Creating a Wiki-Based Help System," by C. Rand McKinney, and "How Microsoft SharePoint Gives You a Realistic Approach to Content Management," by Dan Beall. While a lot more companies are looking at CMS systems for their user assistance content, even more seem to be moving toward wikis as a documentation solution. This seems like the more useful skill to pick up, at least immediately.
Finally, the day slows down a bit. At 2:45, the only one I found for me is "Making Your UA Accessible to All," by Shawn Henry. And at 4:05, I hope to split time between the MadCap and Adobe product demos. At 6 is the Geek Trivia Quiz Show, always entertaining, always fun, and always not well enough attended. Make your plans to be there.
Finally, the past two years I've attempted to take part in the very first part of a very unofficial conference event, the Australian Cultural Evening, or ACE. I've managed to get the Wednesday newsletter to the point the past couple of years where I can make the first stop with the gang, the dinner stop, before I head back and finish up. Whether or not I'll be in the same state this year remains to be seen. However, the Wednesday newsletter is usually the easiest. The vendors have gone, most any big news has already happened, and the issue is a bit of a roundup for the year, with more photos than text. (Not to say that selecting a few good photos from hundreds, then editing and laying them out is a quick task.)
Wednesday is no less a crazy day. Again an early day, three session make for a very difficult decision: "A Style Guide for DITA Authoring," by Tony Self, "Making 'Expando-Magic' Glossaries with XSLT," by Dave Gash, and the Help Authoring Tool Lab, hosted by several good friends and stars. Now to begin with, Tony leads the ACE, so seeing him start early the next day should be...interesting. But it's good stuff too. I never like to miss a Dave Gash presentation, and this is about as high-end techie as it gets at WritersUA, and very useful stuff. And going to either of these means I miss out on potentially useful tool information from people such as Char James-Tanny, Sue Heim, and more. A really, really tough choice to start the day.
At 9:50, the "Designing Out of Box and First-Time User Experiences to Delight Your Customers," by Catherine Moya. I am all about great user experiences, but this is the same time as the Microsoft lab, led my more friends and stars. Some might say that Microsoft long ago gave up its position at the top of the Help heap, but they still have influence in the desktop world, and they do drive a lot of leading-edge ideas.
At 10:50, we break for the peer showcase. It's often interesting to see what others are doing. For me, I'm taking a lot of photos, listening to a few short presentations, and then trying to squeeze in a quick lunch.
At 1:05, I'm again looking at three different sessions: "A Second Look at Culture and Help Usage," by Leah Guren, "What They Won't Tell You About DITA," by Alan Houser, and "Language in Software User Interfaces," by Laura Bergstrom. I'm most torn between more DITA information and more information about how to best create UI content.
Things finally slow down a bit at 2:25. While "Interaction Design for DOOH (Digital Out of Home)," by Doug Bolin, is right up my alley, I don't see how I can miss Dave Gash's second presentation of the day, "Automated Customized Documents with DITA."
The conference closes with a keynote, "Tickling the Brain: Sharing Ideas in Memorable Ways," by Adam Rubin. While we miss out again on a Jared Spool closer, Joe often finds some real diamonds in the rough for intriguing, challenging keynote topics, and this looks like one you don't want to miss because you have to catch a plane.
So there you have it. Yet another insane WritersUA schedule. It's subject to change, of course, but the decisions I'm going to have to make, all day every day, show just how important and useful this conference is.
Sunday, February 20, 2011
Three weeks!
Yes, it's just three weeks until the 2011 conference gets underway. Time flies, and I'm sure these three weeks will go by extremely quickly.
It's almost turned into a 4-day conference what with what's now a full Sunday of events, not only the afternoon supplemental sessions and the evening welcome, but a job hunters tuneup in the morning. The latter adds a nice tidbit to existing usefulness of the conference to those between jobs.
You see, it's a given that bringing your user assistance skills up-to-date gives you an edge in the current tough market. And the ability to network among your peers is invaluable.
All the more reason to put this event in your personal budget if you're in the hunt. It's not too late.
It's almost turned into a 4-day conference what with what's now a full Sunday of events, not only the afternoon supplemental sessions and the evening welcome, but a job hunters tuneup in the morning. The latter adds a nice tidbit to existing usefulness of the conference to those between jobs.
You see, it's a given that bringing your user assistance skills up-to-date gives you an edge in the current tough market. And the ability to network among your peers is invaluable.
All the more reason to put this event in your personal budget if you're in the hunt. It's not too late.
Subscribe to:
Posts (Atom)