A sense of purpose! – Having a sense of purpose has motivated me as a tech writer most reliably over the years, regardless of the project at hand. It helps me overcome adverse conditions and huge workloads. But what is that sense of purpose? And how does it work as a motivating force?
A sense of purpose in tech writing
I usually find a sense of purpose outside the document I produce: It can be a recently hired colleague who tells me my manual helped her get up to speed quickly. It can be a customer services colleague who tells me my online help provided the answers a caller needed. It can be colleague from the training crew who recommends my tutorial before or after a training course. Or it can be a customer who felt confident about upgrading because the Release Notes told him what he was getting himself into.
So to me, finding a sense of purpose goes beyond me and my document (though that should still be well laid out, spelled correctly and all that). It is about the relationships which my documentation facilitates between the product and its users. It is knowing that the product and the company are better for the documentation. And it is frequently knowing that my documentation serves the customer.
How a sense of purpose works
To be happy, your work must fulfill three universal psychological needs: autonomy, competence, and relatedness.
Specifically, excerpted again from the Study Hacks post:
Autonomy refers to control over how you fill your time.
Competence refers to mastering unambiguously useful things.
Relatedness refers to a feeling of connection to others.
That pretty much describes my ideal workplace as a tech writer. Of course, reality takes its toll occasionally, with deadlines, less than useful tools or an out-of-sync irritation when I find that various documents available to customers are at odds.
Ensuring a sense of purpose
If you are managing tech writers, there a few things you can do to make sure your writers can be motivated by a sense of purpose:
- Allow for sufficiently autonomous time management: I’m all in favor of deadlines, but tech writers and managers should sit down to agree on the desired quality and scope of documentation to come up with reasonable deadlines. Or if you have a set deadline first and foremost, agree on what scope and quality can reasonably be achieved within that time frame.
- Encourage writers to reach out to other departments to share contents, documents and purpose: Frequently, training and customer services hold related stakes in having high-quality and useful documentation.
- Ensure that regular documentation user surveys align the supplied documentation with its usage and expectations.
Dan Pink has more advice for managers in his article on “Gainful employment“.
– What’s the best motivation for your writing? What provides you with a sense of purpose?