A little while ago there was a video around that parodied the way that Microsoft did its marketing and packaging when compared to iPod marketing.
The new packaging for Vista and Office 2007 looks pretty good.
Centralisation is everywhere.
Why? There are normally two reasons and they are the usual business reasons – cost and quality. Functions done centrally are supposed to be more cost effective than those done in a distributed fashion. Centralisation allows specialisation which should lead to an increase in quality.
If there is a quality problem, or a need to reduce costs the first mechanism that people turn to it centralisation.
The increase in quality and the reduction in cost is regarded as a certainty.
It’s almost become a business mantra – “I must centralise”.
I am personally becoming increasingly skeptical about centralisation.
I feel that I should declare my experience here. Throughout my nearly 20 years in IT I have been involved in a number of centralisation activities; centralisation to a data centre on a site, then to a data centre in a country, then to global data centres. I have also been involved in IT help desks. When I was a new graduate I would man the help desk for two afternoons a week. I watched on as the help desk went from supporting a site, then to supporting a number of sites within a country, then a country, eventually it supported a number of different customers across different time zones.
I’m not doubting that these activities reduced costs, though none of them gained the cost reductions people were hoping for. There was also a change in quality but it not dramatic and not on every measure.
So why am I skeptical?
My main area of skepticism is caused by one word – change. These centralised entities are terrible at responding to change.
They naturally become highly integrated within themselves
The help desk naturally consolidates to a single set of systems. That is how costs are reduced after all. The consolidation of the systems creates cost reduction and increases the quality. That is until something comes along which drives change. Lots of small systems, each running independently can change when they need to change. There doesn’t need to be a huge requirement to change. When a huge integrated system exists change becomes more and more difficult. Where change is difficult change will either stop, or the cost of change will be dramatic.
People forget that change is inevitable.
The same is also true for IT systems. Changing a single system that does a single role is far easier than one large system that handles lots of roles. I’m sure that some people believe that if the cost of changing one system with one role is X then the cost of changing one system with lots of roles (Y) is less than X * Y. In my experience it’s more than X * Y it’s more like X * 1.5Y.
Because change is difficult it happens rarely. When it does occur the change ends up being massive, it’s normally not possible to change a single entity. The system has coalesced and for one thing to change, lots of things have to change. It’s become a chain reaction. Between the massive changes, though, the quality of services is constantly decreasing as the service delivered becomes further and further from the service required.
I’m not suggesting that we throw out the baby with the bath water here. What I am advocating is that we approach consolidation in a more pragmatic manner. Rather than blindly following the centralisation mantra we should evaluate the centralisation option knowing that change is inevitable and plan for it. In planning for it we may discover that centralization isn’t actually the correct option.
Today Lifehacker has an article entitled “Top time-management tricks” which highlights this statement in Realtor Magazine:
“When I start to feel overwhelmed with clutter, whether it’s on my desk or in my home, I take a short block of time — 20 to 45 minutes — and I turn off all communication; I let voice mail take over. Then I just attack the pile. I’m always amazed at how much I can accomplish in this short period.”
Prior to reading this post I actually did just that. I’ve had a stack of document to review and stuff coming at me from all angles right the way through last week (and weekend). The result was a desk that was a tip and absolutely no focus on what I was doing.
Tidying through the clutter I cleared a whole load of actions off my to-do list. I did add a few extra back in, but these were ones I had been carrying in my head, getting them down on paper made me feel like I was getting rid of even more clutter. I’ve tried to be methodical and to keep my desk tidy, but I’m not that organised, particular when the pressure is on. Taking time out to tidy up makes all the difference to how I feel.
Following I tidy up I often feel the need to change my working practice a little too.
Over on Thinking Faster, Jeffrey Phillips is trying to challenge some of our thinking about change.
I have long puzzled why some change is easy and some change is more difficult, particularly corporate change. Previously I thought the issue was communication and understanding. If we communicate well enough to people they will understand why the change needs to happen and then it will go more easily. I then discovered how difficult communication is. Even when vast amounts of effort were expended on communication, the change still wasn’t easy.
Jeffrey suggests that the issue is really choice and control:
“I think this is driven by choice. I can choose to change my diet or route to work. I can even choose to change my career. However, I want some control when change is forced upon me, and I suspect that many other people feel the same way. The reason people resist change in organizations is not because they can’t change, and really not because they fear change, but because the individuals don’t control what’s happening.”
My experience is that choice and control are part of the story, but that they feed into a bigger issue – felt need. To put it more specifically – do I feel like I need what this change gives me. I’ve deliberately used the word “feel” here, it’s not whether I actually need the thing that this change is giving me, it’s whether I feel that I need this thing. A child feels the need for the favourite toy as much as the need for a glass of water, but they don’t actually need the favourite toy. Adults aren’t too different.
Asking people to take control and to give them a choice about when and how increases their feeling of need. They’ve put something of themselves into something, so they must need it. Giving a child more than one favourite toy is one way of removing their reliance upon one.
Communication is difficult because people will only engage with the communication if they feel they are going to need it. Most people read communications from the Tax Man because the likelihood of need is quite high, fewer people read the leaflet selling double glazing unless you feel like you have a need for new glazing.
Talking of double glazing, a great example of felt need is one of my neighbours who replaced all of the glazing in his house (at significant cost) because he said that the house looked “tired”. He didn’t even try to convince me that it would save him money in the long-run (the usual way of justify a felt need). He felt that he needed to change the glazing, so did.
Quite often, though, the felt need and the actual need are blended together into a complex matrix. Clothes are probably the most interesting example of this. We change our clothes with the seasons (in the UK we do anyway), and we change them because they get worn out. We also change our clothes because fashions change, what we regard as looking good changes. Because of this merged set of actual needs and felt needs there is a whole industry desperately helping us to change. They’re not telling us (directly) that we need to change, we are because we feel the need. One of the actual needs to change our clothes is that they get worn out – but there is very little information from the clothes industry on how long a piece of clothing will last. The reason for this is that one of our felt needs for change normally kicks in before the clothing has actually become worn out. We even see clothing that doesn’t fulfil the actual need, but the felt need is so strong that people wear it.
I’ve been involved in a lot of IT change. Most of this change has been very painful. In most cases we have focussed 100% of our effort on the actual need, and spent a minimal amount of time trying to understand the felt needs. I remember the commotion that one particular lady created by insisting on keeping her current monitor during a desktop refresh programme. Why? Because this monitor had all sorts of stickers on it that this lady felt she needed. The was an actual need to replace the monitor, it was worn out and probably hurting her eyes, but the felt need was far stronger.
We need to get smarter at trying to create a felt need; choice and control seem like good tools to use in this quest.
I decided that my experience with IE7 on Vista was sufficiently positive that today I upgraded my main machine to Windows Internet Explorer 7.0 for Windows XP SP2 or IE7 as it will be known 
.
Over the last few months I’ve been working on a project in my spare time. This project has been a departure for me because it has been for a charitable organisation where the terms of reference have been significantly different.
I’m used to situations where the questions of cost v benefit are defined in pounds and dollars.
I’m used to working in situations where the requirements specification is reasonably well understood (well sometimes anyway).
I’m used to large scale situations.
As a diversion from all of these, this project has been fun. It’s had a life of its own and hasn’t finished yet, but I thought I would share where I am up to.
The project in question is the web site for the church we attend Fulwood Free Methodist Church.
The first question I had was this: “What is a church web site supposed to do?” We had some key aims that we wanted to achieve, but apart from two or three basic things this was a journey of discovery.
My architecture skills helped (a little) with this journey; it helped me to break the problem down into a number of different areas:
It was obvious early on that we needed to have some sort of content management system and to move away from one person being responsible for all of the technology, the content and its freshness. I looked around at a few Open Source Content Management Systems and settled on Joomla. This was a few months ago and it wasn’t 100% clear at that time whether Joomla was going to take off, but thankfully it has. We already had an agreement with a hosting company which included MySQL and PHP included, so that was the easy part.
The next thing to tackle was the audience and to structure the content around the audience. We concluded that our primary audience were those people who didn’t attend, with church attendees being a secondary audience. With that we did a bit of brain storming around the type of questions that someone not attending might ask:
We also wanted to make future events and important content visually up at the front.
Joomla has a concept of Sections, Categories and Items. Items are created in Categories which are within Sections. Any item can then appear on the front page along with selected modules. Modules provide added functionality like a calendar or a document management capability, or a banner. This is then all displayed in a template.
Since starting we have constructed the main site and sorted out the structure. We have also sorted out most of the content, though there is more content to come.
The next challenge was how to make things more interactive. Being a blogger I am now encouraging the church staff to get blogging. Joomla is a bit clunky when it comes to blogging so I decided to make a break from Joomla for blogging and to add WordPress into the mix. Have WordPress alongside Joomla also allowed me to put the mechanics in for podcasting the Sunday Talks.
Although very different to Joomla, WordPress has a similar set of concepts and structures.
So without spending any money on software we created a web presence that:
A big thank you goes out to all of those people working away at producing this software so that the rest of us get such great functionality for the best possible price.
It’s been great fun learning something new.
Go and have a look and let me know what you think www.fulwoodfmc.net.
Looks like it might be time to move house according to this picture and associated article from the BBC today .
It’s not too good for Sue either.
As diet seems to be the main issue and because it plays such a huge part in brain health it’s not just an issue for life expectancy.
Rod Boothby has been having some fun this week poking a stick it the IBM Lotus community (here, here).
I’m not going to join that particular fire-storm, instead I am going to use it as a branching point.
Rod seems to assert two things:
If you read through these two posts you will find these statements:
Quoting Charles Robinson:
“Not everyone likes working with applications in a browser. We’ve done extensive usability testing at work, and in nearly every case users prefer the Notes version to web-based implementations. We tried to force a group of users to only use web-based mail and they simply stopped checking it because they hated using a browser. (We tried them on Zimbra, too, and had the same result so it wasn’t just Domino Web Access.)”
Rod’s answer is:
This, to me, is a surprising result. The examples of Yahoo! Mail, HotMail, Gmail, MySpace, Flickr, YoutTube, FaceBook, Wikipedia and the 50+ Million blogs out there would tend to contradict that user testing.
Is that really how it is for everyone out there? Because it isn’t for me.
I don’t use Web 2.0 applications because of their browser interface I use them for far more basic reasons:
In summary: I use these sites because I get something out of it. I’m selfish. I’m not using them because they have a great interface.
When it comes to using these tools through the browser:
I didn’t write all of these tools so I’m assuming that I’m not the only one who would prefer not to use the browser.
Unfortunately I don’t have any statistics for it, but I would guess that I am using my browser less now than I was 18 months ago. The important thing to me is that the data is in the cloud and that I can access it from wherever. Now that most of my data is coming to me via RSS I don’t have to use that slow browser thing.
The need for accessibility means that I want a browser interface, but I’m not going to use it every day just because it’s there. The browser interface is not optimal so I’m better off using the things that is.
Page optimized by WP Minify WordPress Plugin
