"If you believe that people hate change and that it is your job to change them, they will hate it. If you believe that people thrive on change and that your job is to unleash it, you will tap into a limitless source of ingenuity, energy and drive that will allow you to take your big ideas into big results."
- Michael T. Kanazawa
A centralized system routes information and functions through a main hub to free up resources in other areas. Whether it's for communications, data entry, support ticket-tracking, or something else, the goal of a centralized system is to increase:
- accuracy; bad content leads to poor service
- accessibility; easy-to find resources and easy-to-run reports
- seamless flow; no conflicts or dead ends, start-to-finish distribution
- continuity; a consistent experience across multiple touch points
- cost savings; eliminate manual legwork and duplicate efforts
All of this should be a good thing, right? Right. Except...
Many times anyone outside the central "hub" perceives the system as a bottleneck for their work and a loss of control over their job. The average person doesn't associate "systems" with "good times". And, you won't motivate anybody to replace "what they're used to" with a new policy or rule.
If you're looking for buy-in to generate momentum for a new system across your organization, you've got to figure how how to communicate what people "get out of it" as well as "here's what's at stake if we don't."
- DON'T say: "Everybody has to start doing it this way from now on."
- DO say: "Hey...you've got a job to do, hopefully this will make that job easier."
- DON'T say: "Things are getting out of hand so we're implementing a new policy"
- DO say: "We've reached a size where our old methods are hurting us instead of helping us and here's what we need to adjust."
"It's not that people hate change...they just hate how you're trying to change them."
Jason has implemented quite a few new Tech Ops systems over the years and I've appreciated how he communicates changes along the way. Here's some examples...
- Why do we need new technology guidelines? To maximize empowerment and minimize liability. These guidelines allow you to do what you want to do without blowing yourself (or the church) up in the process.
- Why do I have to run my technology purchases through you when I'm paying for it out of my budget anyway? Dude, that's a great question. We don't need to approve your every move, but face it...we're always a stakeholder. Even if you buy that phone or laptop with money out of your own piggy bank, you'll end up using it at work and that affects all of us. Go through IT and it will increase the church's buying power and support capacity. Cut us out of the conversation, and it will ending up hurting you and the rest of the team. Remember "call before you dig"? It's like that.
- Why do we all have the same computers? Equipment standardization across an organization of our size is like a secret weapon. Yes, you may lose your ability to express your individuality through the computer on your desk, but you'll also lose a mountain of technical barriers. Because we're standardized, our machines are compatible with each other; we can swap pieces and parts on the spot with low to no cost. Plus, our support responsiveness is like BAM! because our depth of knowledge makes us experts on one main platform. What does this mean to you? Less downtime and more productivity (believe me, you'll appreciate this when--not if--your computer goes down).
Before you roll-out your next new system, here's three things you want to be sure you can communicate.
- Current Reality: Use practical examples and stories to describe the situation.
- Solution: Introduce one thing that's changing and a couple of next steps. Keep it simple. Allow room for questions. There's a chance you may have missed something.
- Benefits: Don't take anything away without giving something back. Either identify a tangible pain point that will be eliminated or a value gained as a result of the new system.
[This is an edit to a post I originally published in October 2008.]
Recent Comments