justSayIT, Technical Writers‘ LAUGH: Recent Episodes
justSayITBeth
Experience a comedy club atmosphere with palatable bites of wisdom (10-mins.) on topics directed at the technical writing community but suitable for anyone. Content is wry humour coated to balance the hype of new technology with everyday work-place reality.
A clip from EP-5, a personal remembrance; my mother, also called Elizabeth, became Queen for a day!
We recognize the world's deadliest creatures but what about those found in the technical writing world—they make you want to spit!
Excessive idle talk or chatter is called palaver, yet it can appear in writing. How can Technical Writers avoid it?
The simplest way of gaining goodwill and making people feel special is by remembering their name, and yet how many of us do it? Technical Writers apply names in the documentation we write but do we use names wisely?
Mired in a web of complacency, it's much easier to accept things as they are or do it the way we've always done it because it's comfortable. How can technical writers avoid delivering documentation in the same old way?
Almost every partnership, group or team has one dominant personality that must be "boss". Yet the most prevalent and destructive type of leadership, especially in the workplace, are ineffectual bosses that avoid meaningful involvement with their teams. Listen for tips on how to face those "paper tigers".
Bogged down with “gum” work? It affects your ability to learn, do more promotable work, and to demonstrate your full potential.
Following reason or emotion in decision-making is described as two horses pulling us in opposite directions. How does this impact leadership and teamwork?
Empathy, it’s the oil of relationships that keeps them running smoothly and a critical skill for business. How do we exercise it?
Popularized by Alfred Hitchcock, the master of suspense in horror films, could this plot device be used in technical writing?
There’s much to be learned from puzzles and their "unpuzzling". They can relieve stress and even increase our IQ. How do they affect technical writing?
Myths in technical writing? Let’s bust three common ones. Technology is rapidly changing our profession, yet we must keep our sanity, meet these myths head-on and kick them to the curb!
How can we be careful with words yet provoke thought with wild words? Context is everything!
How does the honour system work when part of a team? What is the language of trust and how can we use it well?
It’s a lot to swallow but if nature can automate the many reflexes used in swallowing then why are technical writers so slow to apply automation to documentation?
From a different angle, let’s look at three familiar models that we use as standards to either imitate or compare.
What does the Rebus Principle and ancient Incas Khipus have to do with changes to technical writing? Aren’t writing basics and tools much the same?
Is curiosity a good trait or one that betrays us; instilling prying behaviour that’s harmful, leading to risk-taking and danger? As writers, how do we apply curiosity to content and meet the needs of our readers?
There are times, especially in our careers, when we need someone with more experience to guide us. The term for this is Mentorship. Total commitment is essential: consider these keys to securing a Mentor and being a Protégé.
Teams need to recognize the importance of having a common understanding of the definition of done, then the strategies required to finish can be applied and everyone can move on.
What is Plain Language and Global English and why is it important to all writers? Create an Information Scent that your readers will pursue to reach their goal.
Talk about missteps; as tech-writers we unsuspectingly stumble upon information landmines. Leverage your combined knowledge; be united in purpose and vision, providing a single source of truth throughout the enterprise.
Just say "No" more often in the workplace: consider these points on how and why you need to do it.