« January 2005 | Main | March 2005 »
February 28, 2005
Archestra Framework: An Overview of its Development
Archestra treats strategy as a managed product.
In this perspective, the strategy management process is similar to the product management process. The genesis of the "product" called strategy is a framework
Processes are developed from models, and models are developed from frameworks.
The Archestra Framework is a structured, evolutionary knowledgebase of terms and concepts related to the underpinnings and lifecycle of a strategy. The Framework provides diagnostic approaches to examining strategy and identifying how strategy addresses renovation and innovation initiatives by managing:
risk and benefit;
their relationships and dependencies; and
the roles and dynamics for acting on them.
Users of the Framework can investigate the content to:
- add and improve definitions,
- document new relationships and patterns, and
- supply diagnostic or engineering tools to apply the content to strategic planning and strategic problem resolution.
Successful applications, related supporting materials from all users, and ongoing investigative references may be donated to the Archestra Foundation Class Library, where also will be stored standardized models and process descriptions for both creating and executing strategy.
Posted by Malcolm Ryder at 8:37 AM | Comments (0) | TrackBack
February 26, 2005
About Architecture
Architecture creates relationships between a space and the intent of that space's usage.
To structure the space for its purpose, architecture supplies reference points, supports, and guides that manage approaches to the space and, likewise, manage interactions and occupancy within the space.
By actively programming the relationship of a location and a purpose, architecture expresses strategy through supportive facilities. These facilities may be conceptual or material, but in both cases they anticipate and amplify the compatibility of certain actions and choices with a probable realization of a goal.
"Probability" in architecture is a matter of special importance, as an architecture always strives to solve the problem of reconciling stability with uncertainty, or intended effects with unintended effects.
Posted by Malcolm Ryder at 1:15 PM | Comments (0) | TrackBack
February 25, 2005
About Strategy
Strategy is the art and science of continuously determining, in pursuit of a goal, where you need to be and why you need to be there.
There are two kinds of strategists: Leaders and Analysts. Leaders try to prove what they believe, and Analysts try to believe what they can prove.
However, these two approaches are far from contradictory. Instead, they are dynamically complementary, and it is typical, not unusual, that a strategist will capitalize on the products of one approach by using the other approach. This "dialog" has no speed limits or prerequisite schedules, and a strategist collaborates with himself or herself as often as with others.
Posted by Malcolm Ryder at 1:07 PM | Comments (0) | TrackBack
February 24, 2005
About Alignment
Usually, our concerns about "good work" are well covered by just three big words in our vocabulary:
- quality,
- performance, and
- value.
Naturally, no one of these three things just arrives on its own. Additionally, it's hard to think of cases where having any two of them is likely without the third.
In the management effort, we constantly see and plan for the relationships that link these three to each other. But of the three things, the issue that is possibly most sensitive to management influence is "performance" -- that is, the execution to desired goals.
I.
Goals are usually thought of as end-points; to set that endpoint the goal provides definitions of certain conditions. We say that execution has had the required impact when execution conforms conditions to meet those definitions.
Among the conditions to be conformed, it's normal that some are already acting separately or interacting for some special purpose while others are at least indifferent to what we now want. For that reason, execution must act on the nature and relationships of those conditions -- and coordinate them so that they don't compete with the intended progress towards the goal. This coordination or alignment helps to overcome inertia, momentum in the wrong direction, and/or volativity.
In other words, alignment is a state that functions as a precondition for performance.
II.
Execution includes both the decisions and the hands-on actions that we call production. Production itself commonly selects inputs from external sources and channels, and "processes" them internally through a designated organization (such as a workgroup or project) under supervision.
This throughput is variable, and to keep it within acceptable tolerances the coordination of external and internal conditions must have high priority.
For example, external conditions include the quality and volume of inputs (supply); and internal conditions include the functionaility and immediacy of processing (readiness). Predictability and consistency is vital in both cases.
Therefore, alignment is needed both in external and internal environments.
Furthermore, because alignment may be practically discovered (self-emergent) or built (programmed), alignment actually comes from four directions:
- emergent external alignment;
- emergent internal;
- programmed external; and,
- programmed internal.
Managing alignment depends on awareness of the environment's dynamics. Each one of the four types of alignment must deal with a set of distinctive dynamics -- the flows and blends of states and events that characterize the conditions of the type of environment. Consequently, the information that each type presents to management can be quite dissimilar to the other three types. Yet each is a significant factor in the supply or readiness aspects of throughput.
Whether overall alignment proves manageable or not depends on leveraging distinctive competencies from within these four different situations in order to achieve and sustain the coordination necessary. A competency dynamically combines awareness with knowledge and skills under real-time demand.
III.
At any given time, all four types of alignment are factors with varying relative impact. Given this situation, the initial problem to address is to successfully sort out and describe the causes and effects characteristic of each area, that are most relevant to execution throughput.
In the representation of the distinctive alignment areas below , the picture shows four corresponding types of influence on execution, along with the two main reasons (accountability and compatibility) that management tracks them.

