<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://experience.fellowshipone.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Delivering Change : teams</title><link>http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/teams/default.aspx</link><description>Tags &amp; Topics: teams</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61120.2)</generator><item><title>What did you learn today?</title><link>http://experience.fellowshipone.com/blogs/deliveringchange/archive/2008/02/13/what-did-you-learn-today.aspx</link><pubDate>Wed, 13 Feb 2008 04:53:00 GMT</pubDate><guid isPermaLink="false">87eee960-b871-44cb-8a98-02588a960c04:9833</guid><dc:creator>FTDeliverySvcs</dc:creator><slash:comments>0</slash:comments><comments>http://experience.fellowshipone.com/blogs/deliveringchange/comments/9833.aspx</comments><wfw:commentRss>http://experience.fellowshipone.com/blogs/deliveringchange/commentrss.aspx?PostID=9833</wfw:commentRss><description>&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT size=3&gt;&lt;FONT face=Calibri&gt;As delivery managers, we have a responsibility to wisely use the time and money provided by the local church to implement Fellowship One.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;We are called to help empower the church to more efficiently bring people to the table of the Lord.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;I often view myself as an educator (amongst other things).&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;I am here to help people understand how to use Fellowship One in their unique environment, and use the wonderful technology we posses to empower the local church.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Sometimes people embrace this, other times it can be more confrontational to get people to leave the comforts of their current church management system and learn something new in the name of progress.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;It requires people to leave their comfort zone and make themselves vulnerable, not many people like leaving anywhere comfortable.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;The delivery team at Fellowship Technologies is an evolving team.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;There was a day and time where we were all cowboys (and cowgirls), roaming the countryside, going from church to church, each doing our own thing as we best saw fit.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Those days are long behind us, and it hasn’t been a painless road, I must confess.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;But I can tell you that the changes we have made have been for the best.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Without a structured process and product (being the service we deliver), we would lose our departmental and corporate identity.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;We now produce a better, more standardized product, and hopefully a more efficient process, leaving us more time to deal with process change within the church itself.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;In order for this to work, people must be open to change, and if necessary, the pain that goes along with it.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;I have been delivering the Fellowship One product to churches now for over 2.5 years and I have learned so much during my tenure.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;I have realized that, yes, I am a teacher to many, but those many are also teachers to me.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;EVERY church I work with teaches me &lt;I style="mso-bidi-font-style:normal;"&gt;something&lt;/I&gt;.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;It’s that something that everyone in my team brings to the table at regular intervals to help us produce a better, more refined product, making better and better use of the church’s time and money.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Without you teaching us about you and what you do, we become stagnant and stale and the product no longer evolves.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Each delivery manager learning something new puts us in a vulnerable place.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;We have to ask ourselves if what we did before was the best way to do things.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;If the answer is no, we have to admit we could have done things better and continue to work hard to discover where we fall down.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;We do this all in the name of helping you, the local church; more efficiently bring people to Christ.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;If I don’t learn at least one thing new during the implementation with a church, I feel I have failed the church, myself, and my future clients (even if it means learning how to be patient!)&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;I encourage all to make a conscious attempt to learn &lt;I style="mso-bidi-font-style:normal;"&gt;something&lt;/I&gt; daily that will help you tomorrow and the rest of your days.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;And please never stop being a teacher.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;We’re a team, and we NEED each other to help make the team successful.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Blessings -&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Jeff Lewis&lt;BR&gt;Delivery Manager&lt;/FONT&gt;&lt;/P&gt;&lt;img src="http://experience.fellowshipone.com/aggbug.aspx?PostID=9833" width="1" height="1"&gt;</description><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/teams/default.aspx">teams</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/Delivery/default.aspx">Delivery</category></item><item><title>Silos… The Unspoken Barrier to Ministry</title><link>http://experience.fellowshipone.com/blogs/deliveringchange/archive/2007/12/05/silos-the-unspoken-barrier-to-ministry.aspx</link><pubDate>Thu, 06 Dec 2007 04:40:00 GMT</pubDate><guid isPermaLink="false">87eee960-b871-44cb-8a98-02588a960c04:9190</guid><dc:creator>FTDeliverySvcs</dc:creator><slash:comments>1</slash:comments><comments>http://experience.fellowshipone.com/blogs/deliveringchange/comments/9190.aspx</comments><wfw:commentRss>http://experience.fellowshipone.com/blogs/deliveringchange/commentrss.aspx?PostID=9190</wfw:commentRss><description>&lt;p class="MsoNormal" style="margin:0in 0in 10pt;"&gt;&lt;font size="3"&gt;&lt;font face="Calibri"&gt;My name is Matthew McMaster and I have been a Delivery Manager at Fellowship Technologies since March of 2004.&lt;span&gt;&amp;nbsp;&lt;/span&gt;In that time I have implemented over 100 churches. Some of them have been very sophisticated in how they communicate within their ministries but many of them have a real silo issue. When each ministry functions as its own separate entity with little or no regard for the larger entity (The Local Church) as a whole, you have a group of silos; not a unified team. An example of this would be when the Youth Pastor gets their new students to fill out a first time visitor card. This seemingly ordinary process is really masking a silo issue. When you look closer at the first time visitor card you will notice it is missing some very important information. What are the parent’s names? Do they have any siblings and what are their ages? What is the best way to get in touch with the parents? Do they have a church home? Now the Youth pastor might say, “That information isn’t necessary for me to reach that student.” This is a silo mentality. The Youth Pastor is forgetting that the student is part of a larger entity of the family. Each member of the family is a potential soul needing to be reached. Each member of the family is the target market for other ministries at The Local Church.&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p class="MsoNormal" style="margin:0in 0in 10pt;"&gt;&lt;font size="3"&gt;&lt;font face="Calibri"&gt;Another example of a silo that I have seen involves working with multiple ministries trying to coordinate volunteer activities. There really is a best first time visitor with children process and it involves “Super Greeters” that can escort a family from one classroom to another explaining the check in and pick up processes. These “Super Greeters” naturally come from the Greeting team which is a separate ministry from the children’s ministry. I have heard from the leaders in this ministry on many occasions, “Why do I need to staff Greeters in the Children’s Building? That is their responsibility!” This silo mentality is detrimental to the volunteers as well as potential guests.&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p class="MsoNormal" style="margin:0in 0in 10pt;"&gt;&lt;font size="3"&gt;&lt;font face="Calibri"&gt;There are many other types of silos but I think you get my point. So now you must be wondering, “What do I do to break down those silos?” The answer is deceptively simple… Cross functional Teams. In future blogs, I will discuss two specific cross functional teams but you can have many more. The first is the Fellowship One Champion Team and the second is the Data Integrity Team. In my next entry, I will be discussing how the Champion Team functions.&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;
&lt;p class="MsoNormal" style="margin:0in 0in 10pt;"&gt;&lt;font size="3"&gt;&lt;font face="Calibri"&gt;Matthew McMaster&lt;br&gt;Delivery Manager&lt;br&gt;Fellowship Technologies.&lt;/font&gt;&lt;/font&gt;&lt;/p&gt;&lt;img src="http://experience.fellowshipone.com/aggbug.aspx?PostID=9190" width="1" height="1"&gt;</description><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/First+Time+Visitors/default.aspx">First Time Visitors</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/Volunteers/default.aspx">Volunteers</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/Student+Youth+Check-In+Name+Tags/default.aspx">Student Youth Check-In Name Tags</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/silo/default.aspx">silo</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/teams/default.aspx">teams</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/Best+Practice/default.aspx">Best Practice</category></item></channel></rss>