Showing posts with label IT Projects. Show all posts
Showing posts with label IT Projects. Show all posts

2012/10/05

Unringing the Bell: Impact of IT systems on Large Business Survival

I've posited that Telstra will be severely challenged within 15 years due to Structural Change within their Industry. They aren't fast or agile enough to adapt to the new world..

What are the factors that will prevent them from adapting? My top two:
  • Management Culture
  • IT Infrastructure
An underlying problem is that we don't have language or metrics to describe and quantify the many important aspects of management. In Physics and Engineering we have many concepts and terms that are measurable to great precision. The importance of those is shown by the materials revolution over the last 100 years. For a tour de force on the topic, a book that's been in print for 45 years: The New Science of Strong Materials.

Whilst "Management" and descriptions and theories about it has become an increasingly large field of study, we don't have a "Science of Management" with precisely defined and measurable terms.

This is crucially important when ownership (shareholders) and control (managers) is separated. The owners have no nuanced, standardised measures to evaluate the most critical part of the business: management. All we've got is the Accounting Standard Reports provided in Annual Reports. This is far from enough to make informed decisions on a business' future prospects.

I can't detail or quantify the many problems of Telstra's Management Culture, just waive my hands and say "it's the vibe". E.g. they not only don't do Customer Service well, they prioritise short-term cost-savings above good service and seem to go to great lengths to not resolve customer faults, at least in some areas.

Management is about doing what's important consistently well, doing what has to be done well enough and not doing at all the things that don't need to be done. [And avoiding entirely the things that should never be done.]

My Professional expertise is in IT Infrastructure. I hold a contrary view to the mainstream Management view of "IT is a Cost Centre". IT provides automated Business Processes, like employees directly responsible for all the Business Revenues: IT is a Profit Centre, not Cost Centre.

We've already seen businesses failure due to their failed I.T. systems: One.Tel is a shining example.

IT Infrastructure has, for the last two decades at least, constrained business mergers. If I recall correctly, the St. George-Westpac merger was cancelled twice due to "incompatible IT systems". Not sure how they solved that in the end.

Westpac itself is notorious for a decade long project, CS90, that was cancelled in December 1990. It was meant to be the ultimate Banking System (an 'ERP') that IBM would resell around the world for them. It was consuming 5-10% of Westpac's operational revenue.

The $10B Telstra "IT Transformation" under Greg Winn ran for around 5 years with the intention of reducing 1500 systems to 300. It failed to meet its targets and went live in 2009 with the 30% most valuable customers not migrated [from my Case Study evidence, now full of migration errors.]

The point: large businesses are inextricably intertwined with their IT Systems - they are part of the Business DNA and essential to the Business Differentiation: What we do differently that people value.

Too often IT Systems are allowed to "grow like topsy" and are never rationalised or reorganised, presumably because no immediate savings or value can be demonstrated, but mostly because nobody is responsible for everything and ensuring IT Systems are well maintained and suitable.

Leading to "Big Bang" projects like Telstra embracing of off-the-shelf ERP and CRM systems to resolve the mess. Inevitably they find that things are much more complex and intertwined than they knew, not the least because they have no correct, current System Maps and the whole was never designed or planned, it just happened. All of which suggests Management asleep at the wheel.

It will probably take Telstra 10 years to get staff trained, most, not all, data corrected in their new systems and workaround established to cater for what the new systems don't do.

But what will it be left with then? Will those systems be nimble, quick and responsive or big, cumbersome and so hard to change as to be effectively frozen?

Young, small companies start small and add functions as needed: the I.T. equivalent of "greenfields".

They don't carry of a legacy or mindset of "we have to cope with everyone and everything".

This is the commercial advantage small ISP's had over Telstra: no past, no baggage, just simple effective systems.

This will be the problem that Telstra will have to face again in 2020 as Retail Providers using the NBN challenge it. Telstra knows the pain, cost and delay in redoing their I.T. Systems, they won't be going there again anytime soon.

