Skip to content

case study 04

EMEA inclusion scaling

 
 
expanded a belonging group from one country into an EMEA-wide system
 
constraint: belonging group structurally limited to one country
intervention: two-layer slack architecture + phased chapter rollout model
result: 100+ new emea members + Netherlands chapter launched
 
details anonymised where needed
 
 
 
 

at a glance

context

a global company with internal inclusion and belonging (IRG) groups. one group existed in Ireland but had no structure for EMEA-wide participation.

my role

regional communications lead (EMEA) for the group, working with the chairs.

timeframe

2-3 months for initial rollout and adoption.

the constraint

the group was designed for inclusion, but the structure made it exclusive - only Ireland had access to community, events, and joining pathways.

the coherence move

I identified that expansion required a scalable communication topology: one EMEA layer for shared belonging, plus local chapters for local depth.

result

an EMEA-wide slack channel launched, 100+ people joined from other countries, and a Netherlands chapter was established using the same template.

 

situation

the chairs wanted expansion across EMEA. but the system only existed in Ireland, which meant there was no way for people in other countries to participate or belong.

  

objective

create immediate EMEA inclusion access without creating a heavy operational burden, and build a structure that could scale into country chapters over time.

 

discovery: the constraint beneath the constraint

the real blocker was not “lack of interest” - it was lack of architecture.

when I met with the US chair for the same group, I learned their structure:

one slack channel per chapter

one shared channel that connected all chapters

Ireland only had a local channel. EMEA had no shared layer, so people outside Ireland had nowhere to enter.

 

the coherence move

I designed a phased architecture:

phase 1: create a single EMEA entry layer so anyone could join immediately

phase 2: allow country chapters to form once membership concentration existed

phase 3: add a local slack channel per new chapter for local events and identity


 

the intervention

enabled chapter formation as a second step rather than a prerequisite 

created the EMEA slack channel as the primary inclusion entry point

defined what content belongs in each channel to avoid duplication

established a simple rule: Ireland content stays local, EMEA channel carries EMEA-suitable and shared posts


 

Implementation

step 1

met with the chairs and clarified the true goal: EMEA-wide inclusion, not just more posts.

step 2

studied the functioning US model and extracted the repeatable structure (shared layer + local chapters).

step 3

set up the EMEA slack channel and positioned it as the immediate community entry point.

step 4

created content boundaries so the Ireland team did not need to double content creation.

step 5

invited participation across EMEA and began running EMEA-suitable events and communications.

step 6

supported the emergence of a new country chapter when membership concentration formed (Netherlands), including creation of its local slack channel.

 

Results

within a couple of months:

100+ people joined from other EMEA countries

EMEA had a clear inclusion entry point for belonging and events

a Netherlands chapter launched with its own local channel

a repeatable template existed for future countries


 

what this demonstrates

I diagnose constraint as structure, not effort

I build systems that create belonging without creating operational overload

I design for scale through phased architecture and clear rules

I create templates that others can replicate across regions


 

work with me

if your organisation is stuck in complexity - growth, priorities, structure, execution - I can help you find the root constraint and restore clear movement.


 

 

coherence isn't insight - it is alignment.

I give you the decision you couldn't name but already knew was true. 

 

coherence work starts with the diagnostic

 

root constraint   written coherence map    14 day action plan

turn complexity into clear direction