Enterprise Architecture is about understanding problems and defining solutions – from the perspective of the enterprise. There are two corollaries: An enterprise architect defines solutions, they do not build, implement or operate solutions, although they may be involved in these processes An enterprise architect looks at problems and their solutions in the context of the whole enterprise, which is far Continue reading What is Enterprise Architecture?
Words like “requirement”, “problem” and “solution” have been overloaded and hence are misused and abused. For example, differentiating between Requirements and High-level Requirements is meaningless without context. Without context, it might be assumed that they are different places on a linear scale. On the other hand if High-level Requirements refer to the business problem and Requirements refers to the solution,then Continue reading Overloaded words that can lead to hubris
A comment I made to Linked In group Systems Thinking World with reference to Systems Thinking and Cross Impact Analysis Does anyone have any experience using Cross Impact Analysis with ST or even SD for creating scenarios and doing futures studies? Do they get along or are there other methods that fit better with the ST perspective? My comment: If Continue reading Systems Thinking. Creating scenarios and doing futures studies