When growth slows down, many companies first look at strategy, marketing, sales or systems. Sometimes the reason is there.
But surprisingly often the problem is more ordinary: the organization cannot get things moving fast enough.
A proposal goes out two days too late. Follow-up after a customer meeting waits. A decision needs three extra rounds. A project start is delayed because ownership is unclear. An important issue stays on the table simply because no one knows who is allowed to decide.
In that situation, growth does not stop because the company lacks direction. It stops because direction does not turn quickly enough into decisions, responsibilities and working day-to-day execution.
I have seen this both as an entrepreneur and in larger organizations. Growth usually does not first stall because there is no strategy at all. It stalls because the organization cannot turn strategy into choices, priorities and action fast enough.
Slowness is usually waiting
When people talk about organizational slowness, they often think about heavy administration, too many meetings or old systems. Those can be part of the problem, but in practice I think slowness is mostly waiting.
Sales waits for approval. Delivery waits for clarification. Marketing waits for a decision. Leadership waits for better visibility before committing to a direction. The customer waits for an answer, even though everyone inside the organization feels busy.
That is what makes slowness difficult to see. No one necessarily sees themselves as the problem. Everyone has a reasonable reason to wait a little longer. Still, the whole system starts moving too slowly.
Typical signs include:
- the same decisions keep returning for another discussion
- a proposal or project depends too much on individual people
- handoffs between sales, delivery and account management require constant separate clarification
- leadership gets the reports, but does not see early enough where work is actually stuck
- people are overloaded, even though the customer does not experience the service as fast or consistent
In this kind of situation, the problem is usually not that people are failing to work hard enough. The problem is that work is not flowing.
The organization looks busy, but still moves slowly.
Customers do not pay for internal waiting
To me, organizational slowness is first and foremost a commercial problem.
The customer does not see whether an issue got stuck because ownership was missing, information was scattered, a decision required approval from the wrong person or internal prioritization was unclear. The customer only experiences that the answer was slow, the proposal dragged on, the start was clumsy or the next step was unclear.
This also shows up quickly in profitability.
The proposal stage gets longer. Winning the deal takes more reminders, more explaining and sometimes a bigger discount. Delivery starts with weaker input. Internal time is spent searching for information, confirming responsibilities and patching handovers that could have been made clear in advance.
So slowness does not only eat speed. It eats quality, predictability and margin.
That is why I see decision-making speed as a leadership team issue. It is not only about efficiency. It is about how well the company can keep its customer promise intact when there is a lot of work, situations keep changing and pressure increases.
Speed in decision-making does not mean making decisions lightly or without judgement. It means the organization knows which decisions require broader discussion and which ones need to be made close to the work.
A slow organization is not necessarily thoughtful. It may simply be unclear.
Performance does not recover by adding more reporting
I have been in situations where organizational performance had to be improved under pressure. The team was overloaded, quality varied and customers were visibly dissatisfied.
In that kind of situation, the tempting answer is to add reporting. More visibility, more tracking, more situational awareness.
Those may be needed, but they do not solve the problem on their own.
Performance improves less by knowing more afterwards and more by helping work move forward better now.
In practice, that means clarifying goals, making responsibilities clearer, tightening the rhythm of decision-making and removing the places where work gets stuck week after week.
I saw the same thing from another angle when developing sales at Eeco. When we built sales models, CRM practices and automations, the goal was not just to document existing work. The goal was to remove unnecessary waiting: make next steps visible, clarify ownership and free salespeople's time for the customer conversations that mattered.
With the model we built, we were able to generate roughly one million euros in annual ecommerce platform sales with two salespeople.
To me, that was not only a sign of sales efficiency. It showed that good commercial work had been made visible enough to be led and replicated.
In both growth and turnaround situations, the lesson has been the same: slowness rarely disappears by hoping. It starts to disappear when ownership, decision criteria and the leadership rhythm are made visible enough.
Slowness often comes from unclear decision rights
Many companies talk a lot about collaboration, but too little about who is allowed to decide what without another round.
This matters more than it may sound.
If every slightly unusual situation requires a new meeting, an approval chain or an informal check, the organization learns to hesitate. People do not make bad decisions, but they also do not make good decisions fast enough.
I do not think good leadership means that everything is escalated to leadership. Good leadership means the organization knows which issues need to be escalated and which ones should be solved close to the work.
In practice, that requires at least three things:
- decisions have clear owners
- progression criteria are visible enough
- the right few things are reviewed early enough every week
When these are missing, the organization looks busy but still moves slowly.
This is especially dangerous during growth. Growth creates more exceptions, interfaces and moments of choice. If decision rights are unclear, every new customer, service, channel or hire adds friction instead of speed.
Then the strategy may be right, but the organization's ability to execute it is too slow.
Four questions that reveal commercial slowness
When I assess whether an organization is slowing down its own growth, I usually look at least at these areas.
1. Where does work repeatedly wait?
Not in theory, but in practice. Where do sales, delivery, marketing or account management have to wait for the next move week after week?
If waiting repeats in the same place, it is probably not a one-off exception. It is a gap in the operating model.
2. Who owns the next step?
If this is unclear, a pipeline, project or change initiative can look like it is moving forward on paper while standing still in practice.
Ownership does not mean one person does everything. It means someone is responsible for making sure the next step happens.
3. Which decisions repeat without shared criteria?
If the same issue is discussed again and again, the problem is usually not the people. The problem is that the decision does not have a clear enough rule, owner or progression criterion.
This is especially true in pricing, proposals, customer promises, prioritization and project starts. If every situation is solved from scratch, the organization spends its decision-making capacity in the wrong place.
4. What does leadership see early enough?
If problems show up only in the monthly report, they are often already expensive.
The organization needs a rhythm tight enough to see where work is slowing down before the customer, margin or team starts paying for it. This is not micromanagement. It means leadership follows the right things early enough.
I find these questions useful because they move the conversation from attitude to structure. Slowness is usually not a personality issue. It is an operating model issue.
Where should acceleration begin?
Making an organization faster does not mean answering everything immediately or making every decision on the spot. Often it is much simpler: remove recurring waiting from the places where it causes the most commercial damage.
I would start with three things.
First, identify where work waits. Not generally, but concretely: where proposals are delayed, where customer situations stay open, where projects fail to start and where people have to ask the same questions again.
Second, clarify decision rights. Who can decide on pricing, exceptions, prioritization, customer promises or the next step? Which decisions need to go to leadership, and which ones must be solved closer to the customer?
Third, bring these topics into the weekly leadership rhythm. Slowness does not disappear because it is discussed once. It decreases only when the organization repeatedly looks at where work stops, why it stops and what needs to change so the same point does not slow things down again.
The goal is not to make the organization restless or reactive. The goal is to make it clear enough that the right things can move without unnecessary friction.
Closing
Growth usually does not first stop because the company has no direction at all. More often, it stops because direction does not turn quickly enough into decisions, responsibilities and working day-to-day execution.
That is why I would not start by asking whether the company needs more meetings, more reports or one more tool.
I would ask: where is work waiting unnecessarily, who is allowed to decide and what does leadership review every week?
When those things are in place, the organization often starts to look calmer from the outside and faster from the inside.
Good performance does not look like busyness. It looks like the right things moving without unnecessary friction.