Aggregated enterprise architecture wisdom
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…
Where to start with this one? Where the heck do I start? How do I get it to stay still long enough that I can start? Threads. Words. Sort-of. Except that as soon as I start to write, it’s gone anyway.…
How can we simplify the SCORE framework – Strengths, Challenges, Options, Responses, Effectiveness – to make it more accessible as a practical, more strategy-oriented replacement for SWOT? As summarised in the post ‘More on simplifying SCORE‘, the way to use SCORE is sort-of…
A couple evenings ago the BCS (British Computer Society) held a open question-and-answer session with John Zachman at the EAC-BPM conference in London. How much has the Zachman Framework for enterprise-architecture changed over the past decades – and particularly over the…
How do we use SCORE, as a practical, more strategy-oriented replacement for SWOT? These are some additional notes as a follow-up and extension to the previous post ‘Simplifying SCORE‘. They perhaps apply in particular to the new simplified layout for…
What tool or graphic would you use to guide a quick exploration of strategy or tactics? Many people would use SWOT, of course – the classic 2×2 grid of Strengths, Weaknesses, Opportunities, Threats: The catch is that it’s very limited…
There are a fair few business-model patterns out there that look really great, really profitable – and yet conceal fundamental flaws that can kill the business outright. (Or, in some cases, it’s not just the business that gets killed… –…
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.…