There's been a spirited discussion in one of the church Yahoo groups about a church whose team wants to change ChMS software for what appears to be all the wrong reasons. The IT Director voiced opposition to the change, and sought the advice of other church IT people.
The conversation was, indeed, high quality and spirited, and then one of the folks said that in that situation the decision should be the IT Director's, and that they would resign if it went against the IT Director's choice.
This turn in the conversation raised a caution flag in me, so I joined in and suggested differently. Here's what I said:
I have worked with many churches over the years in the IT field, and I don't know of any church IT Director who feels as strongly as you that the ChMS decision is theirs. Ultimately all decisions in a church are the pastor's or the governing board's, but this decision is usually owned by the leadership team (which may include the IT Director), and it's the IT Director's role to fully support it. Your church may be different, but if not, I hope that helps.
Some advice I have given many is to never own a hardware platform or software solution so strongly that it defines you. Technology and people change so much and so fast that doing so always puts a horizon on one's career.
His response showed his heart was in the right spot, and he's doing what's right. WTG!
What do you think of the advice I gave? Is there a software or hardware solution you're holding too tightly?