[PAO] 2013 FLWG PA Academy

Mon Sep 16 13:16:19 CDT 2013

That's a great idea setting up a test page to practice on!* That should be
a benchmark training tool. *However, it may be good to note that on the
Facebook page that it is a test page. Instead of closing the page, I would
suggest using the merge feature and absorbing all of the fans and check-ins
into your wing Facebook page. It's easy to do if you are an admin on both
pages.

I was wrong in my interpretation of the regs, but I still stand by not
creating separate Facebook pages for events and sections of a unit. There
is power in numbers. *What you post to your Facebook Page is only seen by
an average of 16% of your fans. *Your post showing up in people's timeline
is based on a algorithm of various factors like how many people like it or
comment on it. If you keep all your activity on one page, it increases the
reach of the message your are trying to get out.

Keeping a single page also cuts down confusion when people are looking for
your page or tagging it in a post. A failed example is a recent post I put
on the FAA's Facebook
Page<https://www.facebook.com/photo.php?fbid=584835464891413&set=a.179563502085280.35688.174311909277106&type=1&theater>.
The "unofficial" CAP page was tagged because it had more fans and came up
first when typing in the photo caption. There is no way to edit after the
fact. Even though only 8,848 people saw this post, it means those 8,848
people may not get the right message about CAP. It's a very common mistake
with tagging posts, which is another reason to have a standard naming
convention for your page -- e.g., "National Capital Wing, Civil Air Patrol"
versus "Civil Air Patrol National Capital Wing" or other combinations. The
tag has to do with the first word in your title.

Paul

v/r
--
*PAUL S. CIANCIOLO, Lt Col, CAP
Public Affairs Officer
National Capital Wing***

Cell: 301-751-2011 <http://www.NatCapWing.org>*
*
Work: 202-385-9599 (@FAA)*
*
**

On Fri, Sep 13, 2013 at 5:53 PM, Jeff Carlson, Group 5 FLWG <
jcarlson at flwg.us> wrote:

