Reasons For IT-Business Misalignment (Part 2)

June 30, 2008

I my last post I said that the cause of the misalignment between business and IT is not caused by different pace of change. IT can change as quickly as the business – but it doesn’t. This post lists some of the reasons for this.


Reason 1: Business always gets a head start.
Given its relatively lowly position in most organisations, IT is always the last to know about what is happening – IT isn’t “kept in the loop”. The business can spend months planning something but IT is often contacted at the last minute and is forced to cobble together a solution in impossible timeframes.

Solution: The business must keep IT in the loop. The earlier in the process the better.

Reason 2: Poor solution development methodology.
Many IT Departments are ignoring modern best practice and continue to use outdated waterfall methodologies or work on multi-year projects. It doesn’t work. And history tells us it’s never worked. And I’m not talking software development specifically. The same applies to any IT project (e.g. implementing a new content management system).

Solution: It’s time for IT to get with the times. Develop interactively. Deliver early. Deliver often.

Reason 3: Trying to predict the future.
If you can predict the future I suggest you channel your talents toward pursuits other than trying to predict future business requirements. Most business will prefer to get something functional today than wait for something with bells and whistles. Don’t over-egg the pudding. If you can’t trace the work you’re doing right now to a business requirement then stop doing it.

Solution: Adopt the YAGNI principle. Learn to say “you aint gonna need it”.

Reason 4: Short-sighted views.
Some fall into the exact opposite trap of Reason 3 and build for the ‘here and now’ but don’t even consider what may be needed tomorrow. You need to find a balance. Some changes are easy to predict – factor them into the design.

Solution: Do things today in ways that doesn’t close any doors that may need opening tomorrow. Build extensible and easily maintainable solutions.

Advertisements

Reasons For IT-Business Misalignment (Part 1)

June 26, 2008

A recent comment on this blog got me thinking. The essence of E.A. Anon’s argument was that the misalignment between business and IT is caused by the business changing quicker than IT. But is this really the case?


The word “agility” is getting a lot of press lately, thanks largely to the hype surrounding SOA. IT must be more agile and respond quicker to changing business needs. Or so the story goes.

But does the business really change quicker than IT? I’m not convinced. Let’s consider strategic and tactical changes separately.

Major strategic changes take time. Think about due diligence and legal issues, developing the business case, securing finance, market research, developing new business processes, possibly re-branding the company and launching advertising campaigns, re-organising the supply chain, developing new products and services, staff training and recruitment. And the list goes on. All of this isn’t going to happen over night. All things being equal, I don’t believe there’s an IT Department out there that couldn’t deliver a functioning solution to support the new business in the time it takes the business itself to organise itself.

Tactical changes on the other hand are implemented by the business far quicker – because the size of the change is smaller. Tactical changes are evolutionary (e.g. mail order company creating an online shop). However, if the change requires little change in the business, then it probably requires little change in IT. Of course it takes longer for IT to build an online shop than it takes for the business to say “we want an online shop”, but with the available technology you could probably deliver a solution in next to no time.

If this sounds naïve then I assure you – the cause of the misalignment between business and IT is not caused by different pace of change. IT can change as quickly as the business. So why doesn’t it?

Over the next few posts I will cover what I think are the main reasons for business-IT misalignment. And what to do about it.


Broaden Your Horizons

June 17, 2008

On every architect’s bookshelf you’ll find a lof of books. Unfortunately the titles of those books are likely to contain words such as: architecture, pattern, model, design and development (to name a few). I find it amazing that everyone talks about “business IT alignment” but many architects bury their noses only in technical books. Technical competence is the bare minimum that is expected of architects. To take the next step you need to broaden your horizons.


Here’s a suggestion – for every TWO technical books (or articles) you read, read ONE book (or article) from one of the following ‘genres’.

Personal Effectiveness and Branding
Time management and efficiency are critical to getting your job done. There is a limit to how much ‘harder’ you can work. Learn to work ‘smarter’. Everyone ‘knows’ how to chair a meeting or make a presentation. But not many know how to do it effectively.

Branding is important. One of the reasons IT folk have trouble interacting with the business is because they look, talk and act like IT folk. You can learn to ‘fit in’ if you make the effort.

Innovation, Entrepreneurship and Leadership
Enterprise architecture should be about these three things. No book can teach you how to be an innovative and inspiring leader or the next billionaire entrepreneur. But you can pick up plenty of tips and ideas on how to think outside the box and get those creative juices flowing.

Sales and Marketing
IT folk are hopeless seem to sell their ideas. If you haven’t learned this by now, here’s a free tip: if you’re an architect and you’re relying on the technical brilliance of your ideas to speak for themselves – find another job because you’ll never be effective in your current one.

