Using Hackpads as Part of Online Dialogue, Deliberation and Collaborative Process
for"DandDTrans," a"community of inquiry and action" regarding the role that Dialogue & Deiberation can play in addressing the mega-crises of our time
Note that the Word version, with proper formatting, can be downloaded here:Hackpad Uses.docx
Using Hackpads as Part of Online Dialogue, Deliberation and Collaborative Processes
Nancy Glock-Grueneich Jan. 13, 2015
Suggestions based on experience so far and assuming more prep time in advance:
1. In general, it seems so far, that trying to create or use Hackpads“mid-stream” of a synchronous, live conversation, by self-organizing“volunteers”—though better than nothing— is less than ideal, but suggests testable questions for future development. In particular, I’d like to see experimentation with:
a. Having people volunteer in advance for the role, having had some practice ahead with Hackpads
b. Using pre-structured Hackpads(with permission to depart from that as needed or desired.)
c. Structuring Hackpads to elicit or capture inherent structures as they occur, ones chosen to match intended outcomes, e.g.
· Stories, concerns, suggested sources, etc.
· Problem solving(as, for example, and in particular using Rough’s Dynamic Facilitation structures or a close approximation
· Argumentation(as, for example, to ISIS or Compendium)
d. Reviewing the GroupWork Pattern cards and/or other models(e.g. IAP2 or NCDD) to identify specific places where such“in process” text capture would be helpful
2. Given that people have to adapt to the technology, as well as to the psychic adjustments of interacting with each other at a distance(and often without visual contact or context, depending on whether they are engaged only via audio or not), I think more time needs to be routinely included.
3. Specifically, asynchronous shared text development, using Hackpad(and perhaps including chat) has potential for leveraging real time plenary, seminar and small-group work on line in at least the following ways:
A. Planning an Event See 1 and 2, above
B. Pre-Event Activities See 1, above.
C. Simultaneously
a. Agendas outline content, process, events.
b. Links to short background materials, accessible as needed
c. Note taking during conversations
d. Quick mid-process review of notes taken or specific portions, as part of conversation
D. As built into the structure, using mature dialogue, deliberation & design methodologies, on line:
a. “Intermissions”(i.e. occurring during“breaks” on a given date or between dates for a process that has a series of events)
b. Harvests
i. Syntheses, including constructs, arguments, findings, plans, etc.
ii. Lists of emerging topics, themes, conclusions, criteria, options, questions, etc.
iii. Links, sources, texts, videos, etc.(with URL’s or references looked up later)
c. Next Round
Instructions, additional materials, new content etc. based at least in part on what has gone before and leading into what will come next
d. Feedback
i. Survey responses
ii. Observations, insights, additional content from participants, in response to specific queries or self-initiated
iii. Process evaluations, questions, and suggestions