Onward and upward

As you may have seen by now, I have taken the decision to take a step back from working at Freeform Dynamics.

When I first became an analyst some ten years ago now, little did I know what the journey would have in store. As far as I was concerned with my background as an IT manager, here was an opportunity to share the lessons and experiences I had learned with a much wider audience. Joining Freeform Dynamics at first glance appeared to be more of the same – of course I would get the opportunity to continue working with Dale and Helen, but being an analyst was being an analyst, right?

Freeform’s model was simple – to offer firms custom-designed research at a more accessible price than previously had been available, distributing it using media relationships and the still-nascent social Web. The ‘trouble’ came as a deeply shared goal emerged from our research programme – to focus on how organisations were really using IT, rather than how anybody might want them to. From within the company, this seemed a most natural thing to do, though over time it became apparent just how out of kilter this sometimes was with the broader landscape of IT marketing.

All the same, we plugged on, using the funding from vendor-sponsored studies to broaden our own understanding of how IT is done. We learned, we debated, we discovered, we tested hypotheses and opinions and we fed it all back into the machine. The partnership with online news site The Register gave us unprecedented access to those at the coal face of IT – from senior decision makers to programmers, operations staff and deeply technical specialists. Working with The Register has been a fantastic litmus test, as its audience does not hold back if what we are saying does not resonate!

Being small also made us nimble and we have been able to flex with the times, riding out both the downturn and the arrival of social media to our advantage. Early on, we had taken the active decision not to write white papers – these are vendor-sponsored short documents that actively promote a specific product or approach – and to this day I cannot get my head around how they are anything other than paid-for advertising.

However, we did spot a gap in the market for orientation guidance, that is, simple to understand, balanced explanations of a technology area – what was it, where it was useful, and how to start thinking about it. As the market for hard-core research dried up during the downturn, we identified alternative revenue streams initially founded on basic primers, which led to working with Wiley on the ‘For Dummies’ imprint. This in turn gave us the idea of setting up our own ‘Smart Guides’ – these in turn have been very successful, and much-coveted.

Freeform Dynamics has grown from success to success, even though it has gone through the same tough times as everyone else, and despite internal challenges such as dealing with Dale’s illness. When he offered me the CEO role two years ago I knew I had no choice – it was an offer I couldn’t refuse, not just because of the opportunity, but also that I couldn’t see any clear future to the company if I said ‘no’. And I haven’t regretted a single moment, it was one of the best decisions I have ever made.

Internally however, we all knew it was not going to be forever. I would love to be the kind of person who could take a role and stick with it for twenty years, but I’m not – on the upside (this is what I like to tell my wife), it’s the breadth of experience that makes me what I am. I initially told Dale and Helen I would join for two years, and then we would see what happened; while I in no way feel I have outstayed my welcome, I have had to ignore or otherwise put off a number of other opportunities and activities. Even as part of such a sterling management team, running Freeform Dynamics has been a full-time job in every sense.

In practical terms, the timing of my departure was never going to be ideal. At this point however, we have defined a structure, approach and organisation which enables the company to lead with its own agenda, rather than being buffeted by the agendas of the industry; we have a more pro-active approach to growing client relationships; we have a renewed focus on research as budgets start to free up, and finally, a reputation that is second to none as a ‘voice of reason’ for the industry. The mainstay of the exit plan was to leave things in good shape, and I believe that is exactly what we have achieved.

I shall be spending the next couple of months dealing with some immediate side projects – yes of course, there is a book in the works, and I’ll be working with Dale and Andy on some research we have been doing into more consumer-related aspects of technology. I’ll also be taking the opportunity to stand back, do some research and have a proper think about it all, something that just hasn’t been possible until now. I’m delighted to remain an active affiliate of the Freeform team, and I am not ruling out anything for the future.

Above all, I am immensely proud of everything we have achieved as an organisation. The Freeform team is undoubtedly one of the best I have ever worked with, not just in terms of competence, which equals any analyst firm out there, but also philosophy. Rather than forming an ivory tower so common among analyst firms large and small, Freeform Dynamics occupies the same space as the people it ultimately serves – those who define, procure and deploy IT systems and services for their organisations. To my very core and whatever happens in the future, I will always be proud to be a card-carrying Freeformer and I look forward to whatever opportunities may arise to work with Dale, Helen and the team again.

