-
Notifications
You must be signed in to change notification settings - Fork 1
/
Workshop Handout - English.html
395 lines (274 loc) · 23.9 KB
/
Workshop Handout - English.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta charset="utf-8" />
<link rel="stylesheet" type="text/css" href="css/style.css" />
<title>Workshop Handout: Patterns For Decentralised Organising</title>
<script src="jquery.min.js"></script>
</head>
<body>
<div id="about">
<p>This page is available in two formats. The "Reader Spread" is suitable for viewing online: it starts with page 1, then page 2, 3, 4 etc. The "Printer Spread" is designed to be printed double-sided on A4 paper, then folded and stapled in the middle to form a booklet. Choose the version you want before printing:</p>
<label><input type="radio" name="order" value="reader" id="reader" checked>Reader Spread</input></label><br />
<label><input type="radio" name="order" value="printer" id="printer">Printer Spread</input></label><br />
<button id="printBtn">Print</button>
</div>
<div id="output">
</div>
<div id="input">
<div class="page">
<h2>Patterns for Decentralised Organising</h2>
<figure><img style="width: 100%" src="img/8-circles-white-all-landscape.png"/></figure>
<div class="page-number"></div>
</div>
<div class="page printPage">
<div class="page-number"></div>
</div>
<div class="page">
<h3>2017 workshop tour</h3>
<p>This year we’re touring the world, meeting with all kinds of groups who are trying to work without hierarchical management structures: co-ops, startups, NGOs, companies, activist networks, etc. We host workshops to share the body of knowledge we're collecting along the way. </p>
<h3>Enspiral: more people working on stuff that matters</h3>
<p>Enspiral is a self-organising <strong>network </strong>of self-organising <strong>companies </strong>and <strong>teams</strong>. We support each other to do <strong>meaningful work</strong>: education, governance, food systems, conscious entrepreneurship, mad science, "stuff that matters". </p>
<p>We are pragmatic idealists learning how to use our <strong>differences as a collective resource</strong>. We are focussed on many <strong>different projects</strong> and we use <strong>different language</strong> to describe who we are and what we do.</p>
<p>Our <strong>shared values</strong> mean we prioritise the <strong>common good </strong>before private gain. We are discovering organisational structures that encourage <strong>relationships of respect</strong> and <strong>equality</strong> rather than <strong>hierarchy</strong> and <strong>domination</strong>.</p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>Loomio: technology for decentralised organising</h3>
<p>Loomio is open source software for <strong>small scale digital democracy</strong>. There are people all over the world, in groups of 3-300, using it to <strong>deliberate</strong> and <strong>make decisions</strong> to organise themselves. <strong>Co-ops</strong> write their constitution, <strong>companies</strong> decide on the annual budget and strategy, <strong>boards</strong> make decisions between meetings, <strong>activists</strong> coordinate community projects, <strong>philanthropists</strong> approve funding applications, <strong>government officials</strong> and <strong>experts</strong> deliberate with <strong>citizens</strong> on new policy.</p>
<p>Loomio is built by a worker-owned cooperative in Aotearoa New Zealand, globally respected for our commitment to <strong>ethical business</strong> and <strong>non-hierarchical management</strong>.</p>
<p><em>Try the software: loomio.org</em></p>
<p><em>Read the cooperative handbook: loomio.coop</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>8 Patterns for Decentralised Organising</h3>
<p>In my role at Loomio and Enspiral, I worked with dozens of groups who are <strong>experimenting with decentralised organising</strong>. I noticed that each team faced similar challenges, and <strong>sharing experiences</strong> between teams helped them to <strong>innovate faster</strong>.</p>
<p>This year we’ve worked with hundreds of groups, sharing these "<strong>patterns</strong>": each pattern is a <strong>challenge</strong> common to many decentralised groups, and some practical <strong>responses. </strong></p>
<p>The patterns are designed to be <strong>remixed</strong>, adapted to your local context. We’ll share 8 of the most common ones here.</p>
<p><em>You can use the blank pages in this booklet to take notes, e.g. how do you see these patterns showing up in your group? What new ideas do you want to try?</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>1. Intentionally produce counter-culture</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_01.png"/></figure>
<p><strong>Challenge: </strong><br/>You want to be non-hierarchical but you have <strong>hierarchical habits</strong>, e.g. telling people what to do, or looking to others for answers. We are <strong>conditioned by culture</strong>: if there is sexism and racism in your environment, it can be imprinted into your habits.</p>
<p><strong>Response:</strong><br/>We can <strong>unlearn hierarchies</strong> together. We can <strong>co-design a culture</strong> that encourages each of us to develop our best qualities, making us all more generous, respectful, trusting, courageous, etc. </p>
<p>How do you produce culture? <strong>Fermentation!</strong> To make sourdough bread, you have a <strong>starter dough</strong>, mixed with <strong>fresh ingredients, </strong>and put it somewhere dark and safe for some time. To ferment a new group culture, your "starter dough" is a person or people who <strong>embody some of the qualities</strong> you want to develop. The “fresh ingredients” are <strong>new people</strong> who have a <strong>desire</strong> to grow in a specific way. We combine these ingredients in a <strong>retreat</strong>: safe, quiet, isolated from the outside world for a few days. </p>
<p><strong>Results:</strong><br/>We learn about each other’s <strong>dreams</strong> and <strong>fears</strong>, building deep <strong>relationships of trust</strong> and <strong>belonging</strong>: the most important resource for all your upcoming challenges.</p>
<div class="page-number"></div>
</div>
<div class="page printPage">
<figure class="pattern printerPattern"><img src="img/8-circles-white_01.png"/></figure>
<p class="notes"><em>Use this page for your own notes.</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>2. Systematically distribute care labour</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_02.png"/></figure>
<p><strong>Care</strong> includes the practical stuff of <strong>hospitality</strong>: preparing a comfortable room with food, lighting, decoration, refreshments, collaboration tools, and tidying up after. It also includes <strong>emotional work</strong>, like noticing tension between colleagues and supporting them to resolve it.</p>
<p><strong>Challenge: </strong><br/>Hierarchical culture trains us to not <strong>share the care labour fairly</strong>. Most groups have one or two people, usually women, doing most of the care work. If they get overwhelmed or frustrated, they’ll stop, and the group loses its gravity.</p>
<p><strong>Response:</strong> <br/><strong>Make all work visible</strong>, so you can share it fairly. E.g. the Loomio team uses "<strong>stewardship</strong>", a peer-to-peer support system. Everyone supports one person, and is supported by someone else. Each pair meets once per month, the steward asks “how can I support you?” and they figure out the answer together. More info: https://loomio.coop/stewarding.html</p>
<p><strong>Results:</strong> <br/>Builds deep <strong>trusting relationships</strong>; dissolves <strong>conflicts</strong>; continuously <strong>improving</strong> <strong>emotional intelligence</strong> of everyone in the group; more distribution = <strong>more resilience</strong>. </p>
<div class="page-number"></div>
</div>
<div class="page printPage">
<figure class="pattern printerPattern"><img src="img/8-circles-white_02.png"/></figure>
<p class="notes"><em>Use this page for your own notes</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>3. Make explicit norms and boundaries</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_03.png"/></figure>
<p>Norms = <strong>how we do things</strong> around here. Boundaries = <strong>what we don't do</strong> around here. Many groups leave these things unsaid, relying on "common sense".</p>
<p><strong>Challenge: </strong><br/>Conflicts grow when people have different unspoken assumptions (everyone has different common sense). When you cross an invisible boundary, it takes huge energy to make the boundary explicit, before you can get to the behaviour.</p>
<p><strong>Response:</strong><br/>Talk about your norms: <strong>how do we want to be together?</strong> e.g. open, honest, authentic, gentle, inquisitive...</p>
<p>Talk about your boundaries: <strong>what behaviour do we want to exclude?</strong> e.g. no mean feedback, no sexist jokes. </p>
<p><strong>Results:</strong><br/><strong>Buy-in </strong>— clarity helps people evaluate whether or not they want to be here. Expectations are clear. There is a process for challenging destructive behaviour, and a process for updating our agreements.</p>
<p>E.g. see roles + responsibilities described in Enspiral’s People Agreement: https://handbook.enspiral.com/agreements/people.htm</p>
<div class="page-number"></div>
</div>
<div class="page printPage">
<figure class="pattern printerPattern"><img src="img/8-circles-white_03.png"/></figure>
<p class="notes"><em>Use this page for your own notes</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>4. Keep talking about power</h3>
<figure class="pattern readerPattern"><img src="img/img/8-circles-white_04.png"/></figure>
<p><strong>Challenge:</strong><br/>Power, influence, status, rank, social capital, volume, access... whatever you call it, I’ve never met a group where it was equally distributed between all members. Equality is a compass point to navigate towards, not a destination I’ve ever arrived at.</p>
<p><strong>Response:</strong><br/>Groups thrive when anyone can safely talk about power differentials. Imbalance can be bad, e.g. inherited privilege, coercion, manipulation, the "old boys club". Some imbalance can be good: earned trust, reputation, eldership.</p>
<p>Transparency reduces toxicity. Discuss together: "<strong>How’s the power?</strong> Who has it? How do you earn it?"</p>
<p>Some roles attract power (e.g. manager, facilitator, spokesperson, coordinator, director). Rotation increases access: take turns, step out, encourage others to step in. </p>
<p>E.g. Loomio team coordinators are elected by the team for a limited term; we intentionally support less experienced people to try the role. See https://loomio.coop/coordination.html</p>
<p>The best 'elders' use their status to praise, acknowledge, and encourage people with less.</p>
<div class="page-number"></div>
</div>
<div class="page printPage">
<figure class="pattern printerPattern"><img src="img/8-circles-white_04.png"/></figure>
<p class="notes"><em>Use this page for your own notes</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>5a. Agree how you’re using your tech</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_05.png"/></figure>
<p><strong>Challenge</strong><br/>Many groups are dissatisfied with their communication technology. Information overload: too much data but can never find the thing you want. Half the team uses this tool, the other half uses another one. Too many tools, don't know how to get everyone's attention, can never find the document I need.</p>
<p><strong>Response</strong><br/>Agree together what tools are for what job. E.g. the 'trinity of digital comms':</p>
<ol>
<li><strong>Realtime</strong>, like chat, messenger, or Slack. Informal, quick, organised around <strong>time</strong>: it's about right now.</li>
<li><strong>Asynchronous</strong>, like email, forum or Loomio. More formal, organised around <strong>topic</strong>. Has a subject + context + invitation. Can take days or weeks. Makes a useful archive, considered comments rather than random messy chatter.</li>
<li><strong>Static</strong>, like a wiki, Google Docs, handbook, or FAQ. Very formal, usually with an explicit process for updating content.</li>
</ol>
<p>Depending on your work, you will need different tools. The important thing is that you have an agreement together about what tools are for what job. With a shared understanding of the tools, they all fit together beautifully. When people have different ideas, it gets messy.</p>
<div class="page-number"></div>
</div>
<div class="page printPage">
<figure class="pattern printerPattern"><img src="img/8-circles-white_05.png"/></figure>
<p class="notes"><em>Use this page for your own notes</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>5b. Introducing new tools</h3>
<p><strong>Challenge:</strong><br/>Introducing a new communications tool usually makes the problem worse. Most groups don’t know how to introduce new tech well.</p>
<p><strong>Response:</strong><br/>This method makes it less likely to go badly:</p>
<ol>
<li><strong>Agree the problem.</strong> What issue do you want to solve? Do other team members agree it’s a problem?</li>
<li><strong>Volunteer(s) test prototypes.</strong> One or a few people research options and come back to the wider group with a recommendation.</li>
<li><strong>Support people to learn.</strong> Once you’ve chosen a new tool to evaluate, make space for people to learn together how to use it.</li>
<li><strong>Reminders build a habit.</strong> It can take weeks to develop a new communication habit. Remind each other gently, "hey we said we’d try using Loomio for these kinds of conversations..."</li>
<li><strong>Evaluate + repeat.</strong> Most importantly, set a time-limit, e.g. "We’ll try this tool for 2 months and then evaluate together. Is the problem solved? Or do we need more training, or a different tool?"</li>
</ol>
<div class="page-number"></div>
</div>
<div class="page printPage">
<p class="notes"><em>Use this page for your own notes</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>6. Make decisions asynchronously</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_06.png"/></figure>
<p><strong>Challenge:</strong><br/>When you say ‘we’re going to be inclusive’, that’s code for ‘we’re going to spend <strong>a lot of time in meetings</strong>.’ Most collaborative groups make decisions in meetings or conference calls. You can think of this as <strong>synchronised</strong> or <strong>realtime</strong> communication: you have to synchronise people’s calendars to book the meeting, then when they arrive, everyone has to pay attention to everything at the same time. It’s very <strong>expensive</strong>, <strong>excluding</strong> the input of people who can’t attend, and often results in <strong>hurried </strong>decisions.</p>
<p><strong>Response:</strong><br/>With a little effort, you can develop a habit of <strong>asynchronous decision-making</strong>. People can participate in their own time, contributing only to the issues relevant to them. This is what <strong>Loomio</strong> is for: more inclusion and collective intelligence, less time in meetings.</p>
<p>E.g. I’m on a Board of Directors. We meet monthly. We co-create the agenda in a Loomio thread ahead of time. A few days before the meeting, the secretary starts a poll to check everyone is happy with the agenda and we’ve all read the reports. We all arrive at the meeting prepared and focussed. We’ll make some decisions face-to-face. For decisions that require input from more people, or if we just want more time to consider options, one of the Directors will take the decision to Loomio. We also use the software to sign off the minutes, and find another meeting time.</p>
<div class="page-number"></div>
</div>
<div class="page">
<figure class="pattern printerPattern"><img src="img/8-circles-white_06.png"/></figure>
<p><strong>Results:</strong><br/>Over time you learn the unique qualities of realtime and async communication. Meetings are good for bonding, brainstorming, and dealing with complex or sensitive topics. Loomio creates more space for deliberation: you can take more time, consider more options, hear from more people, and keep a record.</p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>7. Use rhythm to balance flexibility and focus</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_07.png"/></figure>
<p><strong>Challenge</strong><br/>Hierarchies are designed to manage flows of communication and decision-making. When you remove the hierarchy, you need to replace it with something. If there is no agreed structure, your group can suffer from information overload (everyone asked about everything all the time) and exclusion (decisions made without appropriate input).</p>
<p><strong>Response</strong><br/>Rhythm helps balance <strong>speed</strong> with <strong>participation.</strong> People can trust each other to seek input at the right time, so they don’t need to be involved in every decision.</p>
<p>We create distinct communication spaces for different timeframes, e.g. today’s work is discussed <strong>every morning</strong>; if you want to discuss the long term strategic direction, we have a dedicated space for that <strong>every month</strong>.</p>
<p><strong>Example</strong><br/>Here’s a set of working rhythms we use in the Loomio team. You can adapt to your context, e.g. maybe it makes sense to align with seasons or moon cycles:</p>
<ul>
<li><strong>Daily</strong> "standup" meeting. Everyone answers, “What did you do yesterday? What are you doing today? Are there any obstacles we can help you with?” Quick info exchange, accountability and support.</li>
<li><strong>Weekly</strong> "sprints", a regular working period. E.g. on Monday we agree what work we’re going to do this week. On Friday we share progress and have a “retrospective” looking for improvements to try next week.</li>
</ul>
<div class="page-number"></div>
</div>
<div class="page">
<figure class="pattern printerPattern"><img src="img/8-circles-white_07.png"/></figure>
<ul>
<li><strong>Quarterly</strong> objectives. Every 3 months we have a planning day, looking for agreement on 3 or 4 measurable targets to align all of the work in the cooperative. After we finalise the decision on Loomio, everyone has freedom to do whatever work they feel is most relevant to achieve those outcomes.</li>
<li><strong>Bi-annual</strong> retreats. Every 6 months we go away together for 3 or 4 days. This deepens our relationships, and creates a space for the kind of conversations that can’t happen in the office, e.g. dreaming together about our shared vision, or dealing with a complex tension.</li>
</ul>
<div class="page-number"></div>
</div>
<div class="page">
<h3>8. Generate new patterns together</h3>
<figure class="pattern readerPattern"><img src="img/8-circles-white_08.png"/></figure>
<p><strong>Challenge</strong><br/>If you're not stopping you're not learning. </p>
<p><strong>Response</strong><br/>If you're going to try one thing, do this.</p>
<p>You can choose a frequency that suits you, but let's say weekly. At the end of each week, stop working. Have a <strong>retrospective</strong> meeting. Review the week just been. <strong>What was good?</strong> Notice it and do more. <strong>What was bad?</strong> Discuss. <strong>Agree a change</strong> that you're going to try next week to make it more good and less bad.</p>
<p>I've shared a bunch of collaboration patterns. These are just my way of describing things I've seen. We discovered them by a lot of invention, remixing ideas, making them our own, adjusting them to local conditions. This booklet is not a recipe for you to copy and paste, it’s a guide to a way of thinking. The retrospective is where you learn to notice your own collaboration patterns, and co-design new ones.</p>
<p>See the Retrospective Wiki for ideas of how to host a structure reflection process: retrospectivewiki.org</p>
<div class="page-number"></div>
</div>
<div class="page printPage">
<figure class="pattern printerPattern"><img src="img/8-circles-white_08.png"/></figure>
<p class="notes"><em>Use this page for your own notes</em></p>
<div class="page-number"></div>
</div>
<div class="page">
<h3>Credits</h3>
<table>
<thead><tr>
<td>Contributor</td>
<td>Contribution</td>
</tr></thead>
<tr>
<td>Richard D. Bartlett<br/><a href="http://richdecibels.com">richdecibels.com</a><br/>[email protected]</td>
<td>Writing first draft in English</td>
</tr>
<tr>
<td>Natalia Lombardo<br/>[email protected]</td>
<td>Co-designed first draft with Rich.</td>
</tr>
<tr>
<td>Lucas Tauil de Freitas<br/>[email protected]</td>
<td>Translation for Portuguese (Brasil)</td>
</tr>
<tr>
<td>Sandra Chemin<br/>[email protected]</td>
<td>Revision & editing in English + Portuguese</td>
</tr>
</table>
<h3>License: <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0 1.0 Universal</a></h3>
<p>This work is licensed in the public domain, with no rights reserved. Do what you like with it! If you have contributed, feel free to add your contact details to the <strong>credits</strong> list. See <a href="http://github.com/rdbartlett/patterns">github.com/rdbartlett/patterns</a> for different versions.</p>
<div class="page-number"></div>
</div>
</div>
<script type="text/javascript">
// human readable numbers, i.e. the first page is 1
seq4 = [4,1,2,3]
seq8 = [8,1,2,7, 6,3,4,5]
seq12 = [12,1,2,11, 10,3,4,9, 8,5,6,7]
seq16 = [16,1,2,15, 14,3,4,13, 12,5,6,11, 10,7,8,9]
seq20 = [20,1,2,19, 18,3,4,17, 16,5,6,15, 14,7,8,13, 12,9,10,11]
seq24 = [24,1,2,23, 22,3,4,21, 20,5,6,19, 18,7,8,17, 16,9,10,15, 14,11,12,13]
seq28 = [28,1,2,27, 26,3,4,25, 24,5,6,23, 22,7,8,21, 20,9,10,19, 18,11,12,17, 16,13,14,15]
seq32 = [32,1,2,31, 30,3,4,29, 28,5,6,27, 26,7,8,25, 24,9,10,23, 22,11,12,21, 20,13,14,19, 18,15,16,17]
seq36 = [36,1,2,35, 34,3,4,33, 32,5,6,31, 30,7,8,29, 28,9,10,27, 26,11,12,25, 24,13,14,23, 22,15,16,21, 20,17,18,19]
seq40 = [40,1,2,39, 38,3,4,37, 36,5,6,35, 34,7,8,33, 32,9,10,31, 30,11,12,29, 28,13,14,27, 26,15,16,25, 24,17,18,23, 22,19,20,21]
function printIfExists(elem){
if(Object.prototype.toString.call(elem).indexOf("Undefined") == -1){
$('#output').append(elem)
}
return elem;
}
pageNumbers = $('.page-number');
// for(i=0;i<pageNumbers.length;i++){ pageNumbers[i].append(i+1); }
function printerSpread() {
$('#output').show();
$('#input').hide();
for(i=0;i<seq24.length;i++){
// need to minus one to convert from human readable to computer-readable page numbers
printIfExists(pages[seq24[i]-1]);
}
$('.printPage').show();
$('.printerPattern').show();
$('.readerPattern').hide();
}
function readerSpread() {
$('#input').show();
$('.printPage').hide();
$('.readerPattern').show();
$('.printerPattern').hide();
$('#output').hide();
}
$('#printer').click(printerSpread);
$('#reader').click(readerSpread);
$('#printBtn').click(function() {window.print()});
$(document).ready(function() {
pages = $('.page').clone();
readerSpread()
});
</script>
</body>
</html>