Fall IT Roundtable Invitation

I was part of a group of IT leaders from very large churches that met a couple of times a year for three years or so. The group (which never had a name other than “megachurch IT group”) included Mike Gold of Willow Creek, Terry Chapman of Fellowship Church, Vic Mollett of Southland Christian Church, Eric Busby of Saddleback Church, and others. When last we met in May of 2005 I told the group I would host the next meeting here at Church of the Resurrection in the Kansas City area in 2006. Unfortunately, I got slammed last year with workload and staff turnover issues so I wasn't able to make it happen. I recently exchanged e-mail with Mike Gold about renewing my invitation to host the group here and suggested merging the group with the Church IT Roundtable. He was very supportive and hoped to be able to attend and invite the old gang to join the Roundtable.

Accordingly, we would like to invite you to come to Kansas City for the Fall Roundtable October 3-4, which is right before Leadership Institute, our biggest conference of the year. After the Roundtable you could stay for Leadership Institute if you’re so inclined. I spoke with Tony Dye about getting this on the agenda for discussion at the Spring Roundtable to determine the level of interest. To get the conversation started, please leave a comment here and let me know if this sounds good.

National Church IT Association?

If you read Jason Powell’s blog, you already know about his hope to create some sort of national church IT association. (Tony has arranged for Phill Martin of NACBA to come to the Spring Roundtable to speak about this.) Now as for me, I strongly prefer the roundtable format for meeting with and learning from other church IT leaders. I worry that formalizing and scaling up what we’re doing into a national association would result in losing the powerful, peer-to-peer sharing of the roundtable format. I also worry that we’ll discover even the 25-30 people expected to attend the Spring Roundtable will be too many for everyone to fully participate. So what to do?

Fall Roundtable Format

Now here’s where it gets really exciting (we think?!) or maybe even crazy. For the last couple of years I have been meeting informally with church IT leaders here in the Kansas City area such as Mike Mayfield of Pleasant Valley Baptist Church. I suspect many of you have had similar meetings with other church IT leaders in your own cities. Perhaps some of you have already held roundtables in your cities. This makes me wonder if the best way for us to scale up would be to have roundtables in cities across the country and then link them technologically.

What if we made a first effort at this idea for the Fall Roundtable? What if we limit attendance here in Kansas City to 15-20 people and find some great way to link in roundtable groups from other cities? This idea is partially inspired by the Willow Creek Leadership Summit that brings together church leaders from around the world. We’re imagining some kind of “un-conference” that retains the strengths of peer-to-peer sharing but is scalable to involve many more people than you can fit around one table. We would like for everyone to be able to see/hear each other and use their own laptops to annotate/live blog the discussion and have side conversations. We’re not even close to figuring out how to do this from either a facilitation or technical standpoint, but one idea is to use Adobe Connect (formerly Macromedia Breeze). Whatever the mechanism is, we would need to fully test both the technology and the method of facilitation prior to the meeting. And, no doubt, we’d learn a great deal from doing this once. At that point we would know either a) this works; b) this works but needs to be tweaked/improved; or c) it doesn’t/can’t work.

Please comment and let me know your thoughts or post on your own blog and link back to this post.

Don't you be doing that church hop

Perry Noble points us to Steven Furtick blasting church hoppers/church shoppers like I've never seen it done before. I was fired up by his comments. On the other hand, I have good friends who have struggled with finding the right place where God is calling them to worship, grow, and serve. There's a line between a genuine spiritual struggle and a crassly consumerist attitude toward church.

The best approach for churches is to reach out and welcome everyone with all of their experiences, sins, mistakes, bad hair, doubts, fears, body odor, struggles, biases, broken relationships, addictions, questions, emotions, mental illness, inappropriate behavior ... and yes, even warped attitudes towards church. We start with people wherever they are. And then, pay close attention here, we must rely on the power of the Holy Spirit to work through our teaching, worship, service, and deep Christian community to transform them. No doubt some of those people have been church goers for years, yet they haven't learned even the basics of Christian discipleship. Instead of giving up and calling them out, let's call them up to a richer, fuller, deeper understanding of what Jesus asks of them. To be clear, I'm talking about starting with people where they are, but not being complacent about letting them stay there.

Web Software Developer position open

We're seeking a highly-skilled web software developer for a challenging and fulfilling position at The Church of the Resurrection (Kansas City area). Work in a high-energy, innovative environment with other talented technologists. BS in computer science or related field or equivalent experience required. Minimum of 2 years professional experience with the LAMP platform and 2 years professional experience with the .NET platform. Reports to the Director of Information Technology. Don’t miss this unique opportunity to serve Christ with your software development skills. To apply, please e-mail Cork Kurlbaum (our uber-volunteer/professional IT recruiter) for immediate consideration.

Five hot technologies for 2007

Yesterday Computerworld published an interesting article predicting five technologies will be hot over the next 12 months:

1. Ruby on Rails - web application development framework

2. NAND Flash drives - solid state mass storage with big enough capacity to substitute for small hard drives and 100x the performance

3. Ultra-Wideband (UWB) - short range wireless at 200x the speed of Bluetooth

4. Grid Computing - rent a data center by the gigabyte such as Amazon's S3 service

5. Advanced CPU architectures on higher-density chips

Y2K7

I just spent all day yesterday, along with a co-worker, tracking down one of the more heinous time calculation bugs I've ever seen. If you're a programmer, you probably already know about the Daylight Savings Time change that is occurring in this year of 2007. This is sending a shock wave of problems through the IT industry on a scale of which we probably haven't seen since Y2k. Everyone is having to update code that calculates when DST begins and ends.

In short, Microsoft is either in a very tight spot, or they screwed up big time. With the new calculation of DST, any year previous to 2007 now has the potential to show the wrong time! Here is a quick example.

This page is using JavaScript within the viewers browser to calculate dates. You will notice that if you are viewing this page from Vista, or a Linux based OS, that all the dates are displayed as expected. If you're on a Windows XP or earlier OS, the middle two dates will show as being in DST when they should not be:

Wed Mar 15 00:00:00 CDT 2006 <- Um, not quite yet actually. CDT doesn't start until April 02, 2006 02:00.

This is because MS OS' previous to Vista can only store one set of DST rules. So when you installed that cool new patch that fixes 2007 and future dates, you break every year previous to it. Nice. Granted this only crops up in past dates between the previous DST starting time, and the new one. I.e. between 2007 and 2006, this is between March 11 and April 2. See another conversation on this.

This is going to cause problems until it is fixed. Hopefully MS can get us something quickly, but depending on how deeply the OS is affected by this - they could have a serious issue on their hands.

Kathy Sierra on user happiness

Kathy has an excellent post today on what happens when the "policies and procedures tail" wags the "user happiness dog." I continually remind my IT team here at Resurrection that our job is to serve users, not the other way around. My team has a lot of ideas about how to increase our efficiency, which I think is great so long as it doesn't make things more diffcult for those we serve. Do you advocate for users in your organization?

Skypecast - Cooler than I Thought

I came across the Skypecasts beta directory on Sunday, I don't even remember how. I have been aware of Skypecast for quite a while now through Jason Powell's blog, and had always thought of it as an alternative to hold on-line meetings. I was blown away to find a directory of open discussions taking place about all sort of subjects!

I clicked on a "Join this Skypecast" link for one of the entries, and found myself listening in on a Arabic speaking discussion as though I was standing in a public square in Saudi Arabia and just walked up to a group of people, listening to the conversation. This is wild!

