You’re Not Just a Facilitator. You’re an Architect.  

 

If there’s one idea worth carrying out of the study of collaborative leadership, make it this: 

Collaboration is not something that happens to a group. It’s something a leader builds for a group. 

Effective collaboration requires you to engineer the experience—to design the environment so that participants understand when and how to contribute, and so that the work can move forward even when things get tense or messy. That involves a lot of moving pieces: process flows, communication channels, and meeting design. It can feel like a lot to take on all at once. 

So let’s focus on the one design choice that tends to matter most: ground rules. 

Why Ground Rules Change Everything  

Ground rules—or what some teams call working norms—are the shared agreements that tell a group how to show up together. Not just “be respectful,” but the specific, practical stuff: How do we handle it when someone dominates the conversation? What do we do when we disagree? How do we make sure the quieter voices in the room actually get heard? 

The key word in all of that is shared. Ground rules that a leader hands down rarely stick. Ground rules that a team co-creates together become something people actually hold each other to because they were part of making them. 

When you solicit norms from the group instead of imposing them, something important shifts: People stop waiting to be told how to behave and start taking ownership of how the collaboration functions. That’s not just a process win. It’s a culture win. 

Try This Before Your Next Collaborative Meeting 

Before you bring your group together, try this simple activity to establish working norms: 

1. Send a brief pre-work prompt. Before the meeting, ask each participant to come prepared with one answer to this question: “What’s one thing our group needs to do—or agree not to do—for this collaboration to work well?” This gives quieter voices a chance to formulate their thoughts before the room gets loud. 
2. Open the meeting with norm-setting. Spend the first 10 minutes gathering responses. Write them where everyone can see them. Look for themes. You’re not aiming for an exhaustive list. Three to five clear, specific norms are more useful than ten vague ones. 
3. Name one norm specifically for handling disagreement. This is the one most groups skip—and most groups need. It could be as simple as, “We separate the idea from the person.” Or, “We ask a question before we push back.” When the group decides this together in advance, it’s much easier to invoke it in the moment. 
4. Post the norms and return to them. At the start of each subsequent meeting, spend 60 seconds reviewing them. At the end of the project, ask the group: “Did these norms help us work better together? What would we change?” 

This is the work of engineering collaboration—not just opening the floor and hoping for the best. 

Want help getting started? Bring your project goal to Sophia, the AI Leadership Coach and ask her to help you draft a set of proposed ground rules for your team. You can use them as a starting point to react to together, which is itself a form of collaborative norm-setting. 

Learn more about how to lead collaboratively using the Five Paths to Leadership® model in the Applying the Five Paths course.