Onward and upward indeed!

The great cloud joke

Once upon a time, in the cloud kingdom of Cloudalon, there lived a cloud king. One cloudy day this cloud King, who was cloudily named Cloud Cloud the fifth, called his cloud son, the cloud prince Cloud Cloud the sixth, over to his cloud side.

“My cloud son,” the cloud king said to cloud prince Cloud Cloud the sixth, “in another cloud kingdom a very short cloud distance away there lives another cloud king. This cloud king has a cloud princess that I think that you should marry. Here she is, the cloud Princess Cloudina Cloud of Cloudonia.”
Cloud prince Cloud Cloud the sixth, upon seeing the cloud princess Cloudina Cloud of Cloudonia, agreed to marry her. And so, on the next cloudy day, in the cloud garden, Prince Cloud Cloud the sixth and stood by the cloud altar and watched his cloud bride-to-be, the cloud princess Cloudina Cloud of Cloudonia, march down the cloud aisle wearing a cloud wedding dress and carrying a bouquet of cloud flowers. Just as the cloud princess Cloudina Cloud of Cloudonia reached the cloud altar, however, an evil cloud magician appeared and cast a cloud spell on the cloud princess. In a cloudily moment, the cloud princess Cloudina Cloud of Cloudonia had vanished.

“What have you done?” cried the cloud prince Cloud Cloud the sixth.

“I have sent the cloud princess Cloudina Cloud of Cloudonia to a cloud cave in the cloud mountain Mount Cloudtop. There, in her cloud cave, she is guarded by the cloud dragon Cloudfang. The cloud princess Cloudina Cloud of Cloudonia is cloudily safe there, but the cloud dragon Cloudfang, will not let her rejoin the cloud kingdoms of Cloudalon and Cloudonia.”

“You are cloudily insane,” the cloud prince Cloud Cloud the sixth said to the Cloud magician, but the cloud magician had vanished.

“What are you going to do, my cloud son?” the cloud king Cloud Cloud the fifth of Cloudalon asked his son, the cloud prince Cloud Cloud the sixth.

“I am going to take my cloud horse, Cloud Lightning, and my cloud sword, Cloud Death, and go slay the cloud dragon Cloudfang and rescue the fair cloud maiden the cloud princess Cloudina Cloud of Cloudonia.”

“May the cloud God speed you well on your cloud journey,” the cloud king Cloud Cloud the fifth of Cloudalon cloudily blessed his cloud son, the cloud prince Cloud Cloud the sixth. With that, the cloud prince Cloud Cloud the sixth got his cloud sword, Cloud Death, and his cloud horse, Cloud Lightning, and rode off to the cloud mountain of Mount Cloudtop and the cloud cave thereon, in which lived the cloud dragon Cloudfang and his cloud prisoner the cloud princess Cloudina Cloud of Cloudonia.

The cloud hero of this cloud story, the cloud prince Cloud Cloud the sixth of Cloudalon, rode his cloud horse Cloud Lightning over many cloudy miles along many cloud roads and through many cloud fields. He crossed many cloud streams and many cloud mountains, though none of them were the cloud mountain of Mount Cloudtop and the cloud cave thereon, in which lived the cloud dragon Cloudfang and his cloud prisoner the cloud princess Cloudina Cloud of Cloudonia. When the cloud prince Cloud Cloud the sixth crossed these cloud mountains, he trudged his way through cloud snow. Cloud sand lined the cloud deserts he crossed, and there was cloud water in the cloud oases.

Eventually, the cloud horse Cloud Lightning got tired, so the cloud prince Cloud Cloud the sixth carried his cloud horse Cloud Lightning over many cloudy miles along many cloud roads and through many cloud fields. He crossed many cloud streams and many cloud mountains, though none of them were the cloud mountain of Mount Cloudtop and the cloud cave thereon, in which lived the cloud dragon Cloudfang and his cloud prisoner the cloud princess Cloudina Cloud of Cloudonia. When the cloud prince Cloud Cloud the sixth crossed these cloud mountains, he trudged his way through cloud snow. Cloud sand lined the cloud deserts he crossed, and there was cloud water in the cloud oases.

