Four principles for a sane society

How do we make sense of the big-picture in enterprise-architecture? The really big-picture? Yep, it’s that time of year again: the lead-up to the annual Integrated EA conference, where they allow me to go somewhat off-the-wall and present the current ‘big-idea’

Rumination on the concept of “best practice”

I heard some very interesting talks today from Len Fehskens and Jeff Scott at the Open Group conference.  One thing that I picked up in a meeting yesterday was the notion that TOGAF 9.1 is built on “best practices.”  Today, as Jeff spoke about the transformation of a technical architect into a business architect, and as Len spoke about the challenges of communicating complex ideas, the notion of a “best practice” kept bothering me, and I cross-pollinated my concerns with the concepts that they were sharing.

I agree that the intent of the people who shared their practices with the Open Group was to provide practices that can be taught and followed.  I even agree that the people on the TOGAF committees that accepted the content felt that the practices represented the best that the industry had to offer at the time.  But I wonder if any of the work done in framework committees of any stripe (not to pick on the Open Group) can be held to the standard of being a “best practice.”

Are the practices in the TOGAF framework truly “best��� practices?  Are these practices the best ones that the EA field has to offer? 

I guess I would have to follow the EA rabbit hole and ask “what criteria do we use to judge if a practice is the best one?”

After all, when Jeff Scott talks about business architecture using capability modeling, he believes that the practice of capability modeling is the best one to use for the results he is trying to achieve.  (I nearly always agree with Jeff, BTW.  We sometimes differ in language, but nearly never in approach).  That said, as much as Jeff and I agree, our agreement does not mean that the practice should be considered a “best” practice.  Who are we to say?  We are practitioners.  While that is good, it is not enough in my mind to qualify the practice as “best.”

To be a best practice, in my opinion, a method or approach has to meet a higher bar.  There has to be evidence that it is, in fact, better than just a “good practice.” 

I think a best practice should have:

  • Some measurement (evidence) that demonstrates that it is an effective practice, and that the measurement shows that it is at least as effective as other practices,
  • A clear understanding of the results of the practice and the context in which it is to be performed (think “Pattern Language” criteria),
  • Some analysis to show that it meets other criteria like broad applicability and simplicity, and
  • We should demonstrate the ability for that practice to be understood and performed by people who are currently in the role (e.g. can we teach it, and if we teach it, can others do it?).

 

I wonder if we went through most of our frameworks and highlighted the text that is able to meet a higher bar, like the one I describe, how much of the text would we cover?  2%?  10%? 

Is 10% coverage enough to say that a framework is based on best practices?

The over-certainties of certification

A strange kind of annual ritual that they did there, that subtle ‘work-to-rule’, every year that I worked at that place. Each autumn, up would come the new crop of graduates, each with their shiny new graduation-certificate and their own

drEAmtime

In the Australian Aboriginal culture,  Dreamtime “is a complex network of knowledge, faith, and practices”. Both the word and thus cited definition invite vivid associations. The latter, with what is commonly referred to as Enterprise Architecture (EA), the former – with its current state. Note: With this I’d like to depart from further analogies as […]

How To Understand The Difference Between Value-Proposition and a Product or Service

One of my startup heroes Steve Blank wrote in a blog post that “value proposition is the fancy name for your product or service” It is with some trepidation that […]

How Should we use Cloud?

How should we use Cloud? This is the key question at the start of 2013. The Open Group® conferences in recent years have thrown light on, “What is Cloud?” and, “Should we use Cloud?” It is time to move on. Continue reading

Our relationship to technology isn’t only utilitarian. It…

Our relationship to technology isn’t only utilitarian.

It is also emotional.

Technology empowers us, it amplifies us in the world, and gives us super powers.

Maybe productivity is a not just a function of the design, but also of our attachment to it.

And maybe that emotional connection best expresses itself aesthetically – in personalisation, decoration and symbols of individuality.

And just maybe the reverse applies and standardising, commoditising, and depersonalising technology degrades the productivity of those who have to use it.

Types of Cost

When planning and measuring business benefits there are three basic contributing elements: revenues, costs and intangibles. If you look for guidance on “types of cost” most sources decompose cost types […]

Successful Enterprise Architecture using the TOGAF® and ArchiMate® Standards

The discipline of Enterprise Architecture was developed in the 1980s with a strong focus on the information systems landscape of organizations. Since those days, the scope of the discipline has slowly widened to include more and more aspects of the enterprise as a whole. Architects, especially at the strategic level, attempt to answer the question “How should we organize ourselves in order to be successful?” Continue reading