Growth is generally treated as evidence that an organization is working: more people are being served, revenue is increasing, programs are expanding, new partnerships are forming or a major grant has created new capacity. Those are good problems to have. They are still problems to manage.
An organization can become larger without becoming more capable. In fact, some of the operating weaknesses that matter most at scale are almost invisible when the organization is smaller.
A process that depends on one experienced person works until volume doubles.
A program leader can personally resolve exceptions until exceptions become part of every week.
A spreadsheet can function as a system until five departments need the information.
Senior leadership can coordinate decisions informally until too many decisions begin arriving at the same time.
The organization may still be performing well. Revenue can continue growing. Customers can remain satisfied. Staff can continue finding ways to make things work.
But increasingly, the success depends on effort that does not scale with it.
That is usually when the operating model deserves attention.
Growth changes the work before it changes the organization chart
Organizations tend to recognize growth first through visible measures—revenue, employees, customers, sites, programs. The less visible change is that the nature of the work itself begins to shift.
Consider a program serving five hundred people.
Its manager may reasonably know many of the recurring issues personally. Exceptions can be handled case by case. Reporting can be assembled manually. A few important customer relationships can receive direct attention. Problems between systems can be reconciled when necessary.
At five thousand participants, the same management approach begins producing a different organization.
Exceptions now need rules, reporting needs repeatable data, customer problems need escalation paths, institutional relationships need account ownership, and technology failures affect materially more people.
A decision that once required one conversation now affects finance, programs, technology and service delivery at the same time.
The program did not simply become larger.
It became operationally different.
That distinction is important because adding people to the old model does not necessarily produce the model required for the new scale.
Sometimes it simply gives more people the same ambiguities.
Every organization has an operating model, whether it designed one or not
“Operating model” can sound more elaborate than it needs to.
It is simply the practical answer to a few questions:
Where does important work get done?
Who is responsible for it?
Who makes which decisions?
How do different functions coordinate?
What information does management use?
What capabilities, systems and external resources support the work?
Every organization already has answers to those questions. The issue is whether the answers were chosen deliberately or accumulated over time.
Strategy describes where the organization intends to go. The operating model determines whether ordinary work, decisions, information and accountability can carry it there. Growth is often when the distance between the two becomes visible.
Leadership may have a clear strategic plan.
The organization may know what it wants to expand.
The question is whether the mechanisms underneath it have changed accordingly.
Senior leadership often becomes the first workaround
One of the clearest signs of operating-model strain is that increasingly ordinary decisions begin reaching unusually senior people.
A customer exception comes to the executive director.
A routine vendor issue needs CEO involvement.
Two departments disagree about ownership, so leadership resolves it.
A report cannot be trusted without someone senior reviewing the underlying numbers.
A program manager needs permission for something that occurs every week.
A technical issue becomes an executive issue because no one else can coordinate the people required to resolve it.
Leadership may initially view this as responsiveness.
And sometimes it is.
Executives should remain close enough to the organization to understand what is actually happening.
But there is a difference between remaining informed and becoming the institution's routing layer.
If senior leadership is repeatedly required to connect functions that should already know how to work together, the organization may have an accountability problem rather than a workload problem.
The executive is filling the gap.
That can remain hidden for a surprisingly long time because good leaders are often very effective at doing it.
Eventually their own capacity becomes the constraint.
More meetings are often a symptom, not the solution.
A similar pattern appears in coordination.
Something is being missed, so another meeting is created.
A cross-functional problem arises, so a working group is formed.
Communication is inconsistent, so more people are copied.
Soon the organization has substantially more opportunities to coordinate without necessarily having more clarity.
Meetings are useful when there is something genuinely collaborative to decide.
They are much less efficient when they exist because no one knows where a decision belongs.
If six people attend a weekly meeting largely so that one recurring operational issue does not fall between departments, the problem may not be communication.
It may be ownership.
Who has the authority to decide?
Who needs to be consulted?
Who needs to be informed?
What can be handled without reconvening the group?
What information should already be available before the decision occurs?
A mature operating model reduces the amount of coordination required for ordinary work.
Not because functions become isolated.
Because the organization becomes clearer about when coordination is actually necessary.
Growth exposes dependencies that were previously manageable
At smaller scale, functions can appear more independent than they really are.
Marketing attracts the customer.
Programs provide the service.
Technology operates the platform.
Finance handles the money.
Customer service answers questions.
Development raises funding.
The boundaries look clean on paper.
Operationally, they are not.
A marketing promotion changes purchasing volume, which affects customer service.
A pricing decision changes transaction behavior, which affects finance.
A program rule has to be implemented in technology.
A new grant creates program obligations, reporting requirements, staffing needs and financial restrictions.
An institutional sale affects contracts, invoicing, access, reporting and support.
The larger the organization becomes, the more consequential those dependencies become.
Growth can therefore feel disproportionately complex. The organization has not merely added more units of work; it has increased the number of relationships between the work.
A program that grows 50 percent does not necessarily create only 50 percent more operating complexity.
If growth introduces new customer types, systems, staff, policies, revenue models or compliance obligations, complexity can increase much faster than volume.
The operating model has to absorb those relationships.
Hiring more people may relieve pressure without resolving structure
When capacity becomes strained, hiring is an understandable response.
Sometimes it is exactly right.
There is more work, and the organization needs more people to perform it.
But headcount and operating capacity are not identical.
A new employee entering an unclear function inherits the lack of clarity.
If ownership was ambiguous before the hire, there may now simply be two people negotiating the ambiguity instead of one.
If reporting is fragmented, an analyst may spend more time assembling information than analyzing it.
If technology requires constant workarounds, additional administrative staff may make the workaround more sustainable without making the system better.
If senior leadership is making routine decisions because authority was never delegated, hiring another coordinator may add another layer through which the same decision travels.
This distinction is especially relevant in the current environment.
ASAE's January 2026 staffing research found that association staffing remained broadly stable despite economic uncertainty: just over half of surveyed organizations held staffing steady, while 26 percent increased staff. ASAE characterized the pattern as selective investment in mission-critical capabilities rather than indiscriminate expansion.
That is the discipline: do not stop at whether the organization needs more people. Identify the capability that is missing and the operating arrangement that can provide it best.
Revenue growth can conceal operating deterioration
An organization can tolerate a surprising amount of inefficiency while revenue is growing.
The money arrives.
Demand remains strong.
A successful product subsidizes weak processes around it.
Staff compensate.
Leadership focuses appropriately on opportunity.
The danger is that financial performance can make operating fragility look less urgent than it is.
Suppose a program grows from $2 million to $5 million in annual revenue.
That is significant progress. But suppose that during the same period:
customer-service staffing triples,
refunds and disputes rise,
management reporting remains manual,
the technology stack becomes increasingly fragmented,
executive leadership spends more time on escalations,
and no one can explain confidently which products actually contribute the strongest margin.
The program is financially larger.
It is not necessarily operationally healthier.
Eventually the cost of complexity begins catching up with the revenue that concealed it.
For mission-driven organizations, the distinction matters even more when growth is taking place in a difficult financial environment.
Nonprofit Finance Fund's 2025 survey found that 63 percent of more than 2,200 nonprofit respondents had expanded programs or services during 2024 and 85 percent expected service demand to increase in 2025. At the same time, 36 percent ended 2024 with an operating deficit and 52 percent reported three months or less of cash on hand.
Growth and financial strength are not the same condition.
The operating model has to make the former economically sustainable enough to produce the latter.
The organization should know what must not break
As organizations grow, it becomes increasingly useful to identify the capabilities that are genuinely critical to performance.
Not everything deserves the same degree of management attention.
For one organization, the critical capability may be program delivery.
For another, it may be institutional fundraising.
A professional association may depend heavily on membership data and continuing education.
A healthcare nonprofit may need reliable eligibility and service coordination.
A high-volume education business may depend on transactions, enrollment, accreditation and customer records all working together.
These are the things the organization cannot afford to manage casually. A useful question for leadership is:
What does this organization have to be unusually good at for the strategy to work?
Then:
Does anyone clearly own it?
Is there enough management capacity around it?
Do the systems support it?
Can the organization tell whether it is performing well?
Is knowledge concentrated in one person?
What happens when volume increases?
What happens when that person leaves?
An operating model does not need to perfect every process.
It does need to protect the things on which the institution actually depends.
The organization chart is only part of the answer.
Operating-model conversations often become restructuring conversations.
Should this person report to someone else?
Should two departments be combined?
Do we need a COO?
Should technology sit under finance or operations?
Those questions can matter.
They can also give structure more importance than it deserves.
Changing reporting lines does not automatically clarify decisions.
A new department does not create reliable data.
A COO cannot compensate indefinitely for undefined responsibilities beneath the role.
Two functions can report to the same person and still operate in silos.
The organization chart tells us where people sit.
The operating model has to explain how work moves.
That includes management cadence, decision rights, processes, data, technology, external partners and the practical mechanisms through which functions coordinate.
Sometimes a structural change is necessary.
Sometimes the organization needs very little restructuring and much more clarity.
Data becomes management infrastructure at scale.
In a smaller organization, leadership can know a great deal through proximity.
The executive director knows what programs are busy.
The program manager knows which customers are struggling.
Finance knows where revenue is coming from.
The development team knows which relationships are strong.
As scale increases, proximity becomes a less reliable management system.
Leadership needs information that can travel.
How is the program performing?
Where is demand changing?
What is generating revenue?
Where are costs increasing?
What is happening in customer operations?
Which funding is exposed?
Where are backlogs developing?
What requires intervention?
The organization does not need every available metric.
It needs a reliable management view.
This turns data from retrospective reporting into management infrastructure.
At scale, data helps distribute judgment.
A manager can act without waiting for the CEO to tell them what the CEO has personally noticed.
A function can see its own performance.
Leadership can distinguish an isolated issue from a trend.
And the organization becomes less dependent on informal knowledge moving through particular individuals.
Data maturity is therefore part of operating-model maturity.
Technology should absorb complexity, not merely digitize it
Growth also changes what the organization should expect from its systems.
At smaller scale, technology can simply record the work.
At larger scale, it increasingly needs to reduce the amount of administrative work required to deliver it.
That means automating routine processes where appropriate.
Connecting data.
Supporting customer self-service.
Enforcing well-defined business rules.
Producing reliable management information.
Reducing duplicate entry.
Making exceptions visible.
Allowing growth without requiring administrative effort to rise in direct proportion.
The wrong technology environment does the opposite.
It digitizes the existing complexity while leaving people responsible for stitching everything together manually.
Technology and operating-model design therefore cannot be separated indefinitely.
A system may be technically capable of supporting the organization while still creating an enormous operating burden around it.
External capacity belongs in the operating-model discussion too.
Organizations often think of external partners primarily in procurement terms.
What should we outsource?
Which vendor should we hire?
But there is a broader question.
Which capabilities actually need to sit permanently on payroll, and which need to be reliably available to the institution?
Those are not always the same thing.
Some functions clearly belong internally because they are central to institutional authority, culture or day-to-day leadership.
Some specialist capabilities are needed intermittently.
Some work is standardized enough to purchase efficiently.
And some functions need sustained management and execution but span several disciplines that would be difficult or unnecessary to build as a complete internal department.
The decision should be made around capability, accountability, continuity and economics rather than an assumption that internal is inherently more serious or external inherently more flexible.
The operating model includes both.
The important point is that responsibility remains clear.
Growth should reduce dependence on heroics
Almost every growing organization has people who hold more together than their job description suggests.
They know the workaround.
They remember the history.
They can calm the customer.
They know which spreadsheet contains the right number.
They understand what the executive director really means.
They call the vendor and get the answer.
Those people are valuable.
The organization should not build its operating model around requiring them to remain heroic.
The common failure mode is not a lack of effort. It is that strong people are compensating for an arrangement no one would design from scratch. If routine performance depends on exceptional effort from particular individuals, scale is fragile.
The objective of stronger systems and clearer management is not to remove judgment from work.
It is to reserve good judgment for situations that actually deserve it.
A capable employee should spend less time remembering how to compensate for the organization and more time making the organization better.
Not every period of growth requires a redesign.
There is also a danger in overreacting.
Organizations should not restructure every time revenue increases.
A growing program does not automatically need a new management layer.
A process does not need automation simply because it is manual.
Some complexity is temporary.
Some inefficiency is less expensive than fixing it.
And some organizations can grow considerably within the capacity of their existing model.
The question is whether the pressure is episodic or structural.
If volume settles, does the problem disappear?
Or does every increment of growth make the same weakness more expensive?
Are staff temporarily busy, or has the organization fundamentally changed what it is asking them to manage?
Is one system irritating, or is it constraining the program?
Are executives helping through a transition, or have they permanently become the escalation process?
Operating-model work should be proportionate.
The goal is not organizational perfection.
It is making sure the structure underneath the institution remains appropriate for the institution it has become.
The transition usually happens later than it should
The delay is understandable. Operating-model work rarely feels urgent when growth is going well.
There is always another customer to serve, grant to pursue, partnership to develop or product to launch.
The people who understand the operating weaknesses best are often the same people with the least capacity to redesign them.
So the organization adapts.
One more workaround.
One more spreadsheet.
One more meeting.
One more employee.
One more responsibility added to someone who already understands the system.
Until eventually the organization reaches a point where continued growth requires structural attention that would have been easier several years earlier.
The strongest time to address an operating model is therefore not necessarily when the organization is failing.
It is often when it is succeeding enough that the old model is becoming increasingly expensive to preserve.
Growth has to create capacity, not only consume it
The purpose of scale is not to make an organization busier.
It is to allow more mission, service, revenue or impact to be produced from an institution capable of carrying it.
That requires something important to happen as the organization grows:
its capacity has to grow faster than its dependence on individual effort.
Decisions become clearer.
Information becomes more reliable.
Routine work becomes easier.
Critical capabilities develop stronger ownership.
Systems carry more of the administrative load.
Management attention moves toward the things that genuinely require management.
People spend less time compensating for fragmentation.
None of that happens automatically.
Growth creates the need for a different operating model before it necessarily creates the awareness of one.
The warning signs are often already present:
leadership has become the clearinghouse,
coordination is multiplying,
workarounds are becoming permanent,
data is harder to trust,
technology is shaping program decisions,
customer service is absorbing failures from elsewhere,
new staff are being added into old ambiguity,
and strong people are holding together responsibilities the organization has never formally designed.
None of those signals means growth was a mistake.
They usually mean the opposite.
The organization has become something its original operating model was never built to support.
The next stage is not simply continuing to grow.
It is building the institution capable of carrying what that growth has created.
Sources