#eavoices

April 2017 – Investigative Architecture Training

by

We are pleased to announce our next Investigative Architecture Training which will be held in Lincoln, RI on April 13 & 14, 2017. It is an intensive, interactive two day training for architects, developers and other IT roles who want to take their architectural and diagramming skills to the next level. Practicing architects already understand […]

Organizations as Systems and Innovation

by

Over the last year or so, the concept of looking at organizations as systems has been a major theme for me. Enterprises, organizations and their ecosystems (context) are social systems composed of a fractal set of social and software systems. As such, enterprises have an architecture. Another long-term theme for this site has been my […]

Patterns

by

In addition to story narratvies, I’m planning to use ‘pattern’ format for describing the Change Design tools: Here’s an example that describes the Business Service Specification tool (BSS). I would also then go on to describe how it’s been used in two …

I Don’t Call Myself An Enterprise Architect

by
… anymore.


A few people have asked why I call myself a Change Designer rather than an Enterprise Architect. The reason is simple: the EA label misrepresents what I do.


The popular understanding of  Enterprise Architect is:
  • attached to an I.T. view of the world – I’m not only focused on I.T.
  • often synonymous with large arcane frameworks like TOGAF – I dislike them
  • regarded as slow, top-down, big modelling up front etc – I prefer Dan Ward’s F.I.R.E. approach.


I use the title Change Designer because:
  • They are two simple words, that together, explain what I do – I Design Change (transformational or otherwise).
  • They don’t t limit me to only focus on I.T. – but, at the same time, they don’t exclude I.T.
  • Much of my thinking and toolset come from the world of “Design Thinking” (and Systems Thinking, Complexity Science etc.).


I guess I’m lucky in the sense I’m unemployable now, partly due to age but mostly due to temperament! 🙂 I’m more choosy about the things I work on where and when. All this means I don’t need to splash “Enterprise Architecture” and TOGAF all over my CV to find the next gig – and if I did, I’d probably not meet the client’s expectations!

Follow #foundindesign on Twitter to see what I’m up to these days.

The Open Trusted Technology Provider™ Standard (O-TTPS) – Approved as ISO/IEC 20243:2015 and the O-TTPS Certification Program

by

By The Open Group The increase of cybersecurity threats, along with the global nature of Information and Communication Technology (ICT), results in a threat landscape ripe for the introduction of tainted (e.g., malware-enabled or malware-capable) and counterfeit components into ICT … Continue reading →

The Four Focus Areas

by

The four focus areas aren’t steps in a linear sense – they’re more like wash-cycles. Based on the dirtiness of the laundry is, it might be necessary to go around each cycle a few times. So depending on how ‘dirty’ your problem is; how complex, how big,…

Avoid obfuscation

by

Obfuscation in architecture is usually called different. the meaning of obfuscation is to darken something and as such architects call it black box design. The benefit of obfuscation is therefore that it solves hiding complexities or in other areas hide information. An example was to hide the pay record of a spy in large departments … Continue reading Avoid obfuscation →