> Both Facebook and Twitter were incorporated into the academy’s exercises.
>  Each team was required to post content to the academy Facebook page and
> compose a Tweet that included the academy hash tag.  This was a great
> learning opportunity.  For some members, it was their first time using
> Dropbox, Twitter and even Facebook. ****
>
> ** **
>
> The academy Facebook page was created specifically to be used for the
> training exercises.  I first considered a Facebook group and opted instead
> for a unique page rather than using the main FLWG Facebook site.  This
> gives the option of closing the page after the academy.  We created a
> unique web site that was used during the exercises to create web pages for
> the same reason.  ****
>
> ** **
>
> It was special to see members using social media and making web pages for
> the first time; it peeled away the mystery and they could recognized the
> potential.  It’s one thing to make a list on a PowerPoint slide, it is yet
> another to create an opportunity for practical experience in a guided
> learning environment.  Talk about empowerment!   ****
>
> ** **
>
> The participants learned about utilizing multiple communication channels
> (including CAP radio nets) to gain better control over delivering the
> message and even target a specific audience.  The goal was to get content
> creators to see beyond writing a single release and then hoping to get it
> published by traditional media.  Instead we focused on identifying the
> target audience and selecting an appropriate communication channel prior to
> writing the release and then developing the message based on the interests
> of the selected audience.  We discussed content marketing, developing
> special use web pages and then using Twitter and Facebook to bring the
> audience back to the unit web site.****
>
> ** **
>
> I know every mama crow thinks her baby is the blackest… But this was an
> effective training event because we minimized the passive learning from
> PowerPoint slides and maximized the active hands-on experience which help
> put the key points in real-world context and achieve authentic learning.
> The workgroups allowed more experienced members to mentor their teammates.
>  Based on the feedback I have received from participants, this was a highly
> successful training event!****
>
> ** **
>
> ** **
>
> *JEFFREY CARLSON, Major, CAP*
>
> Director****
>
> 2013 Public Affairs Academy****
>
> Florida Wing Civil Air Patrol****
>
> jcarlson at flwg.us ****
>
> ** **
>
> ****
>
> ** **
>
> *From:* cap-pao-bounces at lists.sempervigilans.org [mailto:
> cap-pao-bounces at lists.sempervigilans.org] *On Behalf Of *Steven Solomon
> *Sent:* Friday, September 13, 2013 2:33 PM
> *To:* CAP Public Affairs Officers
> *Subject:* Re: [PAO] 2013 FLWG PA Academy****
>
> ** **
>
> Maj Carlson's Facebook page for his PAO Academy is permissible and
> appropriate Paul. As per the regulation, below, CAPR 190-1 "encourages" all
> units, including Groups, to create and use social media under the authority
> of the Commander. It makes no difference if the information is posted on
> the unit's main official page or somewhere else. Bottom line is that, we're
> encouraging *more* social media networking, not *less*.
> ****
>
> *b. Social Media. *All levels of CAP, from flights and squadrons to
> National Headquarters, are encouraged to create and use social media to
> help reach out to their membership, potential members, friends of CAP and
> the general public by telling CAP stories on unit social networking sites.
> Units are not required to use social media, but are encouraged to do so as
> resources allow. The responsibility for use of social media by CAP units
> rests with the unit commander and will be overseen by the unit PAO or a
> member designated by the commander under the direction of the unit PAO. **
> **
>
>  ****
>
>  ****
>
>  ****
>
> Regards,****
>
> Steven****
>
>  ****
>
>  ****
>
> STEVEN SOLOMON, Lt Col, CAP****
>
> National Public Affairs Officer
> Civil Air Patrol National Headquarters
> 105 South Hansell St.
> Building 714
> Maxwell AFB AL 36112-5937****
>
> s <ssolomon at cap.gov>solomon at cap.gov <ssolomon at cap.gov>****
>
> Cell: 240-505-6279****
>
>  ****
>
> *[image: CAP Prop Logo 2012 small]*
>
> *... Citizens Serving Communities*
>
>  [image: cid:image001.png at 01CE2BC7.1FAC87D0]<http://www.facebook.com/pages/Civil-Air-Patrol/107647995924164>
>   [image: cid:image002.png at 01CE2BC7.1FAC87D0]<https://twitter.com/civilairpatrol>
>   [image: cid:image003.png at 01CE2BC7.1FAC87D0]<http://www.flickr.com/photos/civilairpatrol/collections/>
>      ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
> ** **
>
> On Fri, Sep 13, 2013 at 10:57 AM, Cianciolo, Lt Col, Paul <
> paul.cianciolo at natcapwg.cap.gov> wrote:****
>
> Not to be a curmudgeon, but doesn't this Facebook Page in itself violate
> 190-1? It may just be my understanding and interpretation though, so please
> correct me. But I thought a social media account is only to represent a
> unit (flight, squadron, wing, etc.) and must be able to be regularly
> updated. Having a page setup for an event doesn't fit into that.
>
> Why wouldn't this info just be posted on the wing Facebook page? There's
> more power in numbers from a central source, especially with Facebook's new
> algorithms for who see's a post.****
>
> Paul****
>
>
> ****
>
>
> v/r
> --
> *PAUL S. CIANCIOLO, Lt Col, CAP
> Public Affairs Officer
> National Capital Wing*****
>
> Cell: 301-751-2011****
>
> Work: 202-385-9599 (@FAA)****
>
> ** **
>
> On Fri, Sep 13, 2013 at 11:42 AM, Jeff Carlson, Group 5 FLWG <
> jcarlson at flwg.us> wrote:****
>
> If you are interested in learning more about the 2013 Florida Wing Public
> Affairs Academy you can visit the Facebook page @
> https://www.facebook.com/FlwgPublicAffairsAcademy?ref=hl for photos and
> videos.****
>
>  ****
>
>  ****
>
> *JEFFREY CARLSON, Major, CAP*****
>
> Director****
>
> 2013 Public Affairs Academy****
>
> Florida Wing Civil Air Patrol****
>
> jcarlson at flwg.us ****
>
>  ****
>
>  ****
>
> ** **
>
> _______________________________________________
> CAP-PAO mailing list
> CAP-PAO at lists.sempervigilans.org
> http://lists.sempervigilans.org/mailman/listinfo/cap-pao****
>
> ** **
>
> ** **
> ------------------------------
>
> *Civil Air Patrol National Capital Wing
> **"Citizens Serving Communities: Above and Beyond"*
>
> *CFC Charity #26757
> **www.NatCapWing.org* <http://www.NatCapWing.org>****
>
>
>
> _______________________________________________
> CAP-PAO mailing list
> CAP-PAO at lists.sempervigilans.org
> http://lists.sempervigilans.org/mailman/listinfo/cap-pao****
>
> ** **
>
> _______________________________________________
> CAP-PAO mailing list
> CAP-PAO at lists.sempervigilans.org
> http://lists.sempervigilans.org/mailman/listinfo/cap-pao
>
>

-- 

------------------------------
Civil Air Patrol National Capital Wing
*"Citizens Serving Communities: Above and Beyond"*

CFC Charity #26757
www.NatCapWing.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sempervigilans.org/pipermail/cap-pao/attachments/20130916/818a3d75/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2324 bytes
Desc: not available
URL: <http://lists.sempervigilans.org/pipermail/cap-pao/attachments/20130916/818a3d75/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2110 bytes
Desc: not available
URL: <http://lists.sempervigilans.org/pipermail/cap-pao/attachments/20130916/818a3d75/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 1370 bytes
Desc: not available
URL: <http://lists.sempervigilans.org/pipermail/cap-pao/attachments/20130916/818a3d75/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 1566 bytes
Desc: not available
URL: <http://lists.sempervigilans.org/pipermail/cap-pao/attachments/20130916/818a3d75/attachment-0002.png>