business goals examples

We couldn't find the page you requested, either because it is temporarily unavailable, has had its name changed, or no longer exists on FindArticles.

This error occurred at: 2009-12-05 15:13:37

If you'd like to forge ahead here are some ideas:

Thank you for visiting FindArticles.

| | | |

© 2009 CBS Interactive Inc. All rights reserved. | | |

Forget 'What are your strengths and weaknesses?' If you want to get the real dope on prospective employees, ask job candidates these seven questions.

Winter is a time of cold weather — ahem, heating oil — and traveling to see relatives –Ā gas for cars, truck and jet fuel for planes. But the U.S. has got a lot of stuff and the fourth quarter for U.S. refiners will likely be as tough as the last. U.S. commercial crude oil inventories increased [...]

Hang onto this essential checklist, so you’ll know what to do when the time comes.

image

Step 1. Identify the Business Strategy

A business must identify what its Business Strategy is. With methods like  image

Porterā€™s Five Forces Concept

         

Collinsā€™ Hedgehog Concept

 

One output from this activity is a set of Business Strategy Statements where each Business Strategy Statement includes Objective, Scope and Competitive Advantage elements. Hereā€™s a link to HBS article describing this in detail.

Step 2. Identify Context Business Processes

Using Business Processes, often in the format of a Business Process Categorization model, identify Business Processes that do not directly enable Business Strategy. There are many methods out there to help do this such as Geoffrey Mooreā€™s Core versus Context, and your common Enterprise Architecture mapping Business Process to Business Strategy activity.

In the Core versus Context method, I refer to the ā€œCore versus Contextā€ concept developed by Geoffrey Moore. In Mooreā€™s book 'Living on the Fault Line', Moore described a method for identifying Core and Context Business Processes and Business Process Activities, "For core activities, the goal is to differentiate as much as possible on any variable that impacts customers' purchase decisions and to assign one's best resources to that challenge. By contrast, every other activity in the corporation is not core, it is context. And the winning approach to context tasks is not to differentiate but rather to execute them effectively and efficiently in as standardized a manner as possible."

In the Business Process to Business Strategy Analysis method, one analyzes the Business Strategy Statements and associates Business Processes that directly relate to Business Strategy Statements. I add a little twist here and assert that Business Processes that do not directly enable Business Strategy are considered Context Business Processes.

The assumption at this point is that Business Processes that are strategic should expect change. Those that are not strategic, therefore Context Business Processes, should expect less change. In fact, according to Moore, Context Business Processes should be standardized.

Step 3. Identify Candidate Platforms

We now need to identify Business Software Platforms. There are number of methods out there to help logically group Functions by Information entities to identify candidate Software Platforms. Methods such as Affinity Analysis, Yourdon and Constantineā€™s Functional Cohesion, and Coplienā€™s Scope, Commonality, Variability Analysis. All three have a common goal when using Business Process and Data as factors to be analyzed which is to mathematically identify logical groupings of processes based on their relationship to data.

The only addition I make to these methods is to only focus on Context Business Processes in the analysis. The assumption I make is that Software Platforms, by their very nature provide reusable/shared automation of business processes and data, represent standardized processes and data. By focusing on Context Business Processes, we simply realize these as Business Software Platforms as a result of the analysis.

Core Business Processes are left to be supported/automated by the more agile Applications because Applications are not specifically designed to be shared or reused. Applications provide time-to-market agility to the business.

Summary - Nothing new just putting together known concepts

This is an interesting post for me because I havenā€™t introduced any new concepts to suggest this new process idea for maturing the Enterprise Architecture discipline. Instead, I pulled together known concepts from business and software engineering domain experts to form a simple 3-step process for identifying Business Software Platforms.

Iā€™m an Enterprise Architect so I also wonder if this idea can be broadened beyond S+S to across the Microsoftā€™s enterprise and, potentially, for any enterprise so I thought Iā€™d publish this idea and share it. Thoughts?

By the way, I realize that this simple process is far from easy as there are lots of prerequisites to complete it such as; Defined Business Strategies exist, an inventory of business processes, an inventory of Business Data, and a mapping from Business Process to Business Data. Sorry if Iā€™ve presented it in a way that appears way too easy. :)

 

Glossary of Terms:

TermDefinitionSourceCompetitive Business Strategy (aka Business strategy)Business Strategy refers to how a company competes in a particular business (note: overall strategy for diversified firms is referred to as corporate strategy).Competitive strategy is concerned with how a company can gain a competitive advantage through a distinctive way of competing. Competitive Business Strategy refers to the aggregated strategies of single business firm or a business unit that incorporates either cost leadership, differentiation or focus in order to achieve a sustainable competitive advantage and long-term success in its chosen arenas or industries. The essence of strategy is choosing a unique and valuable position rooted in systems of activities that are much more difficult to match.