The Design of Authority
Why governance is the quiet engine of creative endurance
Essays on Strategy, Creativity and Management | Edition 03
Introduction
Why do creative businesses slow down just as the market begins to validate them?
Early momentum can feel like proof. The work lands, referrals follow and a recognisable standard begins to travel ahead of every introduction. In that phase, intuition often works remarkably well because the organisation is still small enough for proximity, taste and personal judgement to hold the centre.
Then opportunity multiplies. New clients, collaborations, markets and formats each bring decisions about direction, pricing, capacity and identity. The problem is rarely that the business has become less creative or that the team suddenly lacks ability. It is that the volume of decisions has increased while authority has remained largely where it started.
My thesis is simple: growth slows when decision authority remains implicit.
1. Momentum Before It Had a Name
While studying Finance and Control in Amsterdam, I worked part-time at one of the city's most popular sneaker boutiques on the Nieuwendijk. The shop attracted aspiring designers, artists, musicians and early-stage entrepreneurs, often people with a strong idea and one or two others willing to help make it real.
During breaks and throughout the day, ideas were constantly discussed across the counter or somewhere at the back of the shop. Sometimes someone would stay around a little longer and a casual conversation would become more serious. What started as "have been thinking about this" could gradually become "should actually do this" usually followed by the instinctive question of who could help make it happen. If someone believed in the idea and could contribute, the response was often simply: if I can help, I will.
Because I was studying finance, I became a natural sounding board for some of the practical questions that appeared once an idea started becoming a business. How do you register a company? What needs to be recorded from the beginning? When does an informal collaboration require something more formal? What changes when the first meaningful client or opportunity arrives?
Years later, as some of those ventures developed teams, I recognised a pattern that I would encounter again in much larger organisations. Authority had remained with the founder. Usually this was not because the founder refused to delegate, nor because the people around them lacked ability. It remained there because the standard that had created the business was still closely associated with one person's judgement, and nobody wanted to be responsible for weakening it.
That is where a temporary strength can become a structural constraint.
2. When Possibility Meets Authority
Exploration is not the problem. For many creative businesses it is part of the value proposition. A collaboration can expand the audience, a new format can reveal a stronger business model and an adjacent market can become a source of growth.
The strain begins when possibility expands faster than the organisation's ability to decide. Every new track carries less visible questions about commercial terms, capacity, quality, sequencing and ownership of the decision itself. When those questions remain implicit, small decisions begin to travel upwards because escalation feels safer than interpretation.
The founder gradually becomes the default route through which uncertainty is resolved. The team can remain talented and the work can remain strong, yet execution slows because people are waiting not for an answer they are incapable of reaching, but for permission to act on the answer they already have.
What once looked like taste begins to behave like a queue. The management question is therefore not whether the organisation needs more hierarchy. It is whether authority has been designed well enough for exploration to continue without turning every consequential decision into a founder decision.
3. The Founder Becomes the Operating System
Concentrated authority is often rational in the early stages of a business. Creative coherence depends on judgement, and judgement may initially reside with very few people. The founder sees the client, the product, the commercial consequences and the reputation of the business at the same time, which can make centralised decision-making both fast and effective.
The problem appears when the organisation grows but the decision architecture does not. Who Has the D? How Clear Decision Roles Enhance Organizational Performance, published by Harvard Business Review, examines how ambiguity over decision roles causes decisions to stall even in capable organisations. Its RAPID framework distinguishes who recommends, agrees, performs, provides input and ultimately decides, but the broader point is more important: decision-making deteriorates when authority has to be renegotiated every time an important issue appears.
For founder-led businesses, this is particularly relevant because authority can easily become confused with cultural integrity. If the founder built the standard, distributing decisions may feel as though the standard itself is being diluted.
That is the wrong equivalence. The objective is not to remove the founder from decisions where their judgement genuinely creates value. It is to distinguish those decisions from the much larger number that continue to reach the founder simply because nobody has defined where somebody else's mandate begins.
Boardroom Reframe
The usual view: Slow execution is treated as a capacity problem, so the organisation adds people, time or project management.
The management view: The constraint may be decision rights rather than capacity. When financial, reputational and people decisions have no explicit thresholds, capable employees escalate choices they could otherwise make themselves.
The boardroom question: Which decisions can be made autonomously, which require escalation, and what threshold separates the two?
More capacity cannot compensate for unclear authority.
4. When Decision Rights Stay Implicit
Once authority has become the default route for decisions, hesitation becomes structural. People are told to take ownership but remain uncertain about what they are actually authorised to decide.
Decision Rights for Organizational Acceleration, published by MIT CISR, describes clear decision rights as defining who has authority and accountability for key decisions, supported by guardrails around areas such as purpose, data, policies and resource allocation. The principle is straightforward: autonomy works better when people understand the boundaries within which they can exercise it.
Delegation without boundaries therefore does not create empowerment. It creates uncertainty. A team member who does not know whether a decision with a meaningful margin impact is genuinely theirs to make will usually do the rational thing and escalate. If the same uncertainty applies to client commitments, hiring, investments and brand decisions, the organisation can add people without adding much decision-making capacity.
The deeper lesson is one I have returned to repeatedly in my own work: strategy is not only what the founder wants; it is what the organisation can decide and deliver repeatedly.
5. What Designed Authority Looks Like
Governance is often resisted in creative businesses because the word evokes committees, policies and corporate theatre. At its most useful, governance is much simpler: it makes authority explicit enough that people can act without repeatedly negotiating permission.
For a growing founder-led business, three categories provide a practical starting point.
The first is financial authority. Up to what amount, margin impact or contractual commitment can someone decide independently?
The second is brand and reputational authority. Which choices genuinely affect what the business stands for, how it is represented or the standard customers recognise, and should therefore remain close to the founder or creative leadership?
The third is people and organisational authority. Which hires, promotions or structural changes can be decided within a team, and which require broader agreement because they change the organisation itself?
These thresholds are not intended to produce a rulebook for every eventuality. Their purpose is to create boundaries within which judgement can operate confidently. Below an agreed threshold, people decide. Above it, they escalate, and they understand why. That is the moment governance stops being ceremony and becomes infrastructure.
At MUNDUS CRAS, this forms part of the broader management question of how a business should evolve as complexity increases. The objective is not to push authority away from the founder indiscriminately, but to identify where founder judgement remains strategically valuable and where continued dependence on that judgement has become an avoidable constraint.
Decentralisation is not the objective. Designed authority is.
Conclusion
Momentum becomes pressure when a business grows faster than its ability to decide. Authority will always take shape, particularly where taste, identity and judgement form part of the product itself. The strategic question is whether that authority remains concentrated by default or becomes a system that protects the standard while allowing other people to act.
This is why adding capacity does not automatically create speed. A larger team that remains uncertain about its mandate can still create more routes back to the same founder.
The stronger organisation is not the one in which the founder has become less important. It is the one in which the founder's importance has become more precise.
When a business can state clearly what must remain close to the creative centre, what can be decided elsewhere and what threshold separates the two, founder judgement begins to become organisational capability rather than organisational bottleneck.
Summary Takeaway
If you remember one thing from this essay, let it be this : growth slows when authority stays implicit. Designed authority protects the founder’s standard by making clear which decisions require that judgement and which no longer need to wait for it.