<div dir="auto">Looking forward to it too! <div dir="auto">- Akinbo.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 8 Jun 2018, 5:38 pm Susannah Gray, <<a href="mailto:susannah.gray@gmail.com">susannah.gray@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi, <br>
</p>
<p>Thanks for your note - I look forward to seeing how we can
leverage Instagram/graphics more then! <br>
</p>
<p>Susannah <br>
</p>
<br>
<div class="m_-1313850054052136758moz-cite-prefix">On 05/06/2018 18:21, Adebunmi AKINBO
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Susannah,
<div dir="auto">Great remark. However, I want to correct a
notion on our work with Instagram. A lot can be passed across
considering that everyone gets to use the website.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Am into graphics and a lot of us needs to
understand that our greatest assets online is the Instagram. </div>
<div dir="auto"><br>
</div>
<div dir="auto">One the graphics points to the content, we are
home and dry. Members of the team can easily adapt and
transfer to adoptive regional platform or channels. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, 4 Jun 2018, 8:33 pm Susannah Gray, <<a href="mailto:susannah.gray@gmail.com" rel="noreferrer noreferrer" target="_blank">susannah.gray@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi John, <br>
</p>
<p>Thank you for sending this. A couple of comments below: <br>
</p>
<br>
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434moz-cite-prefix">On
03/06/2018 10:23, John Laprise wrote:<br>
</div>
<blockquote type="cite">
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">At
Large SoMe Strategy</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">Distributed
ALAC Social Media (SoMe) Strategy</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">Purpose:
To enhance global engagement with At Large and build
awareness</span></p>
</div>
</blockquote>
- Who do we want to engage with us - our fellow At Large
colleagues, other SO/ACs, general Internet community and/or
the general public? <br>
<br>
I believe we should have different strategies and approaches
depending on who we are communicating with and why and this
should be the first thing we document so we are all on the
same page about what we're trying to achieve (happy to put
together a few ideas and circulate if you like). <br>
<br>
For example, if we want to get more people involved, the
messages and possibly the platforms should be very different
than if we want to get current At-Large members to comment
on an ICANN document or plan for upcoming sessions at an
ICANN meeting.<br>
<blockquote type="cite">
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">Constraints:
Global, disparate, multilingual user base with
issues of regional import arising</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">Primary
Media: Twitter, Facebook, LinkedIn, Instagram</span></p>
</div>
</blockquote>
- As others have pointed out, the 'big four' only work in
certain regions and for certain demographics. Russia/China
have their own social networks and anyone under 25 is
probably not on any of these except Instagram (which, in my
possibly Luddite-like view, is not going to be of much use
to us as our content and focus are not very photogenic). I
think it may be a good idea to have each RALO put forth the
networks that work for them.<br>
<br>
<blockquote type="cite">
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">Plan:</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">•
RALO leadership should identify 5-10 top SoMe users
within their constituencies based on
engagement/followers and directly approach them to
be deputy content curators.</span></p>
</div>
</blockquote>
- So the idea is that SoME deputies will forward relevant
content to Evin, who will then post it on the At-Large
accounts (or will she be actively following all the deputies
and simply retweeting/reposting etc?). I think this is a
good plan. <br>
<br>
However, with my organisational communications hat on and as
someone who manages numerous social media accounts on behalf
of others, I'd personally be very wary of publishing content
from an official account in a language that I couldn't
understand in case it was inflammatory/incorrect/not
relevant. I guess we have to be absolutely sure that SoMe
deputies are crystal clear on what kind of content should be
disseminated. Again I think this is something that we should
try to document asap.<br>
<blockquote type="cite">
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">•
RALO leadership should select one of these deputies
to be overall SoMe chair at the RALO level who will
interact with the SoMe working group and with ICANN</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">•
Upon their agreement, those content curators should
share their best At Large relevant content (in
original languages)with Evin @ AtLarge for global
sharing on At Large formal channels. </span></p>
</div>
</blockquote>
- Can we also get a list of formal At-Large channels? <br>
<blockquote type="cite">
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">•
RALOs should compile spreadsheets listing SoMe
handles of ALSs and individual members, country of
origin, and primary language of composition</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">•
These lists should be publicly shared and interested
At Large members encouraged to connect/link/follow
these account to build community sharing capacity</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"> </span></p>
</div>
</blockquote>
- Further, I think we need to separate true social media
channels (FB, Twitter etc) and communication tools
(WhatsApp, Skype, Slack). <br>
The former should be used to push relevant content and
disseminate information. The latter should be for
discussion/news announcements as they are closed groups
populated by insiders and we're not going to reach any new
audiences by using these. <br>
<br>
Thanks again for kicking this off! <br>
<br>
Susannah <br>
<br>
<blockquote type="cite">
<div class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">Best
regards,</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"> </span></p>
<p class="MsoNormal"><span style="font-size:16.0pt;font-family:"Garamond",serif">John
Laprise</span><span style="font-size:12.0pt;font-family:"Garamond",serif"></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif">NARALO
ALAC Representative</span></p>
<p class="MsoNormal"> </p>
</div>
<br>
<fieldset class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Social-media-WG mailing list
<a class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434moz-txt-link-abbreviated" href="mailto:Social-media-WG@atlarge-lists.icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">Social-media-WG@atlarge-lists.icann.org</a>
<a class="m_-1313850054052136758m_6824429631876454101m_-4197504132469596434moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/social-media-wg" rel="noreferrer noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/social-media-wg</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Social-media-WG mailing list<br>
<a href="mailto:Social-media-WG@atlarge-lists.icann.org" rel="noreferrer noreferrer noreferrer" target="_blank">Social-media-WG@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/social-media-wg" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/social-media-wg</a><br>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote></div>