Monday, 1 February 2010

Using IT for Competitive Advantage

Over the Christmas break I read Nicholas Carr's "Does IT Matter". I figured it was about time I read it as I believe passionately that IT can make a difference to companies and within the community we operate. Based on a very quick skim read of his article and all the hype and hysteria it seems that Carr disagrees with this. If he was right or at least made some relevant thoughts I really should know.

My synopsis of his book is as follows. Competitive advantage is typically gained by "owning" items that are proprietary in nature. This makes them hard to replicate as it is expensive and takes a long time. Thanks to the long running effects of Moore's law and IT's relentless march towards openness and standardisation IT has rapidly become cheap and widely available. As a result competitive advantage cannot be obtained from IT as anything you do can be easily replicated by others so individual organisations cannot use IT for competitive advantage.

This is not true however for countries and or regions. Increasingly IT is becoming an open and easily accessible infrastructure. If a country or region does not have a "world class" IT infrastructure in place to support their local economy then they will be at a disadvantage compared to regions that do. The use of the word infrastructure is deliberate as this is how Carr sees IT evolving like other key infrastructures such as electricity, rail roads and the much more closely related telephone. A region with a good stable electricity supply has an advantage over one that doesn't. However individual firms cannot use electricity per sa to gain a competitive advantage as it is comparatively cheap and widely available.

His arguments make sense. The book appears to be very well researched and very well written and while there is likely to still be some way to run for true commoditisation of IT, particularly software, I have come away from reading the book believing that it is the most likely outcome.

So, if Carr is right what could this mean for the IT industry?

Hardware Manufacturers

Equipment manufacturers will continue to try and differentiate themselves by building bigger, better and only available here features. While this may allow one firm to perform better than their competitors at the margin increasingly this will become irrelevant as Moore's law will overtake all their efforts and continue to drive the industry to commoditisation.

Software Companies

Carr argues that traditional software companies provided the first major step towards commoditisation for software as packaging software made the IP widely available at a fraction of the price of in house bespoke systems. This model however will come under increasing pressure by the next wave of innovation/commoditisation. This includes both SaaS and open source software solutions which threaten to undermine the current model of licence, maintenance and on going expensive upgrades.

IT Service Providers

Whether they are currently software companies, hardware companies, Telco's, outsourcers or one of the many other service providers and contractors to the IT industry the IT service provider of the future will be the equivalent to the electricity company of the present and their support infrastructure. They will truly be "service providers" rather than product companies.

Corporate IT teams

Probably my main area of interest as this is where I work.

I don't see this as the death of the corporate IT team, at least not while I am still in the workforce. I do see the rise of the truly services oriented IT organisation. Many, maybe all, IT services will be outsourced to standardised utility providers. This can only be achieved successfully if the internal IT organisation is service oriented. That is, a service oriented IT department is be a prerequisite to be able to outsource standardised services to service providers. The main focus of the internal IT team will be to integrate these services both with each other and into the businesses operating model. I expect that an increasing number of these standardised utility providers will be open source communities. Corporates will actively contribute to these communities developing the open source software as well as using it for their core operations.

So my starter for 10 from my Christmas reading. I may well revisit this as I think some more about it.

Saturday, 19 December 2009

Delivering Real Value

At the Warehouse, we run regular courses on “Managing successful projects”. I often get asked to provide support for these courses on behalf of the executive, by welcoming the participants and leading one of the sessions. The irony is that the session they always get me to lead is “What leads to project failure”? During this session we interactively identify why projects fail. There are many reasons why projects can fail. However, I always emphasise what I believe to be two key causes of project failure.

The first is sponsors who are not active champions for the project. I tell our participants that yes; I and my executive colleagues are one of your biggest risks. Normally this is not because we do not believe in the project or that they are inherently bad leaders. Often it is because we try and do too much too quickly and simply run out of time.

