Stacy Derrick Creative

I got back from vacation, opened my laptop, and had that small sinking feeling you get when you realize something has been quietly not happening.

I hadn’t published a blog post in a while. Not a scandalous amount of time. Eighteen days. But I write every one to two weeks, and I had built a system specifically so I wouldn’t have to hold that in my head.

So I went looking for what broke.

Nothing broke

That’s the part that got me.

I have two recurring tasks in Notion. One is a weekly content check that asks whether a post has gone out in the last seven to ten days. The other is a monthly review where I pick the next topic and move it into drafting so there’s always something in the queue.

Both are set up. Both are sitting right there in my task database.

Neither one ran.

Notion’s free plan doesn’t auto-repeat tasks, which means those recurring items are manually cloned. I knew that at some point. I had stopped thinking about it. The last instance got created on August 4th and no successor was ever generated, so the chain that was supposed to catch a slipping cadence just stopped producing links.

No error message. No overdue alert loud enough to register. No red anything.

I had built myself an executive assistant and never noticed she’d stopped coming in.

Why I didn’t catch it

Here’s my honest mental model, and I think a lot of business owners share it: I assumed the tool was watching for me.

That’s not how any of these tools work. Notion shows you what you put into it. Your calendar shows you what you scheduled. Your accounting software categorizes what you feed it. They’re all mirrors. They reflect back the system you built, including the parts of it that quietly stopped working.

A mirror won’t tell you that you forgot to look.

The other one I found

While I was in there, I checked my Client Onboarding SOP.

Step 1 told me to send a Calendly link. Step 7 referenced Calendly again. My 2026 operations plan mentions it too.

I don’t use Calendly. I’ve never used Calendly for this business. My booking runs through a Google Calendar appointment schedule, and it has since I set it up.

That document read perfectly. Clean formatting, numbered steps, professional language. It was also sending anyone who followed it, including future me on a busy day, to a tool that doesn’t exist in my stack. Wrong and functional look identical from the outside.

Then it got worse, in a way I’m still a little embarrassed about. I’d already fixed it. Version 2.2 of that SOP, updated August 7th, corrects the scheduling references. I did the work, saved the new version, and eight days later sat down to write this post and described the problem in the present tense without checking whether it was still true.

So I found a third stale record while writing about the first two, and this one was my own memory of what was broken. The operations plan really does still say Calendly, so there’s real work left. The SOP was already handled and I didn’t know it.

What eighteen days actually cost

Some real things, none of them catastrophic.

Indexing momentum, mostly. My site is young and still building from close to zero. Google rewards consistency, and every post I publish is another signal that this site is active and worth crawling. Eighteen quiet days is eighteen days of not sending that signal.

A Google Business Profile post that should have gone up and didn’t. That’s on the same weekly check, so it lapsed on the same date.

And the one I didn’t expect: the momentum in my own head. I like publishing. I get a little charge out of hitting the button and watching Search Console pick it up. Eighteen days is long enough for that to go cold and for the next post to start feeling like a chore instead of a thing I was in the middle of.

This is most of what I actually find

I do visibility and operations work for small practices, and I want to be honest about what that work usually turns up.

It’s rarely something broken. Broken gets found. Broken gets a phone call.

What I find is a form that’s been collecting responses into a place nobody meant for them to go. A business listing showing hours that changed last spring. A tool still running in the background from a setup two providers ago, doing something the owner would not have agreed to if anyone had asked. An automation that fires perfectly and delivers to an address that stopped being checked.

Every one of those was working. That’s why they survived. Nobody audits the thing that isn’t complaining.

And none of those owners were careless. They were busy, and they were running on the same assumption I was: that a system, once built, keeps being a system.

Your version of this

You probably don’t have a Notion database full of recurring tasks. Doesn’t matter.

This is anytime you believe you have a system and you don’t.

It’s the price on your website that changed a year ago everywhere except your website. The contact form quietly delivering to an email address nobody opens anymore. The hours on your Google listing that were right before you changed your Thursday schedule. The autopay you set up in 2023 on a card that expired.

Every one of those looks fine. That’s what makes them expensive. A form that throws an error gets fixed that afternoon. A form that cheerfully accepts submissions into a dead inbox can run for a year.

What I’d ask you to do

Pick one thing you believe happens automatically.

Just one. Paying a specific bill. Backing something up. A recurring post going out. Your website contact form. Whatever came to mind first while you were reading, that’s probably the one.

Then confirm it. Not “I set that up.” Go look at the actual evidence that it happened last month. Submit your own contact form. Open the bank statement and find the charge. Check the timestamp on the backup.

You’ll either get a small hit of relief or you’ll find what I found. Both are useful. Only one of them stays useful if you skip the check.

I’m fixing my recurring tasks this week, and correcting the Calendly reference still sitting in my operations plan. Not because either one was on fire. Because neither one was, and that’s exactly the problem.

If you go looking and find more than you expected, that’s the work I do. I go through a business the way I just went through mine, find what’s quietly wrong, fix it, and hand you the documentation so you can run it yourself.

Some people take that and go. That’s what the documentation is for.

Other people would rather someone keep an eye on it, or keep doing it, and that’s a real choice too. Plenty of owners don’t want to become their own operations person, and there’s nothing wrong with deciding your attention is worth more somewhere else. I work both ways.

What I care about is that it’s your call, made with the keys in your hand, rather than something that just ends up being true because nobody ever showed you how any of it worked.

That’s a real conversation whenever you want to have it.

I followed this same thread out to the visibility side of it in the next post — the version of “quietly not running” that shows up as a page nobody can find instead of a task nobody did.

Stacy Derrick │ Founder, Stacy Derrick Creative, LLC │ stacyderrickcreative.com

If this was helpful and you want to support the work, you can buy me a coffee at buymeacoffee.com/stacyderrick.

You may be wondering — did AI help write this? Yes, and I want to be upfront about that. The process, the client work, and the thinking behind every step are mine, and they were worth reading before AI touched a word. AI just helped me pull it together more cleanly.