Tony Dye

Best Practices Handbook for Church IT

Imagine if the book pictured here were specifically about CHURCH (or Ministry) IT Best Practices.  How quickly would you buy it?  Unfortunately, it doesn't exist.  But why not?  What if WE wrote it?

What sort of section or chapter titles would you want to see?  Training?  Purchasing guidelines?  Disaster Recovery?  Virtualization?  Desktop standards?

If you have thoughts of subjects, please share.  And, of course, if you have something to contribute...well, let me know!  I may just be motivated to find resources to put this together.

Do You Have a Workflow Technology Solution?

How do you manage "process" in your organization?  Do you have something that helps make sure you don't [easily] miss a step in any process?  Examples:  1) Hiring a new staff member; 2) Ordering, configuring, delivering a new computer; 3) Getting someone keys to the building; 4) Retrieving keys when a staff member leaves.  I'm sure you can add hundreds of others.

What *affordable*, commercial products, fit this market?  Do you agree that churches need such a product?

As a side note, Perimeter still uses an internally developed eForms system that was put together about 8 years ago.  It's a bit crude, but amazingly effective compared to anything else we've seen to date.  CRM/Sharepoint workflow may replace it in the future, but it hasn't yet.

Does IT cause ADD (or ADHD)?

We've joked about this at CITRT events or on the podcast, but after hearing more and more IT people talk about being on ADD medications, I'm wondering -- does being in IT cause it?  Or does IT just attract people with ADD?