The Growth Problem Most Marketing Teams Cannot Solve Alone

A company can have an excellent acquisition strategy, a compelling product, and a talented marketing team, yet still fail to grow. The surprising reason is that growth is often treated as a department problem when it is actually an organisational design problem.

If a customer sees a brilliant advertisement but encounters a confusing onboarding process, the company has not really acquired a customer. It has acquired a temporary visitor. If a product team is rewarded for launching features while customer support is measured on response time, everyone can perform well while the business quietly loses retention.

This reveals a deeper question: What kind of organisation is capable of managing growth as a continuous system rather than as a sequence of isolated tasks?

The answer is not a universally correct organisational model. It is an organisation designed around the movement of value through the customer journey. In other words, the best structure for growth is not the one with the most modern labels, the fewest managers, or the most autonomous teams. It is the one that makes the important connections visible, gives people authority close to the problem, and creates fast feedback between customer behaviour and organisational action.

Growth is a flow, not a funnel

Growth marketing is often described through five activities: acquisition, onboarding, engagement, retention, and monetisation. These categories are useful, but they can also create a dangerous illusion. They make growth look like a funnel in which work proceeds neatly from one stage to the next.

Real customer journeys are less like funnels and more like ecosystems. A person may discover a product through a recommendation, abandon onboarding, return six months later, invite a colleague, upgrade after a support interaction, and then become an acquisition channel for someone else. The stages overlap. Each one changes the probability of success in the others.

A useful model is to think of growth as a chain of promises:

• Acquisition promises relevance: This product may be for someone like you.
• Onboarding promises ease: You can reach value without unnecessary effort.
• Engagement promises usefulness: Returning will improve your situation.
• Retention promises continuity: The product will remain valuable over time.
• Monetisation promises fairness: Paying more will produce proportionate value.

A failure at any point weakens the whole chain. The marketing team may increase acquisition, but if onboarding does not deliver the promised value, the extra traffic simply increases the number of disappointed users. A pricing experiment may improve short term revenue while damaging trust and future retention. A retention programme may send more reminders when the real problem is that the product has stopped solving an important problem.

The organisation therefore needs to manage flows of value, not merely activities. This is where organisational design becomes inseparable from growth strategy.

Growth is not the sum of acquisition, onboarding, engagement, retention, and monetisation. It is the quality of the connections between them.

The hidden cost of dividing the customer into departments

Traditional organisations divide work by expertise. Marketing acquires attention, sales converts demand, product builds the experience, customer success protects relationships, and finance manages monetisation. This arrangement is understandable. Specialisation improves efficiency, at least within each function.

The problem appears at the boundaries. Customers do not experience departments. They experience a single company. They do not say, “The acquisition team was persuasive, but the onboarding function was poorly integrated.” They say, “This product made a promise it did not keep.”

Suppose a software company runs a successful campaign promising that a new user can create a report in five minutes. The campaign team is rewarded for qualified traffic. The product team is focused on a major redesign. Compliance has added three verification steps. Support is understaffed because its budget is tied to ticket volume rather than customer activation.

Every unit may be behaving rationally according to its local goal. The system is irrational. The customer has been passed from one optimised function to another, while no one owns the entire promise.

This is the central weakness of functional optimisation: local efficiency can produce global friction. It is the organisational equivalent of improving every section of a road while leaving a bridge unfinished.

The fashionable response is often to adopt a new model: squads, circles, networks, holacracy, agile teams, marketplaces, or some other structure. These models can be useful, but a label does not solve the underlying problem. An organisation can replace departments with squads and still reproduce the same silos if teams own outputs rather than outcomes.

The critical design question is not, “Which model should we copy?” It is, “Where does the customer value flow break, and who has the authority to repair it?”

The organisation as a learning system

In a volatile environment, an organisation cannot be designed once and then preserved indefinitely. It must be able to learn about its own design.

This does not mean changing the structure every few months. Constant reorganisation is often a form of institutional avoidance. It creates the appearance of movement while making accountability and learning more difficult. A learning organisation is not one that changes everything frequently. It is one that can run disciplined experiments on its structures, practices, and policies, then retain what works.

Consider two companies with similar growth targets.

Company A assigns acquisition to marketing, activation to product, retention to customer success, and monetisation to sales. Each function reports its own metrics. When retention falls, leaders schedule a meeting between departments. The meeting produces a list of possible causes, but no single team can change the entire journey.

Company B creates a customer journey team responsible for a defined segment, such as new small business customers during their first ninety days. The team includes people from marketing, product, data, support, and commercial operations. It has a shared metric, such as the percentage of customers who reach a meaningful outcome and remain active after ninety days. It can test messaging, onboarding, product prompts, support interventions, and pricing offers within clear boundaries.

Company B has not eliminated expertise. It has changed the unit of coordination. The team is organised around a customer problem rather than an internal discipline.

This suggests a practical framework with three layers:

1. The value stream

What sequence of customer outcomes creates sustainable revenue? This is broader than a funnel. It includes the actual progress a customer must make, from first recognition of a problem to repeated value and advocacy.

2. The enabling platform

What shared capabilities allow multiple teams to move quickly? These may include data infrastructure, brand standards, legal guidance, research, engineering platforms, pricing tools, and talent development.

3. The governance boundary

Which decisions belong to the customer team, and which require wider coordination? Autonomy without boundaries creates inconsistency. Central control without autonomy creates delay. Good design makes the boundary explicit.

The result is neither a rigid hierarchy nor an unstructured network. It is a nested organisation: small teams own coherent outcomes, while larger structures provide standards, resources, and capabilities that individual teams should not duplicate.

The missing metric is often a connection metric

