Aggregated enterprise architecture wisdom
Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…
Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…
Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – they either don’t work at all, or they serve someone else’s needs. Or desires. Or something of that kind, anyway. And therein lie…
Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t. And therein lie a huge range of problems for enterprise-architects and many, many others… This is the third part of what should be a six-part series…
Services serve the needs of someone. Disservices purport to serve the needs of someone, but don’t – sometimes through incompetence or failure in operation, sometimes through incompetence in service-design, and sometimes even by intent. And therein lie a huge range of problems…
Services serve: they serve the needs of someone, or, in a broader ecosystem, the needs of something. Services serve – that’s why they’re called ‘services’. Yet what do we call something that purports to serve some need, but doesn’t? I’d suggest…
I’ve long been a fan of Alex Osterwalder’s work. There can be no doubt that he’s had a huge impact on business-architecture – particularly for startups – with tools such as his Business Model Canvas [BMCanvas] and, more recently, Value…
What’s a quick way to keep reminding ourselves about effectiveness in the enterprise, and that tagline of “things work better when they work together, on-purpose”? My suggestion for this is the somewhat-contrived acronym LEARN: eLegant – clarity, simplicity, consistency, ‘feel’, self-adapting…
What’s a simple tagline that we can use to help guide conversations about enhancing of enterprise-effectiveness? My own preference is this: things work better when they work together, on purpose. Okay, I’ll admit that that doesn’t quite give us the full…
Keep it simple. Simple, yet not simplistic. Acknowledge the complexity, yet don’t ever push that complexity in people’s faces. (Not until they’re ready for it and choose to face it, anyway.) Help people find their own effectiveness about creating effectiveness.…
Enterprise-architecture is dead. As a term, anyway. Although it had been dying for quite a while, we do have some certainty now about when it died; we know how it died, and even why it died. And whilst some of us…
Meta-this-that-and-the-other – metamodels, metaframeworks, metamethodology, metatheory, even metatools? What is all this stuff about ‘meta-‘? And what is ‘meta-’, anyway? One answer is that it’s about a kind of recursion that we often need in our work, in which something is applied to…