<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.6" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Cal-MOAA Rally/Annual Meeting</title>
	<link>http://www.cal-moaa.org/blog/2006/11/12/cal-moaa-rallyannual-meeting/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Mon, 08 Sep 2008 13:07:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.6</generator>

	<item>
		<title>by: Phelps</title>
		<link>http://www.cal-moaa.org/blog/2006/11/12/cal-moaa-rallyannual-meeting/#comment-266</link>
		<pubDate>Mon, 08 Jan 2007 06:38:03 +0000</pubDate>
		<guid>http://www.cal-moaa.org/blog/2006/11/12/cal-moaa-rallyannual-meeting/#comment-266</guid>
					<description>Very true.

The CAL-MOAA Rally 2006 was a fine event poorly attended. Why?

MOAA has something like 25 to 35 thousand members in California. A good number of these individuals are not affiliated with a chapter. 

The target for Rally attendance was 500; actual attendance was 50 or so, mainly chapter officers and spouses. I am still convinced the Rally and associated Golf Tournament would have reached or exceeded its attendance goal if every MOAA member in California had been sufficiently informed.

The primary mistake was communications. Few MOAA members knew about the event. Some that did know, didn't grasp that life, including the life of our MOAA, entails a lot more than business meetings. It is enjoyable to do and see things and frequently more fun to do them with others with a similar heritage.

If I had to do it over again, an enticing invitation should have been sent directly to each and every member. I, now with regret, trusted MOAA National, CAL-MOAA, and the individual chapters would fulfill the communications roll effectively. Big mistake. 

To me the MOAA organization is flawed by not assigning each and every member to the chapter in closest proximity to the member. Some chapters are flawed by not being a part of CAL-MOAA. Others are flawed by not effectively passing the word to their membership. 

Without effective communications virtually anything is doomed. The Rally is simply an example. In the military, command and control is essential to an operation - no different in the civilian world. 

Vr,

Phelps Hobart, Chairman
CAL-MOAA Rally 2006</description>
		<content:encoded><![CDATA[<p>Very true.</p>
<p>The CAL-MOAA Rally 2006 was a fine event poorly attended. Why?</p>
<p>MOAA has something like 25 to 35 thousand members in California. A good number of these individuals are not affiliated with a chapter. </p>
<p>The target for Rally attendance was 500; actual attendance was 50 or so, mainly chapter officers and spouses. I am still convinced the Rally and associated Golf Tournament would have reached or exceeded its attendance goal if every MOAA member in California had been sufficiently informed.</p>
<p>The primary mistake was communications. Few MOAA members knew about the event. Some that did know, didn&#8217;t grasp that life, including the life of our MOAA, entails a lot more than business meetings. It is enjoyable to do and see things and frequently more fun to do them with others with a similar heritage.</p>
<p>If I had to do it over again, an enticing invitation should have been sent directly to each and every member. I, now with regret, trusted MOAA National, CAL-MOAA, and the individual chapters would fulfill the communications roll effectively. Big mistake. </p>
<p>To me the MOAA organization is flawed by not assigning each and every member to the chapter in closest proximity to the member. Some chapters are flawed by not being a part of CAL-MOAA. Others are flawed by not effectively passing the word to their membership. </p>
<p>Without effective communications virtually anything is doomed. The Rally is simply an example. In the military, command and control is essential to an operation - no different in the civilian world. </p>
<p>Vr,</p>
<p>Phelps Hobart, Chairman<br />
CAL-MOAA Rally 2006
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
