The aim here is to develop a minimum set of terms useful in developing a framework for describing collaboration. As such they are no much definitions as a start on a working language for collaboration that might be used across disciplines and sectors.
Whether or not people are disposed to be collaborative, in the current context
People whose need is being met. If they pay for that, they are customers
Working together to a common purpose
Where we are collaborating, and what else is happening there
The system by which permissions and rewards are given and protocols enforced
How different are the people involved in the situation
Stakeholders touched by the collaboration process and its results
When group interactions take place
What outcomes people hope for
Where group interactions take place
For collaboration: a set of assumptions, concepts, values, and practices for describing collaboration.
People interacting to some purpose, which may be short term
First thoughts on how to tackle a problem, meet a need
How and why the collaboration started
A creative process to solve problems and meet needs, by developing projects, products, services
People communicating and/or doing things together
Who takes us forward, and in what style, e.g. may be directive, facilitative
An activity performed by a group using a collaboration tool
A configuration of methods, processes, stances, protocols and other elements of the collaboration framework designed to deliver an agreed purpose
Why we got involved
People with similar interests or concerns who interact
For collaboration: the means of communicating and working together on the Internet towards some common purpose.
The result of the process of collaboration, for participants and beneficiaries. It may or may not be positive.
What you can control
Who is involved and what they are like
What happens over time. It may be formal/informal/playful, planned/emergent, convergent/divergent
Products, services or other activities to meet the needs of beneficiaries
The rules of behaviour, permissions and reward systems - how we do things around here
Who knows who, and how they deal with each other
Power to is the ability to achieve purpose; power over is the ability to enforce protocols, give or withhold permissions and rewards.
What we are trying to achieve - for example, projects, products, services for specific beneficiaries; rewards for ourselves.
What you get out for what you put in
Why we stay involved and motivated
The likelihood things may not turn out as expected
How many interests are involved, and how many there could be
A person, group or organisation who affect, or may be affected by the collaboration process
The degree of control a power-holder may cede - for example, on a spectrum of tell, sell, consult, co-design, co-create (where only the last two are collaborative)
How connections are made, decisions taken, protocols applied
A group working together over time to achieve a common purpose
Means of enabling interactions, including events and online systems
People’s preparedness to rely on another’s communications as truthful and actions as well-intentioned.