Building accountability without bureaucracy

Small teams resist process for a good reason: they've seen what it becomes in larger companies. Approvals, forms, status meetings, and a general sense that saying yes to anything takes three weeks.

But the alternative — everyone owning everything — produces its own failure: work that falls between people, decisions that wait for the founder, and problems nobody feels responsible for.

Accountability and bureaucracy are not the same thing. One is about clarity; the other is about control.

Rule 1: One owner per outcome

Not per task — per outcome. "Client onboarding runs smoothly" has one owner, even if four people perform steps within it.

Shared ownership is the most common cause of dropped work in small teams. Two names on something means each assumes the other has it.

Rule 2: Write down who decides what

Most escalation exists because decision rights were never defined. People check with the founder not out of deference but out of uncertainty.

Make three lists per role: decide alone, decide with a second opinion, escalate. Set thresholds in numbers where possible — "refunds under ₦50,000, approve; above, escalate". A single afternoon of this removes a startling volume of interruptions.

Rule 3: Commitments have dates and are visible

"I'll look into it" is not a commitment. "I'll send it Thursday" is.

You don't need a project management methodology. You need one place where open commitments, owners and dates are visible to everyone. Anything else is a private promise, and private promises are the ones that slip.

Rule 4: One short weekly review

Fifteen minutes, standing agenda:

• What was committed last week and did it happen?
• What broke?
• What one process improves this week?

That's the entire management system most ten-person teams need. It creates accountability through visibility rather than supervision, and it's short enough that nobody dreads it.

Rule 5: Fix the system, not the person

When something goes wrong, ask three questions in order: was the process unclear, was it unfollowed, or was it wrong?

Most defects are the first or third — which means the fix is a document change, not a performance conversation. Teams that default to blaming people learn to hide problems, and hidden problems are the expensive kind.

What makes it bureaucratic instead

Four warning signs, worth checking quarterly:

• New approval steps that don't prevent a real, previously experienced problem
• Reporting nobody reads. If a report hasn't changed a decision in three months, kill it.
• Meetings that exist to transfer status rather than make decisions
• Documents longer than a page for tasks shorter than an hour

Every process should be justifiable by a specific failure it prevents. If the justification is "it's good practice", delete it.

The balance

Standardise outcomes; leave method flexible where method doesn't affect the result. Define what "done and correct" looks like, then let people get there their own way.

That's the whole distinction. Bureaucracy controls how people work. Accountability makes clear what they're responsible for delivering — and then gets out of the way.