This is a generic and on-going challenge for all successful businesses, including those small, nimble Retail Providers: how to keep I.T. Systems from degrading into an unchangeable morass?

When Data hardens in Organisational Arteries and structures/processes ossify, a major Cardiac event will follow... More of the Same cannot fix the problems, radical rethinking is needed.

In an increasingly automated world, a problem looms for every large business: what happens to the IT Systems when you downsize?

You get to drag the big, bloated corpse of yesterdays organisation along with you. It never gets better with age...

It's easy to lay-off staff and "reorganise", but I've never heard of any organisation looking to make commensurate simplifications to their I.T. systems.

I suspect that Large Business who aren't consciously and deliberately cleaning-up and refreshing their I.T. Systems will ultimately fail due to the complexity, inflexibility and inadequacy of their Legacy Systems.

You can lay off Staff and cut whole Departments, but where do you start with the weeds that permeate your whole organisation and choke the life out of it?

Once built, it seems you can't "Unring the Bell" of legacy I.T. systems, you're stuck with them and they define what you can do, while smaller companies whizz past you on their way to Market Domination and being strangled by their Legacy systems.



Jerry Gregoire as CIO of Dell Computers in 1999 talked about how he tackled this problem - and won.
When he joined Dell, there was a massive ERP project underway, "One System To Rule Them All". It was late, over-budget and failing. His first action was to cancel the project and front the board...

Instead, he moved Dell to a new architecture dubbed "G2", based around a message broker.
It reduces the N*N-1 or N-factorial system interface problem to one...

All every system needs to interact with every other system is one 'message broker' interface.
It comes with a cost - you need infrastructure and rule sets to switch the messages. But at least that's a known, computable cost.

Dell Business Strategy Secrets
An ERP Package for You...and You...and You...and Even You

2009/04/27

Mircosoft can't write O/S code

This cartoon lampoons Windows 7.0 Beta. Eerie.

It underlines for me that Microsoft is crap at writing Operating Systems code.
O/S's need to be correct, secure, robust (resilient to errors internal & hardware) first and foremost. Only after that look to features and 'performance'.

2008/11/29

Gershon Report - Review of Australian FedGovt ICT

The Gershon Review is good solid stuff that doesn't rock the boat, doesn't challenge current methods & thinking, nor show deep understanding of the field.

It has a major omission - it addresses ICT inputs only.
ICT is useful only in what it enables others to do or improve - measuring & improving ICT outputs is completely missing from 'Gershon'.

It doesn't examine the fundamentals of ICT work:
  • What is that we do?
    How is Computing/IT special or different to anything else?

  • Why do we do it?
    Who benefits from our outputs and How?
Here are my partial answers to these questions:
  1. Computing is a "Cognitive Amplifier" allowing tasks to be done {Cheaper, Better, Quicker, More/Bigger}.

  2. IT is done for a Business Benefit.
    Like Marketing, defining how outputs & outcomes are measured and assessed - both in the macro and micro - is one of the most important initial tasks.

Gershon doesn't address outstanding issues of the IT Profession:
  • improving individual, organisational and general professional competence and performance.
  • Reducing preventable failures, incompetence/ignorance and under-performance.
  • Deliberate, directed & focussed effort is required to institute and maintain real Improvement of the Profession. (vs 'profession-al improvement' of practitioners)
After ~60 years of Commercial Computing:
  • Are there any new ways to stuff things up?
  • Is it "efficient, effective, ethical" to allow known Errors, Mistakes, Failures to recur without consequences? [see FMAA s44]
It isn't like the Government isn't aware of the processes and instruments needed to avoid repeating Known Errors, nor the benefits of doing so.

Aviation is controlled by ATSB (Australian Transport Safety Bureau, previously Bureau of Air Safety Investigation [BASI]) and CASA (Civil Aviation Safety Authority). The USA's FAI publishes hard data on all aspects of Aviation - and mostly they improve on every measure every year. This isn't just due to the march of technology - the figures for 'General Aviation' (as opposed to Regular Passenger Transport) plateaued decades ago... This is solid evidence that Aviation as a Profession takes itself seriously - and that commercial operators in one of the most competitive and cut-throat industries understand the commercial imperative of reducing Known Errors.