Personal Relationships
The trouble with any organisation is that it’s full of those pesky things called “people”. What’s even worse is that these “people” tend not to listen intently to your every word, mindlessly agree and then slavishly obey. Bit of a shame that. While you’re trying to invent some brainwashing device to make everyone see things your way, how about you read the odd book about negotiation, conflict resolution, dealing with difficult clients and ‘winning friends and influencing people.’

This list isn’t definitive – but it’s a start.

Broadening your interests will make you a far more effective enterprise architect. The non-technical side should be half of your job and you need to work on it just as hard as you work on the technical side.


Change Management is not an Implementation Issue

June 15, 2008

It’s good that we’re taking a greater interest in the relationship between enterprise architecture and change management. The interesting thing about most discussions is that they talk about enterprise architecture as the “development” phase and change management as the “implementation” phase. There’s certainly nothing wrong with this but I don’t think it goes far enough.


The reason I don’t think it goes far enough is that change management should be an input into your enterprise architecture work. It shouldn’t be a handover – we’ve built this great thing and now ‘lets do some change management’ and roll it out.

I’ve got a software background so I’ll use a software development analogy. When you’re designing software you should always take into account the deployment environment. If the application is to be deployed in a Microsoft environment then PHP and MySQL aren’t your best bet. This example is far fetched but the fact remains – deployment is a non-functional requirement, it should not be an afterthought. If you can’t deploy your finished application to the target environment then its not a ‘deployment’ issue – it’s a development issue.

What’s this got to do with enterprise architecture? Some EA teams are full of great ideas that never see the light of day purely because the change management issues are not considered up front. Typically this problem manifests itself it two ways:

  • Organisation issues – EA teams generally don’t have the clout to force large scale organisational changes – even when such changes are the right way to go. If your architecture work requires such changes in order to be of value then you’re wasting your time.
  • Technical issues – the EA team come up with a great ‘target architecture’ but don’t provide any guidance on how to get from ‘here’ to ‘there’. Enterprise architecture is a journey not a destination – so you need to provide a map.

Obviously, you don’t want your EA efforts to be hamstrung completely by organisational issues and technical issues. Enterprise architecture should be about change – and change always leads to some amount of discomfort within the organisation. They key is to find the right balance. Some organisations can handle revolution others prefer evolution. You want to push the envelope – but not to breaking point.

PS: If you’re interested in a good book about a similar topic try High Impact Consulting by Robert Schaffer. In a nutshell the book is about tailoring the work you do to what the client is ready to do. No matter how great the work is, if the organisation cannot use your advice (deploy it) it just becomes useless shelf ware.


Business Ecosystems and the ‘Whole Product’ (Part 2)

June 11, 2008

In my last post I discussed three forces that I think will drive the consumer push for ‘whole products’, thus forcing businesses to change to a business ecosystem. In this post, I’ll explain the implications for businesses.


The three forces I discussed in the previous post are:

  • Perfect information
  • Commoditization of products
  • Time poor consumers

So why do I think that these three things will force businesses into a business ecosystem model of operating? In a nutshell: consumers want more for less. Of course, consumers have ALWAYS wanted more for less, so what’s changed?

1. The definition of ‘Whole Product’ is constantly changing.
Thanks to the Internet, there is almost perfect information in the market. As I’ve mentioned before, mainstream consumers buy “whole products” and thanks to the Internet they now know exactly what the whole product actually is. As consumers get more sophisticated, proving the whole products will require an increasingly elaborate business ecosystem. Businesses not capable of providing whole products (as defined by the consumer) will lose market share to businesses than can.

For example, travel agents used to book flights. But now consumers expect to be able to book entire holidays: flights, cars, transfers, tours, train tickets, accommodation and more. And the ecosystem will continue to expand as consumers demand more.

2. There will be a blurring of the “price” and “differentiation” business strategies.
Traditionally, businesses compete either on “price” or on “differentiation”. It all comes down to cost. If you compete on price then you need to make sure your costs are low. If you compete on differentiation then your costs will be higher but you can charge a premium for your value-add. At the high end I don’t think anything will change – the business that focus on differentiation are typically innovators (to differentiate themselves they need to do what no one else is doing). But I think technology changes the equation at the bottom end. Businesses competing on price will be forced by consumers to offer better service. Generally, consumers don’t expect a lot of value add from low cost providers – but consumers WILL demand additional services if they know it won’t add to the cost. And thanks to technology, the cost of providing additional services need not add to costs.

For example, when you want to buy a new dishwasher you pick your model and then shop around. You go with the cheapest price so whitegoods retailers generally compete on price. But even though you went with the cheapest retailer you still expect someone to deliver it and install it. You don’t mind paying for delivery and installation – but you want the retailer to organise it for you. These services require an ecosystem and technology should make the provision of these services low cost.