I began thinking, the potential of this is huge. This is not just free conference calling, this is a globally accessible public forum. If you want to hold a discussion on any subject all you need is to download Skype, advertise the discussion in whatever manner you chose, and host and moderate it. The barrier to holding a discussion is broadband Internet access, a computer, a headset with microphone, and the knowledge to get Skype installed and a Skypecast created. This is exactly the flat world that Thomas L. Friedman discusses in The World is Flat. I found people hosting their own sociological and political discussions, some of them with very controversial subjects, with people from all over the world participating.

Think about that for a moment. If you were to mash the technical ability of Skypecasts up with the right social networking service, you could bring a great deal of the worlds population closer together than ever before. Say you're a student and you are writing a paper on antibiotic resistance. You've got a few questions that you're not able to answer through the Internet resources, so you set up a Skypecast for next Wednesday evening and publish this event through a social network service, asking for help from any experts on the subject. On Wednesday you get to talk with a couple other people writing similar papers and you all share resources, and in the middle of that you get a leading expert join in that has seen your advertisement for the discussion and now multiple people benefit.

The potential uses for churches and small groups really excites me. Imagine a globally diverse small group that anyone can be a part of, or just listen in on. A pastor can host a discussion on applying the scripture to your life, and interact with real people with real questions in a moderated format. I think these sorts of technologies will ultimately re-define the roles of evangelism and caring in the physical church to include the global community. The phrase, 'your neighbor,' will not mean what it used to mean.

I haven't posted here much, so to reiterate why this interests me so much, I am very driven to get churches on-line. By that, I mean encouraging churches to utilize web ministry and enabling them to use technology for ministry and evangelism. Why? Because I strongly believe that on-line evangelism will be highly important in reaching future Christians, and that God has many great things in store for technologies such as Skypecast and social network services.

United Methodists Reaching Postmodernists

A disappointing thought crossed my mind as I drove home early Saturday morning from a late night out. (The late night BTW was much less harmless than it sounds. My wife and I attended a high school musical in support of a friend, and we stayed up late conversing about different subjects.)

What if, on the whole, the United Methodist church can not reach postmodernists? I mean simply can not do it. What if the things that make a worship United Methodist are exactly those things the postmodernist revolts from?

I began thinking about the church reaching the postmodernist, and recalled conversations that I've either witnessed or been a part of. They all go something like this:

UM Pastor: "You say that the service doesn't speak to you, but give me an example of how would you change it?"

Postmodernist: "There needs to be more music. It needs to be cool, not boring. Hip! It needs to be more emotional and less institutional."

UM Pastor: "But those are not specific examples of what you would change about the service today. I understand what you said, but I don't understand how you want us to do that."

The conversation usually goes down hill from there, with the postmodernist trying desperately to explain what hip and cool means and how they could be so very moved if it were done better. Both parties walk away having no idea what the other meant.

I've heard at least one pastor explain this as, "They aren't able to explain what they want." That baffles me, as I'm pretty sure I just saw human beings who speak the same language converse about what they want. This ends up sounding like the modernist saying they are open and willing to improve the worship experience, as long as they don't have to change anything about it at all. Why can't you just be happy with the way it is now?

To me it comes down to this: The answer that modernists are looking for is which portions of the service today need be changed to reach postmodernists, without changing or losing the structure of the worship? What the postmodernist is trying to answer politely - everything. That being said, I'm sure there is a middle ground. I believe that churches that are successful in reaching postmodernists are those finding ways to say yes rather than no, and still hold in their hearts the significance of denominational traditions. Those that tie the significance of a worship service too tightly to the rigid procedural tradition may have a really tough time reaching postmodernists.

Where does your church apply the significance of worship? The process, or the expression? Are they doing church, or being the church?

Mac vs. PC

"As a Mac user, I wish Microsoft would run an Apple-like ad about the process by which Mac users get service for broken hardware. It would be really hard for Apple to respond, because their system for dealing with broken hardware is itself horribly broken. They need serious incentives to fix this." - Dave Winer

Just last week my team at Resurrection and I were joking about exactly this idea. (We support both PCs and Macs.) The Apple commercials are terribly funny, no doubt. But Apple would have you believe that their stuff never breaks. In our parody commercial, Mac would be broken and a poor, hapless user would be striken by the question, "How do I fix this thing?" PC would answer, "I don't know." Then the user would ask, "Who DOES know?" Followed by nothing but dead silence.

When PC is broken, we call our friendly Dell service person, who comes out a day or two later and fixes it. It's painless and nearly effortless. When Mac is broken, we are faced with a small number of bad options, all of which will cost us a lot more time and brain damage than calling Dell. Surely Dave Winer and us aren't the only ones who have faced this issue. Does Apple care?

Visual communication

I've posted before about the importance of visual communication in our world. Unfortunately, I've spent my whole life honing my ability to communicate with words. That skill will be nearly obsolete by the end of my life. Seth Godin points us to an example of how ordinary people can use video technology to communicate. Wouldn't it be cool to use this video to teach church staff about web technology? Would it be even cooler for all of us to learn how to communicate this way?

From Vision to Reality

This past week in our bi-annual all staff meeting Adam, our senior pastor, said something that coalesced a reoccurring thought I'd had for a while. He mentioned a list of large projects our church had either completed, or moved from the idea stage to a living process. Then he suggested that to do this repeatedly and continually succeed you have to go through a strategic planning stage. That's a simple statement right? So now - everybody go do that and succeed much more often .... If only it were that easy.

I'm sure that statement is in a thousand books and repeated by even more people, but the reason I'm blogging about it today is that it seems to be one of those statements where the absorption and understanding of it are worlds apart from the action and ability to perform it. Why is that? Is it simply a factor of the human condition, or is a skill that can be learned and honed? I would lean toward the latter.

Pastor Andrzej from
Katowice, Poland

The idea that strategic planning is a critical ingredient of any vision to reality project is at first too simple to be so profound. One of the questions I have been asked on multiple occasions, after people learn I work at Church of the Resurrection, is "Why is Resurrection so successful?" The last time I was asked this it was from pastor Andrzej while I was visiting him in Katowice, Poland. Pastor Andrzej has been a United Methodist pastor for more than 25 years and is currently positioned in a thriving church with a congregation more than 100 strong. To put this in perspective, the United Methodist presence in all of Poland is less than 4,500 people.
Pastor Andrzej, spoken in my poor English as "ahhn-jay," is a person who comes off very calm, with waters just underneath the surface that are roaring to bring God's Word to the non religious.

Up until now, my answer to the above question has been these things, in short: One is leading with prayer. Another is effective leadership, and the last is an uncommon hive of people who possess a drive from within to do things with excellence. These are still accurate, but what I may now add to those is effective strategic planning.

I think if there were a great suggestion for pastors striving for success in ministry, it would be to educate yourself in strategic planning. When Adam spoke about this at our all staff meeting, Andrzej came back to my memory. He and I had discussed the importance of prayer, and asking for God's guidance. No one should underestimate this, but God rarely lifts those of us up who are sitting back waiting for Him to take the wheel and drive.

It made me wonder what programs or resources we have set up for our local pastors, as well as our International pastors. I couldn't find much searching through Google, though it may have been the keywords I was using. My co-worker Chuck, who you can see in this post's picture, recommended this book by Kennon L. Callahan.

Would anyone else who has read this recommend it? Does anyone know of other resources out there that focus on strategic planning in the church?

Nerds on retreat!

We got out of the office for a day-long retreat yesterday. Most of my IT team was there:




Clockwise starting from left (goofy guy with Texas Tech t-shirt):
Chuck Russell - Internet Communications Director
Jeremy Grabrian - Desktop Support Specialist
Ian Beyer - Network Administrator
George Smiley - Desktop Support Technician (part time)
Brian Slezak - Software Developer
Leo Johns - web consultant (part time)

Oh yeah, and the end of the table with a laptop, a flat-panel monitor, and no one sitting there - that's me. ;-)