Finally, the Cloud prince Cloud Cloud the sixth reached the cloud mountain Mount Cloudtop. There, in a cloud cave on top of the cloud mountain, Prince Cloud Cloud the sixth of Cloudalon could see the cloud smoke from the cloud dragon Cloudfang who lived in the cloud cave in which the cloud princess Cloudina Cloud of Cloudonia was a cloud prisoner. Our cloud hero, the cloud prince Cloud Cloud the sixth of Cloudalon, climbed the cloud mountain Mount Cloudtop and slew the cloud dragon Cloudfang as the cloud beast slept cloudily. The cloud prince Cloud Cloud the sixth of Cloudalon rescued the cloud princess Cloudina Cloud of Cloudonia. But their cloud adventures were not yet come to their cloud close. They still had to get home cloud and sound.

So…

The cloud hero of this cloud story, the cloud prince Cloud Cloud the sixth of Cloudalon, and the newly rescued cloud heroine, the cloud princess Cloudina Cloud of Cloudonia, rode the cloud horse Cloud Lightning over many cloudy miles along many cloud roads and through many cloud fields. He crossed many cloud streams and many cloud mountains, though none of them were the same cloud mountain of Mount Cloudtop which in the cloud cave thereon the cloud prince Cloud Cloud the sixth slew the cloud dragon Cloudfang and rescued the cloud prisoner the cloud princess Cloudina Cloud of Cloudonia. When the cloud prince Cloud Cloud the sixth crossed these cloud mountains, he trudged his way through cloud snow. Cloud sand lined the cloud deserts he crossed, and there was cloud water in the cloud oases.

Eventually, the cloud horse Cloud Lightning got tired, so the cloud prince Cloud Cloud the sixth carried his cloud horse Cloud Lightning and the newly rescued cloud heroine, the cloud princess Cloudina Cloud of Cloudonia, over many cloudy miles along many cloud roads and through many cloud fields. He crossed many cloud streams and many cloud mountains, though none of them were the same cloud mountain of Mount Cloudtop which in the cloud cave thereon the cloud prince Cloud Cloud the sixth slew the cloud dragon Cloudfang and rescued the cloud prisoner the cloud princess Cloudina Cloud of Cloudonia. When the cloud prince Cloud Cloud the sixth crossed these cloud mountains, he trudged his way through cloud snow. Cloud sand lined the cloud deserts he crossed, and there was cloud water in the cloud oases.

Eventually, The cloud hero of this cloud story, the cloud prince Cloud Cloud the sixth of Cloudalon, got tired, so the newly rescued cloud heroine, the cloud princess Cloudina Cloud of Cloudonia, carried the cloud horse Cloud Lightning and the cloud prince Cloud Cloud the sixth of Cloudalon over many cloudy miles along many cloud roads and through many cloud fields. She crossed many cloud streams and many cloud mountains, though none of them were the same cloud mountain of Mount Cloudtop which in the cloud cave thereon the cloud prince Cloud Cloud the sixth slew the cloud dragon Cloudfang and rescued the cloud prisoner the cloud princess Cloudina Cloud of Cloudonia. When the cloud prince Cloud Cloud the sixth crossed these cloud mountains, he trudged his way through cloud snow. Cloud sand lined the cloud deserts he crossed, and there was cloud water in the cloud oases.

Cloud alases and cloud alaks, though, for it seems our cloud heroes, the cloud prince Cloud Cloud the sixth of Cloudalon and the cloud princess Cloudina Cloud of Cloudonia got lost on their way home, for they wandered into the cloud kingdom of an evil cloud king, the evil cloud king Cloud Cloudonovov of Cloudovia. This evil cloud man had the cloud heroes, the cloud prince Cloud Cloud the sixth of Cloudalon and the cloud princess Cloudina Cloud of Cloudonia, arrested and taken to be driven away and thrown into the cloud dungeon. Just before the evil cloud king Cloud Cloudonovov of Cloudovia put them on the cloudy transport, however, he said….

“Cumulon, im bus!”

With many thanks to http://www.sccs.swarthmore.edu/org/swil/JoelPage/purplejoke.html

