Awesome video! You're moving into something that seems simple and obvious, but is somehow a profound shift from previous generations of office workers... Thank you!!!
Hi! In this video you mention about linking SOPs to taks. Whereas, in your video about switching from docs to tasks (clickup), you write SOP directly within description area of a task. I am in the process of moving SOP to ClickUp. Having SOP in task is convenient but what about updating SOPs? What is your way of managing updates?
Ok. And when SOP is updated, what to do with all tasks that are active and were created based on the updated SOP. I think about "mention SOP (task)" in task description. So when SOP changes, all active tasks don't need to be rewrites. @@LaylaPomper
@@MrPioorko Edit: Layla answers this (at least in part) starting at 7:13 in the video 👍! You're looking for the source of truth. Using embeds for Markdown/HTML-based apps or "subdocuments" for Word, you have the task list insert the SOP content, so that updating the SOP (i.e. source of truth) automatically updates every task list based on it. Layla's solution sends the user to visit the latest version, rather than directly including the content, which still achieves the goal of changing one file that updates all the others.
I’m confused. If you create a template SOP task, why would you need to link out to an external doc? Wouldn’t you just go back into the original template and make the updates there so that it reflects in the tasks moving forward? It wouldn’t change anything from the past, correct?
Want to work with me to get your SOPs updated (or created for the first time)? 1 - Join my next live SOP workshop: processdriven.co/services/sop 2 - Unlock 109 SOP examples: processdriven.co/sop
