How I Accidentally Created an SOP (and what an SOP is!)
Before I tell you how I created an SOP (and what an SOP IS), Here’s a mid week recap of my monthly project!
It’s week 2 of my competitive set analysis!
If you missed last week’s post, you can read it here!
This is kind of a “mid-week check in” post 🙂
So this week, I am analyzing lots of various things such as number of flavors available, number of frosting flavors available, fondant options, delivery options, pricing, alternative options (if available – such as gluten free options and such), and style and design options!
So yeah, a LOT! And I’m just going to rant here for a little bit, because you’d think this information would be super accessible online, but IT’S NOT. I mean, come on! How hard is it to put your delivery options on your website? I guess it doesn’t bother me very much. I just emailed them. HOWEVER, Bakery C gained a lot of points in my book because they were the ONLY bakery that had their delivery options online 🙂
Design options are always readily available to view online (which is SUPER convenient!), and now I’m craving cake! 😀
In short, the project is going well and I’m super excited to create the spreadsheets at the end 🙂 I know….I’m a geek 😛
How I Accidentally Created an SOP!
Okay, this is why you clicked on the post, so here it is.
So, what’s an SOP? It stands for Standard Operating Procedure (I know – pretty fancy term!).
A standard operating procedure is a documented process for how things are done in a company or organization. Basically, it’s a very detailed set of instructions on how to do certain jobs within a workplace.
For example, if your company sold smoothies on the street and you had five different people who worked for you making the smoothies, chances are they don’t all make smoothies the same way. That’s why you create a standard operating procedure. It’s a set of exact instructions on EXACTLY how to create a smoothie. SOP’s are also super useful to have around when hiring new employees as you don’t have to spend much time training them because you have a system for that – an SOP!
SO, here’s how I accidentally created an SOP:
I recently joined an existing project during a time of innovation and change, and part of the project involved using a script – the only problem was, there was no script tailored to the new techniques. The old script is phenomenal, but it did not take into account the new technology we are harnessing.
I had mini scripts in my head for different conditions and different scenarios, but they were all jumbled in my head and mixed up. For my own sanity’s sake, I needed to write my own script.
So, I reviewed the old script, taking the essential parts and putting them into mine as well as inserting phrases that had been proven and combined them with the new technology. Eventually (after a few edits), I figured out a script that worked well for me. I didn’t want to wait to continue with the project while I waited for a new script to be written, and this just really helped me get organized and see everything laid out in order. What I didn’t anticipate was other people started using my script as well!
I found a place where there was no system, and created one 🙂
I say I “accidentally” created it because I didn’t know that making a system like that is called an SOP. I learned about those after I wrote the script!
Okay, so I’m only writing about this experience because one of my Praxis advisers challenged me to. It was not my intention to brag about myself or anything like that. In fact, a script was just recently written by the experts in the project that eliminates the need for the one I wrote. But in the meantime, my script helped me to keep going with the project until a permanent solution was given me.
Sometimes you have to fake it til you make it 😉 Again – not illegal things. Obviously. Please don’t be THAT person. You know who I mean.
Until next time,
Hope Szymanski
