Tag Leadership

Culture Wars

No, not of the political variety.  Beyond the mission, vision and values statements, the coffee mugs and the pot-luck lunches, how would your describe your IT Culture?  Who is driving it?

IT Culture Graph

  • Leadership (you):  If staff were asked, would they say that you are actively building a culture around a specific vision you have for the team and the organization?  Would they be able to describe that vision?  Do you have followers within leadership/staff that understand your cultural vision and support you in this effort?  Are you on your own?
  • Rank & File: Is the rank & file culture a blank canvas waiting for you to begin painting, or are you fighting an institutionalized culture that doesn’t match your vision?  Are there so many staff modeling old/negative behaviors that they are overrunning your efforts at the top (tail wagging dog)?  Should you be actively enlisting more followers to assist in this task?
  • Few Specific Individuals: Are there a few specific “informal culture leaders” that staff look to to determine the overall reaction to every new policy or program you roll out?  Are these individuals supporting you, or are they working against you?  How much damage might they be doing?
  • Outside Threats: Is your culture defined primarily by you, and with an appropriate weighing of the outside world?  A little paranoia is normally considered good practice in a competitive marketplace, but has that outside focus become the de-facto culture?   If staff cannot articulate your vision for the type of organization you’d like to build, but can speak at length about negative external reviews or business partner ratings for services provided by IT, you might be in this category.

In my discussions with IT leaders from smaller organizations, one of the most attractive benefits they point to is the ability to build the type of culture they have always wanted to work within.  This is often an etherial thing and hard to quantify, but may include working with individuals with similar levels of passion/energy, personal accountability, challenge, new learnings, work flexibility, and of course the fun quotient.

Infrastructure vs Development

The majority of IT leaders will at some point find themselves in the midst of a conflict between the needs of their business partners and development teams, and the real-world requirements of managing a large systems infrastructure.  The conflicting goals of these groups may have caused simmering frustration just below the surface for some time, then bubbling up with new pressures on software development timelines (go faster!), budget pressures or even the recognition that there is now real competition for internal enterprise infrastructure in cloud computing vendors.

For presentation sake I am combining the Development and Business views, which may include the following:

Infrastructure View:

  • Standardization lowers organizational costs.
  • Control of infrastructure offerings enables a reduction in differentiation, and will increase availability.
  • Infrastructure managers are graded/incentivized in large part on availability and managing costs, rather than on speed-to-market.
  • When developers are allowed to dictate environmental specs, organizational resources may be wasted.
  • There is theoretical potential for cost savings in the management of a large-scale environment serving many internal customers.
  • It is inherently difficult to itemize cost structures for a specific dev/prod environment within a large, distributed enterprise.

What is Pragmatic IT Leadership?

Wiktionary:

pragmatic

Practical, concerned with making decisions and actions that are useful in practice, not just theory

Synonyms

(practical): down-to-earth, functional, practical, utilitarian, realistic

For me, Pragmatic Leadership includes:

  1. While remaining current on the latest practices and emerging trends; determine what will best work for my organization, at this discrete point in time.
  2. In regards to vendor/partner management; be honest about successes and failures, both internal and with my partner, with the primary goal of learning from our shared experience and moving the ball forward aggressively.
  3. When managing internal projects; spend the minimum amount of time on blame assignment, be brutally honest about where we are, our challenges, and how we will move toward success.

These are just a few examples from my list – what does Pragmatic Leadership mean to you?