How can an entire group collaboratively compose a document as a group ... using email?
Here is a methodology for people to come to agreement using email technology.
Example: Agree on a common criteria to evaluate project plans submitted by students in the class.
The problem with email is also its strength -- communications are broadcast from one individual to all others.
Emotionally charged emails are called “flames”.
Email exchanges consists of offer and response cycles, not interactive negotiation.
A number of software tools are emerging.
For over a decade, Bernie Dekoven has been reporting on
tools for collaborating online at his coworking.com website
However, many are reluctant to use new technologies.
My strategy for using email technology to come to agreement is adapted from the same
strategy used to reach agreement in a face to face meeting.
Step 1 - Willingness to Innovate
First, define stakeholders, their mutual goals, the benefit for achieving it,
and the ground rules.
Clarifying this is the first and very decisive battle.
So many people become frustrated because they never did this to begin with and
the lack of clarify undermines everything else they do.
Here is an example of an email to do this:
This trial balloon, in essence, is the first email poll.
If enough people respond positively, we go to the next step.
A followup phone call or physical visit may be needed for those who don't respond.
Step 2 - Structure
The problem with this email is that two questions were posed.
Typically not a good tactic. People might answer only one question and we're left wondering which item they agree with.
But asked two questions is useful to give cover to an innovation that may not be well received.
Anyway, the second step is to identify a pre-existing structure or approach.
An experienced team does this automatically.
Here's a sample email:
I thought that we might avoid reinventing the wheel here
by identifying a criteria structure that others have already used.
One possibility is the list of Core processes in PMP's Body of Knowledge?
It's certainly comprehensive enough. The items are ...
Please let me know if this is OK, or propose a different structure.
A structure consists of deliverables, roles, and steps.
If several structures are proposed, it's ususally best to adopt one rather than trying to merge the two.
Step 3 - Rules for Condensing
Rather than, I've found it better to brainstorm on separate lists at the same time.
Example:
Attached is my list of possible options and a separate list of possible criteria.
Please add your items before we identify the top choices.
Poll A: How many items should be on the list of options?
Poll B: How many items should be on the list of criteria?
We'll limit the lists to the average of items we all recommend, OK?
Here we are proposing both content and process at the same time.
Again, not the ideal of working out a process then implementing it.
But this two-headed approach keeps the emails active at the risk of confusion.
Step 4 - Condense
Example email:
Now we're on our way.
Step 5 - Collect the Scores
Example email:
Step 6, etc.
We're on our way...