-
Notifications
You must be signed in to change notification settings - Fork 0
/
acadia.html
109 lines (92 loc) · 6.33 KB
/
acadia.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
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Colin P. MacArthur - Acadia Youth Technology Co-Design</title>
<link rel="stylesheet" type="text/css" href="style.css">
</head>
<body>
<div class="header"><a href="index.html" style="color:white; text-decoration:none;">
<h1>Colin P. MacArthur</h1>
<h2>User Experience Researcher</h2></a><div class="contact_info">
<div>42 Alpine Street #1, Somerville, MA 02144</div>
<div>(505) 310-3082 - [email protected]</div>
<div><a href="http://colinmacarthur.org">http://colinmacarthur.org</a></div>
</div>
</div>
<div class="navigation">
<ul>
<li class=""><a href="index.html">Contact Me</a></li>
<li class="non-active"><a href="resume.html">Resume</a></li>
<li class="divider">Selected Projects:</li>
<li class="non-active"><a href="laps.html">Redesigning School Websites</a></li>
<li class="non-active"><a href="acadia-persuading.html">Persuading Visitors to Download Digital Publications</a></li>
<li class="non-active"><a href="36views.html">36 Views Lean Product Development</a></li>
<li class="non-active"><a href="WNPA.html">3D Imaging for National Parks</a></li>
<li class="active"><a href="acadia.html">Acadia Youth Technology Co-Design</a></li>
<li class="non-active"><a href="calparks.html">State Park Visitor Information Needs</a></li>
<li class="non-active"><a href="emrs.html">Changing Behavior with Electronic Medical Records</a></li>
</ul>
</div>
<div class="project">
<h3>Acadia Youth Technology Co-Design</h3>
<div class="client"><span class="caption">CLIENT:</span><h4>National Park Service</h4>
</div>
<div class="dates"><span class="caption">DATES:</span><br>March - August 2011
</div>
<div class="story">
<div class="section">
<div class="caption">Motivation:</div>
<h4 class="header">Parks need to build their next generation of advocates.</h4>
<div class="body ">
Current 12-17 year olds are less likely to visit national parks than any other age group. But parks need them to become the
next generation of park stewards and advocates.
</div>
</div>
<div class="section">
<div class="caption">Research Question:</div>
<h4 class="header">We asked: How might technology connect youth to Acadia?</h4>
<div class="body ">
<figure style="float:right; width:6em;"><img src="images/acadia_ipad.png" alt="A young person uses an iPad in the park"><figcaption>A young person uses an iPad in the park</figcaption>
</figure>
The internet, smartphones, GPS, digital signage and sensor networks are an increasingly large part of park visitors' experience.
Instead of decrying the effect of technology on the park experience, we wondered how technology could deepen peoples' (especially
young peoples') connection with their parks.
</div>
</div>
<div class="section">
<div class="caption">My role:</div>
<h4 class="header">I managed the first Park Service team co-designing park technology with young people, instead of for them.</h4>
<div class="body ">
<figure style="float:left; width:10em;"><img src="images/acadia_team.png" alt="The team of interns and assistant leader"><figcaption>The team of interns and assistant leader</figcaption>
</figure>
I led a team of high school interns observing their and others' park experiences, generating insights, and writing proposals
for park websites, apps, games and programs. I also liased with a visiting organizational behavior PhD student, who created
detailed plans for implementing the youth ideas. I also managed an assistant team leader, who kept the group safe and happy.
</div>
</div>
<div class="section">
<div class="caption">Results / Impact:</div>
<h4 class="header">Our proposals for new websites, apps and other technologies kick-started a multi-year technology development program at Acadia.</h4>
<div class="body ">
<figure style="float:right; width:8em;"><img src="images/acadia_tech_plan_cover.png" alt="The team's 11 proposals were compiled into Acadia's first Interpretive Technology Plan"><figcaption>The team's 11 proposals were compiled into Acadia's first Interpretive Technology Plan</figcaption>
</figure>
The team wrote 11 proposals for using mobile devices, websites and other technology to better connect young people with the
landscape and enhance the visitor experience. Almost all were funded and developed in subsequent years. The high schoolers
(now college juniors) who designed the projects are still involved in their creation and maintenance.
</div>
</div>
<div class="section">
<div class="caption">Lessons Learned:</div>
<h4 class="header">What I learned: Co-design requires learning which burdens to share (and not) with your co-designers.</h4>
<div class="body ">
All my expectations about what my high school co-designers would want to do (and not) were wrong. I thought they wouldn't
want to write proposals, but they did. I thought they'd be interested in the technical details, but they weren't. I'd just
share the design process with them, but learned which parts to share with them.
</div>
</div>
</div>
</div>
</body>
</html>