Mission statements, though rarely spoken off are not irrelevant. They’re not spoken of or declared as important as they used. This doesn’t make them unimportant. The Church’s mission doesn’t change; making disciples and teaching them obey Jesus’ teaching. A community of people becoming more and more Christlike. Every church tech team needs a mission statement of sort.
Mission statements, or whatever you choose to call them, are necessary. They are a tether. Stating why your team exists means it doesn’t waste resources on irrelevant pursuits. Everything done, must be deliberate, purposeful. Mission statements, as they state intent, help distinguish between what should and shouldn’t be.
This applies to your tasks and focus. Mission statements help teams weigh the importance of each action. Assess the relevance of technology or its use.
The Place To Start
There are two things to take note in formulating your tech team’s mission statement. A great place to start is always with your church’s mission statement. After all church tech, is church tech. It only makes sense in the context of the church.
Leaders and teams must be marinated in the vision and mission of the church for alignment. Church tech teams get their context from their church’s vision. I need not explain what misalignment
The second component is a (growing) understanding of tech. After all tech is not an end, but a means. When you understand the church’s mission and tech innovation can happen. Tech is the how. Mission statements is where vision and the how intersect. They’re a rally call and anchor.
A mistake many leaders (and teams) make, is think they’re pursuing the same thing. Putting brick and mortar together doesn’t mean you have the same building in mind.
A good exercise for teams is conversation. Somewhere to start:
- My understanding of what we do is ____.
- We serve the church’s mission by _____.
Every team needs a mission statement. It brings everyone on the same page. It gives purpose to every action.