Abstract

Business IT Complexity prevention is a real must for keeping your company agile and adaptive. So stop wasting time and resources on IT complexity. Effective business IT complexity prevention prevents hidden cost, improves quality and enforces an in-depth understanding of problems and customer needs. This zero complexity (0CX) standard defines architecture and design principles to prevent complexity for new products.

Tip

Avoid IT complexity: A high level of complexity often means serious risks and cost for systems. Especially for systems where humans, processes, software and new technology play a major role. So use our zero design complexity principles to prevent IT complexity from the start.

Status of This Memo

This document specifies principles to prevent complexity when designing large scale business IT systems. Discussion and suggestions for improvements of this memo are welcome and encouraged. Just create an issue or pull request at nocomplexity/0complexity.

Distribution of this memo in any form is encouraged, so please share the link !

Language

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 <http://tools.ietf.org/html/rfc2119>_.