If you’re into nostalgia, you can download the other souvenir booklets, dating back to 2006.
Tag Archive for 'pdf'
Beginning Thursday, February 9th, we will begin our Griffin Lake Performance Simulation. Download and reference the pamphlet “Now that I’m A Christian” as it will serve as the starting point for our discussion on Time management and Goal Setting.
As a point of reference, I’d suggest checking out the following videos on Time Management and Goal Setting.
It was a long process, but I’ve finally finished up the 2010 edition of the Music Ministry Management Guide. I figured I should do something a little different for the year 2010, and so I expanded the concepts just a bit. I was really looking to develop something that was simple enough that people would want to read, but would include enough information that people would find it useful and thereby possibly pass it along.
Finishing up the guide has helped me gain a better understanding as I begin to tackle my Griffin Lake Church project. I was looking for a way to develop an analytics package for congregations that will allow them to see exactly what their footprint was at any given moment, and I now think I’m on the right track.
I’m beginning to think more and more about what projects to tackle in the new year, and how those projects will impact the other elements of my work life. But, enough of that, on to the booklet.
It’s rather large if you’re not on a hi-speed line [2mb]. 37 pages.
Of late, I’ve been developing a system for managing the reporting of layby for our members.
The Layby Package [i'm just going to go with that name] is a really a set of database and merge document that allows a congregation to deliver to its members an overview of their giving, either quarterly, bi-annually, or annually.
The key to the whole package is the record keeping. At The Park [The Magnolia Park Church of Christ], the leadership was planning on implementing a giving campaign to coincide with the already existing building fund plan. The result was a system that was first implemented at the Hallandale Beach Church of Christ – the Victory Campaign. Their plan included a campaign brochure, a presentation, and a pledge card. For The Park, I designed a campaign folio, a presentation, a pledge card, a reminder card, as well as the quarterly statement which outlined each individuals giving for the quarter as well as where they stood in relation to their initial pledge.
Now, the Quarterly statement really began in December, 2007, as we were trying to roll out the official yearly statements for members. We decided that in addition to giving them the official statement with the church seal and everything, it would be nice to let each member see exactly what they gave each week. This, in turn, was well received, as many people were surprised to see the peaks and valleys in their giving throughout various times of the year. At the start of 2008 a decision was made that the initial statement would be developed further to include many elements that would be useful to the member. The Following were added for the first quarter statement:
- My Statement Summary – The statement summary includes an overall synopsis for the quarter, letting the member see their Total given, the congregations giving total, Their total given shown as a percentage of overall congregation total, their Weekly Average, their ranking amongst all givers, and finally, The Forecast of their giving for the remaining three quarters, based on current weekly average.
- My 13-Week Report – A charted representation of the quarter with the date and corresponding amount given.
- My Total Amount Given – Pretty much self explanatory.
- My Average Per Week Giving – The average given as a funtion of overall total divided by the 13 week quarter.
- My Personal Rank – We show a ranking that allows the member to see exactly where they stand numerically. We based the number on qualifying givers.
- My 52 Week Forecast – The 52 Week forecast is a total number for the year based on their current weekly average spun forward for the rest of the year.
- My 13-Week High – The 13-week High shows the Largest amount given in any one week. No provision is given for same high given in multiple weeks.
- My 13-Week Low – The 13-week Low shows the Lowest amount given in any one week. As with the 13-week high, no provision is given for same low given in multiple weeks.
- Congregation Total – The congregation total is a whole sum of givings for the quarter by all members for all collections.
- My Percentage – The percentage function is a showing of the members impact on the overall total given for the quarter.
- The Top 10 Givers – The Top 10 Givers for the quarter shows just that – The Top 10 Givers; No totals, just names.
- Graphical Overview – Lastly, we give a graphical overview of the quarter in terms of congregational giving, the overall average per Sunday, and the Per Sunday total. In the future we plan to make use of the Google Charts API to build individual graphical representations for each member, as well as an internet application for congregations.
In the Future, we look to build an internet application that shows the same information for each member.
What do you think? Is this something that you think your congregation could use? What, if any, layby reporting mechanisms do you use?
I’ve been looking forward to writing on this topic for some time now, but have only now gotten around to actually sitting down and taking the time to organize my thoughts for this particular post.
The Idea of ministry management has become a major sticking point for me as I’ve come to believe that ministry can and should work a whole lot better in the engagement of the members of any particular congregation. Congregations, for the most part, have come to take on the idea that individuality saves the day. However, what I really wanted to do was simply create a working model that could be used as a possible framework for training and development purposes.
So, A Framework?
Well, I continue to feel like the best way to understand anything is to actually learn by doing, and since I couldn’t go out and become minister of an actually congregation, or lead a brotherhood, I figure the next best thing has to be trying to work on building a systematic model of what a brotherhood would look like, with congregations of various backgrounds and standings. I wanted to build something that was both easily understandable, yet at the same time was built with a sense of reality, that a user could imagine being at any particular congregation within the brotherhood.
In developing my faux brotherhood, I took into consideration a few things that I felt were necessary elements in building something that was feasibly understandable. Looking for ways to make this whole project manageable in the long run, I set in place some parameters for my brotherhood.
- The local brotherhood could have no more than 15 congregations – I actually came in under the allocation of 15 congregations (13), leaving two out for future purposes. I chose the number 15 as a limit because I didn’t want the entire process to become so expansive as to limit functionality. In a very large local brotherhood with every congregation having fully developed, active ministries, I just felt that planning, even fake planning, would become a task too major to handle effectively.
- I would stick to realistic numbers for the brotherhood – You aren’t going to typically find a brotherhood with massive attendance numbers, so I really wanted to stick to the reality of the actual brotherhood numbers. In writing The Music Ministry Guide, I did a lot of research on the brotherhood-at-large and realized that the total brotherhood is not as large as I thought, and so, my planning reflects that.
- Financial Numbers should reflect actual trends – I built my own scale using financial data that I found at various congregations. Basically, I looked at membership numbers and total giving, and built a simple formula for individual member giving per week and then simply expanded it forward for an entire year.
Now, all of this really is extensive when you understand the actually scope and focus of this research and modeling, and that is simply to develop a single congregation model. I wanted to develop a single congregation for training and development purposes, but when I began building the framework for Griffin Lake church of Christ, I quickly realized that a congregation can’t stand alone, and must therefore be a part of a larger brotherhood. The more I thought about it, the more the reality of an entire brotherhood being built looked feasible.
Now that I have a simple framework to build the rest of my model on, I’ve looked to start planning out the rest of the project. I figure to begin working on the rest of the project immediately.
In last week’s post, I ran down the list of accomplishments for the week, looking at the things we had begun to do in the planning of the 2010 Christian Acappella Music Awards. This week, I figured I’d write about the things we didn’t quite get a handle on, and our ability to reconcile those problems that are seemingly on the horizon.
In terms of show planning there is generally a sense of wanting to simply take the formula that worked and duplicate that over and over again. The shows in 2006 and 2008 were overwhelming successes in terms of planning and execution, and so there is that desire to place the same emphasis on those things that worked for us. The main problems with doing so are 1. The Logistics suggest that we’re playing with a different beast in Atlanta, and, most importantly 2. Show #10 has to be our best. I state point number two, not because it’s seems over the top, but because there really is no room for a slip up in planning or executing CAMA 2010. It really does need to be our best program.
I’ve begun to dissect the map of Georgia [click graphic to enlarge], breaking down every one of the 159 counties and developing a strategy for marketing in those areas that have the highest concentration of congregations. I plan to develop similar maps of Florida and Tennessee, though those will be secondary to the Georgia map and rely primarily on information that I already have stored. In the past 6 months I’ve been able to collect an extensive amount of information on churches in the South and Northeast regions of the United States and hopefully this will suit us in our future planning.
Now, going forward, there is a need to begin looking at the management of the promotions at The Southeastern Lectureship as well as some local marketing opportunities in Jacksonville in November and other concerts in the northern part of Florida. As I continue to develop the protocol for submissions for 2010, I already know that there will be 30 categories in 2010, including the Rubal Lifetime Achievement Award, Artist of the Year, Album of the Year, and Song of the Year. Outside of those, I think every other category is in play at this point as we look at the best fits for 2010.
As I continue to redevelop the new Media guides for 2010, here are the guides from 2006-2008. They’re in PDF Format, for easy downloading
In addition, I also produced a first edition music ministry guide on the behalf of NACAMA that was not released. We decided to continue developing material and produce a greater volume. But here is what was created.
I had the opportunity today to put in some work on the projects I’ve been managing lately and I must say, I am excited to be working on them. It gives me a chance to both fine tune my design skills while also helping to develop my ability to problem-solve by way of solutions development.
Anyway, one of the pieces I’ve been working on has been a 4-up version of the song service planner, small enough to fit in a pocket.
As I’ve written on previous occasions, I am working on a couple of ministry tools for download on this site. This has given me a lot of needed practice in the idea of Prototyping, the art of building a working rough draft.
Interesting to me is the idea of needing to develop a prototype of what is essentially paper crafts, but I’ve chosen to use the process to have what I feel is a dry run or personal pre-release. Each document carries a different purpose, and so, there are inherently different uses for prototyping.
For example, I, of course, am not a performing artist, and therefore the Gig set list and Artist Sales Tracker are really just documents I’m using in a simulated fashion, imaging that I am in either situation. For other documents, like the Bible Study Module, I am actually using this in a practice and am actively revising certain elements by the minute. Just recently, I’ve realized that I would like to have an element that allowed me to track the time I’ve spent studying, and so that is a piece that I’ll be including.
Another piece that is important to me is building something that is accessible and would not require any other modifications from the end-user. This, to me, means that I’ll probably be releasing soft-versions of all of my documents and also continuously updating documents.
Finally, I have an extreme interest in developing online counterparts to each of these pieces, so I’ll also be looking at the software side of prototyping.