• Login

Articles by James A Robertson and Associates

KnE 002 The CIO side of the I.T. Divide
Created by James on 6/13/2013 4:26:13 PM


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 under-performing 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 CIO's and other I.T. executives and managers.  A complimentary series of articles address the subject from the perspective of the CEO and business executives and managers.

Dr Robertson can be contacted at James@JamesARobertson.com


Many organizations experience a breakdown in communications 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 CIO and other I.T. executives and managers on the "technology" side of the fence.  A companion article looks at the situation from the perspective of the CEO and those on the "business" 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 suggest that board members may soon be sued by shareholders for negligence in the event of such incidents.

I consult regularly to organizations who are expressing frustration with I.T. or wondering what direction to take.  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 technologists.  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 CIO and technology executives and managers generally.  These can be summarized as:

The business does not appreciate what we do and some executives are hostile and highly critical

As mentioned above it sometimes happens that there is an adversarial relationship between the business and I.T. functions, more frequently there is a communication breakdown that one or both sides recognize but do not know how to solve.

An essential component of this divide is the need to establish a common vocabulary and understanding between the two parties.

On the one hand this requires a better understanding of the fundamentals of information technology, as set out in the companion article to this for CEO's and, on the other hand, it requires a better understanding of business fundamentals as set out later in this article.

At the end of the day, business executives have a fiduciary responsibility to ensure that they have an informed and effective understanding of I.T., that is, they have a duty of care towards the owners of the business to ensure that I.T. is managed effectively.

I.T. executives and managers have a corresponding responsibility to ensure that they understand the business.

Poor communication is a double edged sword -- when there is a communication breakdown each party is quick to blame the other, however, from a simple statistical perspective when two parties cannot agree and each blames the other for the problem then the chances are they are each about 50% responsible.

Thus, it is vital for I.T. executives and managers to take steps to better understand the business and to equip themselves to communicate with business executives, managers and users in language those people understand.  AND it is vital for business executives and managers to equip themselves to communicate with I.T. personnel in language they understand.

If both sides are taking active and constructive measures to be understood the chances of a breakdown in communication are dramatically reduced.

In seeking to resolve this problem it is important for I.T. executives to understand that it is NOT their responsibility to "sell" business outcomes to the business, that is the responsibility of business executives.

Business asks questions we do not have the technology or resources to answer

A frequent source of frustration for I.T. executives is the unwillingness of the business to invest in the technology they think is required to meet the needs that business expresses.

Frequently business executives express requirements in terms of language that sounds like specific technology, often technology that is costly.  This frequently reflects what business executives have heard from peers in other organiz­ations or that they have read reports of.  An essential assumption that is made in such conversations is that the person making the request has a clear understanding of the language they are using.

Thus, for example, an executive states that they want to be able to get "all information at the touch of a button".  For the technologist these words immediately conjure up a picture of a state of the art data warehouse solution with leading edge business intelligence software coupled with person years of work analysing and developing dashboards.  The business executive responsible for the statement on the other hand is probably not envisaging anything like this.

If the I.T. executive takes such a statement as a mandate for action this can result in large amounts of time being spent formulating a project to deliver "touch of a button" functionality only to be told that the exercise is out of touch with the realities of the organization, or worse still, to be ignored and marginalized as being out of touch with the realities of running a cost conscious organization.

Another dimension of "touch of a button" is that the real need might well be better satisfied by a person with strong grounding in economics, business and statistics, equipped with a modest portfolio of software tools and working in close collaboration with the technologists, supplying answers to information requests within a few hours or even days.

Yet further, "touch of a button" may be hyperbole from an executive whose strength is marketing or some other field where the expression has no precise meaning and where the thought of spending large sums of money on a technical solution had not even entered their heads at the time they expressed the need.

Communication and listening skills and the ability to feed back "I am hearing that you are wanting us to make a very substantial investment in technology in order to deliver 'touch of a button' capability, is that correct?" may be all that is required to head off a major unwarranted investment in time and money.

Scope changes constantly -- business personnel keep changing their minds

An extension of the above point is that business personnel involved in I.T. projects appear to change their minds constantly.

Technologists are accustomed to computers doing exactly what they are told, accordingly they expect precision in what is communicated and, as in the "touch of a button" example assume that users understand exactly what they are expressing.

With most business people this is not the case -- not because there is something wrong with business people but because human beings are much more adaptable to imprecise language than computers are.

For this reason rigorous attention to detail and precise specification of requirement in plain language, before any major investment in technology is made, is vital.