Conference keynotes, and the gulf between simple and complex

Another day, another keynote. This time it’s Microsoft TechEd in New Orleans, and Bob Muglia is on stage being all thrilled about all those new and improved aspects fo IT. Three weeks ago it was Ajei Gopal at CA World. Today, elsewhere in the US IBM is kicking off its Rational conference, and I believe from my Twitter feed that SAS has a gig, somewhere.

It’s important to remember that most normal people don’t spend their lives attending IT conference keynotes. the real attendees at such conferences will have paid through the nose to come, and likely there may have been a little lottery between team mates about who should go. I know that back in my days as a punter rather than an analyst, attending conferences was very much a one-off, not just for cost reasons but also because I would have been too busy actually running stuff. (As an aside, it’s one of the reasons analysts exist)

So, most people in the rather humid hall I am sitting in right now will not have the luxury of comparison between multiple keynotes – and indeed (based on the “time ” thing) may not have had the luxury to stop and think about some of the things that are being presented. But, for better or worse, I do – and so it is that I inevitably start to think about how this keynote compares with those in the current batch, which appear like waypoints stretching back through the history of conference time.

Now I wouldn’t be so trite as to give marks out of ten for individual keynote presenters – though I am reminded of some of those dodgy talent competitions in the Seventies. Actually, even better than that, I wonder what Simon Cowell et al would make of Messrs Muglia and Gopal. The hand would slice, the brow would furrow and the head would shake, before the flabbergastingly obvious, albeit reasonably accurate commentary. “Haven’t we heard this before?” he would ask. Well, perhaps, but Simon never did understand the idea of paradigm shifts.

Strip away the repetition, the pseudo-excitement and exec cameos, and there is generally some good, interesting stuff in the average keynote. This one is no exception – new product announcements, capabilities that are now probable (whereas in previous keynotes they were just possible), yadda yadda. Right now for example, data visualisation is having its time in the sun – and to be fair Microsoft has a good story to tell around its SQL Server tools.

However, one area that’s pretty fundamental to IT never seems to get a mention at keynotes. All these new-and-improved capabilities are based on a core premise that they can exist in some kind of isolation from whatever else is in the IT environment. The irony is of course, that they never can – even small companies have existing technology investments, and anything new will have to work with all that old, and seemingly inferior stuff. This means both an integration impact to get new working with old, and a migration impact as the lucky elements of IT get rejuvenated and or replaced. (Hat tip to Roy Illsley for mentioning licensing as well, just before I posted this.)

Even if it were possible to adopt a green-field approach, the sheer complexity of IT very quickly comes back to bite anyone (particularly in marketing) who underestimates it. I was in a conversation a few weeks ago with a systems engineer at the Symantec Vision conference (yes, there was a keynote there as well, from Enrique Salem). The engineer went through a quick summary of the complications of failing over a production environment, in terms of servers, networking and storage, the level of hard coding still required, and the potential for error if any part of the systems were even slightly different. It was a welcome reminder of just how complex things really are, in most, if not all IT environments today.

I won’t go on as the keynote is due to finish soon. But as well as “star quality” or whatever else we feel should be on the keynote scorecard, let’s have a row for “ability to deliver in existing environments”. Perhaps it is the absence of this as a metric which has led to so many great ideas, presented at keynotes past, turn into dust – or worse, be rolled out again a few years later under a new terminological banner. IT is complex, and will remain so however hard people try to present it as something that is becoming simpler. And the sooner industry figureheads can take this on board and talk about it accordingly, the better.

How much “innovation” is just keeping up appearances?

Focus on business challenges, not technology innovations

The IT industry really does bring out the best and worst traits of human nature. Were we always quite so excitable about the latest big thing? It is difficult to tell, as historical records don’t tend to preserve the glee reserved for all things new and improved, whether or not they have any long-term advantage.

This is particularly relevant given that we are perhaps in one of the most inventive periods since the dawn of humanity – at least, that is how things look from the inside. While the jury is out as to the usefulness and ultimate value of many of our creations, the speed of “innovation” has been accelerating consistently over the past 500 years, such that we have now reached a point where it is impossible to keep up with everything that is going on.