If you have issues and your sponsor is not willing to provide the time and support that you need to resolve issues or align resources effectively for your project, then the project manager needs to have a conversation with the sponsor to resolve this issue.

The potential resolutions are many and varied, however you need to consider the possibility that the project should be stopped or put on hold until it can be given priority. Better to stop early than muddling through with the likelihood of ultimate failure.

The second major cause of project failure is that we stop too soon. A huge effort goes into delivering the project; we get to go live and provide a small amount of post-go live support. We have a party to celebrate success and then leave looking for our next opportunity. We arrogantly assume that what we have implemented the first time is the total and ultimate solution.

We fail to measure on a consistent basis to ensure we get the benefits we expect and we spend virtually no time working with “the users” to ensure they successfully make the transition to the new process. As a result the change usually doesn’t stick and we do not get the benefits we planned, and we wonder why the project didn’t work.

To help reinforce the point, I compare a project to raising a child. There are three phases to each process and below is the short G-rated (approved for general viewing) version.

In stage one both are conceived to high expectations and celebrations. Everybody celebrates what will be and see only the benefits to come, and none of the hard work.

In the project world, we call stage two, implementation. In parenthood it is called pregnancy. During implementation, there is a lot of hard work that needs to be done. There are many reasons for that, however one of the main ones is we often expect people to carry on with our day jobs while at the same time supporting the project.

The culmination of stage two is “go live”. Go lives are often momentous events where everyone is under immense pressure and as a result things are said that perhaps shouldn’t be. The result of go live is, however, miraculous. In one a child is born. In the other a new way of business is given birth too and handed over to the expectant parents.

Stage three is where we raise the child to adulthood so they can effectively leave home and independently contribute to the world. In childhood this process takes years, about 18 years if you are lucky, and lots more if you are not! In projects, however, we spend little time “raising the child”. In essence, we abandon the child to look after itself and seem to expect that everything will work out as it was intended.

In more corporate speak, we spend very little time institutionalising change from our projects. Usually it is a few weeks and we expect everything will work out. The reality is that often it doesn’t.

If as a project manager, or an IS department, we want to add value to our organisations, then I believe we need to ensure the change sticks and delivers the benefits.

Metaphorically, all the value is realised from raising the child to adulthood, it is not in the conception and implementation. If we are truly interested in value creation, we need to stick around for and be active in the terrible twos, through puberty and on into adulthood. If we don’t, the chances of everything working out decrease dramatically.

First Published on www.cio.co.nz

Sunday, 15 November 2009

Paid to do nothing

First Published on www.cio.co.nz

One night after a long day at work I came home wanting to chill out and relax. As a father of four that is seldom an option. This particular night I arrived home right on bedtime and soon found myself in the middle of stories and good night cuddles. In our house the bedtime ritual usually includes a period of time where we ask each other questions about our day. On this particular night my daughter asked me, “Dad, what do you do at work?”

This was not the first time she had asked me this question. On this particular night, being tired and not really thinking, I gave a glib “well, I get paid to do nothing”. I followed this up with what I thought was a pretty good attempt at describing what my job as a leader of a fairly large team actually is. It included an analogy between the principal of her school and what I did at work.

The story went that at school her job was to learn as much as she could and the teachers job was to help her learn. The school principal’s role was to support her teacher and all the other teachers in the school and make sure it ran properly so she and her friends could learn as much as possible.

He didn’t get paid to learn, but he got paid to make sure all the children did learn and to help the teachers to make that happen. At work I don’t get paid to work with computers, I get paid to support the managers, team leaders and all of the team to do their work as effectively as possible and make sure the work is done, I told her.

My daughter went very quiet and looked to be thinking about the ramifications of the answer I had given. I was quietly quite pleased with the answer I had given and then she said, “Dad, if you get paid to do nothing, why does it take so long?” I was stunned, quickly said goodnight and left disgruntled.

