kentbrooks

I was just thinking

Change Agents, Green Carpet to Google Apps: Lessons in Career Life Skills by Kent Brooks

Change is good...you go first.  Change is inevitable. If you don’t like the weather in Oklahoma/Colorado/New Mexico/Wyoming hang around for 10 minutes and it will....yep that’s right CHANGE!  I have always talked around the edges of change but never had to formalize my view on this issue.  I am not sure it is formal but here it goes.  I at least have a perspective on technological change as I was there for the first availability of the World Wide Web...not the Internet Mr Gore, but yes when Marc Andressen, while at the U of Illinois  rolled out Netscape to the masses, I had the opportunity to experience that. When I walked into Western Oklahoma State College in the 1990’s and faced their green carpeted typing and ten key room institutions were hungry to deploy these mysterious technologies and were creating positions for IT directors and CTO’s  When I left August 2010 Google Apps for education fueled communication for that institution.  Typewriters to the Cloud, Green Carpet to Google Apps.  Now as I enter my new position at Casper College we face an environment in which the value of IT departments and services is in question.  I want to thank Debbie Sanders Instructional Developer from Oklahoma State University who is doing an interview project for a class on Change Agents for making me sit down and write down some of my perceptions on change. I am sure this isn't complete, but here it goes anyway. The questions below are in bold text and my thoughts follow:  

1) How have/do you effect change?

  • Find a focus, opportunity is everywhere but hard to focus on because there is so much shiny stuff out there.  You have to narrow down the projects you will focus on.
  • Find out who does the best job at whatever it is that you want to change and copy their style shamelessly, with permission and flattery of course.  
  • Communicate with all who will be impacted, especially your bosses.



2) What are your strategies?

  • Listen to what people are saying even if it hurts your feelings.  I still clearly remember a survey I got back in 1998 asking something about technology which stated, “Looks like he’s trying to build his own empire”  Huge lesson on this one.  I just wanted to deploy great technology that would improve a students learning experience, but not everyone sees things from your perspective.  
  • Communicate intentions openly and well. Apologize for miscommunication and avoid dishonest communication like the plague
  • Be patient and persistent.
  • Be humble mostly...People do not like to be talked down to.  Faculty like it even less.  They are experts, sometimes world renowned experts, in their field and sometimes some new tool of technology can be a barrier when really their only concern is passing expertise on to students in the classrooms.    
  • Be cocky,extolling the virtues of your team, when your team needs you to be...but never at the expense of others.  There are highs and lows in every project. Sometimes when something seems to be dragging out it is your job to remind people of how important your work is and how it will positively impact peoples lives   



3) What is the one change(s) you are most proud of?

Professionally, probably influencing a culture of change for my old institution.  In my view that type of culture is virtually non existent in higher education  Technology comes and goes and will come and go but people don’t necessarily.  Having people with the willingness to “go with the technology flow is critical”

In 1999 when I taught my first online intersession course I did so to see how it would work in concept.  At that time the skeptics were plenty, but those 24 students have turned into   3000 or 4000 intersession students, which has played a big part in stabilizing the institutions finances.  Without that foundation, I doubt the institution would have been ready for the rapid (sometimes triple digit percentage growth from like semesters (fall to fall, summer to summer, intersession to intersession) they encountered.   

4) Do you have a philosophy/framework for how you approach change?

  • Treat people well and listen to them even if you disagree.
  • Change yourself first if change is needed.
  • Let go of a project, issue or even software tool when it is time.



I think items 1 & 2 are obvious if not easy, but I will add a little to item 3.  It is very difficult to let go of one’s children when they mature and go off on their own.  You see this all the time when kids go off to college and the bewildered parents don’t know what to do with themselves.  I believe it is the same way with your work sometimes.  You plant a seed, water it, watch it grow.  However, it is not quite that simple.  We grow attached to whatever it is we are growing.  I believe  we enabled Western to grow with really smart technology choices and unique delivery formats.  It is the norm there now, but people weren’t necessarily jumping for joy with the thought of an open source LMS in those early days.  They thought the winter intersession was silly and compressing it to a 10 day format was even sillier.  However,  those concepts really laid the groundwork for a well oiled delivery of quality education in a fast compressed format.  