It is a very human thing, however, to want to keep up appearances. In the arts it is important to have an opinion on the latest show, film, or book, and our high streets are full of the latest must-have items. You can see where I’m going with this can’t you – yes indeed, our cuckoo tendencies to accumulate shiny things also spills over into how we view, and indeed select and procure IT systems.

We all know this, but many go with it anyway. Marketing departments in IT vendor companies spend their time working out how to make even the most humdrum of technologies look like the best thing since, well, the last best thing. Phrases like “paradigm shift” and “game changer” are used over and again, even though both speaker and listener knows that if the paradigm had shifted as often as predicted, we would have run out of games to change long ago.

Business leaders are subject to the same pressures – after all, in the words of the Matrix agent, they are “only human”. It was only a matter of time before a CIO would say to me that his boss had asked him when could he get some of that cloud computing. The fact that the question doesn’t make any sense is neither here nor there: businesses want to demonstrate they are up with the corporate Joneses, just as CIOs themselves want to have a few leading edge projects on their CVs. Analyst firms as well can be no better, as indeed, if things weren’t quite as exciting as everyone was making out, would we really need analysts to make sense of it all?

Don’t get me wrong, there are lots of new and exciting things made possible through the use of technology IT. It has brought the world closer together, opening up whole new ways of communicating and collaborating, and so on and so on. The danger however, is that we are so busy looking beyond where we are for the next big thing, we don’t give ourselves the time to make the most of what we already have. Organisations don’t always need the latest and greatest technology to thrive, and there is a big difference between being flexible as a business and simply changing because that is what everyone else is doing. Far more important is that their requirements are clearly understood, and that the right tool is selected for the job in hand.

As my old boss Steve, a seasoned programme manager used to say, “What’s the problem we’re trying to solve here?” Okay, his language was a bit more colourful than that but the point still stands. As we look at the waves of so-called innovation and try to decide whether they have any relevance to our businesses, let’s first and foremost focus on the challenges we face, and how best to deal with them. In a couple of years time, when the dust has settled on the latest hyped-up bandwagon, if the challenges still remain then we won’t have been doing our jobs, even if the agenda item of “keeping up with innovation” has been achieved.

Looking back: Software is Art?

The traditional craftsman uses handed down principles and rules of thumb as the basis of his work: experience gained over many years of apprenticeship. The engineer proves his designs at every stage with scientific laws and mathematics. Craft and engineering differ in their techniques but they have a common goal remain the same : to provide efficient, useful artefacts.

In Computer Programming as an art, Donald Knuth summarises this by saying, “Computer programming is an art, because it applies accumulated knowledge to the world, because it requires skill and ingenuity, and especially because it produces object of beauty.”

The knowledge base that we have built up over thirty years is agreed to be incomplete. Reliance is often placed on software craftsmen, commonly known as ‘gurus’ or ‘hackers’ (in the programming world, a hacker is seen as a programmer of high esteem whereas it is the cracker who breaks into computer systems) – the reputation of some gives them almost hero. Robert Baber suggests that when software development progresses to be a true engineering discipline, such characters will disappear to be replaced by ‘members of professional bodies’. If this is going to happen it is a long way off yet.

And what of software itself? Is software an art form? Knuth refers to ‘beautiful programs’, and it is true that an elegantly structured section of code may be a pleasure to look at, at least to another programmer! This point should not be taken too far: a motorway intersection may well be an object of beauty to another construction engineer, but it is probably not for the rest of us. Artistic qualities do however have practical value for software : an elegant program is reasonably likely to be a well-written, maintainable one. It would be worth considering the addition of a little ‘art’ at all stages of the software life cycle. For example:

1. In the specification phase, a common language document is used to show the producer’s understanding of the clients’ needs. A well-written specification will increase the chances that such requirements have been noted; a readable specification may well ensure that both parties read it at all.

2. Software architectures can be elegant or impractical. An elegant architecture is one which ensures that its subsystems work together smoothly and efficiently; an inefficient architecture will be the source of an unnecessary performance overhead.

3. Algorithms can be fluid, smooth in motion or clunky and slow. A well-written algorithm will be more efficient than a badly written one.

