At ‘EA and Systems-Thinking’ conference

For enterprise-architecture and systems-thinking alike, how can we reach towards the opposite of their too-common anti-pattern – all those endless ‘academic’ arguments on LinkedIn? More to the point, how can we bring it out of the abstract, and down into

NOTES – actors, agents and extras in the enterprise

If the enterprise is a story, who are the actors in that story? What are their drivers and needs? How do we model and manage the relationships between those actors in the story? (This is part of an overview and

Some notes on NOTES

What is a narrative-oriented approach to enterprise-transformation? Why use it, and where, and how? And where did all this NOTES stuff come from, anyway? NOTES is, I admit, a somewhat-forced acronym for a way to look at business-change: Narrative-Oriented Transformation of Enterprise

NOTES – putting it into practice

How do we use an narrative approach in enterprise-transformation? What’s different about it, in real-world practice? How does it work? In the first post in this series, I introduced the core ideas for NOTES – Narrative-Oriented Transformation of Enterprise (and)

NOTES – an alternative approach for EA

If – as we’re often told – business-design is about the relationships between people, process and technology, what is it that links all of themes together? Answer: a story. Okay, yes, this is a theme I’ve explored a lot here on

Scalability and uniqueness

What actually do we mean by ‘scalability’ in enterprise-architecture? What can and can’t we scale within the architecture, or the process of architecture itself? These questions came up for me in thinking about a comment by Dave Duggal to the previous