Be the CTO They Need
When I saw this earlier this week, it immediately reminded me of a Twitter exchange I had with the incomparable Alice Keeler (Teacher Tech blog) earlier this month.
While I don't remember the exact details of the conversation (wait, a quick google search and voila!), and that was a few thousand tweets ago, I remember that the main problem was simply that technology directors are mired in fear, uncertainty and doubt, keeping people they allegedly serve stuck in static learning environments.
If one were to make a list of the objectionable actions technology directors make, what would comprise the list?
Here are some ideas:
- "Starting with locking down email/youtube/tools teachers want/need" (Alice Keeler)
- Locking down social media tools.
- Making software and hardware decisions based on their perspective not that of teachers and students
- Virtualizing all the desktops so the CTO has absolute control and end-users cannot load software or customize anything
- Make getting help or support too complicated
- Fear of change
I suspect that the one that scares me the most is choosing expensive solutions over free ones (e.g. MS Exchange/Office365 vs GoogleApps for Education), an inflexibility to try new solutions that may yield powerful benefits.
Some guideposts for CTOs based on my experiences and need to grow:
- Plan for what you can, be open to possibilities.
- Communicate and build relationships to the best of your ability.
- Know what leadership/management style best fits your team.
- Read voraciously, throw innovative ideas and solutions out; don't wait for the best moment because you'll be waiting a long time.
- Recognize you have a short time (2-3 years) to make things happen before things started happening back. (the power of the system to fight back a la Peter Senge)
What would you add?
Everything posted on Miguel Guhlin's blogs/wikis are his personal opinion and do not necessarily represent the views of his employer(s) or its clients. Read Full Disclosure