[2327] in UA Exec
[UA] Let's think: Communications Goals
daemon@ATHENA.MIT.EDU (Sophia Liu)
Thu Oct 1 13:44:35 2015
From: Sophia Liu <sophliu@mit.edu>
Date: Thu, 1 Oct 2015 13:44:12 -0400
To: "ua-exec@mit.edu" <ua-exec@mit.edu>
--047d7b3a85ba805dd605210e9916
Content-Type: text/plain; charset=UTF-8
Hey all,
So this email is going to lay out the goals of effective internal UA
communication that I've thought about, and I invite you to add whatever you
think should be on there. (Feel free to apply all with added points to the
bottom of this list or comments on each item!) Over the course of the next
week, think about what system might work best for our organization, which
of these points below are more important, and we can decide together on
what to use.
An internal communication system should be:
1. *Transparent *(especially for those outside of exec)
2. *Archivable *(and easily accessible)
3. *Easily searchable *(in terms of deadlines, documents, other
references)
4. *Somewhat UA exclusive *(in terms of a method of communication that
is not flooded with other things, such as losing UA emails in all the other
emails that you may have--yes you can use labels, but not everyone does;
not sure if this is a big one, but this would support 3.)
5. *Streamlined *(somewhat; email will perhaps always be used, and we
can use a combination of modes, but we want to keep it to as few systems as
possible so that communication is effective)
6. *Easy to collaborate through*
7. *Sortable in terms of importance and type *(would be nice to have all
reminders in one place, fun things in one place, etc.)
8. *Conducive to feedback *(easy to quickly comment on things, etc.)
9. *User-friendly *(people need to use the system often for it to be
effective)
10. *A system enabling trust and confidence*
Best,
Sophia Liu
--047d7b3a85ba805dd605210e9916
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hey all,<div><br></div><div>So this email is going to lay =
out the goals of effective internal UA communication that I've thought =
about, and I invite you to add whatever you think should be on there. (Feel=
free to apply all with added points to the bottom of this list or comments=
on each item!) Over the course of the next week, think about what system m=
ight work best for our organization, which of these points below are more i=
mportant, and we can decide together on what to use.=C2=A0</div><div><b><br=
></b></div><div>An internal communication system should be:</div><div><ol><=
li><b>Transparent </b>(especially for those outside of exec)</li><li><b>Arc=
hivable </b>(and easily accessible)=C2=A0<br></li><li><b>Easily searchable =
</b>(in terms of deadlines, documents, other references)</li><li><b>Somewha=
t UA exclusive=C2=A0</b>(in terms of a method of communication that is not =
flooded with other things, such as losing UA emails in all the other emails=
that you may have--yes you can use labels, but not everyone does; not sure=
if this is a big one, but this would support 3.)</li><li><b>Streamlined </=
b>(somewhat; email will perhaps always be used, and we can use a combinatio=
n of modes, but we want to keep it to as few systems as possible so that co=
mmunication is effective)</li><li><b>Easy to collaborate through</b></li><l=
i><b>Sortable in terms of importance and type </b>(would be nice to have al=
l reminders in one place, fun things in one place, etc.)</li><li><b>Conduci=
ve to feedback </b>(easy to quickly comment on things, etc.)</li><li><b>Use=
r-friendly </b>(people need to use the system often for it to be effective)=
</li><li><b>A system enabling trust and confidence</b></li></ol><div>Best,<=
/div><div>Sophia Liu</div><div><br></div></div><div><br></div><img width=3D=
"0" height=3D"0" class=3D"mailtrack-img" src=3D"https://mailtrack.io/trace/=
mail/878a69fbd64244a9439ce67b65a7f4c8da685f4d.png"></div>
--047d7b3a85ba805dd605210e9916--