3. Time poor consumers are realising that disintermediation is not always ideal.
The Internet ushered in an era of disintermediation – we could finally cut out the middle man. This has proved to be a double edged sword. In cases where the middle man was ‘Mr 10%’ and provided no value-add, this was a good thing. But in some cases we’ve realised that the middle man actually earned his 10%. Most people are time-poor and are increasingly looking for “one stop shops”.

Again travel sites are an excellent example. We could book out flights, cars and hotels separately but we don’t want to. We want to do it all in one place, deal with one company and pay with one bill. What’s more consumers are willing to pay a small premium for this. If the business charges too much for this, consumers will go directly to the provider. Technology means that you can provide one-stop-shops cost effectively.

So that’s it. The reasons why I think we will have to move from linear supply chains to complex business ecosystems. This change is a challenges to businesses – but it’s also an opportunity for IT. There’s never been a better time to realise the true promise of IT – a source of competitive advantage.


Business Ecosystems and the ‘Whole Product’ (Part 1)

June 10, 2008

In my last post I said that “businesses will be forced to move from the traditional (linear) supply chain to a business ecosystem”. I’ve had a couple of questions about this statement so I thought I’d post an explanation of my reasoning.


The reason I think businesses will be “forced” to move to ecosystems is based around the concept of “whole product”. This is a marketing term and it essentially means “the core product PLUS anything needed to give customers a compelling reason to buy.” The core product might be a computer but the whole product may be the computer plus installation, support, pre-installed software, warranty and training. Mainstream consumers buy ‘whole products’ not ‘core products’.

In order to supply a ‘whole product’ businesses will have to move to an ecosystem model because no single business that can efficiently supply all the ancillary products and services needed to create a whole product.

It’s true that consumers have always demanded whole products – and business have been able to provide them – but I think this demand will increase markedly in the coming years. Three forces in particular will exert pressure on businesses to move to ecosystems:

I’ll explain each one in turn.

1. Perfect Information
“Perfect Information” is an economic term which basically means that all market participants know everything about the market. Thanks to the Internet information is easy to get. With a bit of effort anyone can find out what products are available in the market and where to get the cheapest price.

2. Commoditization of Products
Commoditization is the process where the sales strategy of a product changes from ‘competition through differentiation’ to ‘competition on price’.

Where products are competing on price there is a “race to the bottom” – each market participant looks for ways to lower the price of their product – usually through cheaper manufacturing (e.g. China).

But even high-end, branded products will eventually become commoditized because of the “race to the top”. It works like this. Everyone is trying to outdo their competitors by producing the latest and greatest product but it’s not long before competitors respond with an even better product. The cycle continues as products get better and better. But eventually the market will reach a situation of “performance oversupply”. Consumers will no longer be prepared to pay a premium for all of the bells and whistles if they have no use for them – and the market will begin competing on price at the level of product performance that the mainstream market demands.

3. Time-Poor Consumers
This one doesn’t need any explanation. The one thing every consumer (rich or poor) has in common is that there aren’t enough hours in the day to do everything.

That’s the theory out of the way. In my next post I will explain how I think the increasing demand for whole products will affect businesses.


From Supply Chain to Business Ecosystem via SOA

June 8, 2008

Most of the discussions surrounding SOA focus on the individual organisation. It appears that people are looking to service-orient their own business before looking outside. There’s certainly nothing wrong with this. However, it seems that focussing internally is the ‘default’ position, rather than a considered decision.


Supply chains are complex things and they are the lifeblood of any business. While there’s always room for improvement most organisations have a pretty good handle on them (if they didn’t they’d be out of business).

A traditional supply chain looks like this (simplified):

simple supply chain

But things are changing.

Technology is improving at a rapid rate and we’re living in an increasingly connected world. Consequently, businesses will come under increasing pressure to connect to the outside world. Businesses will be forced to move from the traditional (linear) supply chain to a business ecosystem:

business ecosystem

A linear supply chain is relatively easy to manage. You have two touch points with the outside world. The procurement/logistics functions deal with suppliers and the sales/accounts receivable functions deal with customers. Businesses have been doing this for a long time.

Business ecosystems, on the other hand, have a complex array of relationships and each relationship has to be managed. This can’t be done without the help of technology. Notice I didn’t say it can’t be done efficiently. I said it can’t be done at all.

Service oriented architectures are ideally suited to providing the technical foundation for a business ecosystem. The ROI of outward looking projects may far exceed the ROI of any internal project. There’s no rule that says you must ALWAYS start internally.

Something to think about.