4. The code itself can read like a good book or a child’s first essay. If the code is not readable it will quickly become unmaintainable, especially if its author is no longer available to explain it. Code should be self-documenting. If it is not clear exactly what a given code section is doing then it should be rewritten. In the maintenance phase, the code should also explain how it has been modified, by whom and when.

The quality of the product is dependent on the experience of the software developers – and their management – at their craft. Such craftsmanship must be learned. And as we have already seen, there is not always the time or resources available to provide such training. Peopleware makes the point that developers should be considered as experts rather than resources, and should be given enough space and facilities to permit them to excel. In DeMarco and Lister’s experience, it is this which ensures the optimal productivity of development groups.

Today’s software developer is somewhere between a craftsman and an engineer, using both science and common sense in his work. Tomorrow’s developer may well be the perfectly trained engineer proving everything as he goes. But he is not there yet. At least for the moment, gurus are a necessity and ‘software beauty’ keeps our minds on the goal.

[[And the punchline: this was written in 1994, as part of a bigger piece entitled Craft or Science - Software Engineering Evolution]]

IT looking forward

Video recorded at Microsoft tech days, 16 April 2010, following (and referencing) David Bishop at Microsoft’s “Vision of the Future” presentation.

Enjoy!

201005070936

Welcome Barry and Andrew

It is with great pleasure… Well, I would say that, wouldn’t I. But it really is with great pleasure that I’d like to introduce two new members of the Freeform Dynamics team, Barry Saunders and Andrew Buss.

Barry Saunders has joined us in a business development role for strategic accounts. Barry’s got a solid history of working for, and with, major vendors including IBM and Verizon, and we’re delighted in being able to bring someone with his experience on board.

As a seasoned IT industry analyst, Andrew Buss should need no introduction to the analyst community. From a coverage perspective, Andy will assume the lead for end user computing and access, integrating with the rest of the team to maintain that all-important horizontal insight that is at the heart of everything we do.

You can check the Research Team page for more information about all of us, and of course, do get in touch if you have any questions.

What personality is your IT department?

Over the years I’ve spent quite a lot of time thinking about the idea of IT maturity models – which are great in principle, but, to be frank, a bit of a blunt instrument when it comes to gauging reality. Many IT organisations are quite comfortable where they are in terms of maturity for example – providing ‘good enough’ service levels without necessarily striving to be best-in-class. Meanwhile, the theory that a large proportion of IT depts remain unable to crawl out of the in the primeval swamp of IT maturity is no more than that – a theory.

Are there better ways to consider how IT departments are structured and how they operate? To be sure, different options exist. A couple of years ago I was working with the ideas used in personality testing, to see if I could come up with a similar model for IT. One hypothesis, which I believe to be true, is that most IT departments will remain much the way they are unless they are subject to some external change – replacement of the CIO for example, or merger with another department. Until such times, it is more important to understand what an IT department is, than what it might become.

The personality of an IT department is multi-dimensional. Based on research we gathered with readers of the Register web site (report), coupled with some telephone study work, we were able to derive a number of characteristics of IT organisations, namely:

  1. Organisation – whether the IT function considers itself to be a technical or service department (TECHNICAL vs SERVICE)
  2. Process – the level of formalisation/repeatability of IT development and operations processes (INFORMAL vs FORMALISED)
  3. Approach – whether projects and deployment generally take place individually, or mostly with an eye on a broader strategy (DISCRETE vs PROACTIVE)
  4. Dialogue – how interactive are the communications between IT and the business (REPORTING vs ENGAGING)

None of the above is necessarily wrong. For example, an IT organisation may need to be Technical if the business is highly technology-driven; equally, some companies may benefit from a Discrete approach if lead times are the driving characteristic. Smaller organisations, or branches may have different needs to larger ones, and so on.

Such characteristics offer 16 potential combinations, but not all of these will be generally applicable. Combinations we believe will be more likely are as follows:

TIDR – The classic “traditional IT organisation” – IT exists for its own purpose and there is little or no relationship established with the business. Unlikely that IT has a particularly good reputation, and fire fighting will be common.

TIPE – This is “don’t watch the mouth, watch the feet” as the IT organisation appears to be doing everything right in terms of business engagement, but it still doesn’t appear to be moving forward in terms of maturity. This is due to to unwillingness to change from old practices and organisational models, though IT may be highly competent technically.