Fun With Statistics

So I am perusing the new Umc.org and looking at findachurch - which has been vastly improved - see Resurrections Page here. I decided to play around with the Advanced Search functions - mostly because I couldn't type in 66062 - my zip code, and see Resurrection come up - that's crazy do you know how many resurrection people don't live in the Church's zip code - I'll tell you - most of them, anyway tangent averted back to my point I found some interesting stuff when i searched for churches by size. Here are my results (More than 1000 means between 1000 and 2000 etc)

33 United Methodist Churches with more than 2000 in attendance
136 United Methodist Churches with more than 1000 in attendance
649 United Methodist Churches with more than 500 in attendance
3093 United Methodist Churches with more than 200 in attendance
5348 United Methodist Churches with more than 500 in attendance
8746 United Methodist Churches with more than 50 in attendance
10905 United Methodist Churches with more than 20 in attendance
4648 United Methodist Churches with less than 20 in attendance

So 818 who have made it to 500 + and 3900 approximately who have made it over the 200 barrier. Interesting stuff. Of course since our worship attendance is over 8000 now and they have us listed at 6300 (This is GCFA's fault not UMC.org's by the way) - I dont know how accurate those counts are but there probably pretty close.

Chuck

Who is using the new Blogger?

Who out there is using the upgraded version of Blogger? Is it cool? Should we upgrade?

MailFrontier is nearly perfect again

Last week we finally had time to focus on our spam problem. With some assistance from our friendly SonicWall tech support person, we installed a software update and tweaked our configuration. Turns out that at some point we white-listed everything from cor.org, no doubt to address a false positive situation, but that was a bad idea - too much spam is spoofed to come from your own domain. With the new software and the tweaks, we're back to nearly perfect, and just in time for the long Christmas-New Year's break when many of our staff take vacation. Almost no spam is getting through to our users' inboxes. Wee hoo!

SonicWall, I owe you an apology. When properly configured, SonicWall Mail Security is every bit as good as the spam filter built-in to Outlook 2003.

Guy Kawasaki talks about evangelism - the Christian kind

In case you missed it, I found it very interesting to see Guy Kawasaki reveal a bit of his personal faith in this recent blog post. In the post he includes this link to presentations at a church leadership conference in Hawaii this Fall. I'm glad to know Guy is interested in the original meaning of evangelism and not just his borrowed use of the term.

WEC Update

Now that Web Empowered Church (WEC) has been underway for a couple of years, Mark Stephenson has come to the belief that it won’t reach its full potential without Church Management System (ChMS) functionality, or at least deep integration with an existing ChMS. I totally agree with that assessment. So Mark and I thought it would be a great time to get together with Rubin Perry to discuss how ChMS fits with WEC’s vision and strategy. Like my meetings with Fellowship Technologies and Shelby Systems, our conversation was detailed, candid, and thought-provoking. While I’m not free to disclose everything we discussed, I can say that WEC has deep pockets, a passion for helping local churches use the Internet effectively, and a long-term view.

I’ve noted previously that combining content management (CoMS) functionality with ChMS and Constituent Relationship Management (CRM) functionality in a single, integrated system would be ideal. Most forward-thinking church IT leaders I know agree with this. WEC is looking for churches and church IT leaders who will partner with them to build just such a system based on the LAMP stack and TYPO3. As I mentioned, another possibility would be to do a deep integration of a market-leading ChMS with TYPO3. We’re in the process of discerning whether it makes sense for Church of the Resurrection to be one of those partners.

WEC is fully committed to open source software. By that they mean basing the software on the LAMP stack, licensing the software they develop using the GPL, and employing open source development methodologies. The advantages of this include risk reduction, ease of integration, competitive diversity, and distributed innovation. Already WEC is being adopted by churches around the world that have the technical ability to make use of complex technology. Such churches appreciate the fact that open source means WEC doesn’t have the licensing cost barrier associated with commercial software.

For churches that lack technical skills, however, adoption is challenging. TYPO3 is more than powerful enough for even the largest churches, but it is quite complex, it is difficult to learn, and it suffers from poor usability in some areas. Accordingly, addressing these issues represent top priorities for WEC.

1. WEC is actively working with the TYPO3 Human-Computer Interaction (HCI) team to improve usability.
2. WEC is developing TYPO3 training videos.
3. WEC is working on improved processes for providing tech support.

So that's a summary of how WEC fits into our ChMS analysis. I'm praying for clarity.

Ben Hill UMC

On Wednesday I had the pleasure of visiting Ben Hill United Methodist Church, just a few miles from the airport in south Atlanta. The Foundation for Evangelism’s technology leader, Rubin Perry, is a member of that storied church and one of its hardest-working unpaid servants. After 100 years of ministry, Ben Hill is still learning, growing, dreaming, taking risks, and serving. It has purchased the former headquarters site of Delta Airlines, a large acreage with a number of corporate-style buildings that have been sitting vacant for 20+ years. The site, adjacent to the Greenbriar Mall in Atlanta, has huge potential but carries many challenges. With Rubin helping to manage the project, the church is in the process of remodeling and renovating the first building, which will be used as a worship center when completed. The Holy Spirit is moving at Ben Hill and for that I say, “yeah God!”

The Spam Wars – What Does Microsoft know that SonicWALL doesn’t know?

The New York Times confirms that spam is getting worse, due primarily to two factors: 1) spammers are using farms of spambots running on insecure computers, which are abundant in homes with cable modems, making it ineffective to identify spam by originating IP address. Distributed security threats are always more difficult to block than localized threats. 2) A new type of spam with the message in an image that’s changed slightly each time it’s sent, making it impossible to recognize spam by a checksum on the contents.

I mentioned that the effectiveness of our spam filter, SonicWALL Email Security (formerly MailFrontier), is declining. On the other hand, it seems that Outlook 2003’s junk filter is keeping up. Since I began my experiment the week of Thanksgiving, I'm seeing 94-99% daily effectiveness from Outlook 2003 alone (with MailFrontier disabled on my mailbox). Yesterday it was 100% effective. Other staff we put on Outlook 2003 for our test have given similar reports.

What does Microsoft know that SonicWALL doesn't know? Why would we pay SonicWALL thousands of dollars per year for filtering that is LESS effective than the filter built-in to Outlook? Jerry, my SonicWALL reseller, has tried to get their attention. I also e-mailed one of their product managers nearly two weeks ago, with no reply at all so far. Jerry says we should hear something on Monday. Grrr.

Flurry of posts

Look out for a flurry of posts from me. It's amazing how much writing you can do in an airport and on a plane with no Internet. ;-)

Speaking of the airport, this is what greeted me when I tried to check the price to get WiFi today in Atlanta ...







Note: Because you are using an outdated browser, you may only view the raw textual content of this site. In order to view, use, and enjoy this site to the fullest at the maximum security level, please refer to our Browser Upgrade page to view a list of browsers that support web standards.

Let me see if I have this right, Sprint. I’m using an OUTDATED browser (IE 7) that should be UPGRADED to something that supports WEB STANDARDS (such as IE 6)??? You guys have had months to fix this page. Doesn’t anyone at Sprint use Sprint’s WiFi in airports? Haven’t at least some of them upgraded to IE 7? Even if they were asleep, it’s difficult to understand how they could have missed this. (Yes, Sprint is our friendly, neighborhood, telecom company located only two miles from Church of the Resurrection.)

Which ring makes the most sense?

Here's how I see the Church Management System (ChMS) marketplace. We're confronting the question of which ring of the market makes the most sense for us.


As you move in toward the center, the functionality is a closer and closer match to our requirements, but fewer and fewer organizations will be running it. On the outer rings, more organizations are innovating and influencing the feature set. On the inner rings, fewer organizations are innovating, but the features are more likely to be directly applicable to us.