Aviation shows that profession wide attention to Learning and Improvement isn't just about Soft benefits, but translates into solid business fundamentals. You make more money if you don't repeat Know Errors/Mistakes.

ATSB investigates incidents and looks for Root Causes.
CASA takes these reports and turns them into enforceable guidelines - with direct penalties for individuals, groups and organisations. CASA is also responsible for the continual testing and certification of all licensed persons - pilots, Aircraft Engineers, ...

There are 4 specific areas Gershon could've included to cause real change in the IT Profession - to start the inculturation of Learning & Improvement and the flow-on business gains.
Federal Government accounts for 20% of total Australian IT expenditure. It is the single largest user and purchaser of IT - and uniquely positioned to redefine and change the entire IT profession in Australia.
  • Lessons Learned - Root Cause Analysis of Failures/Problems
    Dept. Finance 'Gateway Review Process' on Projects.
    Needs equivalent of CASA - inspection and enforcement of standards plus penalties/sanctions - Not just reviews and suggested guidelines.
    Not just ICT staff, not just FedGovt but their suppliers/vendors/contractors as well.
    Without real & timely (personal and organisational) consequences, nothing changes.

  • Standish 'Chaos Report' equivalent - real stats on IT Projects.
    Without solid numbers, nothing can change.

  • Operational Reviews.
    How well does an IT organisation do its work?
    Critical Self-assessment isn't possible - exactly the reason work needs to be cross-checked for errors/mistakes/omissions/defects.
    C.f. Military Operational Readiness Reviews - done by specialist, impartial experts.

  • Individual Capability Assessment - equivalent of on-going Pilot etc recertification.

  • Research: Quantifying & standardising metrics and models for "Effectiveness".
    DCITA/DBCDE on macro-economic results.


The ACS describes Gerhon's recommendations as "all aimed at addressing the efficiency of ICT":
  • governance,
  • capability,
  • ICT spending,
  • skills,
  • data centres
  • sustainable ICT
Note the issue of Reducing Faults/Failures/Errors/Mistakes doesn't make the list.
Nor does the idea of institutionalising the building/improving the Profession of IT and increasing the Capability/Performance of IT Professionals.

By the DCITA/DBCDE own reports, ICT contributes 75% of productivity improvements: ICT is still the single greatest point of leverage for organisations reducing costs and improving output.

Does getting IT right in Federal Government matter?
Absolutely.

Gershon delivers 'more of the same' and could conceivably achieve its targets of 5% & 10% cost improvement

2007/03/20

Perfect I.T. Project Management - They're Research Projects!

My last post took me most of a day to produce. Not a great words/minute rate.
I'd expected to spend no more than an hour - it's work that I first did around 2000, so I'm familiar with it.

A friend jibed that "You should've used your I.T. project management methodology".

I do have stong views on managing I.T. projects, especially large one, and they are backed up by the solid research data from Standish Group. They do apply to exactly this task of writing. Unfortunately they offer no useful guidance.

  • All new programs are research projects
  • If you haven't got working code, you don't know how long it can take. If it's a complex task, then beforehand you cannotknow where the 'beartraps' are.
  • At any point in a project, you can only see in detail a couple of weeks ahead.
  • 'Scale' is everthing [Alan Kay's argument]. Don't take on any project more than 30% larger than one you've completed successfully.
  • Everyone is an efficient, effective Project Manager - it's just the Domain and Scale that change.
  • Production of new Software is Pure Research. It relies on Creativity, it will take unanticipated twists and turns, you can't order "breakthroughs" to schedule, seemingly simple things can be 'too hard' and it's only Done when it's Done (The Golden Rule of Open Source). And when you're done, you probably want or need to redo it - completely - and several times.


The Standish Group's rule is: Maximum of six people for six months.
That's a summary of 50,000 detailed case studies. I think it's worth taking on board.

So I feel happy about my little project taking as long as it did.