Showing posts with label SWOT. Show all posts
Showing posts with label SWOT. Show all posts

November 25, 2011

No More Excuses, Please

The New Yorker (24 October 2011) has a clever take on the urge of some--in this case, the privileged--to try and preserve the status quo. However, this can be applied more broadly.
While not an endorsement of any specific movement, this is an acknowledgement of the resistance to change by both organizations and individuals, and the many excuses offered.
Some typical ones we all have heard, in one form or other:
- It's always been this way.
- We've tried "that" before and it didn't work.
- Change is hard.
- Everything is fine just the way it is.
While change for changes sake is obviously pointless, change to adapt to new opportunities and threats is just good business sense.
Additionally, change to address inequalities on inequities is good moral sense.
Of course, we have to vet proposed changes and ensure they are constructive, the best option available, and really doable, so we are not just jumping into something irresponsibly.
When change meets the mark, then to implement it, we have to give it all we've got!
From our leaders, it takes vision, courage, and determination to see what needs to get done, get past the excuses, and inspire change.
From society, it takes sacrifice and hard work to get us to where we must go.
But if it's a destination worthwhile, then we drop the excuses and move to action.

Hopefully, we can recognize when change is indeed, necessary, and not be blinded by our fears and self-serving resistance that hinders the greater good.

Share/Save/Bookmark

January 9, 2011

The Center Of Gravity Is Information

Center of Gravity (COG) is a military concept that Dr. Joseph Strange defines as “primary sources of moral or physical strength, power, and resistance.” From a military perspective, this is where we should concentrate when attacking the enemy. As Prussian strategist Carl von Clausewitz states, “that is the point against which all our energies should be directed.”

In “Center of Gravity Analysis” (Military Review, July/August 2004), Army Colonel Dale Eikmeier describes the framework for COG and how an enemy (your threat) attempts to exploit them, as follows:

· Center of Gravity—the organizations that do the work (e.g. the military/industrial complex)

· Critical Capabilities (CC)—the strengths of the organization—its “primary abilities”

· Critical Requirements (CR)—the supplies that a COG use—the inputs that are their opportunities, if leveraged for future plans

· Critical Vulnerabilities (CV)—the vulnerabilities a COG has—e.g. exposed or unguarded critical infrastructure

From an enterprise architecture perspective, I greatly appreciate this analysis of COG as it aligns beautifully with Albert Humphrey’s famous Strenghts, Weaknesses, Opportunities, and Threats (SWOT) Analysis for organizational strategic planning.

Aside from typical SWOT analysis to develop your organization’s strategy, the COG analysis adds greater offensive analysis to SWOT--like the military, organizations using the COG model can disrupt competitors’ advantages by seeking to weaken them where they are most vulnerable.

For example, EA used in this fashion may lead a company to build a sophisticated online sales site that directs customers away from your competitor’s retail location. Similarly, acquiring a major supplier (i.e. vertically integrating) may disrupt a competitors’ supply capability, and so on. The point is that EA becomes a force for attack rather than a mere planning tool or information asset.

It is at this point that I disagree with the assertion in the article that “Information is not power; it is a tool, an enabler. It helps wield military or economic power. By itself, it is simply information.”

Far to the contrary, information is one of the greatest assets that we have. It is the way that an advanced, intellectually based society competes. Of note, our declining performance in Science, Technology, Engineering, and Mathematics (STEM), which is so greatly worrisome to our leadership, is of concern because it is directly a threat to our competitive advantage, both militarily and economically, in the global environment.

Information, as embodied by the Internet, is now the center of our society. With it, we perform critical tasks of information sharing, collaboration and education. Used effectively, our military has developed robust command, control, communications, computers, intelligence, reconnaissance, and surveillance (C4ISR)—all information-based. Similarly, our industry is highly competitive and advanced because of the engineering, innovation, and people behind it.