Atlanta, here I come

This week I'm going to Atlanta to meet with Tony Dye as well as Mark Stephenson and Rubin Perry. Tony has graciously agreed to show me around Perimeter Church, introduce me to his A-team (A is for "awesome"), and talk about Church Management Systems (ChMS). Mark is joining in on the fun. Separately, Mark and I are going to meet with Rubin at Ben Hill United Methodist Church to talk about WEC's fledgling ChMS project.

This is my second trip exploring ChMS options, following my trips in October to Fellowship Technologies and Shelby. I should know by the end of next week whether my budget request to replace Shelby V5 has been approved for 2007.

Point, click, make a product to sell to the world

My friend Jay points us to Amazon's grand new scheme. Now let's see, how do we point, click, and plant a new church? Or, better yet, point, click, and lead people into a deeper relationship with Jesus? Hmmm ...

Birthplace of the web

Wired posted some pictures of the new particle accelerator under construction at CERN. At the end is this picture of CERN's "Internet Exchange Point," birthplace of the web. I'm feeling all weepy!

MailFrontier is struggling

We have been happy users of spam blocking software MailFrontier since 2004. MailFrontier was purchased by SonicWALL in February. When we first heard about the purchase, we weren't concerned because we respect SonicWALL and are happy users of their 2040 firewall with web content filtering.

Over the last few months, our satisfaction with MailFrontier (now called SonicWALL Email Security) is declining. We don't know if the issues have anything to do with SonicWALL taking over. We only know that spam blocking effectiveness is going down while total volume of inbound spam is increasing. Last week we saw a huge spike in inbound spam (Tony noticed this too) that coincided with most of our staff being out of the office for the Thanksgiving holiday. When they returned to their Outlook yesterday, they found large amounts of spam that got through the filter. With one voice they rose up in open revolt and stormed our IT office with pitchforks and torches.

Ahh the life of an IT Director. Now we either have to make MailFrontier work or start scrambling for other solutions. SonicWALL are you listening?

Mark's questions for staff evaluations

I will be conduction staff evaluations in January/February. This year I'm going to use Mark's questions.

Visual communication

At Church of the Resurrection we're working to get better at visual communication. Visual communication is much more effective than communication with words alone. The problem is, most of us (me included) spent the majority of our education years learning how to communicate with words. And most of us (me included) have spent the majority of our careers communicating with words -- memos, e-mails, talking with co-workers, speaking in front of groups, etc. We need to learn a new skill: visual communication.

Kathy Sierra is one of my favorite visual communicators. Her recent post on creating graphics illustrates why. Kathy, thanks for helping us with this. (Notice that even this post on visual communication has no visuals. See? I need to learn it too.)

Perry Noble provokes his fellow pastors

