I am an early adopter. I love to grab stuff on the cutting edge when I can. I love alpha and beta testing. I love geeking. I love seeing what can be done with any and all kinds of technology. But I don’t implement everything just because I can. One of the biggest drains on time is implementation. The learning curve for adaptation, coupled with implementation, can add hours of lost time plus a lot of aspirin. So, here are a few questions worth answering before jumping into a new technology tool.
- Will anyone be served or helped by the implementation?
- Will it help with communication or will it dilute how communication is being handled now?
- What would happen if the tool was not implemented?
- Will the tool reach people that are not already being reached?
- Will the cost of implementation be worth the benefits derived?
- What would happen if I waited a year for the technology to develop a bit more?
- Am I implementing something that does not have a quality look and feel about it?
- How am I going to let people know about the new implementation?
- How will I measure the success of the implementation?
- Is there someone that can manage this tool and keep it relevant?
Tools and technology are amazing. We can do so much. But let’s not do it just because we can. Let’s ask a lot of questions before we take that next step. Good technology tools often require an outlay of cash and energy. And by answering some of these questions, we tether ourselves to the stewardship of God. And ultimately, He is the One we answer to for all things technology.
pic by aldrin muya







This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.