Small business operating system — no more reminders, no more forgotten tasks

7 min read

There's a question many small business owners often ask each other: “How can the team run independently without me having to remind them of everything?”

That question sounds simple. But behind it lies a very real exhaustion — waking up in the morning to send reminders. In the evening, reviewing who has or hasn't done what. Some days, counting more than twenty reminders. Reminders to send reports, to reply to customers, to issue invoices.

The problem isn't incompetent employees. The problem is the lack of a small business operating system in the true sense.

Here are four principles — distilled from proven operational frameworks — to help build that system without expensive software or external consulting.

The Best Person Is Often the Biggest Bottleneck

Michael Gerber — author The E-Myth Revisited, one of the most widely read books on small business in the world — calls this “the technician's trap”.

The mechanism is simple: skilled workers often become business owners, then continue to work like craftsmen — instead of building systems for others to operate. A skilled tailor opens a shop but still sews every single garment. A skilled chef opens a restaurant but still has to be in the kitchen every day. If they take a week off, the business grinds to a halt.

Gerber distinguishes two ways of operating a business:

Most small business owners spend 90% of their time on the former — and almost no time on the latter. That's why they can't take vacations, can't scale, and always feel like the business is “running them” instead of them running the business.

A Process No One Uses Is Just Paperwork

Gerber distinguishes two types of processes, and the difference isn't in their length or meticulousness:

Dead Processes It's a documented process that no one uses. A beautiful Word file, with numbered sections and a hardbound cover. Left on a shelf, or buried in an email from last year. Many Vietnamese SMEs have such a set of SOPs — and no one remembers they exist.

Living Process It's a process directly embedded into daily work. Each step has a checkbox. Employees open it, follow it, and mark it as done. When the process needs to change, it's edited directly in that file — no meetings, no reprinting, no reminders needed.

Real-world example: a store owner with 8 employees in Da Nang uses only one Google Sheets file — a store opening and closing checklist, 12 steps, opened and ticked off daily. After two weeks, no more reminders were needed. Not because the employees changed, but because the process took over the reminding task.

A point to note: a good process doesn't need to be long. It needs to be correct — the right steps, the right order, and most importantly: used daily.

When Revenue Declines, It's Already Too Late to Impact That Month

In the book The 4 Disciplines of Execution, McChesney and Covey point out that most teams — including small businesses — are only tracking lag measures (lag measures): monthly revenue, quarterly profit, number of orders. These numbers are important, but by the time you look at them, it's too late to make an impact.

Lead Measures (lead measures) are the things that need to be done — if done correctly and sufficiently, good results will follow. This is what needs to be included in your weekly dashboard:

An effective dashboard for a small team doesn't need many numbers — it needs the right numbers. Three to five lead measures, updated at the beginning of each week. No need for Power BI, no need for Tableau. Just one page where a glance tells you where to intervene this week.

Automation doesn't start with software

Automation doesn't start with software. It starts with recognizing patterns.

Some practical examples for small teams in Vietnam:

• Excel formula to highlight orders nearing their deadline — instead of manually opening each file to check every morning
• 3 pre-written email templates for the 3 most common situations: replying to new customers, payment reminders, and post-sale follow-ups — just copy-paste and adjust the name.
• Google Form → automatically populating Sheets for employees to submit end-of-day reports without needing to send Zalo messages to their boss
• Weekly recurring Notion template for team meetings — outlining who needs to do what, what the deadlines are, and where the roadblocks are — no need to start from a blank page every time.
• Automated reminders via Zalo / email for weekly deadline reminders — instead of the owner having to remember and remind manually.

Even just these things — save 4–5 hours each week. And more importantly: it reduces the number of things the owner has to keep in their head.

Don't build from scratch when a proven framework already exists

Gino Wickman — author of Traction and founder of EOS, an operating system adopted by over 200.000 small businesses worldwide — describes the 6 core components of a well-run business:

• Vision — everyone on the team understands where the business is heading
• People — the right people, in the right positions, with the right roles
• Data — have actual data to make decisions (no guesswork)
• Issues — issues are brought to the table and definitively resolved, without letting them pile up
• Process ⭐ — core processes are documented, followed, and improved
• Traction ⭐ — everyone has clear responsibilities, with concrete weekly milestones

For most small businesses, Process and Traction are the two weakest points. And they are also the two things that create the biggest impact when improved.

Wickman doesn't recommend building a system from scratch. He advises finding a proven framework, adjusting it to fit your team, and then implementing it. No need to reinvent the wheel.

That's why Small Team OS Lite BEUP Space's solution comes to life — a set of process templates, lead/lag measure dashboards, and a weekly work tracking system designed specifically for teams under 10 people, running on Notion. Free. No consultant needed, no lengthy training. Just an afternoon to set up and get started.

→ Download Small Team OS Lite for free

For small but passionate teams.

References: Gerber, M. E. — The E-Myth Revisited (1995, HarperCollins) · Wickman, G. — Traction (2011, BenBella Books) · McChesney, C. & Covey, S. — The 4 Disciplines of Execution (2012, Free Press)

Related Posts

• Business Digital Twin — systematizing experience
• Designing knowledge management
• Fabric Inventory Management with Excel — A Real-world Systemization Example