The problem for me was I remember when people weren’t lined up to support and teach in these formats and with these tools.  When it really began to grown in say 2006ish to the 2008ish time frame we really began to see a need to support different areas of this programming.  We first added a Director of Instructional support.  We then met some more  and restructured processes, beefed up technologies and infrastructure and added a very talented, Director of Intersession education which was in fact a great testament to the success of the program, but also another point in time when something that needed to be taken from me so that the program could grow.   It was at that point I had lost “my baby”.  Many people built the monster that supported the program, but nobody had the perspective of 1997 I had when I was basically it for the distance program at Western Oklahoma State College.  Over time there were many times it had become time for me to get out of the way.  I think initiatives flounder because people want to hang on too long, even though it has outgrown them.

5) What step(s) do you recommend to start the "change process" in your organization/district/school?

  • Understand your not an island, your bosses must know what your doing and you must get them and the organization some credit for your activities
  • understand your organization and your industry.  One of my mentors Dr. Greg Moiser  once told me “higher ed is the rock of Gibraltar it changes slowly”,  Understand if your going to make changes in an industry it is likely to be with a pick one small swing and one small stone at a time.  We like to think we are different than everyone else, but truth is there are tendencies or similarities between groups of people, similar types of organizations, and industries which can nearly everyone  
  • Identify champions who will help the cause
  • Focus efforts on those champions to generate momentum and accelerate changes
  • Be excited about the advantages potential changes will bring.  If your not excited who will be.  
  • Identify how open the key constituents or your industry and organization are to change.  You can’t teach an old dog new tricks, but you can always feed an old dog something that tastes good.



6) What should be the first step to get the change process going?

Know that you can’t control everything, you might do everything right and still fail and if you fail on a given project there are still things bigger than that project.  (ie God still loves you, your kids are healthy, your friends will like you anyway, etc. etc. ) It will probably be different for everyone but I think this is what some people might call perspective. If you need a bullet list on this one it would probably be:

  1. What can go wrong?
  2. What are the consequences of it succeeding or failing. Remember sometimes success is a problem.  (Lottery winners who don’t really know how to handle their winnings is the first thought that comes to mind)
  3. Are you really up to this?  People often see the privilege of success, but they don’t see the price you pay for that success.  Change is usually a stinkin’ bunch of hard work.  People don’t see that including your peers and your bosses.



7) Can you give one idea on how to overcome resistance to change?

Change is difficult because IT directors, distance learning people, higher ed in general, and maybe all people are risk adverse.  It’s not change that is the problem it is the threat to ones comfort zone.   The keys are focus and persistence.  In the early days of doing “Radical Technical Stuff” I can’t think of a single project, tool or program we implemented where some skeptic didn’t remark that if you waited long enough, the winds of change would blow in another new software tool, project or program next month. All of our projects, H.323 video in 1998, Moodle in 2004, Google Apps in 2007 were all peppered with skeptics who wanted to wait for the next great thing.  First of all there is no one great thing or killer app so get started with what you have and where you currently are.  The real challenge in all of this may be in identifying the problem,  Some people call this bright shiny object disease. Every sparkling new idea that comes along becomes a distraction for management.

8) What resource(s) (news sites, webtool, conferences, etc.) do you find most valuable in keeping up?

Tech Republic,  CNN’s Tech section has a great summary of general tech stuff,  state organizations such as ODLA are critical and a great source of technology info and perspective. I still filter info through Wes Fryer’s “Speed of Creativity” blog.  He must be a Cyborg to do so much but I am glad someone is out there.

Views: 35

Tags: IT, apps, change, disruption, google, netscape, typewriter

Comment

You need to be a member of kentbrooks to add comments!

Join kentbrooks

© 2013   Created by Kent Brooks.   Powered by

Report an Issue  |  Terms of Service

Locations of visitors to this page