Service, function and capability (an addendum)

How can we clarify the confusion over service, capability and function in enterprise-architecture models? Andrew Marosy made a comment to my previous post on this that really needs to be brought out here in full: You can also visualise a

Service, function and capability (again)

How can we distinguish between service, capability and function in enterprise-architecture models? This is one of those perennial questions that keeps returning time and time again, and it’s one of the key confusions that Enterprise Canvas aims to resolve. But

The Cloud is in the cloud

This one’s another follow-up from the model-development session with Stuart Boardman last Friday, and relates to a different way to understand the often over-hyped Cloud. [I hasten to add that most of what follows is just a minor elaboration on an

How not to use IT in services

Several people picked up on this one after Gerold Kathan sent out a note about it, but perhaps David Sprott said it the best: davidsprott: RT @gkathan: John Seddon – a master class in how NOT to use IT in services. Optimize value, not cost. Brilliant. http://tinyurl.com/dygdcpg It’s a 40-minute video (split into three parts) […]

Selecting Public Cloud Services – Focus on What’s Different

I had the opportunity to participate in a panel discussion last week with a few of my PwC colleagues, Cara Beston and Greg Dupier, during which we talked about both private clouds and also what it takes for businesses to offer public cloud services.  What made this discussion unique for me was that the audience was largely made up of U.S. government contractors, so they were particularly focused on the federal direction and mandates about […]

If you liked this, you might also like:

  1. Public Cloud Adoption – Where Are You?
  2. Why Aren’t CIOs Using Cloud Storage?
  3. You Aren’t Using a Cloud Platform

A Capabilities-based Architecture

As technology architecture professionals, we can only be successful and valuable to those who pay us if we frame our work in terms of capabilities at the outset. If we start with details, we’ll ultimately fail.

IT Made Simple

What would it take for your business to view IT as a valuable, essential partner instead of an annoying cost-center that they’re forced to deal with? Wouldn’t that be better for you and better for them?