Following on that, developing a "common awareness" across the different areas of alignment is the key to their coordination.
IV.
Much of the work of defining the view on each alignment area is carried out by what is now called "business intelligence". Each area reports on matters that explain how its own activity and events are influencing things or are being influenced. Competencies found within the various types of alignment differ , and are and sometimes optimized in ways that increase their differences. From the perspective of execution throughput, the extent of those differences is often not as much in the foreground as it should be. But when recognized, this problem is addressed through integration initiatives.
Integration appears to circulate required information across boundaries, but the crucial work of developing the awareness common amongst the different areas falls to what is being called "knowledge management".
We're very accustomed to the idea of discovering connections through information processing, but to create the common awareness, knowledge processing must also be implemented. Knowledge processing discovers how different things are alike, not just how they affect each other.
V.
Information processing and knowledge processing contribute in different ways. The challenge is to make them co-operate in the four types of alignment.
Management's supervisory responsibility relies on sensitivity to pertinent descriptive facts -- or "intelligence". This naturally tends towards data collection (surveillance) about external factors and data validation (auditing) about internal factors.
But in those efforts:
- surveillance of emergent conditons rests on access, intervention and persistence. These are opportunities that may be highly dissimilar in external versus internal environments;
- meanwhile, the auditing of programmed conditions requires authority, methods and testing -- concerns which have resolutions that are typically unlike across external versus internal environments.
Although these differences are not insurmountable, such inherent limitations of business intelligence reflect the essential difficulty of comparing apples to oranges. Alternative knowledge processing is thus critically appropriate for relating the various areas of alignment. In a sense, solving integration issues with business intelligence is like making a fruit salad that is easier to consume, instead of finding the underlying principle that will make both apples and oranges grow better in the same climate. For the latter solution, knowledge management is better.
Along with the correlation of different competencies, an operational strategy for coordinating effects amongst the different areas must be selected. For any area, this will generally involve calibrating the area amongst the others, through one of four modes:
- waiting (to shrink scope and complexity)
- repositioning (to increase leverage)
- renovating ( to manage change in demand), or
- innovating (to create a new type of relationship).
While pursuing an operational strategy for each alignment area, the group of four strategies must also be co-ordinated with each other and over time.
Overall Alignment should therefore be modelled so that coordinated operational strategies (or "modes") for addressing the four flavors of alignment are visible for all operations to explicitly engage -- making alignment manageable. Effectively, that model of coordination is a portfolio.
Posted by Malcolm Ryder at 1:15 PM | Comments (0) | TrackBack
February 23, 2005
Change and Management
Managing change is always a critical capability, yet is it always an important practice? Consider the idea that things can have a distinction without a difference. For example, if moving to a point two steps to the left gives no "better" point of view, then a distinction without a difference has been achieved. This helps to point out that if there is no point to the difference, then there may be no need to manage the change that creates the difference.
The punchline is that managing difference , as opposed to just managing distinctions, is the essential purpose of managing change. Put differently, change management manages for value -- meaning, the significance of the difference.
For example, pursuit of an opportunity or avoidance of a risk represents basic motives for change management. In practice, when "significant" transformations of a current state can be consistently anticipated and purposefully controlled, Change itself becomes "manageable".
In management terms, the value represented by the significance may be positive or negative, since the value is determined by comparing the result of the transformation to either the prior current state or a currently desired state. Generically, this value assessment identifies positions along three dimensions:
(a.) the intended/unintended;
(b.) the expected/unexpected; and
(c.) the planned/unplanned.
According to the locations foreseen or detectable within that 3-D space for any event, the practical roles of anticipation and control are defined, scoped and scheduled (thereby spawning requirements for related policies, processes, tools, and so on). But this organization of roles happens only because the various locations in that 3-D space are seen as being
(x.) preferable to some degree,
(y.) tolerable to some degree, or
(z.) inevitable to some degree.
Consequently, in acknowledging this second 3-D space that characterizes or "measures" the locations within the first space, we can see that change management is where value and risk are managed together -- making change management always essentially strategic -- whether it is being practiced at the level of operational commitments, or tactical selections, or strategic planning.
Posted by Malcolm Ryder at 8:42 AM | Comments (0) | TrackBack
About Enterprise IT
I.T. in the Enterprise:
The number one "problem" in enterprise I.T. is not techniques fighting resources, but instead it is politics fighting strategy. For I.T. to succeed, a strategy derived from the culture must prevail over the politics derived from the culture.
It is so simple to understand why "successful" I.T. must run the gauntlet of first culture, second politics, and lastly discipline:
- People think they have to get something done.
- They want something to do it with.
- They have to get whatever that is.
- When they get it, they have to actually use it to get something -done.
- Sometimes they do what they originally thought they had to do.
- Sometimes whatever they do causes what they thought they wanted to effect.
Because each one of those six steps is rife with uncertainty or trade-offs or both, the probability that appropriate technology will flow through them all to be appropriately applied is always changing.
Accordingly, without change management, there is no probable IT success.
But without policies, there is no change management.
And without strategy, there is no probable policy success.
Posted by Malcolm Ryder at 3:16 AM | Comments (0) | TrackBack
February 22, 2005
The Foundation Class Library
Archestra's knowledgebase is structured to distinguish its content as much by utility as by topic. This is an ongoing and flexible exercise that often involves identifying multiple purposes for any given item, with a fairly constant possibility of context-sensitive revisions and versions being produced.
Overall, the knowledgebase is managed by a Librarian (who you may contact via email by clicking here ).
Content contributors play key roles as follows:
Authors and Co-authors (originally conceive new work or udate their own work)
Editors (craft release-versions of authors' drafts)
Reviewers (assess relationships of new work to prior work)
Reporters (track and cite occurrences of similar or same work)
Any number of individuals may collaborate in any of those roles. Work produced from those roles is credited by role.
Posted by Malcolm Ryder at 5:01 PM | Comments (0) | TrackBack
February 21, 2005
Models
Models show an inherent structure of an object, procedure or event, in a way that is intended to explain why the structure is viable for the purpose of the object, procedure or event; or, to demonstrate that a certain structure accounts for given expressed characteristics of the object, procedure or event.
The structure exhibited by the model always shows discrete components and relationships.
The definition of the components and relationships is a point of major difference between any two models that (otherwise) both intend to refer to the same object, procedure or event.
For the purpose of modelling, a "state" in the course of changing conditions can be treated as an event. This is especially helpful in describing "problems" with models.
Posted by Malcolm Ryder at 5:02 PM | Comments (0) | TrackBack
February 19, 2005
Archestra Projects
Archestra projects basically catalog individual and collaborative efforts to add to the Framework depth and integrity in any of the following ways:
(a.) identify or propose a new structural component of a relationship in the Framework;
(b.) adjust and validate components and relationships for their integrity;
(c.) demonstrate a method for "managing" development of a component or relationship - including to define, discover, make, test, scale, position, measure, change or delete;
(d.) demonstrate similarities, affinities or integrations between the Framework and other frameworks, models and literatures;
(e.) apply the Framework to designated problems in enterprise strategy, resulting in documented application hypotheses, methodologies, or case studies.
Posted by Malcolm Ryder at 7:28 PM | Comments (0) | TrackBack