Work less, not harder. Researchers have confirmed that overworking is actually not very effective. Not only is it exhausting, but overworking yourself can backfire, burn you out and, ultimately, make you less productive. Many of us have a comfortable side of us, the slacker, that wants us to minimize what we do, and simplify how we do it.
Written by: Johanna Hansen
Image & photo: Karin Askeroth & Christine Svedjemo
Read all about how you can be be a tech doc slacker and still work efficiently.
The mindset of a slacker
Budget and invest to work even less. Timebox and set clear goals, invest by networking, find key persons, and have the courage to wait for others to give the information needed.
Ask questions early on. Rather than wait until the last minute to ask questions, ask as early as possible to raise awareness and interest. Delegate and let go of the stuff outside your control.
Think as a successful Product owner. Schedule your weeks and days in advance. Set the goals for the week, estimate the time needed, and block this time. Keep your to-do list manageable, try to prioritize no more than five tasks to complete.
Limit task switching and focus on one type of work at a time. Split between collaborative work and solo work, e.g., collaborative work between 9am and 2pm. Solo work happens before or after.
Minimize blockers. Simplify the input feed by getting to know your information providers. Continuously evaluate your methods and look for shortcuts.
Automate repetitive things, either by scripting, templating, or reusing
(e.g. automation of graphics creation, automation in Jira, and “Smart” tech writing using variables & profiling, re-use, branching etc).
Focus on the high-level, set a baseline, set up the information flow, reviews, translation and publishing instead of hunting for detailed information.
Copy with pride. Copy from already existing documentation or adapt to an existing process. Handle tech writing as others handle e.g. software development.
We are not perfect – and should not be aiming for it either. Find a good enough level, try to automate repetitive tasks, handle tech writing as others handle e.g. software development. Focus on the high-level, baseline, processes – and let others focus on details. Technical writing is not “rocket science” – copy with pride.
Our advice to you: Have a look at companies that have adapted their Technical writing in a successful way, e.g., https://docs.apptus.com/.