One of the more curious things about organizational life is the amount of time spent discussing structures that audiences will never see.
Organizations devote considerable energy to questions of governance, reporting relationships, departmental responsibilities, approval processes, committee structures, and decision-making frameworks. Entire meetings can be spent clarifying who is responsible for what, where authority resides, and how information should flow from one part of the organization to another. These conversations are often important. Organizations need structure. They need accountability. They need clear roles and responsibilities.
The interesting part is that almost none of this is visible from the outside.
Audiences do not know who reports to whom. They do not know whether marketing and fundraising sit within the same department. They do not know whether programming decisions originate with staff, committees, boards, or some combination of all three. They do not know who approved the website, who wrote the brochure, or which team is responsible for the ticketing platform. More importantly, they generally have no reason to care.
This is not criticism.
It is simply the reality of how people experience organizations. Audiences encounter an organization as a single entity. They experience one website, one brand, one purchasing process, one series of communications, and one overall relationship. The internal complexity that produced those experiences remains largely invisible unless something goes wrong.
That last point is worth paying attention to because it explains why internal organizational issues often appear externally as audience problems.
An organization may understand perfectly well why a process is frustrating. Staff know which software systems do not communicate with one another. They know where responsibilities overlap. They know which procedures were temporary solutions that somehow became permanent. They understand the historical reasons behind various compromises. Audiences possess none of that context. They simply experience the result.
If purchasing tickets is difficult, the audience does not know whether the issue originated with technology, staffing, budget constraints, or governance decisions. They know only that purchasing tickets was difficult. If communications arrive inconsistently, they do not know which department was responsible. If information is confusing, they do not know whether the confusion emerged during planning, approval, design, or implementation. The experience feels unified because, from the audience’s perspective, it is unified.
I’ve noticed that organizations sometimes underestimate the significance of this.
Inside the organization, people naturally understand distinctions between departments and functions. Marketing has its responsibilities. Development has its responsibilities. Programming has its responsibilities. Education, membership, operations, and administration each have their own priorities and objectives. Viewed internally, this division of labour makes perfect sense. Viewed externally, it largely disappears.
The audience experiences the cumulative effect rather than the organizational structure.
This becomes particularly apparent in conversations about communication. Many organizations discuss communications in categories. There are marketing communications, fundraising communications, membership communications, educational communications, patron communications, and stakeholder communications. Internally, these distinctions are useful because different teams are responsible for different objectives. Externally, however, audiences rarely separate these experiences into neat organizational categories.
They experience communication as a relationship.
An audience member does not think, “I am now receiving a fundraising communication, distinct from the marketing communication I received last week.” They experience a continuing interaction with a single organization. Every message contributes to their overall impression of that relationship. Every interaction influences their understanding of who the organization is and whether it values their time, attention, and support.
The same dynamic appears in strategic planning.
Organizations frequently divide strategic responsibilities among departments, committees, and working groups. This approach is sensible because different people possess different expertise. Yet a subtle risk emerges when responsibility for the audience’s experience becomes fragmented across multiple organizational units. Everyone owns a piece of the experience. Nobody owns the whole experience.
What results is often not failure but fragmentation.
Each individual department may perform its responsibilities competently. Marketing creates strong campaigns. Programming delivers meaningful experiences. Development maintains donor relationships. Operations manage logistics. Viewed independently, each area appears successful. Yet audiences do not encounter these functions independently. They encounter them simultaneously.
That distinction helps explain why organizations occasionally feel confused when audiences respond differently than expected.
Internally, people see effort.
They see planning.
They see complexity.
They see the challenges being navigated every day.
Audiences see outcomes.
The difference is subtle but important. Organizations evaluate themselves partly through the lens of intention. Audiences evaluate organizations primarily through the lens of experience. Both perspectives are understandable. They are not always aligned.
This is one reason I find myself returning to a deceptively simple question during planning discussions: what does this look like from the audience’s perspective?
The question often changes the conversation.
Internal explanations become less important. Historical justifications become less important. Organizational boundaries become less important. The discussion shifts toward experience. Can people understand what is being offered? Can they find the information they need? Does the relationship feel coherent? Does the organization appear to know who it is and what it values?
These questions have a useful habit of cutting through complexity.
Not because complexity disappears, but because audiences do not have the luxury of understanding it. Organizations may spend years navigating structural challenges, resource constraints, and competing priorities. Audiences encounter only the visible results of those efforts. The organization may know exactly why a compromise was necessary. The audience experiences only the compromise.
There is a mildly amusing aspect to this reality.
Organizations sometimes devote enormous energy to internal distinctions that audiences never notice while overlooking inconsistencies that audiences notice immediately. Staff can spend hours debating ownership of a responsibility that feels critically important inside the organization. Meanwhile, the audience remains blissfully unaware of the debate and simply wonders why the information they need is difficult to find.
Human beings are often like this. We become deeply familiar with the complexities of our own systems and occasionally forget that other people encounter only the finished product.
The organizations that seem most effective at maintaining audience relationships understand this instinctively. They do not ignore internal structures. Strong internal structures remain important. Instead, they recognize that organizational convenience and audience experience are not always the same thing. When tensions emerge between the two, they make a deliberate effort to understand how decisions will feel from the outside.
That effort requires empathy as much as strategy.
It asks organizations to step briefly outside their own expertise and experience the organization as a visitor, a donor, a ticket buyer, a participant, or a community member. It requires curiosity about how the organization appears to people who do not attend staff meetings, read internal reports, or understand historical context. In other words, it requires seeing the organization as most people actually see it.
The longer I work with organizations, the more I suspect that this perspective is both rarer and more valuable than people realize.
Internal complexity will always exist. Organizations are complicated because the work they do is complicated. Audiences generally understand that. What they are looking for is not perfection. They are looking for clarity, consistency, and an experience that feels coherent. They want to feel that the organization understands them at least as well as it understands itself.
That is not always an easy standard to meet.
It is, however, a useful one.
After all, audiences do not experience departments, reporting structures, committees, or organizational charts. They experience organizations. The more closely an organization aligns its internal decisions with that reality, the easier it becomes to create experiences that feel intentional rather than accidental.
And from the audience’s perspective, the difference is often immediately obvious.
The Myth of the Capacity Problem
If I had a dollar for every time an organization told me it lacked capacity, I would not be retired, but I might at least be having a different conversation about retirement.
The phrase appears so frequently in organizational life that it has become almost automatic. A project stalls because there is not enough capacity. A strategic priority remains unfinished because there is not enough capacity. A new opportunity cannot be pursued because there is not enough capacity. In many cases, the statement is entirely accurate. There are organizations doing ambitious work with limited staff, limited budgets, and limited time. Pretending otherwise would be unrealistic.
What interests me is not the situations where capacity is obviously the problem. What interests me are the situations where capacity has become the explanation before anyone has examined whether something else might be happening.
Over the years, I have noticed that organizations often use the word capacity to describe several different conditions at once. Sometimes they mean resources. Sometimes they mean time. Sometimes they mean expertise. Sometimes they mean energy. Occasionally they mean all four simultaneously. The result is that capacity becomes a catch-all explanation for organizational frustration, even when the underlying issue may be something entirely different.
One reason this happens is that capacity feels objective. It sounds practical and measurable. There is a certain comfort in believing that an organization would function smoothly if only it had more staff, more funding, or more hours in the day. Those are tangible things. They can be budgeted, planned for, and discussed in grant applications. They are far easier to talk about than questions involving priorities, decision-making, or organizational discipline.
Yet I have worked with organizations that appeared chronically short of capacity despite receiving additional resources. New staff arrived. New funding arrived. New opportunities became available. For a brief period, the pressure eased. Then, almost inevitably, new commitments appeared to occupy the available space. Before long, people were once again describing themselves as overwhelmed.
The first few times I observed this, I assumed it was coincidence. Eventually it began to feel like a pattern.
Organizations often imagine capacity as a container. If the container becomes larger, the problem should disappear. In reality, many organizations behave less like containers and more like gases. They expand to fill the space available to them. New funding creates room for new initiatives. New staff create opportunities for additional projects. New partnerships generate additional responsibilities. Growth creates possibilities, and possibilities have a habit of becoming commitments.
None of this is inherently bad. Growth can be healthy. New opportunities can be valuable. The challenge is that organizations sometimes mistake expansion for progress. They become so focused on what can now be done that they spend less time considering what should be done. The conversation remains centred on capacity while the underlying issue may actually involve prioritization.
This becomes particularly visible during planning discussions. Organizations frequently produce lists of objectives that are individually reasonable and collectively impossible. Audience development sits beside fundraising. Community engagement sits beside accessibility. Revenue growth sits beside advocacy, education, partnerships, digital transformation, and organizational sustainability. Each goal has merit. The difficulty is that every goal also requires attention, and attention remains stubbornly finite regardless of how committed people happen to be.
When an organization attempts to pursue too many priorities simultaneously, the resulting strain often presents itself as a capacity issue. Staff feel overwhelmed. Deadlines slip. Important work remains unfinished. The immediate conclusion is that additional resources are required. Sometimes that conclusion is correct. Other times the organization is experiencing the consequences of trying to do twelve important things at once.
The distinction matters because the solutions are very different.
A genuine capacity problem requires additional resources. An organization cannot indefinitely compensate for the absence of people, funding, or expertise through sheer determination. At some point reality intervenes. However, a prioritization problem requires a different response. It requires decisions. More specifically, it requires deciding which worthwhile activities deserve attention now and which worthwhile activities can wait.
That work is often more uncomfortable than pursuing additional resources.
Most people would prefer to discuss what they need rather than what they should stop doing. New funding feels optimistic. Eliminating a project feels restrictive. Hiring additional staff feels constructive. Narrowing priorities feels like sacrifice. Yet the organizations that seem most effective at managing their workload often spend as much time discussing subtraction as they do discussing growth.
I have become increasingly interested in the appearance of capacity.
Some organizations seem remarkably calm despite operating with modest resources. Others appear perpetually stretched despite significant investment. The difference is not always financial. More often, it involves clarity. The calmer organizations tend to know exactly what they are trying to accomplish. They make difficult decisions earlier. They postpone worthwhile ideas. They decline opportunities that do not align with current priorities. From the outside, this can create the impression that they possess greater capacity than their peers.
What they often possess is greater focus.
Focus creates a curious optical illusion in organizations. Because energy is concentrated, progress becomes more visible. Because priorities are clear, fewer people are competing for the same resources. Because decisions have been made, less effort is spent debating what should happen next. None of this creates additional hours in the day. It simply allows the available hours to be used more intentionally.
That may be why I have grown cautious whenever capacity becomes the first explanation for organizational challenges. Sometimes it is the right explanation. Sometimes it is merely the most comfortable one. Capacity is easier to discuss than priorities. It is easier to discuss than trade-offs. It is easier to discuss than the possibility that an organization has committed itself to more work than it can reasonably sustain.
The organizations that navigate this tension most effectively seem willing to hold two ideas simultaneously. They recognize that additional resources can be valuable and that discipline remains necessary even when those resources arrive. They understand that growth does not eliminate the need for choices. If anything, growth often increases the importance of making them.
The longer I spend around organizations, the more I suspect that capacity is one of those words that deserves a follow-up question. When someone says there is not enough capacity, the observation may be completely accurate. It may also be the beginning of a much more interesting conversation about priorities, focus, and the decisions that determine where organizational attention ultimately goes.
Those conversations are rarely as simple as applying for another grant or hiring another staff member. They do not produce quick solutions. They do, however, tend to reveal whether the organization is struggling because it lacks resources or because it lacks clarity about how those resources should be used.
The difference is not always obvious at first.
In the long run, it often makes all the difference.
CONCLUSION
If there is a single theme running through these essays, it is that organizational challenges are rarely isolated problems. Complexity, confusion, burnout, inefficiency, and misalignment often appear to be separate issues, but they usually share the same roots. They emerge gradually through hundreds of small decisions, assumptions, compromises, and accumulated habits.
The good news is that the reverse is also true. Clarity rarely arrives through a dramatic restructuring or a perfect strategic plan. More often, it emerges from a series of deliberate choices made consistently over time. Clear objectives create better priorities. Better priorities reduce unnecessary complexity. Reduced complexity makes alignment possible.
None of this work is particularly glamorous. It involves asking difficult questions, making trade-offs, and resisting the temptation to do everything at once. Yet organizations that do this work well often appear remarkably calm. They are not necessarily doing less; they are simply more intentional about what they are doing and why.
If this collection accomplishes anything, I hope it encourages readers to look beneath the symptoms they encounter every day and pay closer attention to the systems creating them. Because clarity, priorities, complexity, and alignment are not separate conversations. They are different stages of the same one.