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!!!
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
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.
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!!!
Well said! I'm glad you liked the video! Thank you for your support. ☺️
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
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?
Great question! You can create a routine task to verify that the SOP is still relevant and whether or not it needs to be updated.
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 was just about to say this!
I entered my email to get the free templates, but nothing sent to my email? It is not working!