« December 2010 | Main | February 2011 »

January 25, 2011

Go broad before you go deep

Have you ever been in a meeting to make a decision and before the context can be outlined, a few meeting participants have taken over and are going deeper and deeper into a solution based on a suggestion of one of the individuals? Today's reading, "Go Broad Before You Go Deep," from Roger Schwarz's Fundamental Change Newsletter considers just that issue.

Schwarz suggests that when this happens, people feel stuck and often are unable to reach a decision that all can support and act on together, and which may well be better than the one being pursued by a sub-set of the participants.

The author argues that to get the better, well considered decision you need to first bring the entire group to an understanding of the issue and get their initial views of the problem on the table. Only then will you get everyone engaged and be able to go into the details of a specific solution.

Have a great week. . . . jim

January 21, 2011

QotW: Staying positive

"Being negative is easy. There will always be a downside to everything good, a hurdle to everything desirable, a con to every pro. The real courage is in finding the good in what you have, the opportunities in every hurdle, the pros in every con." ~ Carolyn Hax

  • Are you mindful of your negative thoughts and statements? Are they helpful?
  • Consider problems as obstacles or considerations to be overcome.
  • Write 5 things that you like or are grateful for in your job and personal life.
  • What steps can you take to maintain a positive presence?

Extra: Being a good listener

From Steve Saccone's "Everyone Thinks They're a Good Listener ... Are They?", here a few tips to become a good listener:

  • Minimize Interrupting Others
  • Seek Genuine Understanding
  • Be Responsively Empathetic
  • Realize the Importance of Eye Contact
  • Probe with Curiosity
  • Ask Follow-up Questions for Clarity
  • Suspend Being Judgmental
  • Practice Reflective Listening More Than Interpretive Listening

How many of these apply to your listening style today? Which points do you need to improve?

January 18, 2011

Being a Clutch Leader

In the sports world, a "clutch" player performs best when the pressure is on. See "Learning to be a 'Clutch' Leader" by Sean Silverstone, editor of HBS's Working Knowledge newsletter. In the thinking of Paul Sullivan, New York Times business columnist and author of "Clutch: Why Some People Excel Under Pressure and Others Don't," the best example of a "clutch" person is the military leader - someone trained to make combat decisions with life or death consequences. "How Cadets Learn to be 'Clutch'".

Sullivan believes that "clutch" leaders, ones who succeed under pressure, regardless of their field, share five traits all of which can be learned:

  1. FOCUS: They can block out everything that distracts them from reaching their goal. What is your primary goal? How do you keep it in focus?

  2. DISCIPLINE: They stay the course, no matter the pressure. They can do this because they are able to perform their tasks perfectly under normal conditions.

  3. ADAPTABILITY: They "fight the fight, not the plan." They don't let their ego stop them from abandoning the wrong course of action. Are you rpepared to change things that aren't working even if the change is very hard and reverses something you implemented?

  4. BEING PRESENT: Be in the now, not in the past nor the future.

  5. FEAR and DESIRE: The desire for success in combination with the fear of failure.

Excelling at these five traits - focus, discipline, adaptability, being present, and fear and desire - prepares the leader to succeed under difficult circumstances. With this preparation for success, however, comes susceptibility to three common personality flaws that surface under extreme pressure and cause people to choke:

  1. Not taking responsibility for your actions.

  2. Being over confident.

  3. Over-thinking your role in the organization.

So, what we've learned from Paul Sullivan is that hard work focusing on your objective, adapting to your context, and improving you skills will put you in the best position to succeed when it gets tough.

Take some time today to develop your plan to become a better clutch leader in the new year.

. . . . . jim

January 14, 2011

QotW: Using your time

"We shall never have more time. We have, and always had, all the time there is. No object is served in waiting until next week or even until tomorrow. Keep going...Concentrate on something useful." ~ Arnold Bennett

Do you see others accomplish more with the same 24 hours?

Do you put off difficult or important tasks?

What are your 5 professional priorities? Personal priorities? How can you use you time wisely to accomplish them? What will be the benefit?

January 11, 2011

Dawn of a New Day

Ray Ozzie, chief software architect at Microsoft and previously a key figure at Software Arts and at Lotus, and founder of Groove, is leaving Microsoft after a short transition period. Shortly after he made his announcement, Ozzie wrote Dawn of a New Day as an email to Microsoft's Executive Staff and his direct reports. I believe that this piece is a "must-read" for everyone who is, or who aspires to be, a university IT leader. Ozzie has a good track record at producing cutting-edge products and for envisioning the future, and this piece gives all of us a lot to think about.

As I read the piece, three things popped out at me:

1. About every five years the IT industry experiences what appears to be an inflection point that results in turbulence and change.

