June Celebration & Transition Meeting 06/01/2009
Posted by Managing Editor in Events.add a comment
STC Houston Celebrates Our Past and Our Future
STC Houston members will be gathering on June 9th at the Crowne Plaza Hotel for the end of the program year celebration. Come join us for a night of networking and celebrating our accomplishments of this past year. This social event allows us to thank all the volunteers who have contributed to our success. Meet the new Administrative Council members as we transition to the new program year. For more information and to RSVP, please see the List of Events.
Celebration Date, Time, and Location:
June 9, 2009
5:30PM to 7:30PM
Crowne Plaza (formerly Holiday Inn Select)
2712 Southwest Freeway
Houston, TX
June Networking Lunches
Westchase
Stop by on Wednesday, June 3rd from 11:30 AM to 1:00 PM at Luby’s, 12121 Westheimer Rd, #100 (Westheimer near Kirkwood) for good conversations with great people! RSVP to Julia Land, Monica Waddell, or Cynthia Claxton networklunch_westchase@stc-houston.org.
Thanks to the Volunteers on the Newsletter Team!
by Debra Page
Managing Editor
A special thanks to all the volunteers on the Dateline Houston newsletter team for 2008-09!
Newsletter Committee Volunteers
The production of the newsletter is only possible with the hard work and dedication of the editors. The core team includes associate editors Melanie Boston, Jan Brantley, and Jamie Diamandopoulos. Each month, they edit articles and proofread each issue. Next time you see them at a program meeting, be sure to stop them and tell them they are doing a great job!
Newsletter Article Contributors
Thanks to all the volunteers who contributed articles to Dateline Houston this year, sharing information with the community through our online newsletter. You can’t have a newsletter without content, and the following members have taken time out of their busy schedules to write articles for the STC membership: Noel Atzmiller, Guy Ball (OCSTC), Kathy Delisle, Robert Delwood, Alyssa Fox, Rene Gedaly, Lori Gillen, Suzanne Guess, Hillary Hart, Char James-Tanny, Crystal Johnson, Tom Johnson, Linda King, Sharon Lynn, Paul Mueller, Cindy Pao, Alan Porter, Deborah Silvi, George Slaughter, Gary Michael Smith, Becca Taylor.
Pragmatic Thinking: You Can Learn How to Learn 06/01/2009
Posted by Managing Editor in Featured Article.add a comment
Pragmatic Thinking and Learning: Refactor Your Wetware
Author: Andy Hunt
O’Reilly Books, 2008
Pages: 271
ISBN 10: 1-934356-05-0/
ISBN 13: 978-1-934356-05-0
MSRP: $34.95
http://oreilly.com/catalog/9781934356050/
Book Review by Robert Delwood,
Senior Programmer Writer
Let’s take a moment to stop learning about something and start learning about learning. That is, let’s try to understand how we acquire new information in order to retain it in a practical way. Andy Hunt’s Pragmatic Thinking and Learning: Refactor Your Wetware focuses on the brain itself, helping us to understand how it processes information with the goal being for us to adapt more efficiently.
Hunt is a programmer who noticed that in forty years of computer design, the industry’s defect density remained constant. If everything else was changing, the only other factor was people. Perhaps, he thought, we are addressing the wrong questions, and that we aren’t learning correctly. This book isn’t about whether we learn best by doing or being taught, although there is that aspect, it’s about redesigning and rewiring our brains.
First we must understand how learning works. The brain processes information in two modes. The first mode processes the conscious, language, and logical thought, what we commonly view as “thinking”. This is the mode we can explicitly control and is called linear or L-mode. The other mode is very different and processes information in our subconscious. It’s always searching for relationships among memories, finding patterns, and storing data. This is called rich or R-mode. This mode explains why a Jeopardy answer comes to you a week later. It also processes information that can’t be verbalized. Each one of us knows hundreds or thousands of people. We can’t describe their faces yet we recognize them by sight instantly, even twenty years later. Some actions don’t even require conscious thinking. A piano player doesn’t think about each note, it just happens, albeit through practice.
Working against us is that the brain processes so much information that it must make assumptions. Have you ever driven to work and realized you don’t recall anything from the last ten minutes? Chances are your brain decided nothing significant occurred and therefore didn’t index anything. In addition, we forget. Brain chemicals stop working, or older information gets replaced. We think of memories as “read-only” operations (remember, Hunt’s a programmer) but actually, they are “read-write” operations. In other words, the very act of recalling a memory risks changing it. It seems haphazard, but the trick is to make the two modes cooperate.
The traditional approach, the passive act of being taught, doesn’t work. In that regard, no one can “teach” us. We can be lectured all day about rock climbing but it doesn’t make us rock climbers. We have to “learn” and that is tied to experience. That’s why dreams seem so ethereal to describe: There is no experience. Facilitating cooperation between the two modes begins with Hunt’s maxim, “Lead with R-mode; follow with L-mode.” R-mode only needs the most meager of information. Even doodling is helpful since it ties information to an experience. For producing results, take the writer’s adage “write drunk, edit sober.” Not to be taken literally, this stresses letting the creativity flow at first, then use logical processes to refine the work. For learning, gain some experience first, learn more about it, and then dive into the experience.
As an example, he points out a rock climbing course (mentioned earlier). The instructor suited them up, let them practice climbing for 20 minutes, then lectured. As a result, the class gained context for the lecture and could better understand the discussion. This example also included some other fundamentals. They were provided a safe environment to learn (suiting up with supervision); failing was critical to their success (understanding right and wrong footwork); they had a goal in mind (an outdoor climb later in the course), and they were given the opportunity to play (practice climbing). The last point has taken on unfortunate meanings in the workplace, but play is anything that makes problem-solving fun. Finally, they were given a legitimate way to solve a problem, seemingly “doing nothing” by taking a break (“defocus to refocus”).
Many examples may seem familiar and this book attempts to consolidate these into a coherent process. The 271-page book goes into more details, most with concrete and practical examples. In nine chapters, his easy-to-read style takes the journey from being a novice to expert in steps, including understanding the brain, thinking in new ways, the process of learning, how to handle experiences, and redirecting learning processes. In a field with new age nuisances, and almost absurd theories, his approach is grounded and practical.
Managing Your Distractions
As if learning weren’t hard enough, we also have to deal with distractions. A distraction is any event that causes us to lose our train of thought from a deep involvement. Unlike a computer which is designed to switch contexts, the human brain is not. Research shows it takes twenty minutes to recover from a distraction. Ignoring the researchers, just ask any Sudoku player who had to stop to reboot the kid’s computer. Obviously, it doesn’t take much to fragment a work day. Academically, this is known as “cognitive overload,” – but we know it as multitasking, and put simply: It doesn’t work. We can’t concentrate on many things at once and do them all well. Therefore, manage your distractions such as by closing the office door, planning time for those tasks, or simply turning off your email. In a controversial English study, researchers found that bad email habits were more counterproductive than smoking cannabis. Some distractions just require personal fortitude such as avoiding Google, YouTube, Digg, or, perhaps, smoking cannabis.
Walking Problems Through
There are ways to encourage the R-Mode to reveal clues to solving a problem. One easy way is by walking. But you have to do it correctly. Do you know the difference between mazes and labyrinths? A maze has multiple entrances, exits, and presents choices along the way. High walls prevent you from seeing the goal. A maze is meant to be a thinking puzzle. In contrast, a modern labyrinth is meant for mediation. There is only one path and no decisions. Today, you’ll find them near churches, hospitals, and hospices by no accident. These are all places meant for healing and reflection. In our terms, they are meant to minimize L-Mode processes and let the R-Mode take over with a stream of consciousness. A walk on a solitary beach or a quiet woods has the same affect. Ironically, the key on these walks is to not actually think about the problem.
Smart Volunteering 06/01/2009
Posted by Managing Editor in Featured Article.add a comment
Giving of Your Time Effectively
By Guy Ball,
OCSTC Senior Member
What if I told you that you could learn new skills on someone else’s dime, try out new ideas with a “client” who is just appreciative that you’re helping, and maybe even network yourself into a new job or a new direction in the process?
A Win-Win Situation
I won’t use the “dirty ‘V’ word” to taint this conversation. Let’s just call it helping out, paying it forward, maybe even good karma. Works for me. I’ve been loaning my technical writing skills for free to a few nonprofit organizations over the last couple of years and, besides helping them with needed skills, I’ve received more benefits than I ever expected. I’ve learned how to adapt to new situations better, “do more with less,” and to think like a guerilla fighter in the war on providing maximum content on a minimum budget.
And I’m not alone. Look a little closer at our OCSTC organization and you’ll see people who maintain dynamic web sites, produce award-winning newsletters, coordinate educational programs, and organize some pretty great events—all on their own time and with no expectation of financial return.
But let’s talk about sharing communication skills that are, at times, in short supply in the outside world. How many nonprofit groups could benefit from a few hours of your help in rewriting mission statements, program brochures, or event instruction materials for their staff?
Do you want to grow your skill set or offer yourself some variation from the same types of material you do day in/day out? How about creating a newsletter for your local community foundation or an informative web site for a new cancer patient support group? Are you interested in history or science? Small museums are always in need of informative little brochures to help their visitors. They don’t need to be fancy; just well written. How about doing something that impacts not just one or two, but hundreds or thousands of people?
A few years ago, tech writer Sam Poppas was simply helping out when the teacher at his son’s school asked him to speak at career day. Sam puts in his 40-plus hours a week and was content coming home and just dealing with family stuff, but he liked the idea of sharing his career with students. After his presentation, the principal asked if he could help out by writing a brief summary of a program the school was trying to get a grant for. Sam saw how disorganized they were and eventually took over the whole grant application, and the school won the funds. Sam commented that the feeling of elation over the success was unlike anything he’s felt at work for a long time. And without Sam’s help, they probably would not have gotten the grant.
“Writers have a unique and valuable talent that can advance the missions of local nonprofits. Your service is needed now more than ever to help address critical community issues,” noted Dan McQuaid, CEO and president of Volunteer Center Orange County, the county’s leading group connecting skilled volunteers with organizations that need assistance. “Volunteer Center can connect you to make a meaningful contribution that utilizes and expands your skills.”
What sort of projects might you be able to do? I’ve mentioned a few. Others I’ve personally helped with include editing, formatting, and publishing minibooks for a local historical society; collaborating with graphic designers on a downtown walking tour guide; developing a video-based oral history program; and, my favorite, writing a book on local history for a mainstream publisher.
Did I get paid for any of this? Outside of the miniscule book royalty, nope, nada, nothing. Did I learn new tools, have amazing control over projects, and feel like I impacted a whole bunch of people? You bet!
Sam said it well. “I picked up new skills that I was able to bring to my work environment, and it’s made me a bit more valuable. And should something unfortunate happen to my job, I can move into grant writing to bring in some extra income.” (He’s already written a few more.)
Pace Yourself
Let’s talk about the caveats, though. If you’ve volunteered for anything, you know there are too few people doing it, and you will be called on for other unplanned roles. This is a great way to get burnt out on a relationship with a particular group as your workload increases. Try very hard to limit the extra work you find yourself taking on to the tasks you really want to do. Try to suggest better ways to do existing things so that you’re creating a value (and interest) to your work—not just filling in a gap. This philosophy has kept me interested in continuing what I do (15 years with one group alone!)
Try hard not to impact your family time or the open time that’s very important for you. I tend to do a lot of my work late at night once my family has gone to bed. Learn about the group and their operation before you overwhelm them with your great new ideas. Often, an organization operates a certain way because of deeper reasons—or personalities. Your new idea might be wonderful, but it could also hurt them as everyone scrambles to accommodate something you’re trying to change. (On the other hand, you could also be that breath of fresh air they’ve needed for years!)
Don’t start a project you can’t finish. I’ve helped out several groups with web sites that the previous volunteer never completed. The group was left hanging to dry when the well-meaning webmaster got busy with something else in life. Don’t enter into a project if you can’t finish or gracefully complete it in a short time. (Remember, these people will talk—and they will either relate how you “walk on water” or left a big mess that no one could fix.)
Lastly, and possibly just as important. Remember, someday, you will not be there to help. For recurring projects, try to make your work as simple to follow as possible. Try not to work in complex tools if you can. I’ve created newsletters in Word and web sites in FrontPage—all because I knew that whoever was going to take it on would not be using InDesign or Dreamweaver. I purposely designed things that can be easily updated by a novice. (I made sure they had lots of copy/paste solutions.)
The Benefits You Reap
At the start of this article, I spoke of the new skills you would learn, the new ideas you could bring to an appreciative client, and the new career direction you might stumble upon. The more you do, the more you will gain back. It’s worked for so many of us willing to give it a try. It’s really not rocket science. It’s smartly using your talents to help others.
Payback? Well, how about smiling faces, a very grateful organization, a successful event or project where you had serious input, and a wonderful feeling deep in your gut. All without worrying about how it was going to look on your yearly review?
And maybe, just maybe, a payback of a better, smarter you as you head off into the crazy job market.
Guy Ball is a senior technical writer for EADS North America Defense Test and Services in Irvine, California. He’s volunteered his technical writing skills for over 20 years and swears it gave him skills that let him grow his career and discover new opportunities. He’s written a couple of books, created a few organizational web sites, developed an award-winning history coloring book for kids, and works on “too many” unpaid writing projects that keep him up, happily, late at night. His web site is guyball.com.
April 2009 Meetings & Officer Elections 04/01/2009
Posted by Managing Editor in Events.add a comment
Why Technical Writers Shouldn’t Be Writers
April 14, 2009 Chapter Meeting
Presenter: Alan Porter
In twenty plus years as a tech author, editor, heading publications shops, consultant and working for software vendors selling into the tech pubs market, I’ve always heard the same story – heck, I even heard it this week. “Why don’t people respect technical publications?” Maybe part of the problem is that the vast majority of us are Writers. We love the written word. Maybe we love it a little too much? We need to ask ourselves, is the written word the best thing for Technical Publications?
This presentation will take a look at why we are so focused on the written word, and present a few ideas about better ways for us to deliver our message to the end user in a way that increases customer satisfaction, and might even gain tech docs a little more respect…
Alan Porter has 20 plus years experience in Corporate Publishing in the UK and USA. He has been involved in the development and adoption of various publishing standards and has been a regular speaker at industry conferences. He has held senior management positions at various publishing software and services companies, allied with extensive consulting experience. Alan is a regular speaker, blogger, and twitter addict, who is happy to talk publishing to anyone who will listen. He is also a published author with several books, comics and numerous magazine articles to his name.
Date: April 14, 2009
Location: Mustang Engineering – Please note new location!
Wood Group Building, 17420 Katy Freeway, Houston, TX 77094
Time: 5:30 p.m. Networking, 6:30 p.m Program
Meeting RSVP: $10 Members, $15 Non-Members, $5 Students/Retired
Map Diagram Directions from Downtown Houston to the Wood Group building:
- Take I-10 (Katy Freeway) to Barker Cypress Rd.
- Turn right (North) onto Barker Cypress.
- Travel to the first traffic light, and then turn right (East) onto Park Row – The Wood
Group building is the first building on the right.
Important: Any of the popular map applications place the pointer on the Katy Freeway feeder. The actual entry point to the Wood Group building is accessible from Park Row, which is just north of the Katy Freeway.
Parking is free of charge and available in front of the building and within the adjacent garage. After parking, enter the Wood Group building through the double-glass doors, which face Park Row. Upon entry, someone will guide you to the Opus Event room, where Mustang Engineering will host the April STC Houston Chapter meeting.
April Networking Lunches & Webinars 04/01/2009
Posted by Managing Editor in Events.add a comment
Westchase
Wednesday, April 1 from 11:30 AM to 1:00 PM at Luby’s, 12121 Westheimer Rd, #100 (Westheimer near Kirkwood). RSVP to Julia Land, Monica Waddell, or Cynthia Claxton networklunch_westchase@stc-houston.org.
Galleria
Thursday, April 2 at Barry’s Pizza, 6003 Richmond. Starts at 11:30 AM. Please RSVP to Alyssa Fox at networklunch_galleria@stc-houston.org.
North Side
Tuesday, April 21 from 11:30 AM to 1:00 PM at Fuddrucker’s restaurant, 7511 FM 1960 (on the north-bound feeder road by Willowbrook Mall). We sit in the back section of the restaurant. Just place your lunch or beverage order and then walk to the back section (through the doorways). You don’t have to be an STC member to attend. If you plan to attend, please let me know so that we can get a large enough table. Please email your RSVP to Linda King at pastpres@stc-houston.org. I look forward to seeing you there.
April: Elections for 2009-2010 STC Houston Administrative Council 04/01/2009
Posted by Managing Editor in In Progress.add a comment
The election will be held during the regular meeting on April 14, 2009. If you cannot attend, you can print and mail the proxy ballot to STC Houston, as directed on the ballot. Download the proxy ballot.
Candidates have been nominated for the Administrative Council for 2009-2010. Click onto http://www.stc-houston.org/election.htm for more information. If you would like to nominate someone for office, send an email to Alyssa Fox, Nominating Committee Chairperson.
Judging the Science Writing Contest 04/01/2009
Posted by Managing Editor in Education.add a comment
by Cathy Bettoney
Yvonne Wade Sanchez, Cathy Bettoney, and Loubna Ould-Saidia represented STC-Houston at the judging for the science-writing contest at Houston’s Science Engineering Fair (SEFH) on March 7. This year marks the fiftieth annual competition for the fair as a whole, and the twenty-second year of the science-writing contest.
There were 36 judges for the three categories—junior (7th and 8th grades), 9th grade, and senior (10th through 12th grades). Yvonne and I judged the junior division, which had the bulk of the papers—70 entries in all.
We met at 9:30 in the morning at University of Houston-Downtown and munched on a continental breakfast as we went through the judging criteria. Each paper was read by two judges. Contest organizer Dr. Aimee Roundtree asked Yvonne to lead the junior division, since she had judged previously. Under her direction, we winnowed out the papers that deserved a third reading.
Fortified by a Jason’s Deli lunch, 12 junior division judges stayed to continue eliminating papers until about 1:45 p.m., when we were down to seven papers. Each of these was read by all the remaining judges to choose the four best for first, second, third, and honorable mention awards. We completed our task by 3:30 p.m.
My impression is that science writing has improved in the last few years but that the students at this level probably need page limits so that they are more discriminating in their use of sources. The top papers showed an understanding of the scientific method and clear descriptions of the experiments. I would encourage STC-Houston members to join with us next year to promote quality technical communication.
Eight Tips for Successfully Working with SMEs 04/01/2009
Posted by Managing Editor in Technical Writing.add a comment
by George Slaughter
To be successful, writers must consult with subject matter experts (SMEs). Some SMEs are nearby, while others are in other countries. Some speak in engineer-speak, while others take pride in extensively rewriting your drafts because they think of themselves as writers. Some are easily available, while others always seem to be away from their desk.
Regardless of your situation, the following tips can help you be successful in working with SMEs.
- Do your homework. Often, the answers to your questions are in the change forms, engineering reports, marketing specs, project plans, or other material on the team Intranet site (or distributed during a team meeting). Review these documents before approaching the SME.
- Know who to ask. Every product team has one or two people who become your go-to people. (Sometimes they are assigned this role, sometimes not.) Go to these people with your questions first. If they don’t immediately know the answer, they know who else on the team would know—and they can help grease the tracks for you to ask those people.
- Know what to ask. You can demonstrate that you’ve done your homework when you share what you’ve learned as you ask the question. For instance, “The engineering specs say the software will have certain functionality. Yet the change request from last week’s meeting says that this functionality will be different. Can you explain the differences?”
- Know when to ask. Check your company’s Microsoft Outlook directory to see when your SME would be available to take your questions. In some cases, it’s OK to ask your questions during team meetings. Most times, however, it’s better to ask the SME in a one-on-one situation, thereby not tying up everyone else’s time.
- Know how to ask. Personal meetings are best because of the immediacy of feedback. In addition, the tone and inflection of one’s voice, along with nonverbal gestures, promote faster and greater understanding. Phone calls are second best for all these reasons except for nonverbal gestures. Instant messaging software, such as Microsoft Office Communicator or Yahoo Messenger, helps ensure immediacy of feedback. While e-mail is often the only option, it is not always the best option because feedback isn’t immediate, and others who have no role in the conversation are often included, which can lead both to misunderstandings and unwanted delays for clarification.
- Know when to bribe. When posting your drafts for review, think of an incentive to get people to return their feedback to you more quickly. What you offer depends on the team and what you’re willing to provide. Perhaps you could bring cookies or other refreshments to the review meeting.
- Know when to bludgeon. Sometimes bribery doesn’t work and you must resort to other, arguably devious, tactics. If you find it necessary to bludgeon your reviewers, let your project manager—or someone with supervisory authority—do the deed.
- Build a rapport. One project manager I know plays in a rock-and-roll band on the weekends. While I’ve not heard his band play, I’m sure they do a marvelous job. Another project manager is a loyal Auburn University alumnus and football fan, while an engineer on this same team is a loyal alumnus and fan of the University of Alabama—Auburn’s archrival. It makes for some good-natured bantering before team meetings, and when I’ve approached one or the other I can break the ice by cheering or commiserating about how their team fared.
If you use these tips, you can make things easier for your SMEs, whose feedback will make things easier for you when you’re creating your documentation deliverables.
Lessons Learned from Baker Atlas 75th Anniversary Book 04/01/2009
Posted by Managing Editor in Technical Writing.add a comment
Noel Atzmiller is a Technical Marketing Support Award Winner in the 2008-2009 STC Competitions.
by Noel Atzmiller
In 2007, I served as project manager for the Baker Atlas 75th Anniversary Book. This publication documented our company history through the use of engaging text set amidst many historical images. We chose a publishing firm in California, which managed an assigned writer, a graphics department in upstate New York, and a printing company in Dallas, Texas. Although I wrote some document text, my main tasks were to collect information, provide information and direction to the writer and to the graphics department, manage the document reviews, select and provide all images (and their captions), and maintain the production schedule.
When I was asked to lead this project, I had no experience in producing a technical-historical document. I learned a great deal during the process. I gathered some key “lessons learned” into the following categories: Resolve, Research and Respond. I hope this knowledge will benefit others who are faced with producing or managing technical-historical documentation.
Resolve
Before you start the project, identify your primary decision maker. Consult with this person early in the project because several key decisions must be made. Determine the goal(s) and the main message(s) of your document. Will your work be designed to inform, motivate, commemorate or a combination of these objectives? Do you want to concentrate on details of the technological advancement or emphasize the contribution of past employees? Will your document rely on text for telling the story or will images – with captions – be your main vehicle?
Determine at what point to start your historical account, such as a specific event or an arbitrary date. Produce a document outline and obtain approval from the decision maker. Next, determine the tone of the writing, the approximate number of pages, and the basic page layout. If possible, obtain a similar document and refer to it during the discussion; your decision maker might not be able to visualize your ideas and would appreciate seeing a comparable book.
Discuss all costs up front, establish how you will contain them, and obtain a clear indication of your budget. If you plan to select a publishing firm and outside writers, obtain writing samples and sample documents. Require them to produce a preliminary production schedule and study it carefully. Finally, obtain a detailed quote.
Determine the review and approval process. Clearly delineate who will review the drafts and the pre-production copy. Decide if this process will occur in a group setting or if all reviewers will provide one person with their corrections and changes – for subsequent compilation.
Research
If you are working for a “young” company with a short history, you will probably rely greatly on present employees for information. Locate as much information as possible before the writing begins. Extract information from every type of company document you can find, including marketing collateral, advertisements, newsletters, patents, Internet searches and newspaper/magazine articles. Analyze the information and decide what will be used.
Arrange interviews with retirees and current employees. These interviews could be in person, via email, or over the telephone. Produce a set of questions prior to the interviews. If you are using an outside writer, discuss the interviews beforehand and suggest potential questions. Inform interviewees that their knowledge is valuable and express appreciation for their time. During the interviews, be prepared to ask your questions, but also have the flexibility to digress if warranted.
Obtaining images may be difficult, especially vintage photos. If you determine that you need new or additional images, consider a photo contest for current employees. If promoted correctly, a contest can be very useful source of photos. Consider copyright issues if the photos were produced by outside photographers.
Respond
Be prepared to provide material that will supplement or replace the document contents. Draft reviews can quickly reveal gaps in the historical account. Do not be surprised if some information turns out to be wrong or dated incorrectly. If you are dealing with an outside writer, expect requests for additional data.
Photo selection can also require several changes or replacements. Have a collection of alternative photos you can supply when asked. Produce photo captions as early as possible in the review procedure, and be ready to revise them.
After receiving comments and corrections from the reviewers, act promptly to incorporate them into the document. Using the review procedure you established earlier, strive to distribute all updated copies as quickly as possible.
My hope is that these tips and suggestions will be useful for anyone producing a technical-historical document. I have other guidance I could offer on this topic for those who wish it. Feel free to contact me (noel.atzmiller@bakeratlas.com).
My thanks to the following people who assisted me in this article: Pam Boschee, Elizabeth Naggar and Beth Weber.
###
March 2009 Meetings & Events 03/02/2009
Posted by Managing Editor in Events.add a comment
Tools in Technical Communication
March 10th Program Meeting
submitted by Cathy Bettoney, VP Programs
Technical Writers write, yes – but producing information requires a number of other tools that aren’t specifically publishing tools.
We need to create and edit graphics, create wikis, manage knowledge – as well as perform more non-traditional functions, such as creating audio files and icons. We can also be required (or desire) to set up systems for backing up our machines, managing source control of our documents, and bug tracking.
Nikki Bleiel will present her talk. She will discuss and demonstrate a number of low cost or free tools that technical communicators can use to perform a variety of tasks, including:
- Graphic/screen capture creation and editing
- Icon creation and editing
- Building a wiki/knowledge management system
- Create special font characters
- Creating text-to-speech audio files for use in demonstration files
- Automated file backup
- Podcasting
- Source control
- Bug tracking
Nicky Bleiel is a Senior Information Developer at ComponentOne and an At-Large Director of STC. She has fourteen years experience as a technical communicator. Nicky started her career writing books and producing them in hardcopy format, but she has since embraced online help and user assistance, web design, single sourcing, usability, e-learning, and knowledge management. She has presented at many STC meetings and conferences.
Date: March 10, 2009
Location: Mustang Engineering – Please note new location!
Wood Group Building, 17420 Katy Freeway, Houston, TX 77094
Time: 5:30 p.m. Networking, 6:30 p.m Program
Meeting RSVP: $10 Members, $15 Non-Members, $5 Students/Retired
