How to Remove Owner-Dependency From a Singapore SME: A Decision Rights Checklist

To remove owner-dependency from a Singapore SME, don't start by hiring a manager or buying a workflow tool. Start by listing every decision that currently waits for you, attaching a dollar limit and one named owner to each, and writing down the rule you already apply in your head. Most owner bottlenecks are not leadership problems or trust problems — they are undocumented approval rules stored in one person's memory. Once the rule is on paper and bounded by a limit, your team can apply it without you, and the queue outside your door shortens inside a fortnight. The tooling comes after; it only enforces a decision you have already made.

What does owner-dependency actually look like day to day?

It rarely announces itself. It looks like a salesperson holding a quote for two days because they aren't sure whether 12% off is acceptable. It looks like a WhatsApp message at 10pm asking whether to accept a part-payment. It looks like three suppliers unpaid because only you can release the bank transfer, and you were in Johor. It looks like a new hire who cannot access the shared drive until you personally add them.

The test is simple: open your phone and read the last fifty messages your staff sent you. Count how many are asking for a decision rather than reporting a result. If it is more than a quarter, you are the system of record for your own company's rules — and that is a single point of failure no backup covers.

Why does digitalising first make owner-dependency worse?

Because software is faithful. If your current process is "ask the boss", a workflow tool will build you a beautiful, auditable, notification-rich queue that still ends at the boss — only now it is slower, because the request has to be typed into a form first. We have watched SMEs spend five figures on approval software that reduced nothing, because the approval logic was never extracted from the owner's head before it was automated.

The 2027 compliance clocks raise the cost of leaving it informal. E-invoicing through InvoiceNow means your billing documents become structured, transmitted records rather than PDFs you can quietly reissue. Workplace Fairness Act obligations mean hiring decisions need a documented basis. Both reward companies whose decisions already have a stated rule and a named decision-maker, and penalise companies where the answer to "why was this approved?" is "because I said so at the time."

How do you decide which decisions to hand over?

Sort every recurring decision into three buckets and be honest about the middle one:

• Reversible and bounded. A 10% discount, a small purchase, a goodwill credit note, a shift swap. Hand these over immediately with a ceiling. The worst case is a number you can absorb.
• Reversible but unbounded. Discounting with no floor, extending credit terms, committing delivery dates. Hand these over with the rule attached — for example, credit terms up to 30 days for customers with no overdue balance, anything longer comes to you.
• Irreversible or existential. Signing a lease, taking on debt, firing someone, changing pricing structure, giving a third party access to your customer database. Keep these. Owner-dependency is only a problem where it is unnecessary; here it is the job.

The bucket that actually causes the bottleneck is the second one. Owners hold on to those decisions not because they are high stakes, but because the rule has never been articulated clearly enough to delegate.

What goes into a decision rights table?

One page, six columns, reviewed quarterly. It is the single most valuable operational document a 10-to-30 person company can own:

Note what the table does not contain: personality. It names a role, not a favourite employee. When that person leaves, the rule survives — which is the entire point.

How do you stop exceptions from rebuilding the bottleneck?

Exceptions are how owner-dependency grows back. The fix is to make exceptions visible and countable rather than forbidden. Keep one log — a spreadsheet is fine — with four columns: date, decision, who escalated, why the rule didn't fit. Review it monthly and ask one question of each entry: should the rule change, or was this genuinely a one-off?

If the same exception appears three times, the rule is wrong, not the staff. Raise the limit, add the missing condition, and stop answering that question forever. SMEs that run this review for one quarter typically cut escalations by half — not through discipline, but because the rules finally match reality.

What does this look like in a 14-person firm?

A composite from the pattern we see most often: a specialist trading company, 14 staff, the founder personally approving every quote above $2,000 and releasing every payment. Sales cycle averaged nine days, of which roughly three were the quote sitting in the founder's inbox. When he travelled, nothing moved.

The intervention took three weeks and no new software. They wrote the decision rights table, set a $15,000 quote authority for two senior staff with a documented margin floor, moved payment release to dual approval between the bookkeeper and the ops manager, and started the exception log. Quote turnaround fell to under two days. The founder's measurable gain was not free time — it was that the business kept quoting during a week he spent in hospital. The bottleneck had changed shape: from a person to a process.

What is the 30-day sequence to get this in place?

1. Days 1–5: Log every decision that comes to you. Don't change anything yet, just record it.
2. Days 6–10: Sort the log into the three buckets. Expect 60–70% to be reversible and bounded.
3. Days 11–15: Draft the decision rights table. One page. Roles, not names.
4. Days 16–20: Walk it through with each role owner and ask them to tell you the rule back in their own words. Where they can't, the rule is unclear.
5. Days 21–30: Set the limits inside your actual systems — accounting approval thresholds, bank dual authorisation, CRM discount caps, access role templates — and start the exception log.

Do this before you scope any automation or workflow project for 2027. Automating documented decision rights is straightforward. Automating a bottleneck just makes it faster at waiting.

Frequently asked questions

Isn't this just delegation with extra paperwork?

Delegation hands over a task. Decision rights hand over the authority and the rule behind it, with a stated boundary. Most failed delegation in SMEs is actually undelegated authority — staff are given the work but not permission to finish it, so it returns to the owner at the final step. The paperwork is one page, and it is what makes the handover survive a staff change.

What if my team makes an expensive mistake with their new authority?

That is what the limit is for. Set each ceiling at an amount you could absorb twice without losing sleep, then raise it as evidence accumulates. In practice the cost of occasional bounded errors is far smaller than the cost of a nine-day sales cycle and a company that stops functioning when one person is unavailable.

Do I need software to implement decision rights?

No, but you should configure the software you already have. Your accounting system almost certainly supports approval thresholds, your bank supports dual authorisation, and Google Workspace or Microsoft 365 supports role-based access templates. Switch those on first. Buy a workflow tool only if you still have a measurable queue after the limits are enforced in existing systems — and by then you will be able to describe exactly what the tool must do.