Now, when I said I get paid to do nothing I was half joking, but it was only half. If I look at how I actually spend my time, virtually all of my day is spent in meetings.

The form and topics of these meetings are many and varied. They may be one on ones, team meetings, executive briefings, steering committees, operating reviews, meet and greets or many other forums and topics.

If I am not in a meeting chances are I am preparing for a meeting, doing the occasional necessary action that comes out of meetings or reading and answering email and occasionally doing some personal research and study. Not a “productive” task there anywhere!

The organisational focus on meetings is often criticised loudly and with passion. How many times have you said or heard others say, “if only I didn’t have so many meetings, I could actually get something done!” Well what if you didn’t have meetings? How would we get our job as CIOs or senior IT leaders done?

In reality, as leaders of large teams, meetings are the job of CIOs and senior IT leaders. It is how we do what we do, which is to inspire, motivate, align, communicate, prioritise, discuss, decide, reward and recognise our team. There is no other effective way to do these things.

So, if you find yourself or your team lamenting about too many meetings, the problem isn’t too many meetings but that your meetings are ineffective and don’t add value. The answer is not to stop your meetings, but to find out how to have more effective, value-adding meetings. How do you do this?

As some of my previous columns have suggested, thro-ugh focusing on the basics. In this case be prepared, have a clearly defined objective and supporting agenda and ensure you have clear outcomes and next steps that are followed through.

Indeed, I believe meetings are so important that anything we do outside of a meeting should be completely focused on making our meetings more effective, so we can make a difference for our teams.

Friday, 16 October 2009

LGP Fundamentals - an Update

LGP Purpose

Games for Living; Supporting New Zealand as a place where everybody is safe and loved by harnessing the power of immersive games technology to foster the development of life skills and positive lifestyle choices.

Values


We believe that collaboration and leadership occurs naturally in an environment where everyone feels safe and loved. We do this by:

  • living life with a sense of play
  • acting with integrity and for the highest good of all
  • learning and improving
  • seeing people as the best they can be
  • encouraging action
  • being open and inclusive

BHAGs

1. Create a self managing framework for the New Zealand IT industry and Educationalists to engage and connect New Zealanders with today's immersive games experience to teach life skills in fun and sustainable ways.

2. Deliver a pilot LGP Project by Christmas 2009

3. Measurably impact the lives of 2,000 kiwis, their family and friends through the delivery of immersive games technology by Christmas 2012 by:

  • Establishing 50 effective Games Delivery Operations by Christmas 2012
  • Commissioning two immersive games for our communities and for sale


Operations Guidelines


  • LGP delivers Products and Services through LGP Projects based around individual Underserved Communities
  • LGP people honour the LGP Values
  • LGP Teams collaborate to establish and support LGP Projects that deliver measureable outcomes to Underserved Communities
  • LGP Projects contribute to the LGP Purpose and BHAGs
  • Each LGP Team develops and applies effective Selection Criteria and Outcome Metrics

Finance and Administration


The LGP is looking for an existing and related registered Charitable Trust as a home that will support, nurture and administer us so that we can concentrate on ‘doing stuff.’ Is this you?

Invitation


To participate and Do LGP Stuff, start by joining the LinkedIn Life Game Project Group and Subgroup that suits you best ...

Friday, 11 September 2009

Life Game Project (LGP)

LGP Vision

Games for Living - Harnessing the power of immersive games technology to foster the development of life skills and positive lifestyles throughout New Zealand communities.

LGP Purpose

Creating a self managing framework for the Auckland based IT industry and Educationalists to engage New Zealanders with today's immersive games experience to teach life skills in fun and sustainable ways.

Background to LGP

The concept for LGP was born recently out of a meeting between Ian Howard, Parikshit Basrur and myself. Exactly how it came about is something of a blur to me. However, in my brain this is what happened.