An in depth grounding in business as well as in information technology is a necessity for translation between the business and the technologists that serve it.  This is easier said than done, ideally such personnel should be developed over years, working years in line management positions across a diversity of business disciplines and also working years in technology roles across a diversity of technical disciplines.

Few people have the privilege of such diverse experience and few people really want such diversity of experience unless it comes almost accidentally as a consequence of career changes that happen without intentional design.

Depending on the size of organization such a person might be employed full time or might serve as a professional advisor to both the business and technology function on a part time basis.

I.T. is moving so fast we cannot keep up -- we need the business to understand this

"The technology is moving so fast we cannot keep up" is a widely held view.

Yes, it IS so that there are very rapid developments in computer technology.  There are seemingly overwhelming wave after wave of new developments at least some of which do, indeed, require investment to remain current with.  Awareness and alertness on the part of technologists IS an essential part of their function.

However there are many other cases where it should be of no more than passing interest that there is new technology available.

In order to place this statement in context, consider most other areas of life.  Many of us drive to work on roads that are decades old, many live in houses that may be decades old, in fact in some circles it may be prestigious to live in a vintage house and even to drive a vintage car.

We obtain water and electricity from infrastructure much of which is older than we are and many organizations operate factories and warehouses that are decades old.  Yes, there IS newer technology but when the old technology is getting the job done there is no need to replace it.  There was a time when these technologies were developing so rapidly that it was difficult to keep up, but those times are past and most of those technologies are mature and we can keep up at our leisure as time really takes its toll.  I.T. has also reached this stage.

A further example -- the basic Boeing 747 aircraft design is recognizably over thirty years old but it is still a mainstream source of air transport.  By contrast, the Concorde, far and away more technologically sophisticated than the first 747 first flew four years before the 747 yet never "flew" economically and was finally mothballed in 2006, compelling evidence that advanced technology is NOT the primary requirement for successful business technology investment.

The point?

The vast majority of business users do not know how to use the technology that is currently available to them effectively.  Most require time and repeated training to develop real facility with what they currently have and, since it is human beings, NOT machines that deliver value, this points to a major constraint on new technology deployment.

In considering this point consider that I.T. is really about people as evidenced in the section that follows and err toward evolutionary change.

Essential business knowledge for I.T. effectiveness -- The essence of business that is missing from most I.T. conversations

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 business that many people take for granted and which are seldom codified in a formal fashion that everyone can understand and apply.  It is vital that these principles are acknowledged and known by both the business and I.T. function staff in order to understand how to apply I.T. to create value.

These principles are listed below:

1. Every organisation has a fundamental reason it exists, strategy is fundamental, the why, what, how, etc which results in the various "drivers" of the business.

It is necessary to understand and prioritise the core business drivers and to use this understanding to focus everything else thereby creating new opportunities for organiz­ational improvement.

2. Money is only a medium of exchange and measurement, it is a proxy or surrogate for value, a measure of performance of perceived value by people.  Money is easy to measure because it IS an instrument of measurement but strategy and competitiveness determine money yield and require other measurements.

3. Only humans create, destroy and determine value, things only have value IF a human being is willing to exchange (pay) for it.  Things, like computer systems, are inert and their value is determined by what people do with them or think about them.

4. Ways of being create or destroy value:

-- Leadership, empowerment, delegation, loyalty, morale

-- Accountability, responsibility, trust

-- Self discipline, commitment

-- Care, compassion, love, humanity, generosity

-- Esteem, ego, acceptance, recognition

-- Safety, security, health

-- Faith, belief, morals, values, religion

-- etc

This is the essence of what a person gives to an organisation and what a person seeks from an organisation -- how they "are".  I.T. implementations that destroy or weaken these can destroy long term corporate value and competitiveness.

Constantly changing systems when many in the organization have invested huge amounts of themselves in emotionally, through overtime and personal sacrifice in the existing system saps morale and motivation, reduces energy levels and reduces the productivity and efficiency of the organization.

5. Ways of doing create or destroy value:

-- Knowledge

-- Experience

-- Planning, analysis and design

-- Method, process, standards

-- Problem solving, creativity, initiative

-- Systematic disciplined, diligent, productive contribution

-- Communication, language, semantic skills

-- etc

This is the "technology" and capability that the person supplies to the business -- what they do.

