|
|
|
|
|
|
| About Designing for Success by Engineering Against Failure |
|
|
| Designing for Success by Engineering Against Failure is a JAR&A maxim coined to explain succinctly one of the critical differences in the approach of JAR&A to I.T. and Strategy projects. |
|
|
| |
|
|
| Design for Success Alone Guarantees Failure |
|
|
| The conventional approach to I.T. and Strategy projects is to design for success -- this involves statements of vision, mission, etc and requirements specifications of the required end state. Thereafter plans are drawn up to achieve the desired end state. Failure is a dirty word and not something to be discussed in polite company, it is something that cannot happen until it happens which it does 70% to 90% of the time, depending on one's definition of failure. |
|
|
| |
|
|
Eliminate ALL Possible Causes of Failure
-- by Design |
|
|
| The Engineering approach to design, which is instilled in undergraduate engineers from the earliest days of their formal University training is to identify ALL possible causes of failure and then to systematically design all these possible causes of failure out of the system. |
|
|
| |
|
|
| This is accomplished typically using two basic approaches, the one is a "Factor of Safety" which is a factor which numerically reduces the capacity of all components by a specified factor, for example 1.5. |
|
|
| |
|
|
| The other approach is "Probability of Failure" which asserts that there is a certain economic point at which it is not viable to eliminate failure entirely and that some small probability of failure can be tolerated depending on the threat to human life. Probabilities of failure of up to 5% may be tolerated in certain open cast mining situations with probabilities of fractions of one percent being regarded as acceptable in the aviation and similar industries. |
|
|
| |
|
|
| Whether one uses a Factor of Safety or Probability of Failure, the possibility of failure and the consequences of failure are constantly "in the face" of the design team from inception to completion. |
|
|
| |
|
|
| Success is a Given IF Failure is Eliminated |
|
|
| Success is taken as a given, PROVIDED failure is eliminated. |
|
|
| |
|
|
| This results in an approach to problem solving and design which many I.T. "experts" and "strategists" find "negative" and unacceptable. |
|
|
| |
|
|
| However, it is the ONLY way to achieve a successful outcome. |
|
|
| |
|
|
| Meticulous Review |
|
|
| Unless every aspect of the design and project is meticulously reviewed against a comprehensive catalogue of factors giving rise to failure and then designed to eliminate that factor from the design, failure is inevitable. |
|
|
| |
|
|
| Success Results from Designing Failure Out |
|
|
| In other words, success is achieved by designing failure out of the concept, the analysis, the design, the construction, the implementation and the operation of the solution. Whether an I.T. solution or a strategy solution the principle is the same and many of the factors that give rise to failure are similar or the same. |
|
|
| |
|
|
| Sets JAR&A Apart as a Service Provider |
|
|
| This approach, together with the lengthy catalogue of known factors giving rise to failure sets JAR&A apart as a service provider and source of information. |
|
|
| |
|
|
| JAR&A as Partners of Choice for Competitive Advantage |
|
|
| For this reason, whether purchasing one of our eBooks or purchasing a comprehensive, executive level project engagement, JAR&A should be your partners of choice. |
|
|
| |
|
|
| Our approach will ensure that your organization is able to create sustainable, profitable competitive advantage with Information Technology and / or Strategic Planning. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Top of Page |
|
| Use "Back" button on browser to return to the previous page |
|
|