My family and I are committed to making a difference in New Zealand society. The vision we have for this is that we want New Zealand to be a place where everyone in New Zealand can be and is "Safe and Loved". I have been thinking about what I could do to make a difference and move us forward towards this vision. As I thought about this several threads of internal conversations began to form:
  • I believe in the power of technology to make a positive difference. It is one of the main reasons that I do what I do as everyday I get to think about and work on real solutions that make a difference for The Warehouse and for New Zealanders. I wondered, how could I apply technology to this broader mission?
  • The current trends in technology are beginning to change how people are defining reality and community, and how people interact with each other and can support each other. While this movement has huge positive potential, it also has the potential to simply ingrain the "have and have not's" in our society through the digital divide. Once again, communities most in need could miss out as they cannot afford access.
  • I believe in the power of education. When I say education I mean education in the holistic sense. Yes, this includes reading writing and arithmetic; but it also includes learning how to lead a successful life and develop yourself to fulfil your potential. It has been a major part of my life and has provided me many opportunities and there are many examples of programs that show that if people have the skills to be successful in society then virtually everyone will choose a positive role. My favourite example of this is the Delancey Street Foundation who turn around the lives of hardened criminals through peer support and mentoring. Over 90% of Delancey's graduates never offend again. This compares to their peer group where recidivism is typically well over 90%.
I was thinking about all of this and thinking about how I could put it together. As I pondered this my mind turned to the possibility of introducing learning labs into less advantaged communities. That is when I met Ian Howard (thanks to Baz).

Ian introduced me to the huge potential of using modern games to educate in a compelling, fun and personal way. Many modern games today are driven by participants decisions and their ability to complete specific quests or tasks. As Ian showed me some examples I began to see how you could shape the experience in a way that the gamer would begin to naturally assimilate powerful lessons in life in a fun and positive way. I could also see how gamers could be supported by peers and mentors with social networking technologies.

Thus the concept of the Life Game Project was born; and the rest will be history in the making. Game On!

If you would like to know more or contribute in some way then contact me and let's talk!

Saturday, 15 August 2009

The Power of Focus

First Published by CIO New Zealand - www.cio.co.nz

The technology industry, indeed business in general, is enamoured with innovation. Any business oriented magazine you pick up talks about innovation and how to be more innovative. Innovate or die is our mantra and we are constantly on the look out for new bright ideas. If you judge us by our actions it seems we all believe that the person with the most ideas will win and all others are doomed. The result is we are constantly looking for and implementing new initiatives. If something is wrong then start a project to fix it. If your competition seems to be better at something than you are then start a project to fix it. If there is a hot new technology out there you better have an innovation fund available to be able to explore it and get ahead. Change is constant and if you can’t change faster than your competition then you will loose.

I am a big believer in the need for innovation in order to be successful but is it true that the person with the most ideas wins?

While I am no expert I have spent a fair bit of time reviewing the “success literature” and trying to understand what it takes to be successful. One of the common themes within the literature is that all successful people are incredibly focused and they practice constantly. It doesn’t matter if you look at sports stars, musicians’, authors, or business people constant focus and practice wins the day. Being a Kiwi bloke, who grew up in the deep south of the South Island one of my favourite examples is Jeff Wilson. Jeff was an incredible sporting talent who represented New Zealand in both cricket and rugby. As a teenager he also represented the south Island in age group basketball. For all his talent however it wasn’t until he decided to focus solely on rugby that he became a true superstar and one of the world’s elite.

Another great Kiwi example is Dan Carter. Maybe the best first five we have ever had. Dan Carter (and Jeff Wilson in his day) practices constantly. As the greatest first five in our history what does Dan Carter spend most of his time doing at practice? I mean he is already brilliant!! My guess is Dan Carter spends most of his time working on the basics, his fitness, his kicking, his passing and his tackling, over and over again trying to get a little better each and every time. I could go on and on with many examples. There are after all enough examples from any walk of life you wish to name to fill libraries.