Every time a piece of technology is changed a portion of knowledge and experience is discarded and has to be replaced.  The process of discarding and learning anew consumes energy and morale and adds no value until the person reaches a level that exceeds their previous level, which frequently never happens.  Then, the technology is blamed when it is, in fact, the frequently erroneous business decision to replace a functioning system rather than optimize it, which is at fault.

6. Service or supply to others creates exchangeable value -- organisations comprise human beings and exist to supply products or services to other human beings who consider that product or service to be valuable.  This forms the basis of the value transaction.

7. The rest -- technology and methodology, assets, etc.  These form a substantial component of most organisations and are the primary focus of many organisations but they cannot create or destroy any value EXCEPT through human beings.

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.

I.T. 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 the business and to engage in meaningful dialogue with the leaders of the business.

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 with regard to I.T.  This will be addressed from the perspective of how an I.T. executive can work to achieve executive custody from a management team that is less than custodial in its attitude.
print[MAKERATING] The comment feature is locked by administrator.
Sort by:

Random Selection of Articles by Dr James Robertson

TxM 100 Taxonomy Manual Part 1: Introduction, Problem Statement, Definitions and Examples

An overview of the history of the approach and statement of the problem in terms of major deficiencies in high quality management information together with definitions and examples
Std 022 Procurement: 13 Skeleton Agreement

This is a broad framework for a contract.  The exact contract will need to be drafted by your organization's legal advisors based on the legal jurisdiction in which your organization operates
Cnf 046 Insourcing -- Restructuring the IT Department for Better Business Focus and Increased Effectiveness --Armscor Case Study

Case study of a strategic planning project undertaken to develop a customer service focused IT Strategy for the Armaments Corporation of South Africa, the project used strategic marketing concepts to research business user, business requirements and concerns and convert these into a strategic action plan that was measurable and actionable thereby strengthening the position of the IT Department as a partner with the business

Subscribe to our StratNews newsletter

Click here to send us an email subscribing to our free newsletter -- all articles posted by James Robertson will be emailed to you

Dr James A Robertson PrEng The ERP Doctor

Business Systems NOT delivering?

Call the Business Systems Specialist

Dr. James Robinson

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

Click here to read more about the Engineering Approach

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.

Book -- The Critical Factors for Information Technology Investment Success

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:

Connect with James Robertson on LinkedIn

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.

Contact Us

You can contact us on

Email: James@James-A-Robertson-and-Associates.com

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

Articles by James A Robertson and Associates

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

Random Selection of Articles by Dr James Robertson

TxM 101 Taxonomy Manual Part 2: Why Use JAR&A, Required Knowledge and Experience, Cubic Business Model and Chart of Accounts and Taxonomy Software

A discussion of why James A Robertson and Associates are the leaders with regard to this field, a discussion of the knowledge and experience necessary to develop high quality precision configuration, factors causing business information system failure, discussion of the differences between the work of different practitioners, some important principles, giving executives REAL information, the power of an executive with a blank sheet of paper, common mistakes, risks, the Cubic Business Model, Group Consolidation Charts of Accounts and why it is necessary to use software to build and maintain code schemes
Sem 02 ERP and IT Procurement that Delivers Results

Much of what goes wrong with business information systems is that the procurement process is NOT robust enough to filter out lightweight and doubtful bidders and does NOT result in a tough contract that has the teeth to ensure that the successful bidder delivers on their sales promises
Sem 05 IBIS – The Strategic View of Business Information

A three hour Executive Briefing that outlines the most important aspects of what I advocate with regard to Integrated Business Information Systems, including ERP

ArticleTagCloud for Articles Published by James A Robertson and Associates

