-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdelivery.html
446 lines (374 loc) · 15.1 KB
/
delivery.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
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
<title>Step 6: Program Delivery</title>
<script src="site_libs/jquery-1.11.3/jquery.min.js"></script>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link href="site_libs/bootstrap-3.3.5/css/simplex.min.css" rel="stylesheet" />
<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
<script src="site_libs/navigation-1.1/tabsets.js"></script>
<link href="site_libs/highlightjs-9.12.0/textmate.css" rel="stylesheet" />
<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
</style>
<style type="text/css">code{white-space: pre;}</style>
<style type="text/css">
pre:not([class]) {
background-color: white;
}
</style>
<script type="text/javascript">
if (window.hljs) {
hljs.configure({languages: []});
hljs.initHighlightingOnLoad();
if (document.readyState && document.readyState === "complete") {
window.setTimeout(function() { hljs.initHighlighting(); }, 0);
}
}
</script>
<style type="text/css">
h1 {
font-size: 34px;
}
h1.title {
font-size: 38px;
}
h2 {
font-size: 30px;
}
h3 {
font-size: 24px;
}
h4 {
font-size: 18px;
}
h5 {
font-size: 16px;
}
h6 {
font-size: 12px;
}
.table th:not([align]) {
text-align: left;
}
</style>
<link rel="stylesheet" href="styles.css" type="text/css" />
<style type = "text/css">
.main-container {
max-width: 940px;
margin-left: auto;
margin-right: auto;
}
code {
color: inherit;
background-color: rgba(0, 0, 0, 0.04);
}
img {
max-width:100%;
}
.tabbed-pane {
padding-top: 12px;
}
.html-widget {
margin-bottom: 20px;
}
button.code-folding-btn:focus {
outline: none;
}
summary {
display: list-item;
}
</style>
<style type="text/css">
/* padding for bootstrap navbar */
body {
padding-top: 41px;
padding-bottom: 40px;
}
/* offset scroll position for anchor links (for fixed navbar) */
.section h1 {
padding-top: 46px;
margin-top: -46px;
}
.section h2 {
padding-top: 46px;
margin-top: -46px;
}
.section h3 {
padding-top: 46px;
margin-top: -46px;
}
.section h4 {
padding-top: 46px;
margin-top: -46px;
}
.section h5 {
padding-top: 46px;
margin-top: -46px;
}
.section h6 {
padding-top: 46px;
margin-top: -46px;
}
.dropdown-submenu {
position: relative;
}
.dropdown-submenu>.dropdown-menu {
top: 0;
left: 100%;
margin-top: -6px;
margin-left: -1px;
border-radius: 0 6px 6px 6px;
}
.dropdown-submenu:hover>.dropdown-menu {
display: block;
}
.dropdown-submenu>a:after {
display: block;
content: " ";
float: right;
width: 0;
height: 0;
border-color: transparent;
border-style: solid;
border-width: 5px 0 5px 5px;
border-left-color: #cccccc;
margin-top: 5px;
margin-right: -10px;
}
.dropdown-submenu:hover>a:after {
border-left-color: #ffffff;
}
.dropdown-submenu.pull-left {
float: none;
}
.dropdown-submenu.pull-left>.dropdown-menu {
left: -100%;
margin-left: 10px;
border-radius: 6px 0 6px 6px;
}
</style>
<script>
// manage active state of menu based on current page
$(document).ready(function () {
// active menu anchor
href = window.location.pathname
href = href.substr(href.lastIndexOf('/') + 1)
if (href === "")
href = "index.html";
var menuAnchor = $('a[href="' + href + '"]');
// mark it active
menuAnchor.parent().addClass('active');
// if it's got a parent navbar menu mark it active as well
menuAnchor.closest('li.dropdown').addClass('active');
});
</script>
<!-- tabsets -->
<style type="text/css">
.tabset-dropdown > .nav-tabs {
display: inline-table;
max-height: 500px;
min-height: 44px;
overflow-y: auto;
background: white;
border: 1px solid #ddd;
border-radius: 4px;
}
.tabset-dropdown > .nav-tabs > li.active:before {
content: "";
font-family: 'Glyphicons Halflings';
display: inline-block;
padding: 10px;
border-right: 1px solid #ddd;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
content: "";
border: none;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
content: "";
font-family: 'Glyphicons Halflings';
display: inline-block;
padding: 10px;
border-right: 1px solid #ddd;
}
.tabset-dropdown > .nav-tabs > li.active {
display: block;
}
.tabset-dropdown > .nav-tabs > li > a,
.tabset-dropdown > .nav-tabs > li > a:focus,
.tabset-dropdown > .nav-tabs > li > a:hover {
border: none;
display: inline-block;
border-radius: 4px;
background-color: transparent;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
display: block;
float: none;
}
.tabset-dropdown > .nav-tabs > li {
display: none;
}
</style>
<!-- code folding -->
</head>
<body>
<div class="container-fluid main-container">
<div class="navbar navbar-inverse navbar-fixed-top" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html"></a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li>
<a href="index.html">
<span class="fas fa-home"></span>
Home
</a>
</li>
<li>
<a href="about.html">About this Guide</a>
</li>
<li>
<a href="timeline.html">
<span class="fas fa-gear"></span>
Process Overview
</a>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
<span class="fas fa-gear"></span>
Step-by-Step
<span class="caret"></span>
</a>
<ul class="dropdown-menu" role="menu">
<li>
<a href="environmental_scan.html">Step 1: Environmental Scan</a>
</li>
<li>
<a href="planning_committee_vision.html">Step 2: Forming a Planning Committee & Honing a Vision</a>
</li>
<li>
<a href="application.html">Step 3: Application Process</a>
</li>
<li>
<a href="schedule_content.html">Step 4: Developing the Program Schedule & Content</a>
</li>
<li>
<a href="leadup.html">Step 5: Program Lead-up</a>
</li>
<li>
<a href="delivery.html">Step 6: Program Delivery</a>
</li>
<li>
<a href="assessment.html">Step 7: Assessment</a>
</li>
<li>
<a href="resources.html">Further Reading/Suggested Resources</a>
</li>
</ul>
</li>
<li>
<a href="contact.html">
<span class="fas fa-gear"></span>
Contact Us
</a>
</li>
</ul>
<ul class="nav navbar-nav navbar-right">
</ul>
</div><!--/.nav-collapse -->
</div><!--/.container -->
</div><!--/.navbar -->
<div class="fluid-row" id="header">
<h1 class="title toc-ignore">Step 6: Program Delivery</h1>
</div>
<div id="day-1-setting-the-stage" class="section level2">
<h2>Day 1: Setting the stage</h2>
<p>It was important to us to establish a solid foundation of shared expectations on day one of the program. Our first session included an introductory presentation which covered logistics for the week and guided participants through a group norm setting exercise and some icebreakers.</p>
</div>
<div id="building-community-in-an-online-environment" class="section level2">
<h2>Building community in an online environment</h2>
<p>The platform that we used to build our shared group norms on the first day and as a catch-all board for the rest of the week was <a href="https://padlet.com/">Padlet</a>. Padlet is a collaborative shared workspace with lots of flexibility that we selected for its ease of use and anonymity.</p>
<p><a href="https://padlet.com/tculler2/ncgroj57decgz06j">We used a column structure:</a> the first column held our group norms and participants could anonymously contribute to them at any time. We then created a column dedicated to each day of the program and encouraged participants to add any questions that popped up for them as we went that we may not have gotten around to through the course of the day, or that they may not have wanted to voice out loud for whatever reason. We dedicated the first half hour of each morning to reviewing and answering these questions as a group. We never had a shortage of questions to review and received a lot of positive feedback with regards to this structure.</p>
<p>In addition to the Padlet review at the beginning of each day, we also used gifs and memes as a lighthearted icebreaker by encouraging participants to share appropriate gifs and or memes that encapsulated their current reactions to the program. We found this to be both a fun and meaningful way to engage participants in an online environment as it often led to constructive reflections and feedback.</p>
<p>Facilitating cohort bonding in an online only program is an ongoing challenge. In 2020, we encouraged participants to set up a Slack channel for themselves. We chose not to directly oversee this component as we wanted participants to have a space akin to what they would have had if we had been in person: a place to communicate more informally with one another that didn’t directly involve us as program organizers. While participants did take up the charge of creating their own slack channel, the feedback we received with regards to this is that it wasn’t very active and didn’t quite fill the hole we wanted it to fill. In 2021, then, we opted to forgo the Slack channel and added additional optional social time at the beginning of each day. This optional social time was modestly attended, but seemed to be well received by those who did take advantage of it. In 2022, we brought back the Slack channel and structured it differently: we posted prompts in the forum each day to kick off discussion, created a #participants-only channel, and invited presenters and thers to join the conversation. This seems to been an improvement over our use of Slack in the first year, and continues to serve as a space for participants to connect if they would like. For future iterations, we will continue to brainstorm ways to replicate some of the cohort building elements that participants would receive by default as part of an in person program. We do encourage participants to connect with one another on LinkedIn and to consider reaching out to one anther post-program to engage in continued learning groups together.</p>
<div class="figure">
<img src="images/padlet.png" alt="" />
<p class="caption">Our group padlet was an anonymous space for voicing questions and concerns to help jumpstart daily discussions.</p>
</div>
<blockquote>
<p>Tip: Take time at the beginning of day one to create shared group norms and expectations. Consider creative icebreakers and social activities to create a sense of community and mutual support amongst participants.</p>
</blockquote>
</div>
<div id="technical-troubleshooting" class="section level2">
<h2>Technical troubleshooting</h2>
<p>Technical workshops in-person allow for certain affordances that the online environment does not, including the ability for workshop leaders (or participants) to provide assistance to other participants while the workshop continues. With everyone in the same virtual meeting, there are no side conversations that can facilitate this. Multiple people can’t be helped with different issues at the same time. There’s no easy way to peer over at a neighbor’s screen quickly. For these reasons, it is important to have a plan in place for troubleshooting and asking for help.</p>
<p>The first decision that we made to try to work around the limitations described above is to make use of Zoom breakout rooms for troubleshooting purposes. When a participant needed help, the workshop instructor and helpers would quickly try to solve the problem in the main room, but if it required more focused help, we would send the participant(s) and a workshop helper into a breakout room. We asked workshop instructors to slow down the pace while there were people in breakout rooms so that while the workshop would continue, it wouldn’t be as difficult for participants to catch back up once they were done.</p>
<p>One thing that we considered with the breakout room approach was that if several participants needed help with different problems at the same time, we would need to increase the amount of workshop helpers we had on hand. We ended up asking 3-4 people to act as helpers for each workshop (for 8-10 attendees).</p>
<p>The approach we took to technical troubleshooting worked out well for the most part – we were able to solve issues fairly quickly and the workshops generally flowed smoothly. It did take time for everyone to become comfortable with the transition from main room to breakout room, and when to make that transition. After the first workshop, participants became used to going into the breakout room, sharing their screens, and working through issues. Throughout each workshop, we constantly solicited and incorporated participant feedback to improve the process. In the future, we will try to more specifically document expectations around the process to ensure everyone is on the same page.</p>
<blockquote>
<p>Tip: Consider the limitations of technical troubleshooting in a remote environment and create a plan to share with participants, workshop leaders and helpers to establish a process for troubleshooting.</p>
</blockquote>
<p><a href="https://ncsu-libraries.github.io/jumpstart-framework/assessment.html">Next >> Step 7: Assessment</a></p>
<p><br></p>
<p>Last updated on September 26, 2022.</p>
</div>
<p>
From NC State University Libraries.
<a href="https://www.lib.ncsu.edu/jumpstart">https://www.lib.ncsu.edu/jumpstart</a>
</p>
<img src="images/wordmark.png" alt="jumpstart wordmark">
</div>
<script>
// add bootstrap table styles to pandoc tables
function bootstrapStylePandocTables() {
$('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
}
$(document).ready(function () {
bootstrapStylePandocTables();
});
</script>
<!-- tabsets -->
<script>
$(document).ready(function () {
window.buildTabsets("TOC");
});
$(document).ready(function () {
$('.tabset-dropdown > .nav-tabs > li').click(function () {
$(this).parent().toggleClass('nav-tabs-open')
});
});
</script>
<!-- code folding -->
<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
(function () {
var script = document.createElement("script");
script.type = "text/javascript";
script.src = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
document.getElementsByTagName("head")[0].appendChild(script);
})();
</script>
</body>
</html>