4 Reasons to Employ Older Tech Employees

Despite legislation making it overtly illegal, ageism persists in almost every industry.

Being an older technology worker, I’ve seen lots of cases where younger workers are picked over older ones. It happened to me once when I was recruiting a programmer for an employer in Edmonton. After all the interviews, I’d narrowed the candidates down to a 20 something and an individual over 60. Both were very good, both were happy with the proposed salary. I thought the 60-year-old was better and a better fit to our team, but the senior manager tasked with the final selection picked the younger developer.

At times we’re told there’s a staffing crisis, that companies need to import more developers from out of province, but the truth is that outsourcing and downsizing eliminated a subset of viable developers from the market. Those developers, in turn, had to figure out if they wanted to land another job, freelance, or leave the technology industry entirely.

Thinking about how much larger the pool is taking those reasons into considerations, here are four reasons you should consider hiring older technology workers:

1. Availability

In the U.S. and Canada, the number of science and engineering graduates has barely risen in the past decade, according to the Wall Street Journal. Yet the need for developers has risen over the past few years. In theory, that means a lot of older developers out there, ready for hire. The Baby Boomers, who were the first to embrace technology careers are finding it difficult to compete in our anti-age technology work forces. Managers tend to discount their 30+ years of technology work as being “old school”.

2. Stability

As developers age, they generally have less spare time due to family commitments. That doesn’t work for many startups, which expect “death marches” and 80-hour weeks in order to ship products. But older technology workers are often more reliable and stable. They have already gone through the pressures to leapfrog up the career ladder and are more comfortable with their work/life balance. Thus, they often like to stay in the same job for an extended period of time and are not interested in leaving for a “better” position.

3. Specialist Knowledge

The author Malcolm Gladwell wrote, practicing anything for 10,000 hours (that’s 20 hours a week for ten years) is sufficient to master it. That might apply to Roger Womack, CEO of Sportdirector.co.uk, a one-person firm that produces the soccer simulator Football Director for many different platforms. For 30 years, he worked for a variety of game publishers; but in 2007, with decades of experience under his belt, he decided to publish his own game.

“The bar to entry is much lower with technologies like Unity,” he said. “I’d probably make more money now working for someone else than if I was going it alone.” But at 60, Womack has more than enough game-development experience to run a business by himself.

Technology workers need to master more technologies than they did three decades ago. In the early ‘80s, there were very few commercial languages other than COBOL, Basic, and assembly language. Today’s developers, need to contend with version-control systems, build systems, XML, JSON, databases and SQL, not to mention various Web technologies such as HTML, CSS, JavaScript and server-side languages. The tools for technical writers have expanded exponentially as well. In the 80’s, it was Ventura Publisher, WordStar and Harvard Publishing, today it is not just paper documents that need to be created, but you also need to publish documents to the web and create interactive training using numerous softwares, including Visio, Captivate, articulate, Camptasia, FrameMaker, Flash, HTML, as well as the Office Business tools. Project and change management has become part of their work arsenal.

Older tech workers have spent their careers learning new technologies quickly and they all have a system for picking up whatever they need to know; plus there is a growing body of online tutorials helps with that. The biggest roadblock can be in managing one’s time in order to actually learn how the software works.

4. Better at Office Politics

Any tech worker who has been around more than 15 years has probably seen his or her fair share of bad incidents in offices: favoritism, dead-end projects, poor leadership, technical debt, reshuffles, and, of course, the impact of layoffs. They’re adaptable, which is why bringing in a mature team member can anchor a team with a solid core. They also have picked up a variety of skill sets that can “fill the holes” in any team. With older workers, not only do you get a bigger bang for your buck, but you also get a worker who ofter buckles down and gets the job done quickly and efficiently.

Conclusion

I can think of few things as wasteful as discarding technology workers  because of their age. I’ve yet to hear of anyone who has recruited an older person only to regret it. Their skills, particularly in contract work teams can be invaluable. If you’re on the quest for talent, throw the widest possible net and don’t discard the older prospects.

Collaboration – Is the Key

When you are a technical writer or an instruction designer your key skill is collaboration. The extent of collaboration through the creation process is what makes these unique professions. The writer/designer has the software, technical and communication skills to create a final product, but it is their collaboration with the subject matter experts (or SMEs) that makes or breaks the quality of the final product.

Software developers and business people know their jobs and what they do, the writer/designer depends on these subject matter experts (SMEs) for the content that needs to be “translated” from technical jargon to something the layperson can understand. 

When collaborating on any size project(from a single document or a set for an entire release) communication is a skill every member of the team need to use. When working with co-workers or team members, it is important to remembercollaboration is about creating a final product. 

Collaboration is not about competition. Even though a writer/designer may be brought in as a consultant to create the document or training, they work as a team, with the company and keep the good of the project (and of the company) a priority. Being part of this team team allows you to learn from as well as to teach others. Collaborating on a project yields many benefits as well as challenges to the writing/designing process.

