We’re spoiled with choices.
Devices, operating systems and apps; so many options. What you’re doing is so important you can’t be flippant about what to do, right? Which is the right one? Why should you use a particular solution?
Some suggestions on what to do before adopting solutions:
Clarity: what is the problem you’re need to solve? If you don’t answer this question well you’ll drive yourself, your team and church crazy. Important: make sure that everyone involved understands the problem the same way.
You don’t want to commit to something only to discover it is not what you needed. This means creating space for conversations. Being rash here could cost you a lot of money This may mean meetings, surveys and other forms of research.
Having said all this, it doesn’t mean you’re going to get everything right every time. Clarifying will help lower the likelihood of useless pursuits.
From apps to hardware and more, most of the solutions I’ve used are from recommendations. This is why reviews are important. Though you make the decision in the end, they help give a snapshot to get you started. Be mindful of context when you read reviews.
It’s folly and waste of valuable time and resources to solve problems that don’t exist. Context is what gives everything it’s proper meaning. Before adopting any solutions be clear about your context. Finding a problem for a solution is not always the best strategy. When this happens frustration is usually the result.
Everything makes sense in its proper context. (Church) Tech does not or cannot function in a vacuum. It only makes sense when it is solving a clear problem. This is why your church can’t take up every “solution” willy-nilly. Because another church or someone else is using solution, doesn’t mean you should also.
Know your church well. Discuss with your leadership and tech teams on what it is you’re trying to solve. Be clear about how solutions need to fit in.
Context has to do with knowing why and how a particular solution is right for your church in particular.
Always consider options or alternatives. Doing this will also help you determine which features are important. Putting similar products side by side will help you clarify what you might be willing to compromise.
Many options can make it complicated to make decisions, but you can go around that. Keep a simple list about what you like and don’t like about each alternative. Use that to eliminate.
Read or watch reviews. Run controlled tests.
Don’t get stuck in looking for the best solution that you never actually do anything. Remember the saying, “paralysis analysis”? Don’t get so caught up in the cons of some things that you actually don’t adopt. Nothing gets in the way of your church’s mission, like not doing anything.
Do This Before Adopting Solutions
Clarify what problem you are trying to solve and why it’s important.
Know what your particular environment is like, so that you choose a solution that fits.
And, start. Do something.