Most, if not all, pastors I know have thought the same things Perry shares in his post today. They agree with Perry. Acting on those ideas is what they find difficult. (Everyone in my family is a pastor except me, so I have a lot of opportunity to know what's on their minds.) Thanks, Perry.

Shelby is stable! Hallelujah!

In case the suspense has been killing you, yes the awful problems we had with SQL Server and our Shelby database are finally over. We're new now running Shelby 5.6.2009 on SQL Server 2005. It's rock stable and noticeably faster (though still not fast enough by a long shot). Praise the Lord!

Of course, we have had a number of issues with 5.6.2000 and 5.6.2009, which is hardly surprising given Shelby's track record, but all of that seems trivial compared to the database pain that has been relieved. Can I get an amen?

How NOT to move to a new database server

We bought a new server (a shiny Dell 2950 with Windows 2003 x64 and SQL Server 2005) back in May with the idea of moving Shelby and our other SQL databases to it in a planned, smooth way in June or July. We needed to free up a server for our new Rez West office so we figured it was a great opportunity to upgrade the server hardware and maybe speed up Shelby a good bit.

Due to a number of delays in the Rez West office completion, we had plenty of time to play with the new server. As June melted into July, we systematically moved our non-Shelby databases to the new server and started configuring it for Shelby.

When we updated to Shelby 5.6 in early August, massive performance problems followed. After some investigation, we came to the conclusion that 5.6 placed enough additional resource demands on the server that the old guy, a Dell 2500, wasn't getting the job done any more.

Before we could plan a cut over, the real adventure began. The old server crashed on a Wednesday morning, a time of the week when Shelby is typically under its heaviest load. In response, I divided our IT staff into two teams: one team would work on repairing the old server, while the second team would work on moving to the new server. We would go with whichever team finished first. In the course of that, we discovered that Shelby 5.6 still wasn't compatible with SQL Server 2005, despite the fact that we had been told that the May 2006 update would be compatible. So we finished restoring the old server (the crash had been caused by Windows registry corruption) and after a 6-hour outage we had no choice but to stay there - as painfully slow as it was.

By early October, we were faced with a dilemma. We had to move off of the old server to free it up for Rez West (not to mention the fact that it was so slow it was nearly unusable), but we still didn't have a SQL 2005-compatible version from Shelby and we already had databases running on SQL 2005 - there was no going back. That's when we got the idea to use the free version of VMware to create a virtual server for Shelby that would be configured with SQL 2000 and run on the new 2950 server. Our thought was to run this configuration temporarily until Shelby's October update, which was promised to be SQL 2005-compatible. Seemed like a brilliant idea at the time. Little did we know.

We have been on that configuration for the last five weeks, suffering from massive instability the entire time, including another server crash causing a 12-hour unplanned outage two weeks ago. The source of our grief was SQL 2000, not Shelby, but the user experience was that Shelby would randomly get disconnected from its database and start throwing errors. Shelby error handling is an awful mess of infinite loops, so the user's only recourse was to bring up Task Manager, shut down the client, and restart it. We spent hours on the phone with Microsoft tech support. They had us apply all kinds of updates and patches, including an unreleased hotfix. We also tried a number of changes to our VMware configuration, some of which actually made the problem worse. Each time we and our user community hoped that stability would finally be achieved, only to be bitterly disappointed. Not only was this frustrating for our users, but it was embarrassing for us. Though they were characteristically gracious, the users must have been thinking, "Does our IT Dept. know what it's doing?"

Our goal for this time was simply to hang on until we could install the SQL 2005-compatible version of Shelby, which was released last week. Every day the database was flaky and users were inconvenienced. Then we had something go bad last week in Bank Reconciliation, preventing our Finance folks from reconciling October. Shelby tech support concluded there was a damaged software component, which would be reinstalled by updating to the latest software version. So we scheduled the update for Sunday afternoon. Unfortunately, the Shelby update procedure didn't work. We fought that all day Monday and finally got all desktops updated.

The last step was to install new backup software because the version of Veritas we were running doesn't support Windows 2003 Server x64. To address that, we installed a trial version of ARCserv yesterday.

We finally had all the pieces in place to cut over to SQL Server 2005, running directly on our 2950. Then today the Bank Rec thing started crashing SQL 2000 every time we ran it. Since it was crashing and has been completely unstable for five weeks, we figured we would go ahead and cut over with yet another unplanned outage.

So there you have a tale of how NOT to move to a new database server. By the way, so far it seems stable and faster by 50-60%. Now we're praying it's really over.

SQL Server woes

Our Shelby system is down right now because of ongoing woes with SQL Server. When you are responsible for IT in a very large church that uses Shelby for every aspect of church operations, "Shelby down" is not a happy thing. This is an unplanned outage made necessary by the fact that every time we ran a bank reconcilliation this afternoon, it blew up SQL Server 2000 (errors in the log and the need to manually restart SQL Server every time).

In response, we're moving our database to a new server running SQL Server 2005. This is something we've been working on for months. The final step before moving to 2005 was to install Shelby 5.6.2000, which we did earlier this week. (Since we're down, we're installing the 5.6.2009 brand new patch right now.)

We're now 105 minutes into an unplanned 30 minute outage. Remind me again why I have made a 22 year career in IT???

ChMS budget, timeline, and short list

I spent 75 minutes on the phone with Tony yesterday, which is great for me because I'm always smarter after I've talked with Tony than I was before. Perimeter is just ahead of us in the ChMS selection process. He has a deadline of this month to make a final decision. For us, our only looming deadline is to put in our budget request for 2007 this week. I met with our executive management on Monday. Based on that meeting, it seems very likely that our budget request for ChMS will be approved. If so, 2007 will be the year we make a change, but we still have a couple of months to decide what to do.

Here's our short list:

MSCRM 3.0 plus add-ons from Microsoft CRM partners
Fellowship One
Shelby Arena
Build-our-own open source system in partnership with WEC

Interestingly, two of my finalists overlap with Tony's three finalists.

Tony's third finalist is Blackbaud. I'm intrigued by that and enjoyed the chance earlier this year to discuss it in detail with Shelley Hildebrand of Tony's staff at Perimeter. Unfortunately, the cost of Blackbaud is up there near what it would cost to build our own, so that's not a feasible option for us.

Also like Tony, I know there's a chance our short list will get longer before it gets shorter. Did I mention this decision is risky and complicated?

Network World article on church IT

Jason mentioned that Network World featured him extensively in an article on church IT. Jason also gave the reporter my name and I was quoted too (on pages 2 and 4). This is the first time I've been quoted in a national trade publication. Thankfully, I have Brian to keep me humble!

Thanks Frank, Alfred, Steve, Joe, and Mark

I had the privilege of spending the day Friday with Alfred Johnson, Steve Pruitt, and their teams at Shelby Systems. Frank Canady also joined us for lunch. We had deep discussions about the Church Management System (ChMS) market, and specifically the soon-to-be-released Arena ChMS.

I first met Alfred at the IT Roundtable. He arranged the day and introduced me to the senior management team of Shelby. Alfred, you are a gentleman and a great host. The warmth of your hospitality made my time there special.

Shelby has been around a long time and has been a leader in the ChMS market for many years. During my time there, I gained a lot of insight into Shelby's history, how they see the marketplace, and their product plans going forward. Some of those things I was asked to keep to myself, but many of them are open and I will be commenting on them in the coming days.

We had a frank discussion about our concerns as a Shelby customer, and everyone was gracious enough to really listen and take my concerns seriously. At the same time, I was surprised to learn that my impressions of Shelby's customer base and target market were incorrect in several respects. Like the Fellowship Tech team before them, they also indulged me an extensive discussion of strategic considerations without insisting on jumping right to a product demo. There will be plenty of time for that.

The Shelby senior management team is seasoned and humble. They have a good understanding of what the marketplace is asking of them. Regardless of whether we become an Arena customer, I'm glad to say I have new friends in Memphis who care about the local church as much as I do.

I will continue to post about my trip and my impressions as we make budget plans for 2007 over the next few weeks.

Thanks Jeff, Jeff, Curtis, Curtis, and Scott

No, it's not an obscure law firm. I'm referring to Jeff Hook and his team at Fellowship Technologies.

Today I flew to Dallas for a tour and discussions to help me decide whether Fellowship One will be our next church management system. Jeff, Jeff, Curtis, Curtis, and Scott were awesome hosts and I enjoyed my time with them very much. The team is impressive (even those whose names aren't Jeff or Curtis!) and their passion for the local church came through loud and clear. I particularly appreciated the openness of our conversation. Church management system selection can be complex (it certainly is in our case) and the issues often can't be articulated in bullet points or sound bites. So they indulged me by taking the time to fully air the issues and explore them from multiple angles. It definitely sharpened my thinking. I love serious, deep conversations with smart people.

Thanks again Jeff, Jeff, Curtis, Curtis, and Scott!

Friends don't let friends upgrade to iTunes 7.0

You've been warned. Thanks Jason!

Rez West office

Chuck posted back in August regarding the launch of our first satellite campus, Resurrection West (affectionately known as "Rez West"). The staff of Rez West includes a campus pastor, campus associate pastor, operations director, children's director, music people, etc. - 7 or 8 people altogether. They have been officing in a temporary space on the central campus since June.

Meanwhile, our Facilities folks found some space for lease near the junior high school where Rez West worships. For the last couple of months they have been working on tenant finish to turn it into usable office space plus a large general purpose meeting room and a garage for the A/V equipment trailer. Last week, while the tenant finish was nearing completion, it was our turn to come in and start assembling the technology: phone system, voice mail, Internet connection, firewall, network switch, file and print server, printers, and computers.

Everything but the printers and computers are being installed into one cabinet. Here's Ian terminating the voice station wires into the patch panel (the guy on the right is our new desktop support guy, Jeremy, who doesn't even start until November 13 but came out to help):















Me with Ian and Jeremy:














Me testing the jacks by plugging in my laptop. (Meter? We don't need no stinking meter!)

Thanks for coming

A big "thank you" to everyone who came to Church of the Resurrection for Leadership Institute and/or any of the other conferences we had going on last week. My friend Jim posted his final thoughts here.

Leadership Institute blog posts

A number of attendees at this year's Leadership Institute blogged about their experiences. Here are all the posts I've found so far:

Jim Walton
http://churchtechmatters.com/2006/10/04/leadership-institute-bound/
http://churchtechmatters.com/2006/10/05/leadership-institute-session-1/
http://churchtechmatters.com/2006/10/07/it-panel-discussion/
http://churchtechmatters.com/2006/10/08/leadership-institute-website-strategies/
http://churchtechmatters.com/2006/10/08/leadership-institute-web-empowering-your-church/
http://churchtechmatters.com/2006/10/08/wwtd/
http://churchtechmatters.com/2006/10/10/leadership-institute-emerging-colloquy/
http://churchtechmatters.com/2006/10/08/leadership-institute-continuing-the-discussion/

Jay Vorhees
http://onlywonder.com/wordpress/index.php/2006/08/29/im-going-to-kansas-city-kansas-city-here-i-come/
http://onlywonder.com/wordpress/index.php/2006/10/03/kansas-city-day-1/
http://onlywonder.com/wordpress/index.php/2006/10/06/umerging-day-1/
http://onlywonder.com/wordpress/index.php/2006/10/06/the-case-for-the-mainline-church-adam-hamilton/
http://onlywonder.com/wordpress/index.php/2006/10/06/umerging-panel-discussion-with-bishop-jones-schnase/
http://onlywonder.com/wordpress/index.php/2006/10/06/john-wesley-and-the-emerging-church-hal-knight/
http://onlywonder.com/wordpress/index.php/2006/10/06/airport-thoughts/

Jonathon Norman
http://stphransus.blogspot.com/2006/10/pilgrimage-of-ill-repute.html
http://stphransus.blogspot.com/2006/10/two-methodists-and-saint-walk-into-bar.html
http://stphransus.blogspot.com/2006/10/umerging-are-we-there-yet.html
http://stphransus.blogspot.com/2006/10/thoughts.html
http://stphransus.blogspot.com/2006/10/bishop-qa-q1-and-bishop-schnase.html

Steven Fife
http://revfife.blogspot.com/2006/09/looking-ahead.html
http://revfife.blogspot.com/2006/09/good-conversation-at-wonder.html
http://revfife.blogspot.com/2006/10/narthexes-have-changed-little-bit.html
http://revfife.blogspot.com/2006/10/sitting-in-basement.html
http://revfife.blogspot.com/2006/10/flickr-photo-blog-of-emerging-colloquy.html

Gavin Richardson
http://www.gavoweb.com/hit_the_back_button_to_mo/2006/10/blogging_ummmer.html
http://www.gavoweb.com/hit_the_back_button_to_mo/2006/10/umerging_pilgri.html
http://www.gavoweb.com/hit_the_back_button_to_mo/2006/10/cor_youth_room_.html
http://www.gavoweb.com/hit_the_back_button_to_mo/2006/10/umerging_pilgri_1.html
http://www.gavoweb.com/hit_the_back_button_to_mo/2006/10/umerging_the_vo.html
http://www.gavoweb.com/hit_the_back_button_to_mo/2006/10/a_2nd_chance_bl.html

Jason Woolever
http://post-methodist.blogspot.com/2006/10/update-from-cor.html
http://post-methodist.blogspot.com/2006/10/secret-to-dan-kimballs-hair.html
http://post-methodist.blogspot.com/2006/10/highlights-of-today-at-cor.html
http://post-methodist.blogspot.com/2006/10/experiencing-brian-mclaren-at.html

Susan Cox Johnson
http://aunitedmethodistemerging.blogspot.com/2006/10/im-back.html

Joel Betow
http://theconnexion.net/wp/?p=2466

Gordon Pruitt
http://biblemoth.blogspot.com/2006/10/highlights-from-my-trip-to-kansas-city.html

Paul Kethley
http://tpaulkethley.blogspot.com/2006/10/hello-friendsi-am-sendihng-this.html

Josh Tinley
http://scrambies.blogspot.com/2006/10/church-of-resurrection.html
http://scrambies.blogspot.com/2006/10/brian-mclaren-at-cor.html

Abi
http://faithrenaissance.blogspot.com/2006/10/doing-vs-being.html

http://www.corruptgeneration.com/?p=175

ChMS: Buy it, build it, or integrate it?

If you have spent a lot of time thinking about how to improve the Church Management System (ChMS) function in your church, you probably have reservations about buying one of the existing ChMS products (“buy it”) but at the same time realize you can’t afford to build your own system (“build it”). I want a third alternative: “integrate it.”

With the right technical and non-technical factors in place, it should be possible for your team to integrate technology from multiple commercial and open source providers, along with in-house developed modules, to achieve the range and degree of automation that makes sense for your unique ministry.

In my last post, I listed three technical factors that would need to be in place in order for an open ChMS marketplace to come into existence:

1. A common schema for data exchange. (The best technology for this right now is XML. See ebXML for an example.)

2. An architecture for generating and handling data change events (such as a Web Services API).

3. An architecture for single sign-on.

This list comes out of our experience integrating multiple web applications that weren’t designed to work together. Perhaps there are one or two additional technical requirements I haven’t thought of yet. This brings me to the second part of my question ...

What non-technical (business) factors would need to be in place to foster development of an open ChMS marketplace?

I'd like to suggest we work toward the following:

1. Backing of a few influential churches and/or para-church organizations plus one or more open source or commercial ChMS vendors.

2. A funded standards organization.

3. A Kingdom-minded spirit of unity and cooperation across denominational and geographical boundaries as well as among both non-profit and for-profit organizations.

I’ve said before that we have differing styles, mission fields, and theological points of view, but we have one Lord and we proclaim one gospel. We're all on the same team. Could we begin to move together in a direction that honors God and helps the Church pursue the Great Commission?

I look forward to your comments.

Example of how a Standard and an Open Marketplace changed one industry...

I'm on the part-time IT staff at COR, and I get to talk to Clif directly. I agree with his perspectives on ChMS. We've argued out lots of these points over lunches and Skype chats.

I'm also a worship musician. And I was there in 1983 when the music industry figured out something critical: that a common standard could help *everybody*. Even though the manufacturers were scared and skeptical at first, when they finally dived in THE WORLD CHANGED.

In the 70s and 80s, keyboard players (like me; hey it was 1983!) spent thousands of dollars on instruments: music synthesizers with names like Moog and Yamaha. Learning to play them was cumbersome, and each was a completely independent experience.

In 1982 (still pretty much before PC's) my 3-man company became an original member of the old IMA, right along side giants like Yamaha and Sequential. The objective was to develop Dave Smith's idea for a Musical Instrument Digital Interface (MIDI), which was/is merely a language that all manufacturers could use to translate Black & White key presses into music notes for the sound generator of a synthesizer. If there was a *standard* language for this (the unlikely reasoning went), then instruments could communicate, new grass-roots development from outside would introduce hybrid vigor, and everyone would benefit. But, it was a hard sell: most companies had lots of money tied up in their own systems, and saw things through Old-World colored glasses, hoping for customers to stay "locked in" to the company after learning one instrument's subtleties.

AND THEN: "In a rare example of insight and cooperation, U.S. and overseas companies began working together..." (see Mix Mag's interview with Dave Smith) - - and the 2 companies that spent huge $$ to technically design and implement MIDI gave the technology away to everyone and told *them* how to implement it. (read about the birth of MIDI)

So, in January 1983, at the Anaheim NAMM Trade Show, one guy carried one synth to another synth company's booth, one tiny little MIDI cable linked 2 totally different instruments, and The World Changed. We all quickly discovered digital control, computer mixing, new soundscapes, and a slew of eager new companies hatching new strategies to exploit the newly expanding market. Practically every bit of the worship music I listen to (and create) every day depends on MIDI - a standard that everyone bought into when no one was sure anyone would.

Guess what? Yamaha, and Korg, and the Big Boys are still around, leading their industries, and happy that MIDI came along. The MIDI specification, now nearly 25 years old, transformed the creation of contemporary music. Every church I know of uses it every week, and you've benefitted from it a hundred thousand times. You probably even have .mid files on your PC.

The lesson (of course): working to develop or promote standard schemas will help *your company*, *your church*, and *God's Kingdom*.

More about MIDI at these links:
* Wikipedia - -
* MIDI.org - -

Towards an open ChMS marketplace

See previous posts in this series:
The ChMS conversation we started (but know we’ll never finish)
Choosing a ChMS – the risk calculation

Also earlier posts on related subjects:
Integrating CRM and the Web
Open source Church Management System (ChMS)

No customer lock-in
So what could ChMS vendors do to help me with my conundrum and reduce the risk that I’ll make a bad choice? First, let me suggest a non-technical answer: they need to reject the tempting strategy of achieving and maintaining customer lock-in. They need to go out of their way to make it easy for me to change in the future if I so desire. In other words, they need to set aside their interests and focus on the interests of the Kingdom (and in so doing, they’ll find that their interests are served as well). Instead of competing primarily on a feature list, they need to compete on ease of integration, openness, and customer services. If the vendor can achieve lock-in, they don’t have to be great at these things because they’ll have acceptable rates of customer retention regardless, at least in the short term. On the other hand, if the ChMS vendor rejects the lock-in strategy, my risk as the buyer goes down because I know the vendor will have to continue to earn my business long after the initial sale and implementation.

Second (and this is much more difficult), ChMS suppliers need to find their way towards an open ChMS marketplace. By “open” I mean one in which innovation can originate from many places and come together to meet the needs of a particular church at a particular time. For example, wouldn’t it be great if Granger could run Saddleback’s small groups system with Fellowship’s check-in and WEC’s content management? Wouldn’t it be awesome if Perimeter could run Shelby with Resurrection’s missions opportunity registration system? Wouldn’t it be excellent if Resurrection could run iModules’ online community tools with Perimeter’s Elder system and a web store like OS Commerce? I’m envisioning a marketplace in which there could be multiple for-profit companies contributing technology and services alongside churches, para-church organizations, and open source communities giving away software that automates their process innovations. Wouldn’t that be a major advancement for the Kingdom?

What is stopping us from doing this right now? Well that’s easy enough to answer. The systems I mentioned were built at different times on different platforms by for-profit and non-profit organizations without ever considering the possibility of interoperability. So that’s a big technical barrier. Also, the ChMS vendors don’t see an economic incentive to cooperate with their competitors, which is a big non-technical barrier. Could we overcome these barriers going forward?

To overcome the technical barriers, it seems to me we would need three things:
1. A common schema for data exchange. (The best technology for this right now is XML.)
2. An architecture for generating and handling data change events (such as a Web Services API).
3. An architecture for single sign-on.

Tony posted a comment in which he used the term “platform” to describe what we need. He also quoted me in the ChMS Google group, which attracted a number of comments exactly along the lines I’m thinking.

More in the next post ...

Worship attendance

At the Roundtable we had an extensive discussion of approaches to automate worship attendance. Today Kevin McCord weighs in on the same subject. He thinks printing out a nametag will be enough incentive to get many/most worship attendees to stop at a kiosk and check in.

Choosing a ChMS – the risk calculation

As I alluded in the previous post, a huge consideration for me in choosing our next Church Management Systems (ChMS) is minimizing the risk of making a bad choice. The question of ChMS is the most strategically complex and the riskiest decision I’ve faced since becoming IT Director at Church of the Resurrection three years ago. Why do I say that? What makes this decision especially risky?

The risk is high mainly because Church Management Systems automate core processes. In business or church, whenever you automate core processes you set in motion a complex interplay between your operations and your technology. You adapt the automation system as best you can to fit your processes and you inevitably adapt some of your processes to fit the automation system. You train your staff on the system and over time they develop some deep expertise in its quirks. You purchase and integrate other technology with the system. Before long, the thought of changing the system becomes nearly unthinkable. Companies that build and sell systems that automate core processes understand this very well. Once they get a customer fully on board with the system, they know it will be very difficult for the customer to go another direction. The customer is “locked in” and they're happy (that is, the vendor is happy).

Going forward from the initial implementation, a ChMS is likely to become a two-edged sword. While your operations become more efficient, operational innovation can be held back if the automation technology can’t keep pace. Curtis Harris of Fellowship Tech asked at the Roundtable if it wasn’t possible to have a set of best practices that the system would automate, benefiting all churches that use it. I don’t believe that’s 100% the case (although we all can and should be learning from each other). The best senior pastors are the innovators. They zig when everyone else is zagging. So there’s bound to be some mismatches between what any particular system does and my particular church’s unique way of doing ministry. I strongly suspect that will be the case for other churches too.

Right now Resurrection is too dependent on Shelby. If Shelby doesn’t keep pace with new technology and new ministry models, there’s not a lot we can do because we’re “locked in.” If we go out and find a new system that “stinks the least” and change to that system, we might be better off than we are now, but fundamentally it’s the same strategy. Our risk of Shelby not performing simply changes to a risk of the new vendor not performing. And ultimately, I don’t believe it will be possible for Shelby or any vendor to perfectly, exactly meet our needs.

So what could ChMS vendors do to help me with this conundrum and reduce the risk that I’ll make a bad choice? I’ll share some thoughts on that in my next post.

The ChMS conversation we started (but know we’ll never finish)

After a long day of sharing at the IT Roundtable about everything from WiFi to training and volunteers, we took a break around 4:30 pm and began a lot of conversations in groups of 2 to 5 people. The reps from Shelby, ACS, and Fellowship Tech joined in those conversations. That went on for a couple of hours until the long-awaited Church Management System (ChMS) discussion began. We were just warming up when the pizza arrived courtesy of Shelby and suddenly food seemed more important than ChMS (imagine that!). After pizza we toured the facility and had more conversation in small groups. I think I was one of the last to leave at 10:00 pm. So we started the conversation (or more accurately we continued the conversation that has already begun in the blogosphere and on Tony’s Google group), but we didn’t finish it. Reflecting on that, I realized we will never finish it. So here is another installment in the conversation …

To open the discussion I put up the question: “What do we need the system to do?” This is the usual starting place because we typically think system selection is mostly a matter of determining which system’s features have the best match with our needs. Everyone around the table, with the notable exception of Terry Chapman, agreed with my assertion that no available system perfectly meets our needs today. (Terry is the CIO at Fellowship Church, so Fellowship One is a hand-in-glove fit for them.) John Dolan then rephrased my question as: “Which system stinks the least?” And Tony Dye focused in on the “we” in my original question. “Who is ‘we’?” he asked.

Exactly. Depending on who “we” are, a given system might meet our needs. But unless we built it ourselves, as Fellowship Church did, we’re probably stuck forever with the question, “Which system stinks the least?” (And by the way, Terry said he doesn’t recommend building your own ChMS.) So we start with the assumption that, at a high level, the first issue is “build it or buy it?” And most of us get to “buy it” pretty quickly, perhaps without even consciously considering “build it,” because that option is simply not feasible for most of us.

I then wondered out loud whether “What do we need the system to do?” is the right question with which to begin. I would like to ask what I think is a pre-requisite question. In fact, my question challenges the assumption that our top-level options are build it or buy it. My question challenges the assumption that we have to choose a commercial or open source system and run with it. My question is, “What kind of structure do we need in the ChMS market?” Or, “What kind of business model would optimize the relationships among churches and ChMS suppliers?” Or, “Why should I have to choose whether to run Shelby, ACS, or Fellowship exclusive of the others?” Either/or choices might be our only choices today, but can we imagine a marketplace in which both/and is a possibility? That would radically alter the risk calculation and make my job as IT Director much easier. What technical and non-technical principles would need to be in place for such a world to come into existence?

Ruminate on that a bit while I compose my next post. And feel free to comment. ;-)

IT Roundtable at Granger

What an awesome experience it was to be at Granger Community Church with a bunch of other “church nerds” talking about church IT! My only complaint is that our time together was too short. It was great to meet so many of you in person after reading your blogs, and great to renew acquaintances with old friends.

A big “thank you” to Jason for organizing the event and hosting us. Granger is a place where God is doing remarkable things. It was inspiring just being in their facility and interacting with their people.

We definitely need to do it again some time.

To block or not to block?

We're blocking both MySpace and Facebook at our firewall. Our youth pastor and his boss decided to do this because the school districts are doing it. Their argument is: Why should we be less restrictive than the schools? I'm conflicted about it.

Do you have web content filtration in your network? If so, do you block social networking sites? What are the pluses and minues?

By the way, Scoble says MySpace is for kids; Facebook is for adults. Makes sense.

Comparing a podcast to "teleportation" in Acts 8

This morning Mark Batterson posted about how after leading the Ethiopian Eunuch to Christ, Philip "teleported" to Azotus (actually the text says "the eunuch did not see him again ... Philip, however, appeared at Azotus ..."). Mark compared this to his ability to "teleport" all over the world via podcast. Those of us who are church IT nerds and not pastors really need people like Mark Batterson to put what we do in theological terms. Thanks, Mark. Hopefully I'll remember this the next time someone asks me about church podcasting.

Tony Morgan asks a great question

Check out Tony Morgan's post today "Lifting people up or loading people down?" Tony, it's not only volunteers we need to be concerned about. Sometimes it's staff.

This issue of work/rest balance in life is resonating with me, particularly in light of the talks by Andy Stanley and Wayne Cordeiro (thanks Tony for the synopsis) at the Willow Creek Leadership Summit. I attended the Summit with my whole team, several of whom said Andy and Wayne were talking to me. I needed to slow down, they said. So the next week I took a day off and moved my daughter into her dorm for her freshman year at Park University. That was important, but I have some more resting to do.

It's been a difficult summer:

• We lost a staff person in IT - the 3rd one we've lost this year (and it really hurt)
• We had the usual vacations
• I had the most unfortunate experience of passing a kidney stone
• We hosted the Willow Creek conference
• We've had emergency outages in our phone service and our database server (which hosts Shelby and Track It)
• We've had a number of major infrastructure projects going on including new firewall, new web content filtration system, new anti-virus software, new phone company, new online bookstore, new online box office, updated web site navigation, and the biggest of all, our new location - Resurrection West
• And all of this is on top of our routine workload of tech support, computer upgrades, new staff coming in, and on and on

We simply haven't been able to keep up.

So Tony, I'm with you. As one of the burdened, I'm wondering if sometimes we're adding to the burdens of our congregants, volunteers, and staff. If they've had a summer anything like mine, they're ready for some rest. Yet others are ready to take the next step if only we will challenge them. We need wisdom to know when to push and when to relax.

Volunteering at Promise Keepers

This weekend I had the honor of serving as a volunteer Evangelism Supervisor for the Promise Keepers conference in Kansas City. Around 300 men responded to the altar call on Friday night, more than 100 of which were accepting Christ for the first time. I've done this before. It's an amazing experience every time.

I was too busy with my duties Friday night to take pictures, but here are a few shots of serving lunch to approximately 7,000 men on Saturday.

Promise Keepers has been serving lunch at the conference for years. They have it down to a science. A refigerated semi-truck rolled in, a forklift unloaded pallets of boxes, volunteers stacked them just a certain way, and finally the volunteers opened the boxes.

Each box has eleven lunches. They're all the same so people won't take time looking for their preference.

And here they come! (By the way, I saw Jim Walton in this line. I hope you had a great experience, Jim.)

Blastoff

Resurrection West Blasted off today. And I do mean blasted. More than 700 people were in attendance at the LAUNCH of what is essentially a new church. Thats gotta be some kind of record. I think of today as the Wedding, now comes the marriage....

The venue is a Junior High School about 10 miles from the central (original) campus. We use a high definition feed from the central campus (ask cliff if you want to understand all the technology...I just think its cool). Above Left Adam interviews some folks who restore classic cars, and over on the right pastor Molly Simpson gives announcements in front of the HD screen.

Leadership Summit

This is the first time we've hosted the Willow Creek Leadership Summit at Church of the Resurrection. Ian helped me setup a laptop to connect to the Windows Media video stream for use as a backup to the main video feed that comes in over satellite. Turns out, we needed it in the very first session on Thursday morning due to storms in both Chicago and Kansas City. Good thing it worked!

Here's the rigged-up rear-screen projector:

This is the laptop showing the video stream full-screen:

Conference attendees in the sanctuary:

People in the Narthex:

My wife, Laura, and daughter, Beth:

A new Arena?

Jason and Tony, thanks for letting us know about Arena. We're very interested.

Reflections on the TYPO3 Conference

I previously posted about the TYPO3 Conference, but wanted to expand on it a bit. Thinking back on the event re-affirms my excitement to be a part of the Web Empowered Church ministry. This was the second conference, and the second opportunity I had to meet Kasper Skårhøj, the creator of the TYPO3 CMF. Kasper is a character, and a great individual with a strong passion for quality and perfection.

This year, Kasper was in good spirit from becoming a new dad just a few months earlier, but was also excited to renew his connection with WEC. In the past, Kasper expressed how he struggled with the motivation to continue maintaining TYPO3, as it was not a perfect fit for his desires as it was earlier in time. At this years conference, he expressed how deeply connected he now felt to the WEC ministry, and how he wished to contribute more than was able. When he released TYPO3 in the open source world his vision was brining it to the church world, enabling them to perform ministry on the web with ease and ability. It seems WEC has been formed to help push the ball over that goal line. His motivation was renewed with TYPO3 being brought to the church like he initially envisioned.

At the same time, those of us performing WEC tasks have become much more knowledgeable in TYPO3, not leaning so heavily on the TYPO3 community to make progress, and we are giving back to the community more. The WEC ministry is now in full swing, more capable than ever, and more supported than I ever imagined by Kaspers personal commitment who believes it a God match.

So coming back to my reflections, I am excited to be a part of WEC for all of these reasons. God brought me to Church of the Resurrection five years ago for some purpose, and although I don't feel worthy, I believe it was to do my part to bring WEC & TYPO3 to churches. It is exciting to be a team mate with these individuals, and partner with those supporting WEC. I'm looking forward to what the future will bring and where God will lead us.

Blackbaud's open API

In a post last week, Tony Dye quoted Blackbaud's CTO regarding their open API. I hope other ChMS vendors are reading Tony's blog and took note of that post.

I'm done with Pluck

I'm done with Pluck.

Last summer when I began blogging and reading blogs on a regular basis, I surveyed the available RSS readers and ended up liking and using Pluck. I liked Pluck because it integrates with IE and it allows me to mark posts as read so at any time I can come back and see easily the unread posts.

Unfortnately, Pluck has been neglected. It hasn't been updated since last November and now certain bugs are really starting to bug me. Recently I realized that Pluck was missing new posts in some of my favorite blogs. It also frequently has errors reading feeds, which show up as messages I have to mark as read.

I tried Bloglines, which is cool, but it won't import my OPML and I don't have the patience to re-subscribe to all of my feeds in Bloglines.

I'm playing around with Vista beta 2 and Office 2007 beta 2. Vista comes with IE 7 with its built-in RSS reader. So that's my new reader, at least for now. Goodbye Pluck, I'm sorry to leave but you let me down.

United Methodist Worship, North Carolina Style

This past Sunday morning the Web Empowered Church team attended two churches to give our guest, Kasper, a taste of different worship services here in North Carolina, US. First we attended the Long's Chapel UMC worship service. This was a modern church building which extended off an original stone building. The sanctuary felt new, with pews on an angled floor, and a beautiful wooden roof having a look of yellow pine. The roof was flat, and angled upward from the corners of the room up to a square center, which raised up to let light in through small windows at the top. It reminded my wife and I of a Catholic sanctuary we visited last year while we were in Wisconsin. Both created a beautiful vertical space that gave a very personal feel to the room, and left you with a sense of awe.

The service was contemporary, with songs that were thoroughly approved by my wife, and we had the pleasure of witnessing a baptism. Everything had a touch of Southern style to it, which is hard to describe here in words other than "a comfort of home." This was the weekend before Independence Day, so the theme was patriotic, along with the sermon. The pastor spoke about church and politics, Chucks favorite topics I might add, and mentioned Jesus' response to paying taxes, "Give to Caesar what is Caesars, and give to God what is Gods." The message, as it should be - simple, hold God above all things in your heart.

The second service we attended was at the Stuart Auditorium at Lake Junaluska, through the South Eastern Jurisdiction. The auditorium was an open gathering hall, originally constructed with a tin roof and sawdust floor. The building we were in now was more modern than that, but still considered strange, with a very high wood roof and this large white structure coming out of the middle, descending down into the center from the ceiling. The only way to describe this thing was it looked it like it could sprout legs and walk off like a some version of the mechanical beast from the movie, Wild, Wild West. The sides of the building were very open, with fans hanging down to cool the inside temperature.

Other than the distraction of analysing the strange structure, I thought the service had a well seasoned choir, and the speaker of the week was William Willimon. He did use some "churchy" words in the sermon, and lightly dusted the sermon with dry humor about the disagreements between liberal and conservative churches regarding whether the Christian church needed a full body resurrection to believe in Christ. It was delivered in good taste, with no names mentioned.

It was wonderful to be able to experience not one but two Sunday services, both of which my wife attended and survived to my surprise, and something I'll be able to remember quite a while.