The Seven Patterns I See Across Every Community Project
If you work in community settings long enough—across governments, NGOs, regional towns, remote communities, urban hubs, volunteer groups—you start to notice something.
Despite the diversity of contexts, cultures, histories, and challenges, there are patterns that show up almost everywhere.
They’re not “problems.”
They’re not failures.
They’re simply human and systemic rhythms.
Understanding these patterns changes everything.
They help leaders diagnose what’s really happening.
They help teams anticipate barriers before they break momentum.
They help communities feel seen.
And they help projects become more humane, grounded and effective.
Below are the seven patterns I see in almost every community project I’ve worked on over the past 18 years.
Pattern 1: The Relational Gap
Every project starts with the same absence:
People don’t know each other as well as they think they do.
Organisations assume relationships exist because someone sent an email or attended a meeting. But relationships aren’t logistics—they’re social capital.
Signs of the relational gap:
Low trust, high caution
Politeness masking tension
Stakeholders unclear on each other’s motivations
Historical layers no one has named
Until the relational work is done, the technical work can’t land.
Pattern 2: Overwhelm Before Clarity
Communities enter projects with a backlog of unmet needs, unspoken frustrations and layers of fatigue.
This often shows up as:
“We’ve seen this all before.”
“Nothing ever changes.”
“Why should we care?”
Overwhelm isn’t resistance; it’s exhaustion.
Clarity dissolves overwhelm. But you can’t start with clarity—you have to earn it.
Pattern 3: The Story Beneath the Brief
Every project brief leaves 80% of the real story unsaid.
The brief tells you the goal.
The story tells you:
why the goal matters
what’s been tried before
who has been hurt
who has been excluded
who holds influence
where the emotional energy sits
The story is the system.
If you don’t understand the story, you can’t understand the system you’re designing for.
Pattern 4: Competing Realities
Different groups in the same project often hold completely different truths, shaped by:
lived experience
history
culture
power
trauma
aspiration
Each reality is valid, even when they contradict.
The most dangerous moment in a project is when teams collapse competing realities into a single, simplified narrative. That’s when people stop feeling heard.
Soft leadership doesn’t resolve competing realities; it holds them, then builds something that can contain all of them.
Pattern 5: The Momentum Drop
This always happens.
Usually at the moment where excitement transitions into actual delivery.
The momentum drop looks like:
energy dips
decision fatigue
conflict surfaces
invisible labour becomes visible
people pull back
Instead of treating this as failure, I teach teams to anticipate it.
It’s not a cliff; it’s a contour.
If you plan for the valley, you won’t panic when you walk into it.
Pattern 6: The Hidden Work
The work that actually holds community projects together is almost always unacknowledged:
informal meetings
cultural protocols
emotional labour
unpaid time
trust-building
bridging conversations
healing historical tensions
This is the work that determines impact, yet it is rarely funded, measured or named.
Naming it makes it visible.
Making it visible makes it valued.
Valuing it makes it sustainable.
Pattern 7: The Return to Purpose
Projects lose their way.
Not because people don’t care—but because complexity pulls focus.
Again and again, the projects that succeed have leaders who continually return to the grounding question:
“What is the purpose beneath the project?”
Purpose organises systems.
It anchors relationships.
It keeps people moving even when the path is unclear.
When a project loses purpose, it loses orientation.
When it regains purpose, everything re-aligns.
Why These Patterns Matter
The patterns aren’t obstacles—they’re navigational markers.
Recognising them shifts leaders out of frustration and into understanding.
When you see the patterns, you:
reduce reactivity
design with the system, not against it
create more humane processes
build trust faster
increase the likelihood of long-term impact
Patterns are the quiet architecture of change.
I’ve turned these insights into a short PDF guide—The Seven Patterns That Shape Every Community Project.
Download it below and share it with your team. It’s a practical tool for anyone working in community development, social research, or systems change.