From my past experience, university IT has generally been slow to recognize and respond to these forces. How should universities proceed today?

Ozzie believes that our personal-computer centric / server-centric world has become too complex. He sees this complexity continuing to increase as products mature. In his view, complexity is inescapable, sucking the life out of users, developers, and those responsible for IT services and support. This view of the current and the near-term IT environment leads Ozzie to envision a plausible future for IT.

He notes that essentially all of our personal computers are connected to the network and routinely connect to servers. And, he notes that we are also rapidly embracing increasingly powerful app-capable phones and pads as well as innovative services and websites. As we do this, we are mentally moving away from a focus on the artifacts of specific hardware and software. This leads Ozzie to see a world of cloud-based continuous services that we all connect to and appliance-like connected devices enabling us to connect with these services.

2. Continuous services, websites and cloud-based agents we can rely on for more and more of what we do. Always available. Capable of unbounded scale. More and more of our personal and corporate data now sit within these services.

With this comes increasing concerns about issues of trust and privacy. Today, we typically interact with these sites and services through browsers on our personal computers. And increasingly, we also interact through apps loaded onto a broad variety of service-connected devices including phones, pads, and desktop computers.

3. Connected devices beyond the personal computer will increasingly come in a broad variety of form factors. And, from Ozzie's point-of-view, in the future each person will interact with a significant number of these devices each day.

The key difference between today's and tomorrow's devices will be their simplicity and their appliance-like design. He also believes that this will include many embedded devices including sensors throughout our environment. He sees these appliance-like devices as easily configured, interchangeable, and replaceable without loss.

Ozzie believes that we will inevitably progress to this Continuous Devices | Connected Devices model. In his mind the only variable is the rate at which we do so.

If he's correct, are today's app-capable phones and pads precursors of that future? If so, what experiments should we be doing now? What other "killer" applications, services, and devices are lurking out there today that will show up tomorrow in the consumer's hands and on our campuses?

To me, no matter whether you believe Ray Ozzie to be correct or not, IT leaders are being challenged to look hard at the technology we expect to have in place tomorrow. That technology will be different than today and be even more driven by what's available in the consumer marketplace. In addition, university IT, both central and departmental, will likely be pressured to deliver more and higher quality services with fewer resources.

All this calls for IT leaders, working collaboratively across the campus, to develop a path to the next future.

Best wishes on your journey. . . . jim

January 4, 2011

Doing less with less, and failing for success

This Tuesday's Reading "Lessons in IT Leadership: Doing Less with Less and Failing for Success" is from Mark Katsouros, Director of Telecommunications and Network Services at the University of Iowa.*

In Katsouros' view, the combination of expanding IT demands and customer expectations in concert with dwindling resources have meant that doing more with less has been taken to such an extreme that many IT organizations have become "ticking time bombs," way beyond lean and mean to "anorexic and vicious." Additionally, he reminds us to explore lessons from, rather than casting blame for, failure. This will encourage innovative approaches towards greater efficiencies and effectiveness that lean times demand.

Katsouros argues that it is time for:

(1) Doing less with less: Through thoughtful planning and prioritization. He observes that finite resources inevitably have to translate into finite service offerings with realistic plans and resources from provisioning to support. This means:

  • prioritizing services to align with the institution's mission
  • keeping services simple, focusing on meeting needs of the many while sacrificing less frequently used features
  • documenting dependencies to fully understand dependencies between services
  • leveraging the browser as the client
  • documenting your vision and aligning the service's community to the vision
  • separating engineering and operations

(2) Failing for Success: Coaching vs. Persecuting. Katsouros argues that at some point everyone fails and that these failures provide valuable opportunities for the supervisor/coach and staff member(s) to explore lessons growing from the failure. Approaching these lessons constructively and with support, rather than playing the blame game, will encourage employees to innovate, to take reasonable risks, and to leverage their creativity. Great leaders maximize such opportunities for learning.

(3) Learning from the Leaders of Your Past (and Present). Just as we can learn from our past experiences, we have had, and continue to have, opportunities to learn from the great, and the not-so-great, leaders around us. Observe these leadership behaviors and note both those you want to incorporate into into your repertoire and begin practicing these, and those that you want to avoid and be alert to your behavior and avoid these.

In closing, Katsouros summarizes his advice: "plan, prioritize, forgive, learn, and relate." Good advice to all of us.

. . . . jim

January 3, 2011

QotW: Dealing with stones

This week's Quote of the Week is about the obstacles or "stones" that come across our leadership path. How do you deal with the stones that block your path to success? Responding to these obstacles is your leadership moment.

"We can throw stones, complain about them, stumble on them, climb over them, or build with them." ~ William Arthur Ward

What are you doing with your stones? What do you want to do?

How will you recognize your stones? How will you use them to help you and/or others?