The Call to Collaborate is Irrevocable — It Will Never Be Taken Back

Posted on: March 27, 2014

Have you ever been on a project team and felt the ground rules included some of these phrases?I’ll try being nicer if you’ll try being smarter.Any connection between your reality and mine is purely coincidental.E-mail is not to be used to pass on information or data. It should be used only for company business.I’m not being rude. You’re just insignificant.

If you want to be truly collaborative, you gotta have Ground Rules and Rules of Engagement to help organize a team’s efforts to answer the call to collaborate and give it your best shot.
People often confuse the two terms and it’s important for a project team to define them and create a common collaborative language from the beginning.

Differentiating the Terms
Ground Rules are about managing yourself. Following ground rules is doing the things behaviorally that shouldn’t have to be said or written-down. They are basic behaviors you can ask someone to start/stop doing once and that’s all it should take.
Rules of Engagement are about managing your interactions with others.
Ground Rules is a basic idea, whereas Rules of Engagement is a step-up because it involves others and it takes work and accountability.

Context Matters
Today’s focus will be on ground rules. I’m going to give examples of ground rules using two different scenarios – my family and a project team. Interesting enough, project teams tend to mirror families. So, in many ways, using the context of family can help project teams better understand the value of answering the call to collaborate.

Examples of Ground Rules
At our house, family ground rules at dinner time include each child helping out – Molly pours drinks, Aidan sets the table, Joseph clears the table and so on…
In a project team, ground rules may include preparing for meetings, showing-up on-time and turning off your cell phone.

Here’s what it looks like in practice. . .
One of the project teams I’m working with wanted to become more collaborative but didn’t have a common collaboration implementation language. They were confusing ground rules with rules of engagement. They had a packed, two page, single-spaced, 8-point font document full of well-intentioned statements they called rules of engagement. These statements were actually ground rules for the most part, like:
The first response to a new idea should never be ‘no’ and Avoid spending too much meeting time on one topic….

So, we combed through the original document and pulled out the statements that were truly ground rules, per our definition. We gave a copy of this list of ground rules to everyone to talk about and read and we filed-away the master copy in a drawer for safe keeping. Ground rules are basic ideas, so after talking about them and writing them down once, we shouldn’t have to reference this master copy on too many occasions.
You have to start somewhere and identifying and defining ground rules is a great start. As you can see, ground rules help hold together a group of people like a family or a project team and help it function in a more collaborative manner to solve problems.

The call to collaborate in either scenario is irrevocable. You are compelled to answer it in all your interactions every day. Answer the call and give it your best shot.