What's new
Digital Marketers Forum

Digital Marketers Forum is a forum and marketplace for digital marketing news, topics, and services. Our resources help users earn money online with current methods and actionable strategies that make more traffic, higher rankings, and online success easier to achieve.

How do you handle a coworker who never documents their work?

Joined
Oct 3, 2026
Messages
72
Reaction score
8
Have you ever had to take over a task but had no idea where to start because your coworker kept every process in their head? You end up asking the same questions repeatedly just to figure out how things are done. I understand that documenting every little detail takes time, but having a clear record would make things easier for everyone. How would you encourage a teammate to start documenting their work without making it feel like an extra burden?
 
I would suggest taking a quick screenshot of the work completed each day and sharing a short update about the progress. That way, I can easily track where the data, values, and findings came from without having to ask the same questions repeatedly. It also doesn't have to be a complicated process. A screenshot already shows what has been done, how it looks, and when it was completed, so there's no need to write a lengthy report just to document every small task.
 
I would suggest taking a quick screenshot of the work completed each day and sharing a short update about the progress. That way, I can easily track where the data, values, and findings came from without having to ask the same questions repeatedly. It also doesn't have to be a complicated process. A screenshot already shows what has been done, how it looks, and when it was completed, so there's no need to write a lengthy report just to document every small task.
That's probably the simplest way to keep track of your coworker's progress without making documentation feel like another task. And if you're both involved in the same project, they should at least keep you updated on what they've completed and what they're currently working on. A quick screenshot or a short message is already enough to give you an idea of where things stand and what to expect next.
 
I wouldn't even dare take over their work without proper documentation. They should at least leave clear instructions before passing the task to someone else. I'm there to handle the work assigned to me, not spend hours figuring out how someone else does theirs. It's only fair to have the necessary information ready so the next person can actually get started.
 
I wouldn't even dare take over their work without proper documentation. They should at least leave clear instructions before passing the task to someone else. I'm there to handle the work assigned to me, not spend hours figuring out how someone else does theirs. It's only fair to have the necessary information ready so the next person can actually get started.
Same here. I'm not going to waste time trying to memorize a process for a task I wasn't even involved in. If someone needs me to take over their work, I should at least know the scope of the task and what I'm expected to handle. Otherwise, I'll just end up staring at everything, unsure of where to start instead of actually getting work done.
 
Top