What part of your startup still depends on one person remembering to do it ?
I keep noticing how many small teams have important processes that are not really systems yet.
Someone remembers to follow up.
Someone knows which client needs what.
Someone manually checks whether something shipped.
Someone has the spreadsheet only they understand.
It works fine while the team is small.
Until that person is busy, leaves, or simply forgets.
I’m curious about the messy operational side of startups:
What’s one thing in your business that still depends too much on one person’s memory or manual effort?
And have you tried to fix it, or is it still sitting in the “we’ll automate this later” bucket?
Appreciate the honesty here, most people only share the wins.
Yeah, I think the messy parts are usually more useful to talk about anyway. The “someone just remembers to do it” stage is pretty normal, but it becomes risky once the team starts growing.
Agreed — that’s when missed inbound calls get expensive. We’re measuring call → booking over ~14 days for dental/HVAC so the handoff isn’t memory-bound. Curious if you’ve seen a team grow past that stage with a simple log, or if it stayed tribal knowledge?
I’ve seen simple logs work for a while, but only if someone owns keeping them updated. Once the team grows, the log itself can become another thing people forget.
I think the real shift is when the process creates its own evidence instead of relying on memory.
Missed inbound calls and appointment follow-ups are the ones that still bite us when they’re memory-bound. Curious what evidence you use that a follow-up actually happened — a log, a booked slot, or just ‘someone said they called back’?
Booked slot or a system log feels much stronger than “someone said they called back.”
If the only proof of a follow-up is another person remembering it happened, the process is still basically memory-bound.