Recognizing Systems Failure

In the previous lesson, we looked at identity and purpose, the human side of resilience. In this lesson, we look at the fourth pressure in the CRISIS framework: Systems Failure. This is the pressure that explains why so many communities do everything right and still struggle to get ahead.

Communities depend on systems for almost everything: health care, housing, water, power, transport, education, finance, and the programs and approvals that decide what can be built. When those systems work, we barely notice them. When they don’t, the effects are felt in daily life, and they often fall hardest on places that are small, remote or historically overlooked.

By the end of this lesson, you will be able to recognize how systems fail, understand why it is rarely anyone’s fault in the ordinary sense, and see where a community can build its own alternatives.

What we mean by a system

A system is a set of connected parts that work together to deliver something. A health system includes clinics, staff, funding, rules and transport. A housing system includes land, builders, lenders, codes, permits and programs. A food system includes farms, processors, shippers, stores and the people who buy and eat. A funding system includes the programs, applications, deadlines and reporting rules that decide who gets money and for what.

Most systems were designed for a purpose and for a certain kind of place. The trouble starts when they meet a place they weren’t designed for.

What it means for a system to fail

Systems failure doesn’t always mean a dramatic collapse. More often, it is a slow, steady gap between what a system is supposed to deliver and what a community actually receives.

A clinic that is too far away, or closed half the week. A housing program that can’t be used because there is no lender or builder nearby. A funding stream that needs three years of audited accounts from an organization that has never been funded. An approval process that takes longer than the project can wait. A rule written for a city that doesn’t fit a village.

In each case, the system is working as designed. It just wasn’t designed for you.

Why systems fail small and remote places

Several patterns repeat around the world.

Built for scale. Many systems depend on volume to be efficient. Small populations and long distances make delivery expensive, so services are thin or absent.

Designed elsewhere. Rules, programs and standards are written by people who may never have visited the places they affect. Local conditions, knowledge and priorities get left out.

Short cycles. Funding often arrives in one-year or three-year cycles. Real change, such as building an enterprise, training a workforce or restoring land, takes longer. Organizations spend much of their energy on applications and reports rather than on the work.

Silos. Departments and agencies each manage their own piece. A project that touches housing, energy, training and land use must satisfy four different sets of rules that don’t talk to each other.

Complexity as a barrier. The more complicated the process, the more it favours organizations with staff and expertise to navigate it. Small communities pay twice: once for the problem, and again for the paperwork to solve it.

Ownership and control elsewhere. When the land, the utility, the major employer or the decision-maker sits somewhere else, the community has limited power to change things.

History. In many places, today’s systems carry the weight of past decisions that were never fair to begin with.

Systems failure and Indigenous communities

In Canada, as in many countries, Indigenous communities have experienced systems failure in its most concentrated form. Laws, funding arrangements and programs imposed over generations limited Indigenous peoples’ ability to govern themselves, own land and build wealth. Funding for essential services has often been uneven and tied to short-term programs. Many communities have faced barriers to financing, because land held collectively is hard to use as security for a loan. Basic infrastructure, such as clean water, reliable housing and broadband, has lagged far behind the rest of the country in many places.

Indigenous Nations have distinct histories, laws, rights and governance arrangements. Enterprise development needs to follow the leadership and decision processes of the Nation concerned. On the Sunshine Coast, shíshálh Nation regained self-government in 1986.

Rural, remote and island communities around the world, and many neighbourhoods in cities, face versions of the same problem. The details differ, but the pattern is familiar.

Signs of systems failure in your place

Look for these signals.

Services that require long travel, or aren’t available at all.

Programs that exist on paper but are hard to access in practice.

Projects that stall because of approvals, funding gaps or missing skills.

Dependence on one-off grants to keep essential work going.

Decisions about local land, water or resources made by people who don’t live there.

Residents who describe feeling unheard, or tired of consultation that leads nowhere.

Good ideas that never get past the proposal stage.

Money flowing in as grants and flowing straight back out as consultants’ fees and imported goods.

How systems failure creates dependence

When systems don’t serve a community, people adapt. They wait, travel, make do or leave. They also come to rely on whatever help is on offer, even if it is slow, partial or on someone else’s terms.

Over time, dependence builds in three ways.

Financial dependence. The community relies on grants and transfers it doesn’t control, and can’t plan beyond the next funding round.

Capacity dependence. Because the community lacks the staff, tools or funding to run services itself, it depends on outside providers. Skills stay elsewhere, and the cycle repeats.

Decision dependence. Important choices are made through processes the community doesn’t control.

This is the same pattern we saw with climate, waste and purpose. A pressure meets a dependence, and the community pays the price. The difference is that here the dependence is built into the structure of the systems themselves.

You cannot fix a system you do not own

There’s an important lesson in this. Communities can and should push for better systems, through advocacy, policy change and partnership. But waiting for outside systems to improve can take generations. The more reliable path is to build local capacity so the community owns more of what it relies on.

That means owning enterprises that generate revenue, so there is money to invest in local priorities. It means developing local institutions, such as training programs, cooperatives, development corporations and community funds. It means building skills that can be used again and again. And it means forming partnerships where the community holds real authority, not only a consulting role.

This does not mean going it alone. Communities will always need partners, funders and governments. The goal is to move from being a recipient to being a partner with a seat at the table, and ideally with resources of your own.

What building your own looks like

The Sunshine Coast offers a few illustrations.

Connecting services. A municipality can link household organics collection with a suitable local processor and customers for the resulting compost. Clear responsibilities and a workable service agreement turn the idea into a reliable system.

Changing how assets are managed. Gibsons includes its aquifer and other natural assets in asset management. That makes ecosystem services part of ordinary infrastructure planning.

Self-government. shíshálh Nation regained self-government in 1986. Its own account of self-government emphasises responsibility for decisions concerning its people, lands and future.

Building with your own people. At Selma Park, the Nation took on a housing project that the wider housing system had not delivered, using Nation trades and reused buildings.

Local revenue for local priorities. A community forest can pay dividends into a fund that supports local priorities.

None of these removed all the barriers. Each took years, patience and partners. But each shows that a community can build part of the system it needs.

A note on working with systems

It’s tempting to see governments, funders and institutions as the problem. In practice, many people inside them want to help and are constrained by rules too. The most effective approach is usually to work with systems while building alongside them.

Learn how the system works and where it has flexibility. Bring forward projects that meet the funder’s goals as well as your own. Build relationships with the people who administer programs. Show results, and share your learning so others can follow. A well-made business case, which is what you will create in this course, is one of the best tools for this.

Honest limits

Local enterprises cannot replace public services such as health care, schools and basic infrastructure, and communities should not be asked to carry what governments are responsible for. Building your own capacity is meant to reduce vulnerability and add choice, not to excuse systems from doing their job.