ESSENTIAL TECHNOLOGY KNOWLEDGE FOR BUSINESS EXECUTIVES
Dr James Robertson is an independent management consultant who has undertaken an in depth study of the factors giving rise to information technology project failure and the failure of I.T. to meet business expectations. He has developed a concise “Pulse Measurement” investigation to diagnose why I.T. is underperforming and from this analysis of organizational pain he advises organizations how to achieve the true potential of their I.T. investments.
In this series of exclusive articles Dr Robertson shares the insight he has gained in nearly three decades of practical experience with regard to the effective application of information technology. These articles are intended expressly for CEO’s, CFO’s and other senior business executives. A complimentary series of articles address the subject from the perspective of the CIO and I.T. executives and managers.
Dr Robertson can be contacted at James@JamesARobertson.com
Many organizations experience a breakdown in communication between their information technology function and business management.
This results in situations in which organizations make critical decisions without clear understanding of the consequences and then experience considerable frustration and even loss as a result. In many organizations the divide between the "business" and the "technologists" is pronounced and sometimes adversarial.
This article looks at the situation from the perspective of the CEO and other executives on the "business" side of the fence. A companion article looks at the situation from the perspective of the CIO and those on the "technology" side of the fence.
In "CIO Insight" February 2004, published by Ziff Davis, Allan E Alter quotes Harvard Business School Professor Emeritus Richard L. Nolan as saying in a speech before the Society for Information Management the previous October that additional board oversight should be extended to information technology. "IT is the next disaster waiting to happen," Nolan is reported as saying. "Companies are running on autopilot. We're seeing boards that are essentially inactive, while even top managers are giving short shrift to IT."
The article goes on to report major I.T. project failures and to ascribe a major bankruptcy to I.T. system failure and suggests that board members may soon be sued by shareholders for negligence in the event of such incidents.
I consult regularly to organizations who are experiencing problems with I.T. or wondering what direction to take and, in doing this, I have the opportunity to talk to senior executives and CEO's and hear their side of the story and then to talk to the CIO and managers responsible for I.T. and hear their side.
Frequently one would think that one was looking at two different organizations, so distinct are the differences of perspective. In diagnosing these situations I have come to recognize the characteristics of the two poles and have also learned that it IS possible to facilitate the development of a constructive working relationship between the business and information technology. Frequently this does not require a large investment and generally it does not require the replacement of major systems or a change in the contractual relationship (outsourcing) between the I.T. unit and the business.
There are a number of issues that warrant attention in seeking to understand the perspective of the CEO and business executives generally.
I cannot get the answers I want
Frequently executives complain that they cannot get the answers they want to the business questions they are asking even though they know that the raw transaction data is being processed. Often the answer to this question is converted into a requirement to replace the existing system, such as the "E.R.P." system with a new, frequently "big brand", product.
E.R.P. is a commonly used abbreviation in business today but basically it refers to the accounting and related systems in the average business. Trouble is that "E.R.P." sounds much more impressive and, on the other hand, is not well understood. So the phrase takes on a mystique of its own and the product is perceived to have magical qualities to rectify the ills of the business.
Reducing the E.R.P. to its components parts and being clear that none of these are mysterious and none have the potential to magically transform the business is sometimes a key step.
Frequently the problem with getting answers translates to inadequate quality control on the data that is captured or the absence of appropriate provision for data classification and taxonomy (analogous to a library catalogue) which makes aggregation of data in the required manner difficult or impossible.
This is a content issue not a technology issue -- the content is the same irrespective of the computer and software being used -- your name and address are the same in all systems, the ability to process your details effectively is driven by the quality of the content rather than by the constraints of the technology. For example, if your name and address have been misspelt and entered fifteen different ways with fifteen different account numbers the computer will not be able to produce a consolidated statement of your account history without major manual effort to first remove the redundancies for all the people who have data in the system.
I.T. Projects miss deadlines
I.T. projects miss deadlines for a variety of reasons. One of the reasons is the breakdown in communication referred to above. The I.T. team are trying to deliver one thing and the business team are wanting something else with the result that at many project meetings changes are made to the specification or the scope. Frequently these things do not look like scope change or change of specification, for many people they are engaged on a voyage of discovery as they examine the business problem and it seems logical to make the changes.
At one level this is correct, however, if one were building an office building or a factory and at every site meeting the client instructed that walls be demolished, machine specifications be changed, etc, there would soon be an outcry as visible costs escalated and as trucks removed the rubble.
One of the critical challenges with I.T. projects is that the rubble is so intangible. It take seconds to delete days or months of work and there is no visible sign of the damage apart from a loss of morale on the part of those who have invested themselves in creating a solution that they thought was to specification.
It is vital to have a clear and comprehensive specification and to do reality checks on what is being requested. Many things can be created with software but, just as with a building or factory, they take time and cost money. The challenge is for the business to take responsibility for a clear business requirement statement and to develop a meaningful and measurable business value proposition for the real cost of the solution.
This requires both sides to take a stand on only undertaking projects for which there is a clear value proposition.
The answer is frequently "spend money"
As a consequence of the points raised in the previous section, the answer to a business request frequently translates into "spend money". Business users hear about some functionality or capability that some other business has, or claims to have, and then wants that functionality.
The required functionality is often specified in terms which relate to "XXX" where XXX is the name of a large, big brand software product and so what may well have started out as a wish list or fashion statement translates into a groundswell of opinion that the current system is "no good" and that it cannot do whatever is "required".
This results in a loss of confidence in the current system and a loss of morale and motivation of those who are operating the system. It can also result in pervasive corridor talk that permeates the board room until there is no confidence in the existing system and the notional requirement for something different becomes self fulfilling.
Frequently the answer to such a situation is a concise evaluation of what is really required and what really exists and then a board level decision to take custody of the existing system and "make it work". "Make it work" is a quality board decision starting with the Chief Executive which is then enforced throughout the organization in tandem with actions to remediate what needs to be remediated.
Outsource / insource
One of the consequences of the situations described above is that business executives decide to "outsource" the I.T. department to a third party organization.
Frequently this decision will be found to translate to "we do not know how to get this thing to work but there must be someone out there who can make it work" and so a key corporate resource is sold off to a third party. Sometimes this works because the act of outsourcing requires a solid contract and the legal advisors insist on tying up many of the loose ends resulting in conversations that should have taken place internally at lower cost being transferred to contractual negotiations.
Many times, however, the issues of mythology, lack of executive custody, etc transfer onto the outsource contract and frustration continues to the point where in some organizations the debate converts to whether to "insource" or look at changing outsource contractors.
The answer to this debate is generally a pragmatic look at what can be achieved and a realization that the factors causing failure are people related and not technology related. In fact, with a pragmatic understanding of the real issues, either insource or outsource can be made to work.
I.T. is moving so fast it seems to be hijacking the business
A widely believed myth is that "I.T. is moving so fast we cannot keep up with it" which translates in practical terms to a situation where it appears in some organizations that the business is being hijacked by the pursuit of the latest technology.
While at some level it is true that the technology is evolving at great speed, the good news is that in many cases business does not know how to apply the technology that already exists effectively and therefore the new technology is frequently irrelevant – improved utilization of what exists will frequently meet the real need.
On closer examination of the "moving so fast" myth it becomes apparent that for most organizations, most of the functions they perform have not changed much in the past decade and are unlikely to change that much in the decade ahead. Coupled to this, most organisations are not using what they already have to anything near its full potential.
Take what you have and learn how to use it really effectively in your business. A simple example, many organizations operate software which requires staff to capture text based information about interactions and yet they do not train those operators to touch type -- so they peck with two fingers and low speed and low accuracy and the effectiveness of the entire system is compromised. A touch typing course at a secretarial college is one of the most valuable "computer literacy" actions that many organizations could take for many of their staff, including executives who are answering their own emails.
Essential technology knowledge for informed business I.T. decisions
In responding to my experiences in evaluating I.T. situations where the business complains of under performance I have come to realise that there are some essential principles of information technology that many I.T. people take for granted but which are seldom communicated to people in the business in a formal fashion that everyone can understand and apply.
These are discussed below.
In considering the practical use of Information Technology it is important to recognize that the technology is abstract and complex. It is difficult to gauge the suitability of a system without looking in detail at numerous screens and reports, accordingly, it is relatively easy to take the route of "demolition" as opposed to "evolution" -- progressive enhancement of the existing solution.
In considering options it is useful to draw comparisons with physical world metaphors such as factories, warehouses, municipal services, buildings, etc.
Different I.T. solutions have different parallels, for examples, a big transaction processing system is like a large factory -- it uses standard production units which may be from various manufacturers assembled to convert specific raw materials to specific manufactured products with a limited number of operators for a large number of consumers ignorant of the process.
Following are some principles that I have found that many business people are either not aware of or do not accord sufficient importance to in taking I.T. decisions:
-- Computers are adding machines (on / off switches)
Computers are binary adding machines or switches that do all that they do by switching 0's and 1's (binary code). Everything that you experience with a computer is the ultimate outcome of switching based on binary patterns "10011010...".
Computer processors are machines nothing more and software and data are stored as streams of binary code. As a consequence, computers are predictable -- one could even call them "stupid" -- they do exactly what the instructions tell them to do.
But the process of following these instructions is not visible and they are executed at such huge speed that they appear mysterious and even magical to those who do not know how they work.
-- Databases are warehouses
Databases are comparable to physical warehouses. Particular pieces of information are classified and stored in a manner that facilitates their retrieval.
If the warehouse is well managed and well operated retrieval of information will be fast and flexible. A warehouse that is badly managed will not yield the expected outputs, not because of the technology but because of things that people are doing or not doing.
For this reason, content, standards and people (including corporate politics), NOT technology, are the primary inhibitors of system effectiveness.
There are also different approaches required to get data onto a disc for transaction processing and getting data off the disc for management decision support. In the absence of structured management input to the implementation of a system the probability of structured management information is radically reduced.
-- Automation software products are like machines
Automation software, ranging from word processing software to spreadsheets through to specialized systems like customer relationship management (CRM) are all comparable to machines.
An operator gives instructions and provides input to the machine which executes those instructions and produces output. No matter how sophisticated the software it is no more than a machine and the level of training, precision and deftness of the operator determines the quality of the output.
Most users of automation software are using a minute fraction of the functionality and therefore constant upgrading of the software is not necessary. The challenge is the business outcome NOT the technology.
-- Networks are postal systems
Networks are sophisticated postal systems. All data transmission on a network comprises electronic packets of binary information with an address on the front and a return address on the back.
The Internet functions by sending huge numbers of packets backwards and forwards to exchange complex binary information that is used by people to do things they experience as valuable. The Internet is not about technology, it is about communication and psychology.
-- People and business strategy determine the value delivered
In essence people and business strategy determine the value that is generated through the application of technology.
Information technology is inert, it is NOT strategic in and of itself, it does NOT create value in and of itself.
People create or destroy value.
Business executives who clearly understand these principles and apply them will find that they are much better able to define an appropriate role for information technology in their business and to engage in meaningful dialogue with those responsible for the technology.
The next article in this series will discuss the real issues with regard to achieving high levels of executive custody of Information Technology – an essential requirement for responding to the increasing threat of Governance liability of business executives with regard to I.T.
A simple confidentiality and non-disclosure agreement which you can tailor and elaborate on as you see fit and which may vary depending on your legal jurisdiction and your attorney. I recommend that this initial document is kept simple as you want ALL persons attending the initial tender briefings to sign this
You would possibly have a much more comprehensive agreement for your short list bidders and possibly more comprehensive still for your final choice although I personally hold that very detailed documents of this sort tend to be excessive
Click here to send us an email subscribing to our free newsletter -- all articles posted by James Robertson will be emailed to you
Business Systems NOT delivering?
Call the Business Systems Specialist
Dr James A Robertson -- has been involved in the effective application of Business Information Systems, including but NOT limited to ERP, since 1987 and in the profitable and effective use of computers in Business since 1981.
Drawing on a diversity of experience, including formal military training in Quick Attack techniques at the Regimental Commander level, Dr Robertson has developed highly effective methods of investigating any sub-optimal Business Information Systems situation -- be it an established system or a stalled project or any other source of Executive frustration -- quickly and concisely diagnosing the root cause of the problem and prescribing concise practical actions that Business Executives can effectively act on see the Pulse Measurement page and also the Sample Reports page for redacted real reports.
He has also developed highly effective methods of strategically enriching systems to unlock the full potential of existing investments, see the Precision Configuration page and couples this to architecting small pieces of clever software that harness the full potential of your investment, see the Software page.
If you are having problems with your systems, your project or your IT Department, call The Business Systems Specialist
Business System Failure is RIFE -- we offer insight into why this happens AND WHAT is required to prevent it.
Failure is at epidemic levels with massive damage done to client companies -- if you are NOT aware of the extent of the problem please visit the About Failure page for a catalog of major failures running to billions of Pounds and Dollars.
All evidence indicates that the established players do NOT know how to deliver stable, reliable high value solutions that WORK.
There HAS to be a better way!
This website provides information relating to that way with a large collection of white papers, presentations, standards documents, etc that you can use to start bringing the situation under control
We also offer high level advisory services with regard to the application of the principles advocated on this website
We offer an ENGINEERING APPROACH to addressing these issues
By Engineering I mean the formal, structured, highly disciplined, highly systematic, highly practical approach that consistently delivers results in ALL areas of human endeavor where formally trained and certified engineers are the ONLY practitioners permitted to operate -- think large buildings, factories, motor vehicles, aircraft -- highly complex systems that work at a level that we take it for granted that they WILL work and where failure is all but unthinkable and, when it happens, attracts immediate public attention and rigorous investigation directed at ensuring that such failures are prevented in the future -- in fact, everything that the management consulting industry that implements complex software systems is NOT
This approach is discussed further on the Engineering Approach page.
In 2003 I undertook an in-depth analysis of all the information and experience that I had gathered with regard to the factors giving rise to Business Information System failure including ERP and general IT and classified this information into a number of categories including "The Factors Causing Failure" and "The Critical Factors for Success" based on this I developed a two day Course "The Critical Factors for Information Technology Investment Success" which is still offered today.
Based on this I wrote the book of the same name, which is available in electronic form here for download:
James has a very detailed profile on LinkedIn should you require further information about him.
You can also connect with him on LinkedIn at http://www.linkedin.com/in/DrJamesARobertsonERPDoctor
James has an open networking profile -- click on "Connect" and use email address James@LinkedIn-at-JARA.com.
You can contact us on
LinkedIn at http://www.linkedin.com/in/drjamesarobertsonerpdoctor
Facebook at https://www.facebook.com/james.a.robertson.393
Mobile: +44 (0) 776-862-2875
Landline: +44 (0) 207-059-0007
Fax: +44 (0) 844 774 4580
There is a large body of white papers, articles and other content produced by Dr James Robertson available on this website
Please click here to visit the detailed listing of articles
About Dr James A Robertson PrEng -- The Business Systems Doctor -- and Other Topics
Catalogue of Major Business Information System Failures
About the Engineering Approach
James Robertson's Value Add
Attributes of a HIGH VALUE solution
Recognizing Business System Failure
The Critical Human Foundation
Old Software IS Viable
From South Africa
Competencies of Dr James A Robertson PrEng
About Professor Malcolm McDonald
Table of Contents
About my relationship with the Almighty Creator, Yah the Eternally Self-Existing
Comments relating to the Business Systems Industry and other topics
Testimonials and other positive material regarding James Robertson
List of Articles
Achieving High Value Business Information System outcomes
Executive Custody -- What is it and HOW do you get it?
The REAL Issues in Integrated Business Information System Success
Part 1: Introduction
Part 2 -- Mythology and Lack of Executive Custody
Part 3 – Strategic Alignment and Precision Configuration
Why your ERP is NOT delivering and HOW to FIX it
IT Project Management
CEO Anthony Lee Comments on his experience of the Pulse Measurement
No Charge Guarantee on the Pulse Measurement Service
Examples of Pulse Measurement Outcomes
Critical questions regarding the Pulse Measurement™
The Pulse Measurement Workflow
The Critical Factors for Business System (ERP+) Investment Success in the Pulse Measurement
Indicative Pulse Measurement Durations
What is a JAR&A Pulse Measurement?
Survival of the fittest – why it makes sense to measure the pulse of your business
Examples of Pulse Measurement Outcomes over 24 years
Sample Pulse Measurement Reports
Strategic Essence: The Missing Link in Business Information Systems
Strategic Essence: Overview
Strategic Essence: Part 1 -- Strategy Defined
Strategic Essence: Part 2 -- Differentiation
Strategic Essence: Part 3 -- The Essence IS Different
Strategic Essence: Part 4 -- The Essence should be the Point of Departure
Strategic Essence: Part 5 -- Discovering Strategic Essence
Strategy -- the Essence of the Business: What is it and how do you develop actionable strategic plans?
Simple Steps to Increase the Strategic Value of your ERP Investment
Free Strategic Snapshot Toolset and Manual
A strategy focused planning system beyond traditional budgeting
Tough IT and ERP Procurement and Contracting that Works
Robust Business Systems Procurement
Part 1 -- Introduction
Part 2 -- Bill of Services, Laboratory, Go-live Certificate, etc
Part 3 -- Executive Engagement, Bid Compliance, Adjudication and other matters
Guidance and Advisory Services
The Art of Project Leadership
Why Regular Communication with the CEO is Vital
The Business Simulation Laboratory
Precision Configuration and Strategic Business Information Architecture
Precision Configuration based on Strategic Engineered Precision Taxonomies
The JAR&A Cubic Business Model
Highly Structured Strategic Chart of Accounts -- a Vital Element of your Corporate Information Arsenal
The Product Catalogue -- an Essential Element of any Precision Configuration
Attributes -- answers to the questions you have NOT yet thought to ask
Case Studies of Notably Successful Projects with high value Precision Configuration
092 Doing things differently and better -- ASCO Case Study 2-- BPM Summit 2013
088 Strategic ERP Invesment -- ASCO Case Study -- Service Management Conference and Exhibition Africa
026 Information Architecture and Design of FIS for Rennies Group -- Financial Information Systems Conf
018 CRM Risk Control: Designing and Implementing an Integrated Risk Mgmt Sys -- Integrated Risk Mgmt Conf
011 V3 Consulting Eng: Benefits of MIS to Professional Practice -- SAICE 15th Ann Conf on Computers in Civil Eng
Strategically Enriching your Business Information Systems
Part 2 -- Principles of Data Engineering
Part 3 -- Steps in applying these recommendations
Simple Steps to increase the strategic information value yield from your Business Systems Investment
The Full JAR&A Taxonomy Manual
Part 1: Introduction, Problem Statement, Definitions and Examples
Part 2: Why Use JAR&A, Required Knowledge and Experience, Cubic Business Model and Chart of Accounts and Taxonomy Software
Part 3: How to do it, Case Studies and White Papers and other References
Example General Ledger Manual
Business Process -- Irrelevant, Distracting and Dangerous
The RIGHT Approach
Custom Strategic Software Design and Oversight of Construction
Standards for Custom Software Specification
What IS Software?
Critical Factors for I.T. Success
A Moral and Ethical Dilemma -- Systems that Fail
Case Studies examining Business Information System failures
The BBC Digital Media Initiative Debacle
The Bridgestone -- IBM Conflict
Speaking and Training
Showcase of Conference Presentations
Most Viewed Presentations
Briefings and Seminars
Why your ERP/BIS is NOT delivering and HOW to FIX it
ERP and IT Procurement that Delivers Results
The Critical Factors for IT and ERP Investment Success
Conferences and Public Presentations
Conferences 80 to 99 -- 2009 to Present
Conferences 60 to 79 -- 2005 to 2009
Conferences 40 to 59 -- 1996 to 2005
Conferences 20 to 39 -- 1994 to 1996
Conferences 01 to 19 -- 1989 to 1994
On-Line Seminars (Webinars)
Webinar on Preparing and Presenting Webinars
Contacting James A Robertson and Associates Limited