Should you include what not to do in your systems?

Okay, welcome to today's episode.

My name is Tom Rolley of systemio.dev.

I want to revert back to two days ago when we covered the making of the jelly for those of you who've been following along, we went through and my daughter jumped midlife and was asking whether we could make green jelly.

Now we went and did that.

And to do that there was this little box here, this airplane, Jelly lime-flavored now, it's been eaten.

So I don't have an example of the final product.

But as you can imagine, it was just normal jelly it was it worked out really well.

And to do it, we followed the process, and they kind of laugh on the jelly to actually give that so you can see number one ready number two set number three jelly, but it actually tells you what to do.

Empty the contents of aeroplane original flying flavored jelly into a bowl and add one cup of boiling water, Stir and dissolve and then add that 200 mils of cold water and stir.

refrigerate until firm and wobbly for a minimum of four hours make 500 grams of jelly.

Now, this is why I wanted to bring your attention.

Serve with your flavor fresh fruit do not add fresh pineapple, kiwi fruit, or por por as jelly will not set.

So you can notice two things here, we've got, first of all, a way of taking the stuff that comes in essence turning it into the final product.

And it's also conveniently located on the side of the box.

So as long as I don't lose this box when I'm making the jelly, which hopefully I open it up all the stuff out and it's ready to go.

I can even read the instructions before I've got to open it, I follow the instructions.

And my last point here is that they've also included what not to do.

Why? Because in this case, if you add fresh pineapple, if you add kiwi fruit, if you add por por to your jelly, then there must be some enzyme there must be some special feature of those fruits, that means that the jelly won't set, which means that your process won't work.

So in this case, it's critical.

In many processes.

It's not that important.

Like there's a lot of things to or not to do.

But it won't destroy the end process.

And therefore it doesn't really matter.

But in this case, that is things not to do that if you know that it's important not to do this.

For instance, one comes to mind about using Hero poster IO, which is what we used to schedule out the future quote cards, that if it says posts now it means that a button has been missed.

And if you click that post now then it won't be scheduled at all.

And so that actually is a warning in there it says Warning.

If it says post now, don't click the button.

It shouldn't say schedule means that you've missed an important step.

But most of the other steps most the other systems don't have anything like that.

Why? Because really, it doesn't matter if you follow the instructions.

There's not a negative outcome.

But sometimes it's important and being aware of that.

It is an important thing to document what not to do, then that should be in the process just as much as what to do is in there as well.

An example of this that's that lime jelly.

It was really good.

My daughter loved it.

It's simple to make simple to follow.

But note that it does include a negative consequence if you do certain things and that's also in the instructions.

All right, that's all I got for you today.

If you're looking for a way to improve your systems and business, then head over systemio.dev.

Thanks so much for tuning in.

Look forward to seeing on tomorrow's episodes, we continue this journey into the power of systems and processes in business.

See you then.