TFPR – The IT department feels it can do no wrong, and sure enough it is running a tight ship. However there is a feeling from the business side that something is lacking, as IT wants to engage on its own terms and sometimes gives the impression that it knows what is best for the business. IT wants a place on the board, but the business doesn’t feel comfortable with this.

TFPE – While just about everything is in place, IT still thinks like a bunch of techies. This is fine for businesses that are themselves technical, but it may mean that the cost of technology is not fully understood. In other cases it is likely to show itself in a lack of responsiveness as IT works to solve the biggest technical issues rather than understanding what’s the most pressing business need.

SFDR – While the IT function is doing what it can in terms of external processes, it lacks the necessary communications between development and operations. This may be because of political, or geographical reasons; in any case, the result is that ops falls back onto simple reporting, rather than being part of the dialogue itself.

SFPR – While everything is going generally right, IT may well be disappointing when it comes to engaging with the business, resorting to only sparse reporting on progress and performance. This may well be because the business itself does not understand why it should have to engage.

SIDE – There is a high level of engagement with the business, which is admirable. However, perhaps due to a traditionally fragmented approach to IT implementation, lots of legacy or otherwise (e.g. mergers), the environment itself is not in the best state, nor is how it is managed – so backups may be done inconsistently, or there may be security issues for example.

Such a model offers a useful starting point for any IT organisation, in terms of what is going to work – level of process, technology adoption and so on – as well as injecting a level of realism into proceedings. We all have aspirations, but we’re not going to get any better unless we understand ourselves first – that’s the principle anyway. Similarly, for vendors, the opportunity exists to create offerings based on how things actually work, rather than any over-aspirational view, or one-dimensional perspective on IT maturity. And meanwhile, models such as this may offer more realistic paths towards best practice, if and when we move into a more dynamic IT world.

More detail is available on this if it would be interesting and useful to anyone, including broader definitions of all 16 personalities. For now, I’d be very interested in feedback on the principle of the model itself – and whether or not it would work for you. So, if you have any thoughts on this, please do let me know.

Quick take: top ten worst passwords

This makes interesting reading – it’s a report, sponsored by those good people at Imperva, about password worst practices. It’s got some sage advice too, for anyone who wants to know how to get a bit better at setting passwords.

Her’s the top 10 – personally I’m surprised that swear words don’t figure, but that’s small consolation.

1. 123456
2. 12345
3. 123456789
4. Password
5. iloveyou
6. princess
7. rockyou
8. 1234567
9. 12345678
10. abc123

Take a look at the full report here.

P.S. There may be a longer take on whether Imperva *should* have conducted the analysis, but perhaps that one’s for history to decide!

Looking back… and forward

This year has not been easy for many. By all accounts it has been a polarised recession: some of the largest companies have fallen, while for others, business has been booming. The stock markets plummeted only to rebound; organisations have offered themselves up for sale and then decided, actually, they could go it alone; redundancy packages have been announced and then withdrawn; in the UK, house prices are once again higher than they no doubt should be – with the net effect of leaving individuals and companies alike with that best-just-get-on-with-it feeling.

In IT, perhaps, we have seen it all before. This is my tenth year as an analyst – and I seemed to spend most of the ‘middle years’ introducing every article and paper with the words, “as we emerge from the downturn…”. Now here we are again: budgets are being squeezed, Opex is generally the focus over Capex, and vendors and end-user organisations are having to demonstrate value in everything they propose. But ROI is no longer being punted as yet another “next big thing” – it is merely something that needs to be taken into account because it would be foolish not to.

Speaking personally, one thing is for sure, this certainly was an interesting (in the Chinese sense of “May you live in interesting times”) year to be taking over in charge of a company. Freeform Dynamics may be small but – just like any other company – we still have P&L to consider, bills to pay, mouths to feed. Looking back, I believe 2009 will be the year that we grew up as a business – across the team we learned to be more disciplined about what we do and how we do it. We remembered what it was we were set up to achieve, and I can now explain to family members what it is I do without them looking politely puzzled, or simply glazing over.

