Evolutionary path of enterprise IT

I’ve been giving much thought lately to the question of what enterprise IT departments should look like. Not in terms of technologies they support, but in terms of their organizational posturing. That is the question most interesting to ponder, and most crucial to answer.

What I began to develop is that there are about three different stages in evolution of corporate IT. My thoughts on these stages are not yet complete and I will probably continue to refine and develop my views on this topic, but as plainly as I can see it right now, these are the stages.

Stage 1 – the infrastructure provider. I wrote before about how IT tends to focus on providing basic services which can now be procured cheaper elsewhere. But it seems this is the first stage of a modern enterprise IT department – when most of the time and resources are spent on providing basic services. In my observation, this is where the customer satisfaction levels are lowest as IT has little time to “raise their heads and look around”, busy dealing with the basic while the organization is clamoring for something else.

Stage 2- the force multiplier. Having the infrastructure side of things well in under control, the majority of time and resources of this department is spent working with other departments to understand and enhance their operations. This is the stage to which most of the current IT departments gravitate and virtually every organization I worked at, or speak with, are in some sort of a transition between stage 1 and stage 2.

Then there is stage 3 – the business unit. To me, this is the panacea. This is the stage where both the infrastructure and the force multiplier efforts are well under control, and the IT department can now become “one of the guys” – a revenue generating business unit. The resources dedicated to the first two stages have slack, which is then used by the organization to generate revenue for the company. Outside of providing consulting and stage 1 and 2 services to other companies, I presently find it difficult to justify engaging in any other activity, but I think this should be the ultimate goal enterprise IT.

I will continue to think through this, but what do you think about the concept, the stage definition, etc?

Posted in Information Technology | Tagged | Leave a comment

Stopping the cycle of exclusivity

This morning, I received an email letting me know there is one active discussion on the Center for Higher Education Chief Information Office Studies group on LinkedIn.  The discussion was started by Wayne Brown who is the owner of the group, and also the starter of most of its’ discussions.  This particular discussion is titled “How to help with mentoring higher ed technology leaders who want to be CIOs?”  Expectantly, the responses follow a familiar path – identify potential, create activity, teams, groups, networks, etc.  While all of that is fine and good, what it started for me is a train of thought based on the fact that the whole discussion is off mark.

It is hard to reject the fact that within IT, there are those who would be considered technology leaders (and so potentially CIO material) and those who are not.  It is also hard to reject the fact that non-technology leaders, as in those who show up to work, perform some business as usual tasks and go home, these IT workers far outnumber those considered to be technology leaders (especially since the definition of who a technology leader is, is not set and varies depending on who’s talking).

But reading the discussion, I can’t help but think that what we need to do is not cultivate this minority for the sake of granting them entry into an even smaller minority and then waiting for that brilliance to trickle down to the masses.  If the complaint about these sorts of mentoring opportunities is that CIOs have so little time, and some environments are not friendly/setup/conducive to this sort of activity, then the cycle will continue to perpetuate – the technology leaders will become overburdened CIOs with little time for mentoring, leaving the next wave of technology leaders to emerge on their own, float into CIOs peripheral vision, and be granted a few mentor-ship opportunities per month.  And on, and on, and on.  As it were, so it’ll be.  What problem does that solve?

What we need to focus on is cultivation of technology leaders from rank and file of the IT.  If the CIO only has 4 hours a month to mentor someone, it needs to be a group of average performers to turn them into technology leaders.  And technology leaders need to be in a position to do the same, so that more people are involved not only in trying to patch another server farm with another round of patches, or beat back the users from BYODing, but in raising the collective consciousness of the IT profession.

The CIOs also need to go back to their local universities and in those 4 hours a month work with them to shape technology education.

Maybe only then can we stop being startled by each new technology twist or turn, because when you get down to it, what we’re really startled by is not the technology itself, but the thought of having to deal with it side-by-side with IT majority.  And that is a far more important problem to solve.

Posted in Information Technology | Tagged , , | Leave a comment

The Path To Staying Irrelevant

If IT department wants to be viewed as a cost center and stay irrelevant, it should continue to provide commodity services like email, storage, and network connectivity.  It should also complain about how difficult it is to provide these services.

If IT department wants to be viewed as a business partner, it should ensure that these commodity services are provided by vendors who can now provide them better and cheaper, and focus on understanding the business, and addressing its higher order needs.

Posted in Information Technology | Tagged , | 1 Comment

Beginning of a Journey

Student Journey Map - Day 1

