[2329] in UA Exec
Re: [UA] Let's think: Communications Goals
daemon@ATHENA.MIT.EDU (Sophia Liu)
Thu Oct 1 20:25:14 2015
In-Reply-To: <CAKyRmfRUJqsQjcBkxAjsWt88O4wqbRehLy18chh_BGNue9K3LA@mail.gmail.com>
From: Sophia Liu <sophliu@mit.edu>
Date: Thu, 1 Oct 2015 20:24:48 -0400
To: Lillian Chin <ltchin@mit.edu>
Cc: "ua-exec@mit.edu" <ua-exec@mit.edu>
--089e010d8dc424ea1c0521143221
Content-Type: text/plain; charset=UTF-8
My intention with point 10 was for the communication system to be a place
where people feel comfortable participating. Trust is, of course, built
primarily in the community itself, but I do think the mode of communication
can impact how comfortable people feel participating (e.g. non-face-to-face
communication might inhibit trust and confidence because you can't read a
person's reactions.) If that's a bit too wishy-washy for the group, we can
remove it, but I think it makes an important point.
The points you mentioned are also important! I think that they're covered
in 9. and 1., but please feel free to add more detail to them if you think
they're insufficient.
Sophia Liu
Massachusetts Institute of Technology
Vice President of the Undergraduate Association
Departments of Chemical Engineering and Biology
On Thu, Oct 1, 2015 at 7:15 PM, Lillian Chin <ltchin@mit.edu> wrote:
> Can you elaborate on Point 10? Is this "trust and confidence that the
> communication system works and will always work" or is this "external
> people using this have trust and confidence that the UA knows what they are
> doing"
>
>
> On Thu, Oct 1, 2015 at 1:44 PM, Sophia Liu <sophliu@mit.edu> wrote:
>
>> 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
>>
>>
>>
>
--089e010d8dc424ea1c0521143221
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">My intention with point 10 was for the communication syste=
m to be a place where people feel comfortable participating. Trust is, of c=
ourse, built primarily in the community itself, but I do think the mode of =
communication can impact how comfortable people feel participating (e.g. no=
n-face-to-face communication might inhibit trust and confidence because you=
can't read a person's reactions.) If that's a bit too wishy-wa=
shy for the group, we can remove it, but I think it makes an important poin=
t.<div><br></div><div>The points you mentioned are also important! I think =
that they're covered in 9. and 1., but please feel free to add more det=
ail to them if you think they're insufficient.=C2=A0</div><img width=3D=
"0" height=3D"0" class=3D"mailtrack-img" src=3D"https://mailtrack.io/trace/=
mail/9dbc292971fe178169c53260e207102f691095fc.png"></div><div class=3D"gmai=
l_extra"><br clear=3D"all"><div><div class=3D"gmail_signature"><div dir=3D"=
ltr"><div><div dir=3D"ltr">Sophia Liu=C2=A0</div><div dir=3D"ltr"><div><fon=
t color=3D"#999999">Massachusetts Institute of Technology</font></div><div>=
<font color=3D"#999999">Vice President of the Undergraduate Association</fo=
nt></div><div><div><font color=3D"#999999">Departments of Chemical Engineer=
ing and Biology</font></div></div></div></div></div></div></div>
<br><div class=3D"gmail_quote">On Thu, Oct 1, 2015 at 7:15 PM, Lillian Chin=
<span dir=3D"ltr"><<a href=3D"mailto:ltchin@mit.edu" target=3D"_blank">=
ltchin@mit.edu</a>></span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><fon=
t size=3D"2">Can you elaborate on Point 10? Is this "trust and confide=
nce that the communication system works and will always work" or is th=
is "external people using this have trust and confidence that the UA k=
nows what they are doing"</font><div><font size=3D"2"><br></font></div=
><div><font size=3D"2"><br></font><div class=3D"gmail_quote"><span class=3D=
"">On Thu, Oct 1, 2015 at 1:44 PM, Sophia Liu <span dir=3D"ltr"><<a href=
=3D"mailto:sophliu@mit.edu" target=3D"_blank">sophliu@mit.edu</a>></span=
> wrote:<br></span><div><div class=3D"h5"><blockquote class=3D"gmail_quote"=
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr">Hey all,<div><br></div><div>So this email is going to lay ou=
t the goals of effective internal UA communication that I've thought ab=
out, and I invite you to add whatever you think should be on there. (Feel f=
ree to apply all with added points to the bottom of this list or comments o=
n each item!) Over the course of the next week, think about what system mig=
ht work best for our organization, which of these points below are more imp=
ortant, 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>Archi=
vable </b>(and easily accessible)=C2=A0<br></li><li><b>Easily searchable </=
b>(in terms of deadlines, documents, other references)</li><li><b>Somewhat =
UA exclusive=C2=A0</b>(in terms of a method of communication that is not fl=
ooded with other things, such as losing UA emails in all the other emails t=
hat you may have--yes you can use labels, but not everyone does; not sure i=
f 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 combination =
of modes, but we want to keep it to as few systems as possible so that comm=
unication is effective)</li><li><b>Easy to collaborate through</b></li><li>=
<b>Sortable in terms of importance and type </b>(would be nice to have all =
reminders in one place, fun things in one place, etc.)</li><li><b>Conducive=
to feedback </b>(easy to quickly comment on things, etc.)</li><li><b>User-=
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,</d=
iv><div>Sophia Liu</div><div><br></div></div><div><br></div><img width=3D"0=
" height=3D"0" src=3D"https://mailtrack.io/trace/mail/878a69fbd64244a9439ce=
67b65a7f4c8da685f4d.png"></div>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div>
--089e010d8dc424ea1c0521143221--
