Current Issue

Chapter News
Features
Viewpoints
Student Views
From the Editor's Desk
Message from the President
Reviews
Society Notes & Community Announcements




 Article Archives 

Book Review
Career Development
Case Studies
Content Management
Contracting & Consulting
Core Competencies
Meeting Reviews
Usability
Networking
Online Help & Embedded Assistance
Technologies
Translation and Localization
Up and Coming Corner
Information Architecture


 Past Issues 

May, 2012
April, 2012
March, 2012
February, 2012
December, 2011
November, 2011
October, 2011
September, 2011
August, 2011
June, 2011
April, 2011
February, 2011
January, 2011
August, 2010
July, 2010
June, 2010
May, 2010
April, 2010
March, 2010
February, 2010
January, 2010
December, 2009
November, 2009
October, 2009
September, 2009
July, 2009
June, 2009
May, 2009
April, 2009
March, 2009
February, 2009
December, 2008
October, 2008
September, 2008
May, 2008
April, 2008
February, 2008
January, 2008
November, 2007
September, 2007
August, 2007
April, 2007
March, 2007
January, 2007
November, 2006
October, 2006
September, 2006
August, 2006
March, 2006
February, 2006

January Notes

Share on Facebook :: Printer Friendly Version

- Dalyce Epp, Coast Lines Editor

Published: January 2007 in Editor's Notes

Recently, I suffered a slight humiliation at the office of my client. I took advantage of someone’s absence to update a document on his laptop instead of doing the work at home as I normally do. What I hadn’t counted on was that IT had just installed the newest version of MS Office on his computer the day before. The interface was almost completely foreign, and very few of the normal keyboard shortcuts worked! I ended up taking twice as long to complete the work as I might have.

But, the really embarrassing part was when I tried to save my version on the desktop. I searched high and low trying to find the “save as” function in the alien interface, and finally staggered into the hallway and pulled an unsuspecting support person in to help. She didn’t know either, but between us, we figured it out.

The fact that I’d earlier had to help an officemate who couldn’t find the “undo” icon gave me small comfort.

I learned some very good lessons from this experience: one, don’t change things for the sake of change (sounds a little like, “if it ain’t broke, don’t fix it”) and two, be prepared for change.

Previous: January Program Meeting: Legal Issues in Technical Communication

Next: Business addressing challenge of e-accessibility, expert tells UN panel


 Subscribe via RSS

Visit the main STC website.

STC advances the theory and practice of technical communication across all user abilities and all media.


STC-related links

Note: You may need to be logged into these services to view the pages.

©2012 STC CWC | Home | .(JavaScript must be enabled to view this email address)