You are currently browsing the Time For A Pause weblog archives for the day 20 March 2009.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Feb | Apr » | |||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | 31 | |||||
- Architecture of Happiness (5)
- Spirituality (6)
- Uncategorized (4)
- 16 March 2011: Brain Therapy, Exercise 4: The Universal Model of Belief
- 16 March 2011: Greetings Once More
- 16 March 2011: Brain Injury Awareness Day
- 10 November 2009: A Note on Your Divinity: The Natural Condition of Love
- 22 May 2009: A Note on Your Divinity: Divine Intelligence
- 22 April 2009: Earth Day Reminder to Claim Abundance
- 21 April 2009: Revelation on the Healing Powers of the Universe: Miracles
- 20 March 2009: Brain Therapy, Exercise 3: Defining Business Architecture
- 13 March 2009: Brain Injury Awareness
- 2 March 2009: A Note on Your Divinity
Archive for 20 March 2009
Brain Therapy, Exercise 3: Defining Business Architecture
20 March 2009 by blog.
Brain Therapy Exercises 1 and 2 introduce the concept of a Business Architecture paradigm in an attempt to explain some aspects of my life as a semi-retired consultant and to address the question, “What can we do to make the make the world a better place?” These exercises show by example that Business Architecture is about describing how things operate. Exercise 1 is a draft Operational Business Architecture artifact, the Architecture of Fear, that was reverse engineered from reality to explain how the world operates and why we see the outcomes we do today. Exercise 2 also provides an Operational Business Architecture product, the Architecture of Abundance, to show how the world might operate in a future-state with people working together to achieve outcomes that would make the world a better place.
Our next exercise for the brain is the development of a definition of “Business Architecture.” This will allow me to tackle some structured thinking that will, with hope, require intense concentration, thereby inducing the physiological phenomenon of the creation of neuropathic synapses that increase the brain plasticity that is integral to the miraculous abilities of the human being. This should greatly advance my recovery and improve my odds in the long run. So let us dive right in.
Business Architecture may be formal, as defined by various methodologies and techniques, but given the current state of my brain (e.g., recovering) and presumption of fiat from nearly two decades working in strategy, operations, and technology, we shall structure our initial definition informally:
Business Architecture is anything that helps people from different parts of the business (especially the non-technical and technical people) to develop a common understanding of exactly what needs to be done.
The development of Business Architecture as a management tool stems from the thorny issues businesses face trying to figure out technology. In the business world, there always seems to be some issue of getting technology to do the things that people want it to do. Owners, managers, workers, customers, nearly anyone who has ever done or dealt with business can probably relate to the challenges people face integrating and using technology. In larger organizations, this is often characterized as getting the “business people” to understand the “technical people” and vice versa.
Business Architecture is a tool of management communication intended to convey, in non-technical terms, concepts of operations that get people on the same page, regardless of which part of the business they primarily deal with. It is about helping people articulate and understand strategy, define the appropriate organization and resources, and work together towards desired outcomes.
In practice, Business Architecture becomes the basis for Technical Architecture that further decomposes the business into increasingly detailed specifications for technological systems. The general, widely used term for a comprehensive and formalized approach to Business and Technical Architecture is Enterprise Architecture (EA). EA is a practice of developing business and technical architecture tools that support an organization’s strategy by aligning non-technical, functional operations with the technical infrastructure. This is done to crystallize the strategy and increase the efficiency, returns, and capabilities from investments in organizational systems and technology. Organizations and people – businesses – that understand how to do this typically significantly increase their competitiveness through innovation and productivity improvements.
The usage of Business Architecture, however, is necessarily not limited to solely addressing issues of aligning business and technical resources. While technology is critical to every business, at the end of the day a business is only as good as its people. Business architecture, therefore, must address all business processes, people, and resources, specifically as they are organized and deployed. Business Architecture is an idea that by codifying and clearly articulating strategy, using common terminology and the visual presentation of information, people from all domains in the business will understand what needs to be done. This is called alignment of business resources and is critical in efficient, innovative, and successful organizations.
Business Architecture draws on three disciplines in the development of its methodologies and practices:
1) Management Science, which provides ideas of process analysis, analytics, strategy, management, and communication. The “business” in Business Architecture is about getting things done. Business Architecture concerns itself primarily with Strategy and Planning (i.e., defining the mission, vision, goals, objectives, and tasks) and Organizational Systems (i.e., defining and managing the structures, resources, and operating models for the organization).
2) Civil Architecture, which provides ideas on design, the visual presentation of information, and communicating across technical and non-technical domains. Business Architecture is less concerned than civil architecture on a formalized methodology of design. Rather, from civil architecture, the idea that a single “blueprint” can be used to communicate across domains is the central adaptation. Business Architecture produces unified blueprints that everyone follows in building and operating the business.
3) Computer Science, which provides ideas of structured systems analysis, abstraction, and computer architecture and engineering. Business Architecture codifies system design and uses abstraction to communicate and produce increasingly detailed specifications as appropriate to the needs of the business stakeholders. The concepts are valid whether applied across an organization (i.e., Enterprise Architecture) or down to individuals and processes (e.g., work plans and packages).
The practice of Business Architecture, even as it draws on ideas from science, is really an art. The art is the production of unified communications that articulate what the business is about and move people to action. There are numerous ways to do this, several common frameworks and methodologies that specify useful artifacts, and increasing use of the concepts. Business Architecture, however, is less concerned with how the architecture is produced, for example, compared to Civil Architecture, than it is concerned with producing visionary artifacts, using whatever process and tools are relevant and most appropriate to the business. The objective is to present a conceptual model that enables people to think about the challenges, understand the critical questions, and take actions towards desired outcomes.
There is a great body of work in Enterprise Architecture. Various methodologies and techniques have been developed and the formalization of EA continues. My take is that while a formalized approach may be useful, the most important idea is the concept – that by clearly articulating the strategy and helping people develop a common understanding of the mission, vision, goals, and objectives of an organization many of the problems that often seem intractable can be solved.
My journey through a couple of decades in strategy, operations, technology, has led me to discover many tools and techniques, out of the academic and commercial realms, for accomplishing non-technical and technical tasks in organizations. The love in Business Architecture stems from its positioning at the nexus of strategy, operations, and technology – you have to do it all to understand and get it right. Done right, Business Architecture is a powerful, invaluable tool that can help organizations – and people – realize new capabilities and increase competitiveness.
Business architecture cuts across organizational boundaries to take an enterprise view so that people understand not only their roles and functions but also what individual actions are required to accomplish strategic objectives. The Brain Exercises will continue to explore using this technique to ask people, “What can we do to make the world a better place?” By cutting across human organizational boundaries (i.e., we address people in every family), Business Architecture allows us to take a global view (i.e., with the Earth as our enterprise) so that we may not only understand our roles in creating the outcomes we see in the world today, but also what individual and organizational actions are required to overcome fear so that we may accomplish the strategic objective of creating a world of abundance.
We shall pause here and seek discussion on our emerging definition of Business Architecture. I look forward to your input. In the meantime, the physiological developments occurring simultaneously to this writing are signaling that the author’s brain is ready for another element of healing – sleep.
Cheers,
blog

Posted in Architecture of Happiness | 1 Comment »