Most organisations track stage metrics. They measure impressions, leads, activation, daily use, churn, and revenue. These numbers matter, but they do not always reveal where the system is failing.

The most revealing measures are often the connections between stages. For example:

• The percentage of acquired users who reach the first meaningful outcome.
• The time between sign up and successful use.
• The percentage of active users who understand the next valuable action.
• The relationship between support resolution and future retention.
• The proportion of upgrades that remain profitable after accounting for service costs.

These are connection metrics. They show whether one part of the organisation is successfully handing value to another part of the customer journey.

Imagine that a company increases its advertising budget and sees a twenty percent rise in sign ups. That looks like growth. But if the activation rate falls from forty percent to twenty five percent, the organisation has not created growth. It has created a larger queue at the entrance to a broken process.

A simple diagnostic can help. For each transition in the journey, ask four questions:

1. What promise is being made?
2. What evidence shows that the customer received value?
3. Which team can change the experience if the promise fails?
4. How quickly does that team receive reliable feedback?

The fourth question is particularly important. An organisation may know that retention is poor, but if the evidence arrives three months after the relevant experience, learning is slow. The organisation needs shorter feedback loops, not merely more dashboards.

This is why organisational architecture and growth analytics should be designed together. A metric without decision rights is decoration. A team without timely evidence is guessing. A growth system requires both.

Why autonomy works only when the work is coherent

Autonomy is frequently presented as a cure for bureaucracy. Give teams freedom, remove approvals, and innovation will follow. Sometimes it does. But autonomy can also create a collection of small businesses that compete for attention, duplicate infrastructure, and optimise contradictory outcomes.

The answer is not less autonomy. It is coherent autonomy.

A team should be autonomous when three conditions are met:

• It owns a recognisable customer outcome.
• It has enough capability to influence that outcome.
• Its decisions do not create unacceptable damage for other parts of the system.

A team responsible for onboarding cannot be genuinely autonomous if it cannot change the registration flow, the first use experience, or the messages users receive after sign up. It has responsibility without power. Conversely, a team that can change any part of the product, pricing, and communications without shared standards may move quickly while creating confusion and risk.

Coherent autonomy resembles a well designed city. Neighbourhoods can develop their own character, but they still depend on shared roads, utilities, building codes, and emergency services. The city is not controlled from one room, yet it is not a random collection of private decisions.

In a growth organisation, shared standards should protect the things that must be consistent: customer trust, data definitions, brand promises, security, legal obligations, and technical interoperability. Teams should have freedom over the things that benefit from local knowledge: experiments, sequencing, messaging variations, workflow design, and the precise tactics used to reach an outcome.

This division is more useful than the simplistic contrast between centralisation and decentralisation. The real question is: What must be common, and what must be adaptable?

A practical redesign exercise

Leaders do not need to reorganise the entire company to begin. They can start with one important growth problem and use it as a design experiment.

Choose a customer segment where performance is disappointing. Map the journey from first contact through repeat value. Do not map internal departments first. Map what the customer must believe, do, and experience at each step.

Then identify the friction points. A friction point might be a confusing message, a missing product capability, a delayed handoff, an unclear price, or a policy that forces customers to repeat information. For each point, record the team that currently owns it, the team that can actually change it, and the metric used to judge success.

The gaps will usually fall into one of four categories:

• Ownership gap: Everyone influences the problem, but no one owns the outcome.
• Capability gap: A team owns the outcome but lacks the authority or skills to improve it.
• Feedback gap: The organisation cannot see the problem quickly enough.
• Incentive gap: Teams are rewarded for actions that damage the wider journey.

Each gap requires a different intervention. Ownership gaps call for a cross functional outcome team. Capability gaps require authority, tools, or staffing. Feedback gaps require better instrumentation and research. Incentive gaps require measures that reward durable customer value rather than isolated activity.

Run the experiment for a defined period. Compare not only business results, but also the speed of learning, the number of dependencies, and the time required to make decisions. If the new arrangement improves the outcome and reduces coordination costs, extend it. If not, change the design rather than defending it because it resembles a fashionable model.

The goal is not to find a perfect structure. It is to create an organisation that can repeatedly discover better structures.

Key Takeaways

• Design around customer outcomes, not internal specialities. Organise at least some teams around a coherent journey, such as reaching first value or remaining successful during the first ninety days.
• Measure the handoffs. Track transitions between acquisition, onboarding, engagement, retention, and monetisation. These connection metrics often reveal more than isolated stage metrics.
• Match responsibility with authority. Never assign a team an outcome it cannot materially influence.
• Use coherent autonomy. Give teams freedom over local experiments while protecting shared standards for trust, data, security, and interoperability.
• Treat organisation design as an experiment. Test structures and policies against observable outcomes, then adapt based on evidence rather than loyalty to a model.

The company that can grow is the company that can learn

Growth marketing is usually understood as the search for better levers. Which audience should we acquire? Which message improves activation? Which feature increases retention? Which price increases revenue?

But the more difficult question comes before all of these: Can the organisation learn quickly enough from the answers?

A company may possess sophisticated analytics and still learn slowly because insight is trapped between departments. It may have autonomous teams and still move poorly because those teams lack a shared definition of value. It may pursue every stage of the customer journey and still fail because the handoffs between stages are treated as nobody's responsibility.

The mature view of growth is therefore organisational. Sustainable growth is not simply more traffic entering a funnel. It is the repeated conversion of customer insight into coordinated action, and coordinated action into durable customer value.

The strongest organisation is not the one with the most elegant chart. It is the one that can notice a broken promise, place the right people close to it, give them enough authority to repair it, and learn from the result before the market moves again.

That is the real advantage of organisational design: not control over the future, but the capacity to keep discovering what the future requires.