When I get to work do I see this pattern of practice in the IT industry? Do we focus on the basics and look to get a little bit better at the basics every day? Often the answer is no. Rather we look for that one killer initiative, the emerging technology that will change the world or the silver bullet that will solve all our problems. Some times we even have big initiatives for continuous improvement. ITIL, maybe Six Sigma or Lean IT. Better yet what about Lean Six Sigma (maybe there’s a marketing opportunity for Lean ITIL)! We work hard on these initiatives and we spend a lot of money on them. And when they don’t work what do we do? Do we look to practice and improve a little day by day like the most successful people do or do we look to the next initiative. Usually we look to the next initiative. Indeed, I suggest that if you look back through our history as an industry it is full of silver bullets that didn’t quite fulfil their promise.

I suggest it’s time we stop looking for silver bullets. We stop defining and implementing initiative after initiative, innovation after innovation. Instead let’s look at and understand the basics of what it means to be world class in IT and work hard to implement these basics and get a little bit better at them everyday. Not very glamorous I know, but then how glamorous is it for Dan Carter to take dozens of kicks at goal every day? While it might not be glamorous practice and continuous improvement is the key to success.

Saturday, 27 June 2009

How to sell to a CIO (aka tips for tech companies)

First published in CIO New Zealand. www.cio.co.nz

Before I took up the role of CIO at The Warehouse I was a partner with Deloitte Consulting. As with most professional services firms my role was a mix of selling and delivering services to clients. Because of this when I joined The Warehouse I was quite open to meet with potential service providers to see what value they could add to us.

I was unprepared for the onslaught however. Every week I get many phone calls and emails from companies who have a great product or service to sell. When I respond to these calls I find that they never provide me with value for my time. As a result I now work diligently to avoid all and any approaches from companies wishing to sell me something. While this preserves my time I am convinced that there must be solutions out there that will help our organisation and talking to the owners of those solutions seems like a sensible way to find out about them. The question is how can I do this in a way that adds value rather than destroys value?

I have talked with other CIOs about this issue either in person or online over one of several social network groups I belong to and I have discovered that I am not unique. This is a very prevalent issue so to try and cut through this here is Owen’s tips for how to successfully sell to a CIO.

Do your research before you come to see me. Doing your research shows that you are serious about us as a client because you have invested your time. As a publicly listed company our business strategy is available in public domain if you are prepared to look. Don’t stop at the company level either. Research what is going on in our IS team. For better or worse I have a reasonably high profile and so there is a lot of information available about what we are trying to achieve.

I don’t buy technology I buy solutions to business issues so when you come and see me sell me a solution to my business issue. Selling technology isn’t a bad thing. It just doesn’t work for most CIOs. If I like your business solution I probably won’t buy straight away. I will probably refer you to one of my team and someone in our business outside of IS. You will then need to sell to them to as they will need to live with the solution day by day.

Listen and act on what you hear. If I ask you to change a proposal or to pitch it in a particular way trust that there is a reason. I will tell you if I can but I can’t always tell you. If I do this it’s a great sign as it means I’m interested and one of the best ways to build a relationship is to show that you have listened and responded to my needs. If you can’t for some reason then be up front and acknowledge it. I’ll appreciate the honesty and think of you next time when you may be able to help me.

Be honest at all times. If you aren’t it will only come back to bite you and your organisation. In particular, don’t tell me how important I am to you and that you want a long term relationship with me if you don’t really mean it. If you are successful in winning business with us I will find out if you are serious the first time I ask for a change to our arrangement and you begin to quote the contract to me. This lacks integrity and you are unlikely to win any additional business.

Never tell me I’m strategic because every time someone has said that they very quickly try to increase the price or decrease the discount I receive.

Finally, for me pitching via email is better than by phone. I don’t answer the phone but I do at least browse all my emails. If you follow some of the guidance above and I like what I see you might get a response and a chance to pitch your solution to me or one of my team and that might just lead to value for everyone.