Does your business continuity strategy include the people behind your systems?

Jerrod Stewart - Director of Information Technology

• Meet the Fam

• 24 years in IT

• 13 years at COTM

• Love the outdoors

About Me

Question?

Who is that one person in your ministry, that has all the passwords, or the intellectual know how, or is constantly being leaned on to get something done?

Church on the Move - quick history lesson

• 34 years young

• Founded by Pastor Willie George in 1987

• Lead Pastor Whit George

• Dynamic church with three locations

• Lincoln Christian School

Intro to Move

• In-house custom built ChMS that served COTM for roughly 13 years

• Originally launched with Check in System

• Volunteer, room roster, email blast portal, small groups, Outreach, and integrations with LCS SIS, Hubspot, and Tableau

• Primarily architected and developed by one individual

•No clear WHY

•No clear EXPECTATIONS

•No clear PROCESS

Houston We have a Problem

SYMPTOMS

• Dev team wasn’t growing, everything fell on one individual

• Lack of roadmap, documentation, and training

• Firefighting

• Inability to keep up with the demand for new feature requests

• Ministry teams no longer using the system

• BYOT - Bring your own Technology

• Data silos

• Define a clear WHY

• Define clear EXPECTATION

• Define a clear PROCESS

• REPEAT and REFINE as needed

Times they are a changin!

BENEFITS (so far ;-)

• Team/s focused on building for the future of ministry

• Layers of support

• A whole new perspective - COMMUNITY

• Training classes, documentation

• Product roadmap

• What? You have a conference

Key Takeaway

• Define a clear WHY

• Define a clear EXPECTATION

• Define a clear PROCESS

• REPEAT and REFINE as needed

Final Thoughts

Who is the person that you identified from my earlier question?

Challenge: Go have a conversation. If it’s you, let somebody know and begin the process of walking it out!

Your ministry is too important to let it all ride on one individuals shoulders!