Enterprise architecture, once a small part of the IT infrastructure, can actually play a far greater role in the information society if we allow it to. We have morphed from the industrial age of the 18th and 19th centuries to a highly advanced information society that creates new sources of critical capability, but also new critical vulnerabilities that must be defended. And we must also leverage the vulnerability of our enemies in order to stay viable. Whether it’s cyber-warfare or economic survival, information is at the heart of everything we are successfully doing today.


Share/Save/Bookmark

February 8, 2010

From Planning to Practice

Real planning is hard work. I’m not talking about the traditional—get the management team together, offsite for a few hours or days and spell out a modified mission and vision statement and some basic goals and objectives—this is the typical approach. Rather, I am referring to thinking and planning about the future with a sense of urgency, realism, and genuine impact to the way we do our jobs.

In the traditional approach, the management team is focused on the planning session. They are engaged in the planning for a short duration, but when back in the office, they don’t go back in any meaningful way to either refer to or apply the plan in what they or their employees actually do. The plan in essence defaults to simply a paperwork exercise, an alignment mechanism, a check box for the next audit.

In contrast, in a comprehensive planning approach, the focus is not on the planning session itself, but on the existential threats and opportunities that we can envision that can impact on the organization and what we are going to do about it. We need to look at for example: What are our competitors doing? Are there new product innovations emerging? Are there social and economic trends that will affect how we do business? How is the political and regulatory environment changing? And so on. The important thing is to think through/ work through, the impact analysis and plan accordingly to meet these head-on.

This is similar to a SWOT analysis—where we evaluate our Strength, Weaknesses, Opportunities, and Threats, but it differs in that it extends that analysis portion to story planning (my term), where the results of SWOT are used to imagine and create multifaceted stories or scenarios of what we anticipate will happen and then identify how we will capitalize on the new situation or counter any threats. In other words, we play out the scenario —similar to simulation and modeling—in a safe environment, and evaluate our best course of action, by seeing where the story goes, how the actors behave and react, and introducing new layers of complexity and subtext.

Harvard Business Review (HBR), Jan-Feb 2010, has an article called “Strategy Tools for a Shifting Landscape” by Michael Jacobides that states “in an age when nothing is constant, strategy should be defined by narrative—plots, subplots, and characters---rather than by maps, graphs, and numbers.”

The author proposes the use of “playscripts” (his term), a scenario-based approach for planning, in which—“a narrative that sets out the cast of characters in a business, the way in which they are connected, the rules they observe, the plots and subplots in which they are a part, and how companies create and retain value as the business and the cast changes.

While I too believe in using a qualitative type of planning to help think out and flesh out strategy, I do not agree that we should discard the quantitative and visual analysis—in fact, I think we should embrace it and expand upon it by integrating it into planning itself. This way we optimize the best from both quantitative and qualitative analysis.

While numbers, trends, graphics, and other visuals are important information elements in planning, they are even more potent when added to the “what if” scenarios in a more narrative type of planning. For example, based on recent accident statistics with the car accelerators (a quantifiable and graphical analysis), we may anticipate that a major foreign car company will be conducting a major recall and that the government will be conducting investigations into this company. How will we respond—perhaps, we will we increase our marketing emphasizing our own car safety record and increase production in anticipation of picking up sales from our competitor?

Aside from being robust and plausible, the article recommends that playscripts be:

· Imaginative—“exploring all the opportunities that exist.” I would also extend this to the other relevant element of SWOT and include envisioning possible threats as well.

· Outward-facing—“focus on the links a company has with other entities, the way it connects with them and how others perceive it in the market.” This is critical to take ourselves out of our insular environments and look outside at what is going on and how it will affect us. Of course, we cannot ignore the inner dynamics of our organization, but we must temper it with a realization that we function within a larger eco-system.

To me, the key to planning is to free the employees to explore what is happening in their environment and how they will behave. It is not to regurgitate their functions and what they are working on, but rather to see beyond themselves and their current capabilities and attitudes. Life today is not life tomorrow, and we had better be prepared with open minds, sharpened skills and a broad arsenal to deal with the future that is soon upon us.