7 steps to FIX your ERP      80:20 regarding software replacement      aborted projects      abstract      abstractness      accounting      actionable      adjudication      Advantage Data Transformer      advisory      agreement      all possible classifications      all reports      all software elements required      all spreadsheets      all tasks required to execute the project      Alpha Omega      analysis of data      analytics      animation      answers to the questions we have NOT yet thought to ask      Armscor      arrogant ignorance      art of strategic business information system project leadership      ASCO      attendance register      attorney      audit      audit cost reduction      bankrupt organizations      basis for achieving alignment      basis of payment      basis of pricing      better way      bid adjudication      bid adjudication score sheet      bid compliance      bid compliance checklist      bill of materials      bill of services      BIS      BIS failure      BIS success      boots in the mud      BPM      BPM dangerous      BPM distracting      BPM ineffective      brainstorming      break it until it does NOT break anymore      break it until it will NOT break any more      budget      budgeting      business engagement      business executives      business improvement      business information system      business information system failure      business information system success      business information system taxonomies      business information systems      business information systems procurement      business information systems projects      business integration      business intelligence      business intelligence models      business knowledge and experience      business participation      business process      business process mapping      business requirements focused      business requirements specification      business simulation laboratory      business systems      business systems laboratory      business understanding      by the book      care      case studies      case study      CEO      CEO -- project leader communication      CEO as custodian      CEO definite views      certificates      challenges      challenging presentations      change facilitation      change for strategic reasons      chart of accounts      classification schemes      clever software      client changing scope      client compact      clinical codes      coaching      Cobol      COBOL CAN be retained      Cobol still viable      code schemes      coding conventions and standards      cognitive span      collapse      communication      competitive advantage      competitive advantage through precision configuration      competitiveness      compiler      complexity      compliance      compliance checklist      comprehensive testing      Compuware      conference speaking      conferences      confidentiality      configuration      consultant NOT delivering what required      contract      contract certificates      contract law      contracting      contractors      corporate planning      cost      cost-quality-time      CPT 4      CPT4      critical factors      critical factors for IT investment success      critical factors for success      critical factors for technology success      critical human foundation      critical issues      critical issues analysis      critical requirements      CRM Risk Control      cubic business model      custom development      custom software      customer focused      data      data content      data engineering      data entities      data warehouse      DB2      definitions      design against failure      design and development      design for success      determination of strategic essence      determining strategy      diagnostic code      diamonds in the dust      differentiated      differentiation      diffusion of innovations      discovery      dislike of failure      dispute resolution      do NOT change systems because of alleged software redundancy      do things competitors could NOT do      document pack      Dr James A Robertson      Dr James A Robertson PrEng      dramatic benefits      dramatically improved strategic management information      driver of success      Dunning-Kruger effect      ease of use      economic collapse      economics      effective communication      effectiveness      efficiencies      efficiency      efficient filing of emails      eliminate light bidders      email      engineer against failure      engineered data      engineering      engineering approach      engineering approach to strategy      engineering failure      engineering laboratory      engineering services      engineering solution design      engineering techniques      enhance differentiators      enhance the differentiators      enhancing the value of your present investment      ensuring project success      enterprise resource planning      ERP      ERP configuration      ERP failure      ERP procurement      ERP success      ERP taxonomies      ERP value      essence IS different      essence of business      essence of the business and how it thrives      ethics      examples      exceptionally bad code design      executive briefing      executive briefings      executive custody      executive decision support      executive engagement      executive forum      executive frustration      expose hidden agendas      facilitation      factors causing failure      factors causing IT investment failure      factors causing technology failure      factors to manage for success      failure      failure to address soft issues      fashion      file table of contents      Financial Information System      financial information systems      financial management      fixing your ERP      focus for projects      folder design      foundation for delivery      full training      functional entities      future      Gantt Chart      gap analysis      general ledger      George Paton      go-live      go-live certificate      governance      governance = care      governance failure      group consolidation      Group Consolidation Chart of Accounts      growth      gut feel factors      hand holding      harshest judge of governance      hate failure      head count reduction      health management software      hierarchies      high level requirements      high road      high value      high value implementations      high value solutions      high value systems implementation      highly effective chart of accounts      holistic view of solution      how do you achieve executive custody      how the organization differentiates itself      how to      how to do it      huge opportunity      human foundation      hype      Hyperion      IBIS      ICD 10      ICD10      importance of executive custody      improved management information      in-box rules      incremental enhancement of existing systems      ineffectiveness      inefficiency      information required from third party suppliers      information technology      information technology failure      Information Technology Strategy      information technology success      Informix      in-house courses      innovative software solutions      innovator      inside head of CEO      insightful      instructions      intangible      integrated business information system      integrated view of business      integrity      intelligent data      interactive training material      interview      invitation to bid      isolated CEO = explosion      IT      IT and strategy      IT Audit      IT failure      IT governance      IT lies      IT management      IT mythology      IT non-performance      IT people who lie      IT personnel socialization      IT procurement      IT projects that fail      IT strategy      IT systems      IT systems procurement      IT the harshest judge of governance      James Robertson      Jof Nelson      key performance indicators      Kirsten Speer      knowledge management      laboratory      lack of an engineering approach      lack of precision configuration      lack of strategic alignment      lawyer      leadership      legal agreement      legislation      lies      list of required software      listen carefully      litigation      logical entities      loss information      low road      loyalty      MacDonald      maintain code schemes      maintenance      maintenance management      Malcolm McDonald      management      management information      managing contractors      manual      marketing hype      master data      master data classifications      master test data      mature facilitation      mature facilitator      measurable      measures of alignment      mentoring      Microsoft Outlook      misrepresentation      missing link      mistique      morals      Munich      mystique      mythology      new future state      New South Africa      no drill down      non-disclosure      NOT classic project management      obsolete is a fashion statement      obsolete software      old software IS viable      once software works it always works      on-line seminars      opportunities      opportunity to turn the economy around      organizing Microsoft Outlook      orientation of IT staff      own business experience      passion to enable clients to thrive      people are part of the system      personality matrix      planning      platform for a tough contract      precisio      precision      precision configuration      precision configuration advisory      precision configuration leadership      precision data      precision taxonomies      Predictive Index      preparatory steps      prescribed table of contents      presentation technique      presentations      preventing failure      preventing falure      preventing project failure      pricing      principles      problem statement      procedure code      process      processor ignorant of language      procurement      procurement timeline      professional speaker      Professional Speakers Association of Southern Africa      profitability      programming languages are for the programmer      project facilitation      project leader      project leader -- CEO communication      project leadership      project management      project management IT project management      projects      prove it works      PSASA      psychology      psychometrics      public conferences      public presentations      public speaking      Pulse Measurement      quality      REAL issues in Business Information Systems      REAL value      recognizing failure      redaction      reduced audit costs      reduced head count      reference documents      Reg Barry      regulatory body      relationship Almighty      relationship orientated      remediation of existing systems      Rennies Group      reports      reports not reliable      request for proposal      requirements specification      results orientated      RFP      right things      rigorous process      rigorous strategic planning      risk management      Robert Priebatsch      robust business information systems procurement      robust business systems procurement      robust contracts      robust procurement      robust solutions      SAICE      SAP ABAP is similar to COBOL      scheduling procurement      scientific professional      score sheet      screen design      seminars      SEPT      service orientated      Service Orientated Architecture      simple techniques to enhance business information systems value      simulation      sloppy configuration      SOA      socialization      software      software assets      software design      software does NOT wear out      software is instructions for the bricklayer      software schedule      software specification      software specification standards      solution experience      solution knowledge      South Africa      South African Institution of Civil Engineering      speaking      Spirit Led      standards      strategic      strategic advisory      strategic alignment      strategic analysis      strategic analysis and design      strategic business improvement      strategic custom development      strategic definition      strategic discovery      strategic driver      strategic driving force      strategic engineered precision configuration      strategic engineered precision taxonomies      strategic essence      strategic financial information      strategic gap analysis      strategic governance      strategic information      strategic management      strategic management information      strategic plan      strategic planning      strategic project leader      strategic snapshots      strategic software      strategic solution architect advisory      strategic solution architect leadership      strategic solution architecture      strategically designed chart of accounts      strategy      strategy defined      strategy focused planning      Strategy Snapshot Toolset      StratGap      StratSnap      strengthen differentiators      structured analysis      structured chart of accounts      substantial management information      succeed by engineering against failure      success      successful deployment      survive      system knowledge and experience      table of contents      tailored presentations      take notes      taxonomies      taxonomy      taxonomy software      technology      technology failure      technology issues      technology management      tender document pack      tender pack      tender pack table of contents      test data      testing      The Critical Factors for Information Technology Investment Success      the Critical Factors for Success      the essence of the business      the essence of the business and how it thrives      the essence of the organization and how it thrives      the factors causing failure      the first hour      The REAL Issues in Business Information System success      things right      third party suppliers      third world countries      thrive      time      tipping point      tough certificates      tough contract management      tough contracts      tough procurement      tough terms      training      training material      treatment code      understanding of data      understanding the engineering approach      Uniface      unlocking value      use different languages for new components      V3 Consulting Engineers      validation data      value      versus process      video      webinar      webinars      weighted factors      what is executive custody      what is strategy      what is the essence of this organization and how does it thrive      what to do      where is IT going      why executive custody is required      why the organization exists and how it thrives      why your business information system is NOT delivering and HOW to FIX it      why your ERP is NOT delivering and how to fix it      workflow      writer     

Search Articles

Table of Contents


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

Reference Articles

List of Articles

Article Catalogue

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

Pulse Measurement

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

Procurement Documents

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 1 -- Introduction

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?

IT Effectiveness

Organizing Outlook

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

Other Seminars

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