The Technical Writer’s Struggle in Office Space

In the movie Office Space, Tom Smykowski (played by Richard Riehle) writes technical manuals for the software company. His job as a technical writer becomes a point of discussion in the film, particularly when he tries to justify his role in the company by explaining that he takes the specifications from the customers and brings them to the software engineers. This portrayal, while comedic, highlights the frequently misunderstood role of technical writers in the IT world.

If you haven’t seen the film, there’s a recurring mention of “TPS reports” (Test Program Set) which become a symbol of pointless bureaucracy and mundane office tasks. Throughout the movie, various characters remind Peter about the cover sheets for TPS reports, highlighting the complexity of creating, maintaining, and archiving corporate procedures.

Explaining your role as a Technical Writer

If you’re a technical writer, you’ll relate to Tom’s dilemma. For Tom the struggle wasn’t the nature of his job, rather how to explain the value of his writing activities during HR reviews. So how can you approach this?

1. Define your core functions

Tom Smykowski might have struggled to explain his job, but as a technical writer, you’ve got a clear set of core functions that are crucial to any company. You’re not just pushing papers around like those TPS reports – you’re creating and maintaining documents, simplifying complex information, and ensuring consistency and clarity in technical documentation. It’s like being a translator, but instead of languages, you’re translating “tech speak” into something the average Joe can understand.

Key points:

– Document creation and maintenance is the backbone of your role

– You’re the go-to person for making complex information digestible

– Consistency and clarity in documentation are your superpowers

2. Highlight your impact

Unlike the seemingly pointless tasks in Initech, your work as a technical writer has a real, tangible impact on the company. You’re not just improving the user experience; you’re actually reducing the number of support calls the company receives. That means fewer people saying, “PC Load Letter? What the **** does that mean?” Your work enhances product usability and ensures compliance with industry standards. In short, you’re making everyone’s life easier, from the end-users to the support team.

Key points:

– Your work directly improves user experience

– Clear documentation leads to fewer support calls

– You play a crucial role in product usability and industry compliance

3. Quantify your contributions

In the corporate world, numbers talk. Unlike Peter Gibbons, who couldn’t quantify how much work he does in a given week, you can back up your value with cold, hard data.

Keep track of metrics like reduced error rates in documentation or improved user satisfaction. If you can show that your work has led to a 30% reduction in customer support time, that’s something even Bill Lumbergh would have to acknowledge.

Key points:

– Track tangible metrics related to your work

– Focus on improvements in error rates and user satisfaction

– Quantify the time and resources saved by your contributions

4. Demonstrate cross-functional collaboration

You’re not stuck in a cubicle all day muttering about staplers. As a technical writer, you’re the ultimate team player, working with engineers, product managers, and support teams. You’re involved in the product development lifecycle from start to finish. It’s like you’re the glue holding all these different departments together, ensuring everyone’s on the same page – literally and figuratively.

Key points:

– Emphasize your collaboration with various teams

– Highlight your role throughout the product development process

– Show how you facilitate communication between different departments

5. Showcase your technical expertise

You’re not just a writer; you’re a tech-savvy professional who understands the ins and outs of the product and industry. Unlike Milton, who was shoved into the basement with his red stapler, you’re right in the thick of things, using specialized tools and software to create top-notch documentation. Your technical know-how is what sets you apart from your average writer.

Key points:

– Demonstrate your deep understanding of the product and industry

– Highlight the specialized tools and software you use

– Show how your technical expertise enhances your writing

6. Prepare a portfolio

Unlike the characters in Office Space who seem to produce nothing of value, you’ve got tangible proof of your skills.

Putting together a portfolio is like creating your own personal Greatest Hits album, but instead of chart-toppers, you’re showcasing your best documentation work. Include some before-and-after examples of improved documentation – it’s like the technical writing equivalent of those dramatic makeover reveals on TV.

Key points:

– Compile examples of your best work, respecting confidentiality

– Include before-and-after examples to demonstrate your impact

– Use your portfolio as concrete evidence of your skills and value

7. Use relatable analogies

When explaining your job, channel your inner Peter Gibbons talking about the “Jump to Conclusions” mat. Come up with relatable analogies that make your role clear to anyone. You’re like a translator, but instead of converting Spanish to English, you’re translating complex tech jargon into everyday language. Or think of yourself as a bridge connecting the product team to the end-users. These analogies can help even the Lumberghs of the world understand what you do.

Key points:

– Compare your role to familiar concepts like translators or bridges

– Use analogies to make your job more relatable and understandable

– Choose comparisons that highlight the value and necessity of your role

8. Emphasize continuous learning

In IT, you can’t afford to be like Milton, stuck in the past with outdated skills.

As a technical writer, you’re constantly learning and adapting. You’re not just keeping up with industry trends and technologies; you’re staying ahead of the curve. This continuous learning not only makes you better at your job but also more valuable to the company.

Key points:

– Highlight your commitment to staying updated with industry trends

– Demonstrate how your evolving skills benefit the company

– Show that you’re proactive in expanding your knowledge and capabilities

9. Discuss your role in risk mitigation

Your job isn’t just about making things easier to understand – it’s also about keeping the company out of hot water. Clear documentation can reduce liability and improve safety. It’s like you’re the company’s safety net, preventing those “O-face” moments of panic when something goes wrong. By creating  accurate documentation, you’re helping to protect both the users and the company.

Key points:

– Explain how accurate documentation reduces company liability

– Highlight the safety improvements that come from good documentation

– Emphasize your role in protecting both users and the company

10. Prepare a concise elevator pitch

Finally, unlike Tom’s long-winded explanation about taking the specifications from the customers to the engineers, you need a short, snappy summary of your role. Craft an elevator pitch that’s clear, compelling, and brief – something you could deliver between floors without boring or confusing your audience. Think of it as your own personal TPS report, but one that actually matters and doesn’t need eight different cover sheets.

Key points:

– Craft a brief, compelling summary of your role and its importance

– Practice delivering your pitch clearly and confidently

– Focus on the key value you bring to the company in just a few sentences


Remember, unlike Tom in Office Space, your goal is to articulate your value without resorting to convoluted explanations. Focus on how your work directly contributes to the company’s success and user satisfaction.

Stand up for yourself, speak clearly, and let your value shine through – no red stapler required!

If you want to learn more about creating a career as a technical writer go here and here to learn more.

Sign up to the newsletter to keep up with industry trends, job openings, and tech doc tutorials.