One of those great back-and-forth Tweet-conversations: this time about the relationship between technology-architecture and enterprise-architecture, triggered by a post by Forrester consultant Gene Leganza on ‘15 Tech Trends EA Should Watch‘ (ZDNet summary here). The conversation meandered to a set …
Over on the long-running LinkedIn thread about enterprise-architecture as a bridge between strategy and execution, there was a bit of discussion about trusted advisors and a potential role for Pat Ferdinandi‘s parrot (Scarlet – the star of Pat’s enterprise-architecture how-to …
Over on LinkedIn, a great throwaway line from Nic Harvard: @Nic: “What EA is, is a need. Not even a want” There is indeed a huge need for enterprise-architecture (‘EA’). That fact becomes obvious as soon as we take anything …
One of the most essential tasks in enterprise-architecture is that of enabling conversations on architectural issues, with any groups of stakeholders, anywhere across the enterprise. Our toolsets play an important role in those conversations. The right tool used in the …
Next-generation toolsets for enterprise-architecture? Read more »
In part this is a follow-on from the previous post on the fundamental flaws underlying all forms of currency, but it also has many implications for businesses, enterprise-architectures, societal models, corporate social responsibility and much else besides. And don’t worry, …
Any competent observer of economics would acknowledge that the money-based model on which most current economics is based is in deep trouble right now: somewhere between seriously-dysfunctional and completely broken. Many of the purported key-metrics such as GDP and GNP …
Been having a fairly intense (but good 🙂 ) discussion on the LinkedIn Enterprise Architecture group, about standard economics and its impact on enterprise architecture. This is one of the many side-threads popping up off Kevin Smith’s now long-running discussion …
Why Economics 101 is bad for enterprise-architecture Read more »
Development of new ideas, processes and practices will always be a social process, and always somewhat messy. To enable that development to happen, we need social conditions that can support it – and screen out behaviours that prevent it. Those …
There’s a core theme that reaches right to the heart of every enterprise-architecture: what is the appropriate tradeoff between sameness versus uniqueness? The classic Taylorist solution has been to emphasise extreme sameness: to force everything – and everyone – to be …
Okay, so that’s all of the Mythquake book-project. The chapters, in variously-complete condition, are as follows: Mythquake MQ-1: Everyday upsets MQ-2: The centre of the universe MQ-3: I am what I do MQ-4: Whoever you voted for… MQ-5: Money makes …