2 days ago

Building effectiveness in a small business

One of the great things about doing my ‘Tetradian on Architectures‘ mini-video series is that I get to tackle real-world questions about everyday enterprise-architecture, sent in by people all around the world. In this case, for the current episode in

3 months, 7 days ago

Sensemaking and the flocking of Boyds

It began with an octopus; wandered into an accidental remark about “a flocking of Boyds”; and then drifted off somewhat sideways from there. But seems that this crabwise shuffle may be leading somewhere useful – for my current explorations of

3 months, 21 days ago

Sensemaking: Down in the dungeons

Following on from the previous post ‘Sensemaking: Into the void‘, what’s a good everyday analogy or example on how to develop our skills in sensemaking and strategy? In particular, how to understand, apply and use the ‘sense, make-sense, decide, act‘

9 months, 12 days ago

Review-interview on ‘Changes’

It’s been good to see another review of my book ‘Changes – a business novel‘: (There’s a sizeable free-sample of the book on Leanpub: go to the home-page for the book, and then click on the ‘Read free sample’ button

10 months, 26 days ago

On innovation, foundations, scaffolding and Portakabins

Given that I’m reframing my work here as ‘maker of tools for change’, it seems worthwhile to republish from my now long-defunct Sidewise blog this 2010 post on some on the realities of change that must be acknowledged and addressed if

1 year, 2 months ago

This is not a project

My apologies to René Magritte, as I appropriate his point, if not his iconic painting. After I posted “Storming on Design”, it sparked a discussion with theslowdiyer around context and change. In that discussion, theslowdiyer commented: ‘you don’t adhere to a plan for any longer than it makes sense to.’ Heh, agree. I wonder if […]

1 year, 5 months ago

I Don’t Call Myself An Enterprise Architect

… 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.
1 year, 6 months ago

Managing Fast and Slow

People have a complicated relationship with the concept of cause and effect. In spite of the old saying about the insanity of doing the same old thing looking for a different result, we hope against hope that this time it will work. Sometimes we inject unnecessary complexity into what should be very simple tasks, other […]