Share/Save/Bookmark

June 22, 2008

What Not to Tell Your Boss and Enterprise Architecture

ComputerWorld Magazine, 20 June 2008, tells us five things you don’t want to tell the CIO and which I believe tracks closely with the enterprise architecture function and goals, as follows:

  1. “All about the technology -- and nothing about the business”—just like enterprise architecture is about business driving technology, rather than doing technology for technology’s sake, so too the CIO is interested in aligning business and technology. So don’t just go to the CIO talking technology solutions unless you have a clear understanding and can articulate the business requirements.
  2. “There's only one solution”—in enterprise architecture and IT governance, we validate requirements against the architecture—the baseline, the target, and the transition plan. It is especially important to check if there are existing systems, products, and standard that can be used to meet user requirements, rather than building or acquiring something from scratch. There is rarely only a single technology solution for a business problem. Therefore, we need to evaluate the proposed new IT investment in terms of the return on investment, risk management, strategic business alignment, and technical compliance. Additionally, we need to review the analysis of alternatives to make sure we are effectively managing our scarce IT resources.
  3. “Bad opinions about your colleagues”—EA planning and governance makes information transparent and enables better decision making. With EA information, vetting of IT investment and collaborative decision making, there is no need to point fingers at each other over failed IT projects. Instead, through sharing information and bringing IT project stakeholders together, we all have input into the decision process and share the project risk.
  4. “There's no way”—With enterprise architecture, rather than say there’s no way to achieve enterprise goals or overcome technical challenges, we develop a target and plan for how we will do it. No, the goals are not achieved overnight, but rather by following a meticulous and vetted plan, usually over a period of three to five years, we can transform the enterprise.
  5. A surprise”—Bosses don’t like surprises. In a professional setting, we usually like rational thinking, process, structure, and planning, so that we can effectively deal with the chaotic world out there. EA planning and structured governance helps the organization stay on course and not get surprised or thrown. The planning process itself involves looking at our strengths, weaknesses, opportunities, and threats, and makes us more self-aware and proactive as an organization, so there are less surprises waiting to ambush us.

EA helps us to NOT have to tell our boss, the CIO, things he doesn’t want to hear, because we are proactive in our approach to planning and governance.


Share/Save/Bookmark

January 18, 2008

SWOT Analysis and Enterprise Architecture

“SWOT Analysis is a strategic planning tool used to evaluate the Strengths, Weaknesses, Opportunities, and Threats involved in a project or in a business venture. It involves specifying the objective of the business venture or project and identifying the internal and external factors that are favorable and unfavorable to achieving that objective.”

SWOT factors can be broken down in internal/external factors and helpful/harmful factors, as follows:

  • INTERNAL/EXTERNAL—SWOT looks at both organizational or internal factors (strengths and weaknesses) and environmental or external factors (opportunities and threats).
  • HELPFUL/HARMFUL—SWOT examines those factors that are helpful (strengths and opportunities) and harmful (weaknesses and threats) to an organization’s objectives .

SWOT analysis is used to generate strategies, as follows:

  1. How can we use each strength?
  2. How can we stop each weakness?
  3. How can we exploit each opportunity?
  4. How can we defend against each threat?

(Adapted from Wikipedia)

According to the American Management Association, “SWOT is perhaps most useful as a tool for organizing data and allowing you to distill them down to a few strategic priorities.”

SWOT Analysis is a tool that can be used by User-centric EA in analyzing the business and technology baseline of the enterprise and coming up with strategic priorities to address in the target architecture and transition plan. Of course, the target architecture will capitalize on organizational strengths (by building on the strength of its people, process, and technologies), mitigate weaknesses (through skilled performance management, business process improvement, information sharing, and technological solutions), exploit opportunities and defend against threats (through integration and differentiation, partnerships and alliances, marketing and communciations, and so on). SWOT Analysis tells the EA practitioner what he/she needs to know to develop strategies for the enterprise to target.
Share/Save/Bookmark