It’s been a hard year, but equally, it has been a good year for Freeform Dynamics. As we’ve grown we’ve learned more about how to engage with the audiences that matter to us most, that is, the community of mainstream IT decision makers and professionals. At the same time our writing skills have been developing, both through sheer force of having to do lots of it and with the help and support of David Tebbutt, who brought a much-needed level of editorial discipline to the company in the two years he was with us. Another high point was undoubtedly being voted second analyst firm in Europe by those people who manage analyst relationships. Strip everything else away and all it meant was, “The people we like to talk to.” Which, of course, means a great deal.

What of next year? When it comes to predictions, I’m afraid I can’t share some of our competitors’ opinions that Cloud Computing will be “The big thing” to happen in 2010. It occurred to me quite recently where the confusion lies – that in this wonderfully innovative and yet charmingly backward industry, changes that happen to IT vendors are often misinterpreted (transference, maybe?) as changes to how organisations do business. If we turn the telescope around, yes, sure, I have no doubt that Cloud Computing is already having quite an impact on the vendor space and will continue to do so. But while changes in the engine might be profound, we are a long way off achieving what end-users might consider to be a smoother drive. Back in 2002 I called the journey towards the Universal Service Provider “the revolution that never was” – and while I remain confident of the destination, it will take more than a few articles in Management Today, a hastily-organised conference and a Twitter hashtag to get us there.

My money is on virtualisation – an area of IT where the reality and the vendor hype do appear to be achieving some level of parity. Most organisations are still, in general terms, only trialling virtualisation. We can say both that the best is yet to come, and the fan has yet to meet the fecal matter. This will be a big year for infrastructure – getting the hardware layer working as a layer, moving data and execution capability around, building in the qualities required to underpin acceptable levels of service delivery, from data protection to risk mitigation. Very boring, very necessary, and undoubtedly where much of the action will be.

I’d also spare some thought for Green IT. We shall continue to see the debate broaden beyond power and cooling, and come April of course, “Green” will become a compliance issue. On the radio the pundits are talking about the failure of Copenhagen, but at the same time, individual countries have now moved a lot closer to deciding their own strategies. IT undoubtedly has a major part to play, not just in sorting itself out but particularly in how innovative use of technology can help reduce the overall footprint, and we shall be continuing to watch this area with interest.

Meanwhile, service provision in general is, as implied by Cloud, going to continue in its rapid evolution (that’s one for the punctuated equilibrium fans). The machinations of vendors are quite fascinating – companies with their heritage(s) in hosting, telecommunications, software, hardware, internet search and so on are all deciding, rightly or wrongly, that they are running after the same ball. It is like watching a flotilla of tankers trying to turn around and head in the same direction, towards a goal that remains, thus far, a mirage – some parts of the model are proven (managed services, outsourcing, certain contractual vehicles and so on) but others (Platform as a Service, anyone?) remain highly speculative.

Then what is this goal? IT is not an end in itself, it’s a set of mechanisms that help individuals collaborate better, and companies deliver services to their customers. Much depends on integration – at both a hardware and software level. It is all too easy to work out potential answers, but far harder to establish what will really make a difference given the mish-mash of technological slurry that already exists. At Freeform Dynamics we shall continue to peel back the layers of understanding, as seen through the optic of what’s really going to make a difference to mainstream IT – the centre of the bell curve. Our core business remains research, from which we shall continue to deliver down-to-earth, practical guidance aimed at real people, not theorists. It’s a simple enough vision: if you can’t see the wood for the trees, who would you rather meet – an elf with a magic map, or a woodsman?

From our perspective, we’ll be starting the new year with a team at full strength – we’re all delighted to welcome Dale back, now he has finally been able to say goodbye to what at times was a truly debilitating illness. We have some announcements up our sleeves, and we shall continue to grow our team of analysts, both to strengthen our core areas of coverage and grow beyond them. My heartfelt thanks go out to everyone in the team, for sharing the passion about what we are trying to achieve and working so hard to deliver on it.

A huge thank you also to everyone we have interacted with. It’s a complex web, isn’t it – the touch points between technology producers, consumers, commentators and advisors will no doubt continue to blur. 2010 will be “interesting times” for many, and we have learned enough over the past few years to not take anything for granted. But there remains plenty to look forward to.

Follow

Get every new post delivered to your Inbox.