User Tools

Site Tools


collaboration:short_a-z

Designing collaboration - Short A-Z

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.

Collaboration terms

Attitude

Whether or not people are disposed to be collaborative, in the current context

Beneficiaries

People whose need is being met. If they pay for that, they are customers

Collaboration

Working together to a common purpose

Context or situation

Where we are collaborating, and what else is happening there

Control

The system by which permissions and rewards are given and protocols enforced

Diversity

How different are the people involved in the situation

Ecosystem

Stakeholders touched by the collaboration process and its results

Events

When group interactions take place

Expectations

What outcomes people hope for

Forums

Where group interactions take place

Framework

For collaboration: a set of assumptions, concepts, values, and practices for describing collaboration.

Group

People interacting to some purpose, which may be short term

Ideas

First thoughts on how to tackle a problem, meet a need

Initiation

How and why the collaboration started

Innovation

A creative process to solve problems and meet needs, by developing projects, products, services

Interaction

People communicating and/or doing things together

Leadership

Who takes us forward, and in what style, e.g. may be directive, facilitative

Method

An activity performed by a group using a collaboration tool

Model

A configuration of methods, processes, stances, protocols and other elements of the collaboration framework designed to deliver an agreed purpose

Motivation

Why we got involved

Network

People with similar interests or concerns who interact

Online systems and tools

For collaboration: the means of communicating and working together on the Internet towards some common purpose.

Outcome

The result of the process of collaboration, for participants and beneficiaries. It may or may not be positive.

Ownership

What you can control

People

Who is involved and what they are like

Process

What happens over time. It may be formal/informal/playful, planned/emergent, convergent/divergent

Projects

Products, services or other activities to meet the needs of beneficiaries

Protocols

The rules of behaviour, permissions and reward systems - how we do things around here

Relationships

Who knows who, and how they deal with each other

Power

Power to is the ability to achieve purpose; power over is the ability to enforce protocols, give or withhold permissions and rewards.

Purpose

What we are trying to achieve - for example, projects, products, services for specific beneficiaries; rewards for ourselves.

Return

What you get out for what you put in

Rewards

Why we stay involved and motivated

Risk

The likelihood things may not turn out as expected

Scale

How many interests are involved, and how many there could be

Stakeholder

A person, group or organisation who affect, or may be affected by the collaboration process

Stance

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)

Structure

How connections are made, decisions taken, protocols applied

Team

A group working together over time to achieve a common purpose

Tools

Means of enabling interactions, including events and online systems

Trust

People’s preparedness to rely on another’s communications as truthful and actions as well-intentioned.

collaboration/short_a-z.txt · Last modified: 2017/06/12 10:20 (external edit)