Aggregated enterprise architecture wisdom
I love beer commercials. A couple of years ago, Miller Light created an ad campaign (later regarded as one of the ten best campaigns ever) in which consumers of the frothy brew disagreed over their motivations for choosing Miller Light. “Tastes Great”,…
A fascinating 10 minute video from Stanford’s Robert Sutton. It discusses the mind-set and strategies of companies that are most adept at building and spreading high standards. And here is the link to “Robert Sutton’s Guide to Excellence”: http://strat.bz/wqRmb2P.
The first enterprise to have an effective technology would benefit from a competitive advantage.
The enterprises that choose and properly integrate the increasing plethora of technologies would do best.
Data can be very revealing, inspiring and surprizing. Or it can be ignored, overlooked, misused, and abused. Personally I’d prefer if data was used at the end of the spectrum where it can do some good, change perceptions for the better, and make a positive difference in our world. Which is why I was fascinated…
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…
Just a short mention here: I’ve just published a new column on the site of the Enterprise Architecture Professional Journal titled Reverse Cloud. It deals with the latency effect in networks (which is thoroughly explained in an aside) and describes a scenario … Continue reading →
Just a short mention here: I’ve just published a new column on the site of the Enterprise Architecture Professional Journal titled Reverse Cloud. It deals with the latency effect in networks (which is thoroughly explained in an aside) and describes a … Continue reading →
This model is part of my toolbox for working with capability architectures. The Capability Inventory I know that there is certain ways of naming a capability and also that there are other principles that people and I promote that you should adhere to when designing your capability map. Here I’ve taken some liberties in regards to those […]
This model is part of my toolbox for working with capability architectures. The Capability Inventory I know that there is certain ways of naming a capability and also that there are other principles that people and I promote that you should adhere to when designing your capability map. Here I’ve taken some liberties in regards to those […]
How are you?
Busy? oh thats a shame.
That thing you are working on thats really really important? i’m sorry, its probably not.
That deadline that is causing you stress, its an arbitrary deadline and it isn’t important.
That last big project you worked on, think about all the things you did as part of it, How many of the things you worked so hard on was actually useful? hardly any.
Look back at the last year, count the number of things you did that were really important, be honest, did you have to use the fingers on your second hand?
Laziness isn’t a negative thing, laziness in its purest form is honesty, honesty with yourself about what is really important and what doesn’t matter.
“There is nothing quite so useless as doing with great efficiency something that should not be done at all” – Drucker (Management guru and aphorism rich Philospher King of Laziness)
Busy is self-deception, protecting your ego and your self-importance.
Unless your job involves something akin to hacking coal out of a mine you don’t need to be busy, you need to be creative and for that you need focus and space and for that you need Lazy.
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… –…
Often when talking with fellow data architects I experience that many data architects have lost the basic modelling skills and are usually just deploying the same pattern over and over. That may be excusable for a developer, but not for an architect. So usually the first thing I see is that most data architects will … Continue reading On stupidity – Common Data Architecture →