Collaboration also produces well rounded and effective products and it allows the participants to learn about other people in the organization that can contribute their expertise in future projects that may not even relate to the subject at hand. 

Good writers or designers become great writers through collaboration and discovering new ways to
improve their writing process. In addition, by collaborating with subject matter experts, designers, and publicists, technical writers quickly learn about other fields and the ways writing impacts various disciplines.

Collaborating on a project with a team provides many benefits not only to the success of the deliverable, but it aids the team members to grow professionally.

Great Info Graphic on Change Initiatives and Training

I was reading some of the blogs I follow, and this infographic from Training Folks really resonated with me having been involved in a number of change initiatives.  
This infographic shows some of the facts and best practices in implementing and supporting training for important change initiatives.

Technical Writing and Instructional Design

Recently, I have been asked, "I have been more involved in Instructional Design in the last year, though in both contracts it was in relation to software and teaching people about how the software is used in the organization. An employer thought I was too involved in Instructional Design to be considered for a Technical Writing position. Is having too much Instructional Design in my resume going to affect how employers will think about my Technical Writing skills? "

Technical Writing and Instructional Designing are never considered one and the same. If you go for a job interview, the hiring manager asks you for relevant experience in Instructional Designing or Technical Writing.

• If you are applying for the post of a Technical Writer, only your experience in technical writing is considered.
• If you are applying for the post of an Instructional Designers, your experience on paper is considered and salary is fixed accordingly.

I have never felt Technical Writing and Instructional Designing are different  professions. I have been involved in both throughout my career. And I have often wondered the following:

• Why is Instructional Designing and Technical Writing treated separately?
• Do these job functions require completely different skill sets?
• Is it really difficult for a Technical Writer to get into Instructional Designing or vice versa?

This table shows the differences between the two:

	Instructional Designer	Technical Writer
The Work/Job	Design and develop  training solutions (classes, documents, manuals) for a variety of problems/ initiatives. Can include software/hardware	Develop documentation or manuals for software/hardware/products
Industry	Varied	Software/hardware
Products	E-learning training and reference materials, Instructor Led training, Blended Learning programs,  Presentations, Guides, Workbooks and Manuals	Manuals: Help, installation, API Guides: Troubleshooting, Installation, Quick reference Other: FAQs, Whitepapers, brochures, marketing, presentations, etc
Tools	Word, Visio, Excel, FrameMaker, Captivate, Articulate, Camptasia, Photoshop, Illustrator, Power Point, Adobe Acrobat, LMS, Snagit, DreamWeaver, Blogs, SharePoint	RoboHelp, Word, Visio, Excel, FrameMaker, Photoshop, Illustrator, Power Point, Adobe Acrobat, LMS, Snagit, DreamWeaver, Blogs, SharePoint
Skills	Knowledge of Instructional design concepts, Language, Storyboarding, creative, Visualization and research skills, Exceptional ability to relate to people. Skills to take complex information and translate it into language appropriate for the situation	Language, technical  and research skills, technical writing tools Skill in understanding and translating highly technical material into the level of language appropriate for the situation

The table shows the basic skills, and to some extent, the tasks comparable for both these professions. So, why these two professions are considered different?

Some points to support the difference would be:

Technical Writing

• Is a support function
• Requires familiarity with technology
• Requires working with technology
• Has got to do with information architecture and design
• Industry – software, telecom, anything that deals with applications, tools

Instructional Designing

• Is a main stream job that requires superb people and change management skills 
• Requires more of creative and visual skills
• Has got to do with course architecture and design
• Industry – varied

These differences are not convincing enough to makes these two professions poles apart. In my opinion, what differentiates these two professions is:

• The kind of solution you come up with
• How you  implement it

I believe these two professions are not considered same can be attributed to the following beliefs:

Technical Writing

• You don't need to be creative
• You don't need to be creative innovative
• You don't need to know how people learn new things

Instructional Designing

• You don't need to understand technology
• You don't need to learn any graphic design or authoring tools

In today's business, I do not believe any writing professional can avoid using or knowing about technology. You need to be creative in any profession. Creative skills set you apart from others, no matter what you do. If you ask me if  Technical Writing is better than Instructional Designing or vice versa.

I have worked on e-learning courses and user manuals and combined to two for "Just In Time" Learning (or Help).  Both Instructional Design and Technical Writing are are not that different a solution and the skills required is almost the same. And I believe instructional design is a much bigger umbrella under which technical writing also falls. 

If you think there are differences, please comment. 

Video Sample

I have created a short promo video. It is still in draft as my audio equipment is in Calgary and I am in BC, but I am uploading it so I can get some constructive criticism.

If you can't see the video, here is a direct link https://www.youtube.com/watch?v=HVXCrOUuh0c

Please let me know what you think.