After spending some time becoming acclimated with the new world of MBA program office, I launched a project which I am very excited about.  This project comes straight out of the relatively new discipline of service design (if you don’t know what service design is, check out http://thisisservicedesignthinking.com/ or a list of resources which I’ll put together at some later date.)

Student Journey Map - Day 5

I chose to begin the project by creating a student journey map.  Although traditional journey maps tend to focus on customer touch points – that is points where customers interact with the service provider, I wanted to document various decision points, pain points, or just points in time, along the journey.  Granted, the overall purpose of the exercise is to create a tighter, deeper relationship with the customer by identifying various points, and then making them into touchpoints, but the distinction I would like to make here is that not all of these points will become touchpoints: we may choose not to engage the students during a particular point, even though we’re aware of it.  To me, touchpoint map is something we can develop from this stage one map.

Student Journey Map - Day 10

Because of the number of people involved in the process, the overall goal of the project, and the crazy schedules everyone follows these days, I also chose to not make it a hosted, guided affair.  Instead, we posted some brown paper on one of the walls and invited all staff  to contribute their points at their leisure.   Expectantly  the progress is somewhat slow, but it is moving along nonetheless.

 

Posted in Information Technology | Tagged , | 1 Comment

Compromise on needs to not meet them

When faced with customer needs, we only have two options – to meet them or not.  A simple choice, however, turns into a source of tremendous dissatisfaction.

If we choose to meet the need, it is always with some judgment, or stipulation, which always results in some sort of a change.  Whether due to budgetary constraints, or requirement analysis of multiple interested parties, or lack of technological/human ability, we’ll inevitably deliver something that isn’t quite right.

Customer: I need a purple widget 2 inches wide, 3 inches high, and 1 inch deep.

We: Sure, we can do that.

Three months go by.

We: After talking to all of the stakeholders, we determined that it’d be cost effective for us to produce a blue widget 3 inches wide, 2 inches high, and 1 inch deep.  It saves us a lot of money and allows more people to use the widget.

Customer: Yay!  Widgets! Efficiency! Cost savings!

Few days go by.

Customer: Umm .. I still wish I had that widget

If we choose to not meet the need, it may be for a variety of reasons – because we cannot meet it, would not meet it, or even choose to ridicule the user for even considering THAT to be “a need.”

Sometime ago, I heard a quote somewhere that a compromise is something neither party wanted.  I think that since personal and organizational needs are typically put through a compromise machine, they are typically unmet, forcing users to settle for a widget that isn’t right for what they need.  Obviously, this results in all sorts of negativity and dissatisfaction, from all sides.

The reason for this divide is that the base upon which these solutions are delivered is too rigid and inflexible.  Technology must have these constraints; budgets must have others, regulations yet others, and so on.

Wouldn’t it be something to build a frame, which can support not only any number of scenarios, but support those varying scenarios simultaneously?  A goal worth striving for as its achievement can have significant implications.

Posted in Corporate Culture, Information Technology | Tagged | Leave a comment

Ajax, Odysseus, and philosophical approaches to fair compensation

This week I was lucky enough to wiggle my way into a lunch and learn with Dr. Paul Woodruff, among many things, the author of The Ajax Dilemma: Justice, Fairness, and Rewards.

The lunch and learn was on the topic of fairness, and Dr. Woodruff went over the story of Ajax, Odysseus, and Achilles’ armor.  He used the story as a way to talk about the fairness of compensation, what should be compensated more – loyalty or performance, and why newly brought superstars are compensated much higher based on their potential contribution vs. a hard-working employee that’s been contributing steadily for a very long time.

I basically see a number of problems with using that example.

First, I believe that the reward in question for Ajax was too far outside of the normal rewards which are sought after in today’s corporate culture.  Dr. Woodruff’s argument is that Ajax both did not understand the value of Odysseus to the Greek Army, and felt like he was taken for granted.  Both are interesting assumptions and fun to ponder, but as we bring the example into today’s era, we have to deal with reality.  And it is such that if what’s at stake is a reward far outside of the norm, say 100 years worth of someone’s salary, all sensitivities be damned – virtually everyone’s going all out for it, and no amount of understanding or appreciation can adequately substitute for the reward.  That is not a typical scenario in a corporate environment.

What people are typically after is something smaller, much more attainable, far more tangible.  Employees typically feel unappreciated, underpaid, overworked, without purpose.  I do not believe that example of Ajax applies here.

Which brings me to the second problem I see with this scenario – intrinsic motivation vs. taking money off the table.  I have to keep referring to Daniel Pink’s Drive and as I previously pointed out, one of the lesser appreciate points of his book – before people can be intrinsically motivated, they have to be paid enough to take money off the table.  The reason why I think this is in play here, is because too often, companies are trying to design recognition and rewards programs around this misunderstanding and trying to substitute gratitude for this “taking money off the table.”  It can’t be done. You can say “thank you” all you want, but if the employee worries about paying bills, or not being able to afford a vacation, no amount of thank yous will help the employee feel appreciated, or properly compensated.

So I don’t agree with Dr. Woodruff’s conclusions in the case where the reward is so large that almost everyone will just go for it.  And I don’t agree with him in the case where monetary compensation is still very much on the table and the employee has to worry about anything else but the job at hand.

The question, to me, is whether Dr. Woodruff’s conclusions apply in the case of an employee for whom the compensation is enough to be off the table, and the reward is relatively small.  In that instance, I think Pink has it right and antiquity in Dr. Woodruff’s interpretation supports it – it’s not about the money, or the armor itself, it’s about recognition, respect, honor, satisfaction, gratitude.

Granted, this does open up a host of other issues that have to be resolved – like what is proper and sufficient compensation, and how does one offer it, and is it really enough, etc.  These questions might be tough to answer, but in the long run, they are worth researching because building a successful organization depends on it.  The alternative, I feel, is to simply run around in circles, wondering why nothing works and morale plummets.

Posted in Corporate Culture | Tagged , , , | Leave a comment

Culture as you leave is not as important as culture as you stay

Or try and get some things done.

Read a great post by a former colleague, Ron Thomas, on culture and its importance to employee morale.  

I agree with virtually everything Ron says, but as I read the article, what was going through my head was that culture is responsible for success or failure of virtually any corporate initiative.  It’s not that culture is some ubiquitous thing that’s out there, it’s something that impacts what we do day in and day out.  And it is the accumulation of these daily interactions that cause someone to become disenchanted. 

As we undertake any new project, or participate in any new initiative, or attempt to implement a change, the biggest obstacle is not money, or timeline, or lack of executive support, it’s culture.  At each point, we have to overcome some aspect of the entrenched culture, and the greater the divide between what’s attempted and what’s entrenched, the more effort has to be expanded to overcome just the sheer resistance.  All of that on top of the regular challenges associated with implementation of anything new.

Because of this constant resistance and run in with the culture, projects either get abandoned, or have to be re-shaped, burring them under a mound of change requests, eventually spinning out of control.

When that happens, that’s when we, as IT professionals, get frustrated and lose interest, thereby becoming part of the entrenched culture and the problem it presents.  Either that, or we leave with a strong desire to publish an op-ed in the New York Times like the one Greg Smith did.

At various points in the day, I find it to be a conscious effort to constantly check in and figure out if what I’m doing is in line with the culture I want to have on my team, or falling into the line of thinking and working as my predecessors did.  It is a daily struggle, but I also find that it is definitely possible to resist the overall pressure of the external culture, and create the atmosphere I’m proud, even if it’s just within my team.  The hope is that at some point, it will rob off on others around us.

Posted in Corporate Culture | Tagged | Leave a comment

Creative Problem Solving

Everyone is really good at creative problem solving.  The question is where and when do they apply it most, or best.  

An unmotivated employee might be creatively problem solving his next vacation plans for half a day.  An underpaid employee might be creatively problem solving how to start a business using his work time.  A burnt out employee might be creatively problem solving how to pass off some work to someone else.  An unsecure employee might be creatively problem solving how to find a more secure job.  

All the while, the manager is wondering why the projects are not getting done.  Or if the manager is unmotivated, underpaid, and burnt out, he might not even care anymore.

The question is, what problems are your employees motivated to solve – their own, or ones you’d like for them work solve.  Everyone problem solves…

Posted in Quotes | Tagged | Leave a comment

Manage through Gartner

Whenever I hear “best of breed” implementation, I want to run for cover.  “Best of breed” tells me that we are about to spend a ton of money, not worry about requirements, invite an army of consultants, implement a product that doesn’t fit in a really messed up way, and then have to constantly force our users to use the damn thing even though we see little point in it ourselves. 

I’ve been through a number of “best of breed” implementations and they’ve all gone this particular way.

 To paraphrase Stephen Covey, seek first to understand, then to implement.

Posted in Corporate Culture, Information Technology | Tagged , | Leave a comment