[2328] in UA Exec
Re: [UA] Let's think: Communications Goals
daemon@ATHENA.MIT.EDU (Lillian Chin)
Thu Oct 1 19:15:23 2015
In-Reply-To: <CABVWso=v=BurGA9=yrEBJO9j_xdCm_CD7ZqSm_hR-NSTZ0tj=A@mail.gmail.com>
From: Lillian Chin <ltchin@mit.edu>
Date: Thu, 1 Oct 2015 19:15:00 -0400
To: Sophia Liu <sophliu@mit.edu>
Cc: "ua-exec@mit.edu" <ua-exec@mit.edu>
--001a11471d487e91e70521133808
Content-Type: text/plain; charset=UTF-8
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
>
>
>
--001a11471d487e91e70521133808
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<font size=3D"2">Can you elaborate on Point 10? Is this "trust and con=
fidence that the communication system works and will always work" or i=
s this "external people using this have trust and confidence that the =
UA knows 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">On Thu, Oc=
t 1, 2015 at 1:44 PM, Sophia Liu <span dir=3D"ltr"><<a href=3D"mailto:so=
phliu@mit.edu" target=3D"_blank">sophliu@mit.edu</a>></span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
#ccc solid;padding-left:1ex"><div dir=3D"ltr">Hey all,<div><br></div><div>=
So this email is going to lay out the goals of effective internal UA commun=
ication that I've thought about, and I invite you to add whatever you t=
hink should be on there. (Feel free to apply all with added points to the b=
ottom of this list or comments on each item!) Over the course of the next w=
eek, 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.=C2=A0</div><div><b><br></b></div><div>An internal communication sys=
tem should be:</div><div><ol><li><b>Transparent </b>(especially for those o=
utside of exec)</li><li><b>Archivable </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 flooded with other things, such as losing UA =
emails in all the other emails that you may have--yes you can use labels, b=
ut 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 use=
d, 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)</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 p=
lace, etc.)</li><li><b>Conducive to feedback </b>(easy to quickly comment o=
n 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 confi=
dence</b></li></ol><div>Best,</div><div>Sophia Liu</div><div><br></div></di=
v><div><br></div><img width=3D"0" height=3D"0" src=3D"https://mailtrack.io/=
trace/mail/878a69fbd64244a9439ce67b65a7f4c8da685f4d.png"></div>
</blockquote></div><br></div>
--001a11471d487e91e70521133808--
