Elliot didn't mean to become the bottleneck.
He started his company in a college dorm with $500 and a dream. 5 years later, it was doing $2.7M ARR… and Elliot was still signing off on every task, replying to every Slack, and editing every landing page like it was a hostage negotiation.
His desk? A battlefield. Sticky notes. Half-drank coffee. A whiteboard with what might've been a marketing plan or a crime scene diagram.
His team was loyal. Talented. But they'd become weirdly dependent on him.
"Hey Elliot, do we offer Net 30?"
"Can you approve this?"
"Can you resend that doc? The link is haunted."
He tried fixing it.
Asana. Slack. ClickUp. A Notion board titled "Do Not Let Me Burn Out" (which he never opened).
Then came The Meeting — a 1-hour check-in that became a 4-hour existential crisis.
That's when it hit him:
He wasn't leading a business.
He was babysitting chaos.
After The Meeting, Elliot had a thought:
"Maybe I need systems. Real ones."
So he cracked open a Google Doc and tried to write an SOP.
It started as "How to onboard new clients."
It became a 14-page monstrosity with footnotes, internal links, and a flowchart that required a PhD in hieroglyphics.
He posted it proudly in Slack on Monday:
"🎉 New SOP! Please review."
The reactions?
👀
👍
😬
Nobody followed it.
Turns out… SOPs don't matter if no one reads them. Or understands them. Or uses them.
Elliot realized: Systems are useless without buy-in.
To be continued…
Next email drops in a couple days…
–Ryan
P.S. If your team's SOPs are basically unread fan fiction or you're drowning in approvals, tasks, and cursed Google Docs…
Elliot would've clicked this 😉: [book a quick chat]
No comments:
Post a Comment