Governance

Governance is the operating system through which an organisation makes decisions, assigns authority, controls exceptions and keeps execution aligned with direction. In an SME, governance is not a boardroom abstraction. It is the set of rules, roles, thresholds and rituals that prevents every decision from returning to the founder.

In brief

Governance answers practical questions: who can decide, who must be consulted, which decisions escalate, which forums exist, which indicators matter, and when a project should stop.

Many SMEs have management but little governance. People work hard, meetings happen and decisions are made, but the rules of decision-making remain implicit. The founder becomes the default forum, the default tie-breaker and the default exception handler.

Good governance does not mean adding bureaucracy. It means reducing ambiguity enough that the company can move without asking permission for everything.

Operational definition

Governance includes four elements.

Decision rights: who can decide what, within which boundaries.

Rituals and forums: where recurring decisions are made, reviewed and escalated.

Rules and thresholds: the conditions that define when a decision stays local and when it moves upward.

Accountability and review: how decisions are checked after the fact and how the organisation learns from them.

A governance system is weak when these elements exist only in the founder’s head. It is stronger when they are explicit, used and periodically reviewed.

Why it matters for SMEs

SMEs often grow faster than their decision architecture. At small scale, the founder can see most things and decide quickly. As volume, people and complexity grow, that same centrality becomes a constraint.

The first symptom is escalation. Every unusual case goes upward. The second is hesitation. People wait because they are not sure they have the right to decide. The third is orphan decisions: issues everyone sees but nobody owns.

The result is not only slowness. It is loss of managerial energy. The top of the organisation spends attention on choices that should be local, while strategic decisions wait.

For investors, governance matters because it shows whether the company can keep operating when the founder is not the live control system.

Observable signals

Look for repeated phrases such as “ask the founder”, “better not decide”, “who approved this?” or “we discussed it but nothing happened”.

Look for meetings that generate conversation but no accountable decision.

Look for decisions reopened after they were already made.

Look for escalation of small exceptions.

Look for initiatives that continue because nobody has the authority to stop them.

Look for managers who formally have a role but practically lack decision boundaries.

Common mistakes

The first mistake is confusing governance with hierarchy. An organisation chart says who reports to whom. Governance says how decisions are made and reviewed.

The second mistake is adding committees without decision rights. A forum without authority produces discussion, not governance.

The third mistake is overcorrecting with excessive control. If every local decision requires approval, governance becomes a queue.

The fourth mistake is designing governance around current people instead of roles. This preserves dependency and makes every replacement disruptive.

Operational example

A 38-person service company has weekly management meetings, but the same issues return. Pricing exceptions, delivery priorities and resource allocation are discussed repeatedly, yet decisions are reopened by the founder during the week.

The issue is not lack of meetings. It is weak governance.

The company defines decision rights for three recurring categories: discounts, delivery exceptions and resource conflicts. Each category receives an owner, a threshold, minimum information and a review rhythm. The weekly meeting changes: it no longer reopens every decision but reviews exceptions and decisions outside threshold.

Within two months, founder interruptions fall and lead time on commercial decisions decreases. The meeting becomes a governance forum rather than a status ritual.

Diagnostic questions

Which decisions always escalate to the same person?

Which decisions are discussed repeatedly without closure?

Which forums have the authority to decide, and which only exchange information?

Which thresholds define local autonomy?

Which decisions are reviewed after the fact instead of authorised before the fact?

Which projects continue because nobody owns the stop decision?

Practical implications

Start with recurring decisions, not abstract structure. Identify three to five decision categories that create the most delay or escalation. For each, define owner, threshold, minimum information and review.

Then check the rituals. Each recurring meeting should have a clear governance function: decide, review, escalate, learn or coordinate. If a meeting has no decision function, reduce or redesign it.

Finally, protect review from becoming preventive control. Good governance often shifts control from “ask before acting” to “act within boundary, review after”.

MARTRO reading

In MARTRO’s reading, governance is where process diagnosis becomes organisational architecture. A flow may show where work waits; governance explains why the decision that would move it is not available.

Governance is not a layer above operations. It is embedded in operations through decision rights, thresholds, stop rules and review rituals. This is why MARTRO reads governance through evidence: escalations, waits, reopened decisions, orphan issues and unresolved exceptions.

When to go deeper

Go deeper when the founder remains the default decision point, when meetings do not close issues, when delegations do not create autonomy, or when growth increases delay rather than only workload.

Natural next steps are decision rights, decision latency, RACI and stop rule.

Frequently asked questions

Is governance only for large companies? No. SMEs need governance as soon as proximity is no longer enough to coordinate decisions.

Is governance the same as hierarchy? No. Hierarchy shows reporting lines. Governance shows how decisions are made, escalated and reviewed.

Does governance slow the company down? Bad governance does. Good governance speeds the company up by reducing repeated permission-seeking and unclear escalation.

Where should an SME start? Start with recurring decisions that create delay: discounts, exceptions, purchases, priorities, hiring, project stops.

What is the simplest governance artefact? A one-page decision-rights table with owner, threshold, required information and review rhythm.