Opinions and thoughts on finding order out of chaos, simplicity out of complexity and what and how technology can (and cannot) be used to create great user experiences and services
User Needs...
The Steve Jobs mantra is that customers and users do not know what they want until you give it to them. Who of us knew we needed an iPad until we saw one and then purchased one.
Remember the famous Henry Ford quote of "If I asked my customers what they wanted they would have said 'a faster horse' "
There is also a school of thought that we need to develop user centred design so that we develop IT systems that users want and need.
Do these two schools of thought contradict each other?
I think not. The important thing in user centred design is to as soon as possible show users what an IT system will and could look like and get them to touch it, feel it and use it. They may ask for things to be added and changed. You can also add things that they didn't know they wanted and see if they do really want them and need them.
Using this approach will avoid the age old trap of users specifying lots of requirements and what they think they want in their heads and then IT going away and translating this into an IT system that misses the mark. Try getting five people to describe a car in words and then getting someone to build it from the words. You will get some interesting results.
User centred design and delivery will allow users to quickly be able to touch, feel and see stuff and then say "nah maybe not" or "wow that is good how about adding this". All before too much time and money is spent building stuff.
Humans like to see and touch and play with things.
IT Strategy - does it need to die and be reborn?
Is the iPad a glimpse of what future computing will be like?
In simple terms I think this because
- it turns on instantly. None of this MS Windows or Mac booting and sitting around twiddling your thumbs with the iPad;
- you don't have to get into the bowls of it and be an amateur techie to get things working or fixed
- using the applications is intuitive and you can work it out without fear of crashing your machine or getting some technical configuration dialog up;
- using touch to get things done is fast and again intuitive;
- it is a good size and weight. Not too big, not too small and not too heavy.
What convinced me even more of this is that my wife uses it and likes to use it. My wife is not a technology fan and hates PCs and electronic gadgets in general. She thinks the iPad is quick and convenient as she can use it whenever and wherever she wants and needs it. If we fancy seeing a movie we can just turn it on and check the cinema listings in the kitchen. Just like picking up the listings from the paper.
Another incident that convinced me was when I was using my laptop and my youngest wanted to do things by touching the screen. To this two year old it was the obvious thing to do and the keyboard was not.
So these are some of the reasons I think, and hope, the iPad is the future of what computing will look like and perform like.
I haven't yet tried to use it to read a book yet so it may not replace everything just yet.
One final point is that I wrote this blog on the iPad at a time convenient to me and it was a breeze.
Footnote (Nothing is perfect)
(1) iTunes needs sorting though. Having all you iPhone and iPad apps in one list is not user friendly. Maybe this is due it being an PC/Mac application ;-)
(2) I have to admit that I had to post the blog from my laptop as the Blogger editor doesn't yet appear to work on the iPad Safari browser.
What if kids ran your business
I was watching television the other day and saw the advert for Andrex toilet tissue where they have a baby running the company.
It made me recall a conversation I had with my 6 year old daughter some time back were she wanted to do something the next day but we had other plans. I said to her “There are lots of things Daddy wants to do but he can't” as I pictured some of the dreams and ambitions I have had and still have. Some fulfilled and others not. I will always remember her reply to me “Why not?” The innocence of a child I thought whose world has not been set any boundaries as to what can and cannot be done.
On another occasion I got a great piece of advice from someone who told me “to get your point across to any audience write it in 2 or 3 sentences as though explaining it to a 6 year old”. A piece of advice I have used since and it works. Try it especially if you want someone to explain something to you. It is challenging but the results are worth it.
So this got me thinking I wonder what it would be like if we got some children still at school into the working environment and told them what we do and challenges we have and asked them what they would do to resolve them?
For example I wondered how my daughter would get an organisation to embrace Enterprise Architecture. So I asked “how would you get someone to build something in a way you wanted them to do it”. She replied “I would build it first so that they could copy it”
I then asked “What would you do if they would not copy it?” and she said “Find some other people to copy it”
Sounds like she is creating a stakeholder power map without knowing it.......
I wonder what possibilities would be created if we thought in the same curious, inventive and unbounded mind of children? Are they the great untapped innovators?
Next time you have a challenge approach it with a view that no idea is a bad idea and break down those perceived barriers you have built up over time.
Footnote – Is Bob the Builder an Enterprise Architect? The other day my daughter said to me “Before you start anything you need to have a plan of what you want to do and how to do it. Just like Bob the Builder” Is she an Enterprise Architect in the making.......
Open Business
I have entitled this post Open Business. It could quite easily be titled Open Government, Government 2.0, Open Insurance, Open Retail, Open any business for that matter. So for the purposes of my thoughts here today I have made it generic and called it Open Business.
I was thinking of actually calling it Open Enterprise which then got me thinking. If I was going to call this Open Enterprise and now I am calling it Open Business should we bite the bullet and get rid of the term Enterprise Architecture and call it Business Architecture. It is the architecture of a business after all. Let it encompass all the layers of an Enterprise Architecture that we have today – business, application and technology. Maybe call the layers something like operation, application and technology layers of an organisations Business Architecture? Operation may not be the best term but hopefully you understanding what I am trying to saying. It may help to get rid of the stigma of IT not being part of a business when it is. Something I have written about previously in you never here of business/finance alignment. Anyway that is maybe for another discussion.
The purpose of this posting is around opening up an organisations knowledge capital to allow others to create innovative and exciting value from it. The United States Government has an initiative on-going at present, data.gov, to provide access to government data for others to use and create innovative and exciting applications. The UK Government is doing a similar thing with data.gov.uk as part of Smarter Government. We all know how google maps is changing the way we find out where places are and how to get to them both on the Internet and on smart devices such as the iPhone. Is there a website with a location service on it anywhere that doesn't use Google Maps these days?
This is all good stuff and there are some really innovative and exciting opportunities being created. I love Google Maps on the iPhone with the overlay of traffic data hot spots. Information is important, see Wisdom Hierarchy. However the one thing that strikes me about this is it just providing information.
For me the real opportunities are in governments and organizations that not only provide access to the information that they hold, they also provide access to core business services and functions that they perform. In simple IT terms a set of business application programming interfaces (APIs). This, coupled with access to an organizations information, will provide really ground breaking innovative applications for consumers.
Imagine a world where you can go to book a holiday from a site called YourPerfectHoliday.com (I made this up and the domain is for sale...). It takes in your personal information of where you have been, what you like to read and watch, integrates that with information from travel companies on what destinations may match what you like and then offers a set of option. You select an option and it makes the booking direct from the site with the company offering the holiday. It also books any transfers and train ticket. This is because that company has not only provide access to its data it has provided an API for others to use. So have the train companies to book train tickets and airline companies for flights. You don't have to book them individually and you don't need an administrative person doing the bookings in the background manually.
This is only a simple example but the possibilities for consumers are immense. More choice and value. For the organizations that provide the information and APIs it offers many more avenues for access to the services they provide rather than people having to go to them directly.
Imagine the possibilities if government not only offered access to its information but also provide APIs to allow you to claim benefits, tax your car and renew your passport. The opportunities seem endless.
So to me Open Business is not just opening up access to information but also to core business services and functions to provide innovative transactional opportunities. Roll on Open Business
Strategically Relevant Technology
Whilst reading some stuff in the blogosphere this week I came across the following blog post from November 2009 in 2020 Science.
There was a paragraph in this that just jumped out at me as simple, straight to the point and true. It is why IT strategies and IT visions created in IT departments are never implemented and why IT people get frustrated. It stuck in my mind so much that I wanted to reproduce it.
“Strategically relevant technology does not just happen. It depends on targeted investment, coupling outputs to needs, and working with stakeholders to develop and implement appropriate and acceptable solutions. And it takes time – lots of it.”
All too often there is an arrogant, we know better attitude in IT and it is little wonder that the rest of organisation just goes off and does it's own thing.
IT organisations need to communicate, work with and be part of an organisation not just order takers or a creators of stuff.
They need to ensure that IT ideas are linked to the needs of the organisation and its aims and objectives otherwise you are relying on a build it and they will come approach. Understand what they want and maybe what they don't realise they want and convince them they need it.
I was once told by an executive that one of the best training for IT professionals are sales courses to learn the art of selling stuff.
It does take lots and lots of time and lots and lots of conversations and lots and lots of selling to build up that trust, reputation and relationships for IT people and the IT organisations.
The hard work is ,however, worth it as the rewards, relationships and outcomes you create within an organisation are immense.
Low Tech Crowd Sourcing
It is strange but this week both my world of internet information in the form of blogs, social networks, RSS feeds etc. and my world of work seem to have been dominated by a focus on Enterprise 2.0. It got me really excited about the possibilities in a business organisation.
But is this all something new or is it just good ways of working that have been around before repacked for the 21st Century?
There are times when we have an idea, vision or thought of what could be done. However we don't quite know the outcome in exact detail. We have a feeling and unclear image of the outcome. It just feels like a good outcome. People call it intuition, application of experience and knowledge or just plain luck. So what to do?
One approach I use in these situations is get together a group of people who have an interest or stake in this area and others who don't but are innovative thinkers. I then put forward my unclear thoughts and open it up to the group of people. Is it mad, does it feel right, what do people think? The group then verify and build on the thought. This can result in my initial unclear outcome image being shot down in flames (and I learn something), becoming a clear outcome, an even better outcome or an outcome I didn't even think about. The group also feel ownership and empowerment as they helped to create the outcome.
This is what I am now going to call low-tech crowd sourcing. I may even patent it and call it LoweTech© Crowd Sourcing after my surname! It is getting a group of people together for a 30 minute discussion on an initial thought (I am a big fan of 30 minute meetings as they are focused and get results) using low tech tools such as the telephone or just meeting face to face. And most importantly it works.
So maybe crowd sourcing is LoweTech© crowd sourcing for the 21st Century
2010 Predictions
Pretty much everyone is making predictions for 2010 in all walks of life. So I thought I would throw my hat into the ring with some of my predictions for 2010 from the world of IT. Some are consumer based predictions, whilst others are what I class as enterprise based for large organisations.
In no particular order.
1. Bits of Cloud (Fluff) - In 2009 there has been lots of talk about this new silver bullet called Cloud Computing. To me it looks like the old Application Service Provider (ASP) models that were the rage in the early 90's but that is another story. For me Cloud Computing is just the bringing together of lots of different existing technologies and tools and creating new opportunities and value. In 2010 I see some of these technologies taking off and becoming more common rather than Cloud Computing in its purest form. The main one of these is virtualisation. It will become the common default configuration at all levels of an architecture from servers to clients. Gone will be the days of dedicated hardware for a specific task. This will not only be in the computing arena but also the storage arena.
For me there are still some areas around security, information ownership and quality of service that will need to be resolved before public Cloud Computing becomes the norm. There will many private Cloud Computing instances out there. There are even some today that I have been involved in.
2. Touch - I have an iPhone and the interface is a dream. For Christmas I got a Nintendo Wii with a unique and intuitive interface. The kids love it. 2010 will be the year of touch and movement becoming the interfaces of choice. This will be true for consumer based technology products such as phones, televisions and home appliances. In the enterprise we will start to see enterprise based applications start to embrace this new form of interface.
Until we have a faster way of inputing data, which will probably be speech, I don't however see the death of the keyboard. They will be smaller and lighter and maybe projected onto existing surfaces to use. But not yet replaced.
3 - Location, Location, Location - Location based services and augmented reality will take off in 2010. We have so much information available to us these days that we need to ensure that we get the information we want, when we want it, with the minimum of input from ourselves. Location based services will provide that to us. It could be in the form of reviews of restaurants we are looking at in the street, to having immediate travel information and guides when we are standing next to a famous artefact. We can do this now using searches and entering postcodes but in this day of wanting things faster and easier why have the wasted step of us having to know where we are, let technology do that for us. These services can be augmented with additional information on other areas of that may also be of interest helping us to experience new things.
4 - Video - Building on the Touch point how we receive information will start to change in 2010. Text will start to be overtaken by video. Images and video are more easily digested and understood then pages of text and diagrams. 2010 will be the year that video starts to become more common for providing information. The age of the video blog is coming. A good example I like to refer to is a video explanation of what architecture is. This to me gets the point over better than any slide deck or text
5 - The sum of the parts is bigger than each individual piece - 2010 will be the year that we start to see innovation taking off. Not by creating new technology but by packaging up existing technology, services, tools to create new opportunities and products. For example the iPhone doesn't contain any breakthrough technology. It is the way that existing technology has been packaged together to create a new product. This will be the innovation in enterprise IT in 2010. A good overview of this can be found in http://www.cio.com.au/article/330587/no_1_cause_it_failure_complexity
2010 will hopefully see the UK Government open up some of its information as part of Digital Britain providing the perfect opportunity and platform for this to be packaged up innovatively to create new applications for us all to use. What they are I do not know, but that is the beauty of opening up this information.
So that's it. A quick dump from me of predications for 2010. I am already wondering what my review of this will be like in December 2010.
Interested to know what your predications are for 2010
You need to know what you are doing
It sometimes amazes me that the simple things are often forgotten about and people dive into firefighting and ideas generation. They miss the big picture and end up busy being busy.
One of these is the simply having a list of stuff that you are doing and is going on. What is sometimes called a portfolio. What is even more amazing is the difficulty people have in gathering the information to create one.
I have frequently had to create a portfolio of initiatives at the start of a new role. If for the simple area of just getting an understanding what is going on.
My approach has always been to get something that is just good enough in order to get things started. All too often the purists try and create the perfect portfolio that satisfies everyones desires. They ultimately fail to deliver anything and the organisation carries on as before.
My portfolios have gaps and initially have inaccurate information. However the practice of putting it on the table and regularly reviewing it cleans it up over time. It also helps to start to cleanse the areas providing the information for the portfolio, helps to clarify where the data is coming from for it and more importantly where it should come from. All too often you get delivery information from finance and finance information from delivery.
We then have a list of stuff we are doing. It can then be monitored for strategic alignment, delivery, duplication, value delivered etc. It is also something that new stuff can be reviewed against and added to.
So my advice is to create yourself a portfolio of initiatives from whatever you have at the start. Otherwise how will know what you are doing and more importantly they are the right things to be doing?
This is such a simple thing to do and can provide great value
Why will no one implement my IT Strategy?
I was talking to a friend who works in a large private sector organisation recently and he was moaning about how he couldn't get anyone to implement his IT Strategy. I asked him what the problem was. He said “...I have a vision for IT in the company that will add great value” after which he started to tell me about how the strategy would but in a flexible and agile framework to allow the creation of new business opportunities better, smarter and faster.
“It all sounds good” I said “So how are you looking at putting this IT Strategy in place?”
He replied “Well we have written the IT Strategy and what the vision looks like now I just need people to invest in it and deliver it. But they don't seem to be interested”
“What business benefits are you delivering as you start to put the IT Strategy in place?”, I asked.
“Oh those come when we have but the IT Strategy in place” he replied
“Hmm”, I said. “So you want people to invest in some IT that could give them benefits in the future? A platform for the future?”
“Exactly” he replied confidently.
“Well as you are not an IT company such as Microsoft or Apple it may be difficult to invest in IT for the sake of it” I said “I have adi fferent approach that may help you”
“What's that” he replied curiously.
“Having an IT Strategy / Vision is a good thing. However trying to implement it in isolation of the rest of your company is difficult. What you need to do is work with the rest of the your company to understand what their business visions and objectives are. From this you can then identify opportunities that will help them to deliver their objectives but also help you to start to slowly build you IT Strategy and platform of the future. So over time you will start to deliver your IT Strategy but will also be delivering value to your company”
“That sounds like a plan”, he replied, “but it feels hard and slow”
“Delivering strategy is hard. Coming up with the vision is the easy bit. Working out how, what and when to deliver it is the hard bit” I replied “It is also not slow as you are delivering value across your company both from an IT and non-IT point of view. So it is a win win for everyone”
“It's worth a try” he said as he gazed at the ceiling thinking of how to start to make this happen.
This is one of the reasons why IT Strategy never gets implemented and it ends up as a dusty document on a shelf somewhere. The IT department come up with these grand visions but then don't do the hard graft of working with the rest of the organisation to understand and identify opportunities to deliver business objectives whilst starting to delivery parts of the IT strategy.
Pinyin - A form of Enterprise Architecture
I am learning Mandarin with my daughter at the moment. Mainly to keep one step ahead of her so that I can help her with her homework. In order for non-Chinese natives to understand the Mandarin language, help with input of Mandarin into Computers a romanization of the Chinese language is used called pinyin
For someone who speaks English pinyin can seem a strange translating language. The reason is that the pronunciation of pinyin is not a one to one translation to English pronunciation. Let me explain.
The character for water in Mandarin is
The pinyin for water is shuÄ
In English this is pronounced shway with the “way” pronounced with a tone that goes down and then up. Click here to here what it sounds like
So what has all this got to do with IT you may say? Well at the weekend I was reading an interesting blog from Peter Kretzman entitled Complexity Isn't Simple: multiple causes of IT failure. There where some interesting debates in the comments regarding requirements analysis. As an aside my view on this is that it is the complexity of requirements and number of requirements that are a major factor in IT failure. Peter mentions how the telephone has evolved over the years from what it was in the 1980's to what it is now. Think the iPhone or Android phone today comapred to what you had in the 1990's. What would have happened if organizations had tried to make the iPhone in the 1990's? Probably a disaster. Anyone remember trying to get e-readers in the 1980's? Remember the Newton? The mobile phone of today has built up over time. At each stage adding a little bit more value. Making sure that additions work and integrate. This is what organizations should do with new ideas. Start small and then build up over time. At each stage adding a little bit more value. Rather than trying to do it all at once. Something that can help you in this endeavour is a set of guiding principles to ensure new bits fit and help the whole. Maybe an Enterprise Architecture? But that is another story.
Back to pinyin. Whilst reading this I thought about how we use Enterprise Architecture to not only articulate a single version of the truth for an organizations future state but also as a means of ensuring that all parts of an organisation speak a common language and understand each other. It is the pinyin of business.
So if Mandarin is the language of the IT organisation. Lots of symbols, which are meaningless to the rest of the organisation. Then if all those who use speak in romanization languages are the non-IT departments of an organisation how do they communicate with each other? Pinyin of course. Mandarin (IT) speakers understand it and are taught it. Non-mandarin (non-IT) speakers can relate it to their language and understand it also. Therefore pinyin is a form of Enterprise Architecture.
Which all relates to some thinking that I have held true for sometime. Enterprise Architecture is nothing new. It is an approach and a way of doing things. It is more important to use the principles and approaches that Enterprise Architecture provides and advocates rather than going around spouting we must do Enterprise Architecture, we need an Enterprise Architecture. Just do the right think and call it whatever is meaningful to your organisation. Find what it's pinyin translation is.
What's in a name - Everything
I recently tweeted on maybe the perception of Enterprise Architecture and Chief Architects would change from being seen as the domain of IT to being seen as the domain of the entire organisation if they were renamed Business Design and Chief Business Designers?
It made me think of situations during my career where a name has set certain perceptions for myself and/or others or confused.
Enterprise Architecture – Isn't this something IT do?
First up is that old favourite Enterprise Architecture. I was once on a journey of moving an organisation from having an Enterprise IT Architecture to having an Enterprise Architecture covering Business, Applications and Technical Architectures. The Enterprise IT Architecture started in the IT organisation, as is quite common, and covered Application and Technical Architecture. This objective was a real challenge as I was driving and influencing this from within the IT department.
Whilst on the “world tour” of communicating, stakeholder managing, explaining and extolling the value of Enterprise Architecture I recall speaking to an executive in the organisation. I asked the question “does this Enterprise Architecture thing make sense in terms of what it is trying to achieve and the value it provides?” Their reply was that they thought it was technical. It had the words Enterprise and Architecture, which they associated with IT.
A valuable lesson I learned from this is to never use the word Enterprise Architecture if you can help it. Communicate the approach, the method and value, provide examples and scenarios and let the organisation call it what they want. It is the outcomes that we should be most interested in achieving. Not what we call things. Using Enterprise Architecture can set a certain perception which can be hard to overcome.
IS, IS/IT, ICT – Oh Computers.
So a name can set a certain perception. It can also create confusion. An area where a name can be confusing, to me at least, is in the usage of IS, IS/IT, ICT, IT, TS. It makes me think that we in IT are sometimes trying to be too clever for our own good. If you speak to the average person in the street outside of IT and say I work in IS, IS/IT or ICT they will wonder what you are talking about. Tell them IS/IT stands for Information Systems/Information Technology they will probably say “Ah you work in IT”. Why over complicate the situation. Just call it IT or maybe even simpler call it Technology. Someone I know who is definitely not in IT just says “Oh you work in computers”. However I think have Business Strategies for Computers, Computer Architectures or Computer Designers maybe going a little too far.
Organisation Names
A final example is in the names of teams and functions that creates confusion and therefore cannot set any perceptions. I have seen some team and function names that have actually required me to spend considerable time working out what they actually do. They haven't altered my perception of the team as I couldn't work out what they did from the name so I couldn't set any. It was just confusing. When I actually found out what they did it all became very clear - they were the IT department!
Simplicity – Influences perception, removes confusion
So simplicity removes confusion and can help in setting perceptions. One organisation I know had an IT function that wanted to be integrated with the rest of the organisation. It's vision was to be integrated so that it could help shape the organisations vision and direction and provide value enabling IT capabilities to support this aim. In essence creating co-determinate strategies.
The function initially started out being called Technology Office. As it moved on the journey to become integrated it renamed itself to Strategy and Architecture, removing Technology. Then it renamed itself to Strategy and Business IT Systems, removing Architecture. It then renamed itself to Future Design. Simple, doesn't mention IT or Architecture at all. It does exactly as it says on the tin - It designs the future. That is my perception anyway.
It made me wonder what others have done with regards to names to help to set certain perceptions and remove confusion?
Innovation Speed Dating
Recently I was traveling on a train reading some papers for an innovation workshop I was attending. In the papers there was a press release, from a leading newspaper website, taking about a recent new service that had been implemented. It even included quotes from satisfied users of the service and people within the organization. I thought things have been moving fast in the last couple of months because I don't recall this being implemented or even being discussed. Had I lost my finger on the pulse. I then glanced to the top of the page and noticed the date of the press release was 2011! Ah I thought this is a mock up of the possibilities the innovation workshop could achieve. It got my attention.
So the innovation workshop commenced following a short intro of the objectives it was straight into the first of three themes to brainstorm. We brainstormed and threw out ideas that stimulated other ideas for 20 minutes then it was over. We agreed as a group our top 3 ideas and fed this back in 5 minutes. Then onto the next theme in the same format. At the end all the ideas where collated and we are going to vote on the top three to take forward.
It was like Innovation Speed Dating.
However it got result and some really interesting ideas were discussed. You could see the passion in people as an idea took hold and the possibilities became apparent. Some of the ideas I had never thought of myself. But when but forward were inspirational, inspiring and sometimes so obvious. Some of these may have been missed if we had gone down the traditional waterfall approach of requirements produced and then IT respond with a solution.
This was also innovation brainstorming as an organization not as the business or IT we were working as a group of individuals adding value to the organization as a whole. Something I am passionate about and talked about in my post on you never hear of business and finance alignment.
Technology is pervasive these days. Most people have a hotmail, gmail, yahoo mail personal email account. They use facebook, online banking, shopping etc. They can see what IT can do and with a little nudge, through innovation speed dating, are able to find new business value enabling services using some of the IT approaches and services they use everyday in their daily lives.
IT solutions are no longer the domain of a few geeks talking a foreign language in white coats in a basement. This workshop reinforces why I believe my vision of Real End User Computing is achievable
The workshop was inspiring.
However before I get carried away I am not advocating this is all you need to do to generate new ideas and make them a reality. You still to need to ensure that they produce a coherent whole, create enabling capabilities that could be used elsewhere in other ideas, for example process management capabilities. You don't want to end up building vertical silo ideas, services and capabilities. Who wants to end up with three process management capabilities with 3 times the implementation and operating/maintenance costs. Not good.
So you need to ensure all this is underpinned by good old Enterprise Architecture models, frameworks and governance. These will help to turn prototypes into pilots into full scale services. If we don't do this there will be anarchy. A good post by The Enterprising Architect on Is Architecture the Enemy of Innovation shows how the two can and should work together
This workshop was simple to setup and execute but was exciting, interesting and inspiring. I am really looking forward to seeing some of the ideas being taken forward and to the next innovation speed dating workshop.
My Vision - Real End User Computing
I have a vision of what IT in the future will look like that I like to call “Real End User Computing” REUC. This is not End User Computing or Shadow IT done by a sub-set of an organization and sometimes embraced by IT or blocked. No it is much more than that.
“Real End User Computing” is in a world where the suppliers of IT provide reusable business services that consumers can mashup to provide any number of solutions to meet their business needs. IT simply just keeps the lights on.
It is the evolution of the APIs we now see. For example in GoogleMaps , FaceBook and the iPhone. However in this world these are not technical APIs for technically savvy people to use. They are business APIs where business knowledge and understanding is what you really need to know. The interface to use these and create new capabilities is simple and non-technical. These types of platform exist today in one form or another – Microsoft Silverliight, Force.com, etc. This is the evolution of what is current.
It is the evolution of the operating system up the technology stack. REUC resides in a world where we will have a financial operating system with financial business services to use, government operating systems, retail operating systems. All providing business services, not technical services, and the ability to join them up in any number of ways. For example you can add information created in one business services to another. A user can orchestrate business services and at decision points raise tasks in the task service for management in the task management service which is displayed in the business portal service.
Putting the power of creation in the hands of the consumers of IT. Allowing them to experiment and create new, often unthought of, capabilities adding value to an organization. The suppliers of IT keep the lights on and add more business services for the consumers of IT, if required. So no longer do IT create solutions they create services for consumers of IT to use to create solutions.
You will need to ensure you publish and have the right business services at the right level, not too big or too granular. This will require the disciplined usage of Enterprise Architecture to ensure coverage. consistency, re-use and interoperability of the services. Get this right and REUC can become a reality
REUC is my vision of the future of IT and I believe it is achievable.
What's your vision of the future of IT?
Why do organizations have an innovation function?
I was at an event this week and where there was lots of talk about needing to be innovative. This phrase sometimes confuses and other times irritates me. People seem to use it as a nirvana for doing things better. It is as though what they have been doing previously was not doing things better or innovative.
To try and understand what others thought of innovation I did a couple of tweets on Twitter on this very subject. What came back was to me a very good definition of innovation
“Not business as usual that adds value”
Now call be old fashioned but isn't that what the human race has been doing since the dawn of time? It is what makes us what we are. The invention of the wheel was innovative, Newton's laws were innovative, the PC was innovative. In fact finding a better way to get to work maybe faster, more economical, less stressful is innovative.
To me innovation is what we all do everyday. Doing things better, smarter or in a more interesting way.
So when organizations say the need to be innovative or embrace innovation it really confuses me. Surely you must have been innovative to get to where you are today? Even if that was copying someone else's idea. That is also innovative.
From a technology perspective you see many organizations that have a function that covers strategy, architecture and innovation. My view is that the art of doing strategy and architecture is innovative so why do you actually need a function dedicated to it?
As I said innovation is part of being human. It is part of life. We are all innovative so why do we need to try and seek it?
Sorry we don't work like that
At the weekend I did the weekly shop at a major retailer and also dropped into a major hardware store to purchase some padlocks. What struck me was the different view of customer service.
Whilst at the supermarket queuing to pay for my purchases a number of tills were starting to get a backlog of people queuing. Rather than let us all just wait managers opened up other tills and manned them and a message came over the tannoy for all staff who could operate a till to go to the till. I quickly moved to an empty till, paid and was on my way.
The organisation was flexible to the situation and demands of the customer.
Contrast this to my experience at a major hardware store. Big queues building up, lots of staff just seeming to walk around and no real sense of thinking out of the box and opening up some empty tills to help reduce the queues. I eventually got fed up put my potential purchases down, left and went to another rival store and purchased my padlocks there.
Now I may say that I am not loyal. However psychologically I probably am. I will remember the experiences above and will probably return to the same supermarket and go to the rival hardware store.
Customer service is important and sometimes it is the little things that matter. Being flexible to adapt to the situation and provide a service that benefits everyone with little effort.
It made me think of the relationship and service of IT organisations to their customers. There must be an IT training course that teaches the so often heard responses to customers and requests of
- It's a bit difficult.....
- It doesn't work like that...
- We don't work like that and can't meet that timescales / cost
- Before we can start we will need a, b, c, d, e, f, g,......x, y, z all signed in triplicate
- etc.
In IT we talk about agile development to develop code faster and more closely aligned to what a customer wants. We need to extend that to the IT organisation as a whole. We also talk about agile processes and procedures that can adapt, change and flex as the demand from customers adapts, changes and flexes.
If we don't, then as I did, they will go to a competitor. If an IT organisation wishes to be truly part of a business and not a supplier of services then they need to look at the customer service they provide. Not just in terms of costs and schedule but also in terms of flexibility and agility of delivery.
Customer Service perfection is a great goal to achieve. But remember perfection is a journey not a destination and you need to be able to take different roads on that journey.
