Very helpful video. The "go to grandma's house" example is one that will stick. The getting there is the process. The different ways in how to get there, bike, foot, by car, and the steps to take are the sop's.
If we are creating SOPs for each individual fork in the road or variation or if then instance. What is the best way to reduce redundancy in those SOPs across multiple? as a programmer who cringes at the notion of having to maintain duplicate information across similar records, there has to an efficient dynamic way to handle those if then instances. We are using smart suite upon your reccomendation. for something that only has two options I feel like nesting the variations in option headers would be so much easier to maintain. at the very least, linking to records that have all the initial same steps makes sense. linking records to different pages sounds like it will be kind of difficult for people to follow along though. not exactly the most user friendly... Edit: spoke too soon before the video end. networking is the answer..
So an SOP is like a recipe for doing something you do often to standardise is so that everyone does things in the same order and in the same way. Because the way I make lasagne is different to the way you make lasagne unless we follow the same recipe😅
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
How would you explain the difference between a process and a standard operating procedure? What made it click for you? 😊
Very helpful video. The "go to grandma's house" example is one that will stick. The getting there is the process. The different ways in how to get there, bike, foot, by car, and the steps to take are the sop's.
Love that the "Go to Grandma's house" example is sticking!
Thank you so much for all the effort you put in for us to learn! ❤
Hey Andrea! Thank you for the kind words! I'm so glad this was helpful!
This is absolutely fantastic! Thank you so much for demystifying SOPs.
Glad it was helpful!
Whole lot of knowledge I got in one shot!...awesome, thank you so much :)
Happy to hear this, Hamzri!
Thank you, great information
Glad you found it useful!
Excellent SOP, you have helped me to think about how they form the basis of creative App making
Great to hear!
Awesome explanation, Thanks for the effort. You smash 🙌🏼
Glad you liked it!
Thank you!!! 🙏🏾
You’re welcome!
Very great video❤❤❤
Thank you 🤗
If we are creating SOPs for each individual fork in the road or variation or if then instance. What is the best way to reduce redundancy in those SOPs across multiple? as a programmer who cringes at the notion of having to maintain duplicate information across similar records, there has to an efficient dynamic way to handle those if then instances. We are using smart suite upon your reccomendation. for something that only has two options I feel like nesting the variations in option headers would be so much easier to maintain. at the very least, linking to records that have all the initial same steps makes sense. linking records to different pages sounds like it will be kind of difficult for people to follow along though. not exactly the most user friendly... Edit: spoke too soon before the video end. networking is the answer..
Exactly! ☺️
so an SOP is like a function?
Hey! Process is the action the SOP is like the instructions/recipe :)
@@LaylaPomper 👍
So an SOP is like a recipe for doing something you do often to standardise is so that everyone does things in the same order and in the same way. Because the way I make lasagne is different to the way you make lasagne unless we follow the same recipe😅
Exactly! 🎉
Darn, now I'm hungry for lasagna...
@@LaylaPomper if you ever need an analogy I'm your gal lol
Smith Barbara Martinez David Davis Sarah
Just commenting for the Algorithm.
Thank you so much Dani!