Architecture and OODA Loops – Fast is not Enough

Sense-making and decision-making are critical skills for the practice of software architecture. Creating effective solutions (i.e. the collection of design decisions that make up the product) is dependent on understanding the architecture of the problem. In other words, the quality of our decisions depends on the quality of our understanding of the context those decisions […]

The Seductive Myth of Greenfield Development

Greger Wikstrand‘s tweet from earlier this week packed a wealth of inspiration into one image: The second statement particularly resonated with me: “The present is built on the past.” How often do we, or those around us, long for a chance to do things “from scratch”. The idea being, without the constraints of “legacy” code, […]

All models may be wrong, but it’s not a contest to see how wrong you can be

The one thing you can be sure of is that nothing is dependent on only one thing. Michael Feathers‘ tweet last week brought this to mind: Too often we construct simplistic mental models that fail to account for outcomes that are possible, but inconvenient for us in some way. As Aneel noted while discussing OODA […]

We Deliver Decisions (Who Needs Architects?)

What do medicine, situational awareness, economics, confirmation bias, and value all have to do with all have to do with the architectural design of software systems? Quite a lot, actually. To connect the dots, we need to start from the point of view that the architecture is essentially a set of design decisions intended to […]

Hearts and Stars and Prison Riots (User Experience Matters)

So Twitter decided to make a change, and people have been reacting (and reacting to the reaction): As Jeff Sussna noted, there’s a reason for the reaction: In my old, pre-IT life, I’ve seen that same cavalier attitude toward change cause a real-life riot (for the record, it was a jail riot rather than a […]

Full Stack Enterprises (Who Needs Architects?)

In my last post, “Locking Down the Prisoners: Control, Conflict and Compliance for Organizations”, I returned to a topic that I’ve been touching on periodically over the last year, organizations as systems, which overlaps significantly with the topic of enterprise architecture (not to be confused with enterprise IT architecture of which EA is a superset). […]