In 2014 Don't Let Tech Turn into SOS. #TechRevival

SOS - Save our Ship (ok, it doesn't really stand for that, but we all recognize SOS to mean something like it)
or
SOS - Same Old Stuff (or SOSDD- Same Old Stuff Different Day, yeah, I know most people say something besides stuff)

If our Tech Language and Management is centered on SOS, we will fall into the following traps.

Distress - If DISTRESSED times are the only time we talk about our technology, it will be nearly impossible for technology to have a real impact or make real change. It is seen as a necessary evil, instead of opening new potential.

Save Us - If the Tech Team is only included or called when things are broken, all we can do is treat the symptoms. In addition, IT may be seen as the creator of the problem, so they had better fix it now, which does not allow Technology to thrive.

Helpless - If SOS is called for technology and IT help always fixes it for you, how does staff ever learn from it? Give someone a fish, feed them for a day. Teach someone to fish and they end up spending all of their money at Bass Pro, err, I mean they can feed themselves.

BUT the worst of all is...

Ambivalent - Once users could go either way with your technology, take it or leave it, you are in real trouble. You don't want to hear things like:

• "Go ahead and change the tool, not like it matters, you will just change it again later..."
• "Nice Tool!" (secretly scampers off and continues to use work-around)
• "You are the IT group, just tell us what to do and make it work."
• "Our technology is fine, but I don't need it to accomplish my goals."

So what are we supposed to do?

Have a Vision and Share It!

You need to be able to tell the story of how technology is benefiting your organization and how you plan to improve it.

What if you asked an org about what they accomplished in 2013 and they answered:

"We answered our phones 11,123 times, turned on the lights each day we worked, paid our bills, had 50 staff show up each day they were supposed to and shook 4,234 people's hands."

If that seems messed up, then why do we talk about our IT like:

"Network is stable, 2,456 help desk tickets completed, 4 major projects completed on budget, 99.99% uptime, implemented 7 new tools." 

Who cares.

A real strategic technology plan. I strongly believe a Strategic Technology Plan aligned with your mission can make all of the difference. Especially if you turn it into a short digestible, visual document to be shared with all staff. 

The key is to be able to express the impact on staff efficiency, process effectiveness and new opportunities which came from your technology. What changed because of the technology you implemented?

Communicate it. Change the tone of communication about your technology, get the positive message out there. Paint a picture of the potential future.

Yeah, I know what you are thinking.  We are hesitant to share our future technology plans, because things change so fast and we aren't sure we will be able to do it all. To me the key for this is to focus on the direction and strategy, not the timeline and the tool.  

Here is what I like to do:

• Share the specific projects coming in the next year, WITH specific goals on how it will change how we work and improve our organization.
• Describe the long term strategy by talking about the philosophy and focus over the next 4-6 years.

Example:

• Next year we will implement a new CRM (Customer Relationship Management) system. Our goal is to replace many of the manual processes tracked in Excel and decrease the paperwork needed. We will be improving our intake process to allow our admissions team to focus on the client, limit multiple data entry points and not be as distracted by the tools.
• Over the next five years we will be looking to move systems to the cloud to shift internal support staff to focus on users, centralize staff collaboration tools to clear clutter and improve communication and look for ways to improve our business processes to better leverage our tools.

But the only way you can do the communication above is to be able to back it up with a Strategic Technology Plan.  You need to have the conversations about priority, upcoming projects, long term vision and have buy in with your plan before you can share it.

So a technology plan is more than just a document needed to manage your projects, it is a key to making technology a force for good in your organization.

Start 2014 right with a technology plan. 

New to Tech Planning? Read this article from Tech Soup!

Ready to add mission and strategy to your tech plan?

• I would suggest reading my resources about IT Alignment  (and if you need help, let me know). 
• Then complete the IT Alignment Assessment to identify areas to add to your Strategic Tech Plan.