Monday, August 10, 2009

Performance Analysis (PA)

http://www.josseybass.com/legacy/rossett/rossett/what_is_pa.htm

What is Performance Analysis?

A serious definition goes like this:

Performance analysis involves gathering formal and informal data to help customers and sponsors define and achieve their goals. Performance analysis uncovers several perspectives on a problem or opportunity, determining any and all drivers towards or barriers to successful performance, and proposing a solution system based on what is discovered.

A lighter definition is:

Performance analysis is the front end of the front end. It's what we do to figure out what to do. Some synonyms are planning, scoping, auditing, and diagnostics.

What does a performance analyst do?

Here's a list of some of the things you maybe doing as part of a performance analysis:

  • Interviewing a sponsor
  • Reading the annual report
  • Chatting at lunch with a group of customer service representatives
  • Reading the organization's policy on customer service, focusing particularly on the recognition and incentive aspects
  • Listening to audiotapes associates with customer service complaints
  • Leading a focus group with supervisors
  • Interviewing some randomly drawn representatives
  • Reviewing the call log
  • Reading an article in a professional journal on the subject of customer service performance improvement
  • Chatting at the supermarket with somebody who is a customer, who wants to tell you about her experience with customer service
  • A performance analysis identifies where we are, where we want to go, the reasons why we aren't there yet, and recommends ways to get there.

    According to Wendy Clash an Educational Technologist at San Diego State University
    Department of Educational Technology offers this information.

    After determining the cause(s) of a performance problem, you recommend solution systems.

    Cause:

    Solution:

    Motivation

    information, documentation, coaching.

    Environment Support

    flexibility with schedule and job duties, availability of tools, reorganization of workplace.

    Organization Support

    incentive programs and appraisal process, change in policy

    Knowledge and Skills

    instruction, coaching, job aids, and electronic support systems.

    Solution systems are easy to implement when they require minor changes to company policy and/or the working environment.

    When delivery of information or more significant changes are needed, it's time to call in the experts.


    Knowledge Engineering

    http://www.epistemics.co.uk/Notes/61-0-0.htm

    Knowledge engineering is a field within artificial intelligence that develops knowledge-based systems. Such systems are computer programs that contain large amounts of knowledge, rules and reasoning mechanisms to provide solutions to real-world problems.

    A major form of knowledge-based system is an expert system, one designed to emulate the reasoning processes of an expert practitioner (i.e. one having performed in a professional role for very many years). Typical examples of expert systems include diagnosis of bacterial infections, advice on mineral exploration and assessment of electronic circuit designs.
    Importance of Knowledge Acquisition

    The early years of knowledge engineering were dogged by problems. Knowledge engineers found that acquiring enough high-quality knowledge to build a robust and useful system was a very long and expensive activity. As such, knowledge acquisition was identified as the bottleneck in building an expert system. This led to knowledge acquisition becoming a major research field within knowledge engineering.

    The aim of knowledge acquisition is to develop methods and tools that make the arduous task of capturing and validating an expert’s knowledge as efficient and effective as possible. Experts tend to be important and busy people; hence it is vital that the methods used minimize the time each expert spends off the job taking part in knowledge acquisition sessions.
    Knowledge Engineering Principles

    Since the mid-1980s, knowledge engineers have developed a number of principles, methods and tools that have considerably improved the process of knowledge acquisition. Some of the key principles are summarized as follows:

    * Knowledge engineers acknowledge that there are different types of knowledge, and that the right approach and technique should be used for the knowledge required.
    * Knowledge engineers acknowledge that there are different types of experts and expertise, such that methods should be chosen appropriately.
    * Knowledge engineers recognize that there are different ways of representing knowledge, which can aid the acquisition, validation and re-use of knowledge.
    * Knowledge engineers recognize that there are different ways of using knowledge, so that the acquisition process can be guided by the project aims.
    * Knowledge engineers use structured methods to increase the efficiency of the acquisition process


    Knowledge engineering (KE) was defined in 1983 by Edward Feigenbaum, and Pamela McCorduck as follows:

    KE is an engineering discipline that involves integrating knowledge into computer systems in order to solve complex problems normally requiring a high level of human expertise.[1]

    At present, it refers to the building, maintaining and development of knowledge-based systems.[2] It has a great deal in common with software engineering, and is used in many computer science domains such as artificial intelligence [3], [4], including databases, data mining, expert systems, decision support systems and geographic information systems. Knowledge engineering is also related to mathematical logic, as well as strongly involved in cognitive science and socio-cognitive engineering where the knowledge is produced by socio-cognitive aggregates (mainly humans) and is structured according to our understanding of how human reasoning and logic works.

    Various activities of KE specific for the development of a knowledge-based system:

    * Assessment of the problem
    * Development of a knowledge-based system shell/structure
    * Acquisition and structuring of the related information, knowledge and specific preferences (IPK model)
    * Implementation of the structured knowledge into knowledge bases
    * Testing and validation of the inserted knowledge
    * Integration and maintenance of the system
    * Revision and evaluation of the system.

    Being still more art than engineering, KE is not as neat as the above list in practice. The phases overlap, the process might be iterative, and many challenges could appear. Recently, emerges meta-knowledge engineering[5] as a new formal systemic approach to the development of a unified knowledge and intelligence theory.


    http://en.wikipedia.org/wiki/Knowledge_engineers



    Knowledge engineers are computer systems experts who are trained in the field of expert systems. Receiving information from domain experts, the knowledge engineers interpret the presented information and relay it to computer programmers who code the information in to systems databases to be accessed by end-users. Knowledge engineers are used primarily in the construction process of computer systems (Bultman, Kuipers & van Harmelen 2000).

    Using information relayed by the domain experts, knowledge engineers are experts at constructing meaningful, useful, and simplistic Knowledge-Based Systems (KBS). Often knowledge engineers are employed to break down the information passed on by domain experts into more simplistic terms which cannot be easily communicated by the highly technalized domain expert (ESDG 2000).

    SCORM-compliant courseware

    What is SCORM?
    Wikipedia has this definition. Sharable Content Object Reference Model (SCORM) is a collection of standards and specifications for web-based e-learning. It defines communications between client side content and a host system called the run-time environment (commonly a function of a learning management system). SCORM also defines how content may be packaged into a transferable ZIP file.

    SCORM is a specification of the Advanced Distributed Learning (ADL) Initiative, which comes out of the Office of the United States Secretary of Defense.

    SCORM 2004 introduces a complex idea called sequencing, which is a set of rules that specifies the order in which a learner may experience content objects. In simple terms, they constrain a learner to a fixed set of paths through the training material, permit the learner to "bookmark" their progress when taking breaks, and assure the acceptability of test scores achieved by the learner. The standard uses XML, and it is based on the results of work done by AICC, IMS Global, IEEE, and Ariadn.

    I like to example given by Rustici Software on the website scorm.com. They explain it is terms of DVD's. Regardless to the type of player the you own, you expect for any of the movies that work in that player despite who made it. This is true because to standards that established in that industry.

    SCORM stands for “Sharable Content Object Reference Model”.
    “Sharable Content Object” indicates that SCORM is all about creating units of online training material that can be shared across systems. SCORM defines how to create “sharable content objects” or “SCOs” that can be reused in different systems and contexts.

    “Reference Model” reflects the fact that SCORM isn’t actually a standard. ADL didn’t write SCORM from the ground up. Instead, they noticed that the industry already had many standards that solved part of the problem. SCORM simply references these existing standards and tells developers how to properly use them together.


    SCORM is produced by ADL, a research group sponsored by the United States Department of Defense (DoD).

    For information on SCORM, check out this sites.
    www.toolbook.com/community_scorm.php
    www.scorm.com/scorm_explained

    Electronic Performance Support Systems

    The Encyclopedia of Educational Technology defines EPSS ase an extension and further development of the workplace job aid. As described by Rossett & Gautier-Downes (1991), job aids support work and activity, are external to the individual and have three discrete functions, which are:

    1. providing information,
    2. supporting procedures, and
    3. guiding decision making.

    When these three functions of job aids interconnect within an integrated technology-based system, a “highly sophisticated technological job aid” called an electronic performance support system results (Van Tiem, Moseley, & Dessinger, 2004, p. 71). Characteristic advantages of an EPSS over a traditional non-technology based job aid include:

    * user ability to quickly access large quantities of information,
    * support for multiple users anywhere at any time the delivery technology is available, and
    * user ability to receive interactive coaching and guidance.

    Electronic Performance Support Systems

    Gloria J. Gery, a consultant in the fields of business learning and electronic performance support, is the author of "Electronic Performance Support Systems" (Gery Performance Press, 1991), the seminal book on EPSS.

    Gloria Gery published a book in 1991 that defines electronic performance support systems (EPSS) as
    "an integrated electronic environment that is available to and easily accessible by each employee and is structured to provide immediate, individualized on-line access to the full range of information, software, guidance, advice and assistance, data, images, tools, and assessment and monitoring systems to permit job performance with minimal support and intervention by others."

    Every article that I researched start with Gery's definition. She is concerned the expert of EPSS.

    Also in 1991, Barry Raybould gave a shorter definition:

    a computer-based system that improves worker productivity by providing on-the-job access to integrated information, advice, and learning experiences.

    According to an article that I found entitled, Types of Electronic Performance Support Systems:Their Characteristics and Range of Designs by Deborah Alpert Sleight in 1993 who is an Educational Psychologist at Michigan State University, types are some common uses for EPSS.

    An electronic performance support system (EPSS) displays some or all of the following characteristics.

    Computer-based: EPSSs are computer-based, which is what the "electronic" in their name indicates. There have been older attempts at performance support systems, such as a series of manuals, job aids, and other paper material. But it wasn't until the advent of powerful multimedia computers that optimal performance support could be made possible. Optimal support includes quick and easy access to the information needed at the time the task is being performed.

    Access during task: EPSSs provide access to the discrete, specific information needed to perform a task at the time the task is to be performed. This is a two-part characteristic: 1) access to the specific information needed to perform a task, and 2) access to the information at the time the task is to be performed. If one part of this characteristic does not exist, then the characteristic changes and is no longer a performance support characteristic. The discrete, specific information provided may be:

    * data: the type of data may be textual or numeric, such as prices, locations, and names. Or they may be visual, such as photographs and motion video footage. Or they may be audio, such as conversations, speeches, and music.
    * instruction: the instruction may be a list of steps to take, a motion video showing a procedure, or a simulation of a task that allows the user to practice.
    * advice: the advice may be an expert system that asks the user questions, then suggests the most appropriate procedure or step to do next.
    * tools: the software tools may be a spreadsheet, a statistical analysis package, and a program that controls industrial robots.

    This availability of information, instruction, advice and tools makes much prior training unnecessary.

    This makes EPSS versatile and user adaptive.

    She states that the benefits of EPSS are:
    Used on the job: An EPSS provides information to people at their workstation on the job, or in simulations or other practice of the job. The information is provided at the worker's workstation as the worker sees a need for it. The EPSS can be used in simulations or other practice of the job, so that the worker learns both the information he or she will probably need when doing the job, and how to use the EPSS itself.

    Controlled by the worker: The worker decides when and what information is needed. There is no need for a teacher, as the worker is guided by the needs of the task. The motivation is provided by the worker's desire to accomplish the task.

    Reduce the need for prior training: The easy availability of the information needed to perform a task reduces the need for much (but probably not all) prior training in order to accomplish the task.

    Easily updated: The very nature of an EPSS, that it provides the information needed to perform a task, requires that it be easily updatable, in order to keep the information that it provides current. The computerized nature of an EPSS makes updating faster and easier in some ways than in other media, such as print, video, or audio.

    Fast access to information: The user must be able to access the needed information quickly when it is needed on the job. Otherwise the EPSS is no better than a set of manuals, which probably contain the information, but the information is difficult to find when needed.

    Irrelevant information not included: The user is able to access only the specific, discrete information needed at that instant, instead of having to wade through loads of irrelevant information to find the few details needed. This is one of the problems with instruction that is not specific to a task; it forces the user to sift through it looking for the details needed. This sifting not only slows the user down, but can result in confusion.

    Allow for different levels of knowledge in users: In order to speed up information access and understanding, an EPSS can provide minimal information for those who do not want details, yet, through the hypertext links in the databases and through optional tutorials, provide detail for those who do want more.

    Allow for different learning styles: Through multimedia, an EPSS can accommodate users with varied learning styles, thus providing more optimal learning. The same information can be presented in visual, textual, and audio formats, with the user selecting the format.

    Integrate information, advice, and learning experiences: An EPSS can integrate information, advice, and learning experiences for the user. For example, a database entry might describe a procedure. The user may not know if the procedure is the proper one to use, so he or she might turn to the advisor to find out. The advisor would ask the user some questions about what he or she needs to accomplish, then would suggest which procedure to use. The user might then access a tutorial on using the procedure, and practice it through a simulation, before actually performing the procedure.

    Artificial intelligence: Artificial intelligence is an essential characteristic of EPSSs, according to Carr (Carr, 1992), but not according to Gery. I think that at this early stage of performance support system design and use, AI is not essential, but that eventually it will be one of the defining characteristics of EPSS. This will happen when research on EPSS and on AI has progressed further.

    An EPSS is not an absolute system that contains all these characteristics. Rather, different systems will fall on a continuum of these characteristics. An EPSS displaying all these characteristics would be the ideal. Since performance support systems are still young, it is more likely that many will display only the key characteristics.

    Sunday, August 9, 2009

    Learning management System

    Being new to all of the terms, I goggled LMS. Wikipedia defines LMS as is software for delivering, tracking and managing training/education. LMSs range from systems for managing training/educational records to software for distributing courses over the Internet and offering features for online collaboration. In many instances, corporate training departments purchase LMSs to automate record-keeping as well as the registration of employees for classroom and online courses.
    I found in my searching the BlackBoard is a LMS offered by the Dell corporation. WOW! Something that I could visibly see.

    This is Dell description of BlackBoard on Dell.com. "Blackboard is software for delivering, tracking and managing training/education. LMSs range from systems for managing training/educational records to software for distributing courses over the Internet and offering features for online collaboration. In many instances, corporate training departments purchase LMSs to automate record-keeping as well as the registration of employees for classroom and online courses".

    LMS allow educational organization the ability to modified and republish single courses to various audiences while maintaining different versions and history. The objects stored in the centralized repository can be made available to course developer and content experts throughout and organization for potential reuse and re purpose. The eliminates duplicate development effort and allow for the rapid assemble of customized content which is very cost-effective.


    I do not know all the capabilities of Blackboard due to limited usages, but I find it to be okay. I really do not have anything to compare it to. It has met all of my educational needs.

    According to Renee Greene of ehow.com, here are some to the cons with LMS.Learning does not happen in a vacuum,~~ according to Godfrey Parkin, a specialist in online strategy and marketing innovation. "...an LMS, as available today, is not a universal solution for a corporation's e-learning problems. In fact, an LMS is often the albatross around the neck of progress in technology-enhanced learning." He believes that the vendors of these software systems remove control from end-users--the instructors and learners. In an exaggerated effort to "do it all," LMS appears to cause more confusion than it resolves. Centralized learning, Parkin says, limit options in that they are more focused on tools and the warm bodies who use them than the needs of the instructor to maintain flexibility in his teaching methods.
    I agree.
    All though there are some cons, the positives of LMS are tremendous. According to an article that I found on a website called NetDimension, these just to few of the pros to using a LMS and their product which is Enterprise Knowledge Platform (EKP).

    A learning management system is now used not only to implement an organization's learning development but also to measure and report on training delivery, ensure employee compliance, automate reporting and tracking, as well as deliver assessment and testing.

    Whether your organization is starting a departmental pilot or rolling-out a global installation, NetDimensions' Enterprise Knowledge Platform (EKP) learning management system, is secure, reliable, easy to use and quick to implement.
    EKP enables you to manage:

    * Performance appraisals
    * Training programs
    * License and certification requirements
    * Competencies
    * Compliance initiatives
    * Succession planning

    NetDimensions' learning management system will help you:

    * Improve the efficiency of compliance programs.
    * Increase knowledge retention and make learning more efficient.
    * Measure the effectiveness of training.
    * Identify skills and competencies.
    * Decrease operational and travel costs.



    EKP is a powerful, multilingual learning management system that manages the entire training and development process from delivering and tracking to testing and reporting.
    EKP is optimized for:

    * Reporting & Tracking
    * Assessments, compliance procedures and licensing
    * Managing employee competencies and performance
    * Centralizing global knowledge
    * Transforming the learning process
    * Managing information – Integrate & Disseminate
    * Enhancing the front-end learning experience (EKP Portal Toolkit)
    * e-Commerce Management

    EKP Features List:

    * Automated reporting and tracking
    * Standardized procedures
    * Centralized global knowledge into one system
    * Increased organizational interaction and exchange of knowledge
    * Tracked regulatory compliance
    * Access, monitor, review and update materials anytime, anywhere 24/7
    * Integrated management of your entire training process
    * Supports 30+ languages

    Monday, July 13, 2009

    Change Management

    I was unfamiliar with the term change management in respect to instructional technology. I want to find a simple explanation for this terminology.

    According to website wikipedia, change management is an
    IT Service Management discipline. The objective of Change Management in this context is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to controlled IT infrastructure, in order to minimize the number and impact of any related incidents upon service. Changes in the IT infrastructure may arise reactively in response to problems or externally imposed requirements, e.g. legislative changes, or proactively from seeking imposed efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement initiatives. Change Management can ensure standardized methods, processes and procedures are used for all changes, facilitate efficient and prompt handling of all changes, and maintain the proper balance between the need for change and the potential detrimental impact of changes.

    I have find the article explaining ten principles of change management.

    10 Principles of Change Management
    By John Jones, DeAnne Aguirre, and Matthew Calderone

    4/15/04 Tools and techniques to help companies transform quickly.

    In this article, the authors discuss how in 2004 senior executives in large companies had a simple goal for themselves and their organizations: stability. This stability would give their shareholders the safe, more than predictable earnings growth. Five years later, during the recession, that is still have very prevalent concern.

    This presents most senior executives with an unfamiliar challenge. In major transformations of large enterprises, they and their advisors conventionally focus their attention on devising the best strategic and tactical plans. But to succeed, they also must have an intimate understanding of the human side of change management — the alignment of the company’s culture, values, people, and behaviors — to encourage the desired results. Plans themselves do not capture value; value is realized only through the sustained, collective actions of the thousands — perhaps the tens of thousands — of employees who are responsible for designing, executing, and living with the changed environment.

    Long-term structural transformation has four characteristics:

    • scale (the change affects all or most of the organization),

    • magnitude (it involves significant alterations of the status quo),

    • duration (it lasts for months, if not years), and

    • strategic importance.

    Yet companies will reap the rewards only when change occurs at the level of the individual employee.

    No single methodology fits every company, but there is a set of practices, tools, and techniques that can be adapted to a variety of situations. What follows is a “Top 10” list of guiding principles for change management. Using these as a systematic, comprehensive framework, executives can understand what to expect, how to manage their own personal change, and how to engage the entire organization in the process.

    1. Address the “human side” systematically.

    • Any significant transformation creates “people issues.” New leaders will be asked to step up, jobs will be changed, new skills and capabilities must be developed, and employees will be uncertain and resistant. Dealing with these issues on a reactive, case-by-case basis puts speed, morale, and results at risk.

    • A formal approach for managing change — beginning with the leadership team and then engaging key stakeholders and leaders — should be developed early, and adapted often as change moves through the organization.

    • This demands as much data collection and analysis, planning, and implementation discipline as does a redesign of strategy, systems, or processes.

    • The change-management approach should be fully integrated into program design and decision making, both informing and enabling strategic direction. It should be based on a realistic assessment of the organization’s history, readiness, and capacity to change.

    2. Start at the top. Because change is inherently unsettling for people at all levels of an organization, when it is on the horizon, all eyes will turn to the CEO and the leadership team for strength, support, and direction. The leaders themselves must embrace the new approaches first, both to challenge and to motivate the rest of the institution. They must speak with one voice and model the desired behaviors. The executive team also needs to understand that, although its public face may be one of unity, it, too, is composed of individuals who are going through stressful times and need to be supported.

    Executive teams that work well together are best positioned for success. They are aligned and committed to the direction of change, understand the culture and behaviors the changes intend to introduce, and can model those changes themselves. At one large transportation company, the senior team rolled out an initiative to improve the efficiency and performance of its corporate and field staff before addressing change issues at the officer level. The initiative realized initial cost savings but stalled as employees began to question the leadership team’s vision and commitment. Only after the leadership team went through the process of aligning and committing to the change initiative was the work force able to deliver downstream results.

    3. Involve every layer. As transformation programs progress from defining strategy and setting targets to design and implementation, they affect different levels of the organization. Change efforts must include plans for identifying leaders throughout the company and pushing responsibility for design and implementation down, so that change “cascades” through the organization. At each layer of the organization, the leaders who are identified and trained must be aligned to the company’s vision, equipped to execute their specific mission, and motivated to make change happen.

    A major multiline insurer with consistently flat earnings decided to change performance and behavior in preparation for going public. The company followed this “cascading leadership” methodology, training and supporting teams at each stage. First, 10 officers set the strategy, vision, and targets. Next, more than 60 senior executives and managers designed the core of the change initiative. Then 500 leaders from the field drove implementation. The structure remained in place throughout the change program, which doubled the company’s earnings far ahead of schedule. This approach is also a superb way for a company to identify its next generation of leadership.

    4. Make the formal case. Individuals are inherently rational and will question to what extent change is needed, whether the company is headed in the right direction, and whether they want to commit personally to making change happen. They will look to the leadership for answers. The articulation of a formal case for change and the creation of a written vision statement are invaluable opportunities to create or compel leadership-team alignment.

    Three steps should be followed in developing the case: First, confront reality and articulate a convincing need for change. Second, demonstrate faith that the company has a viable future and the leadership to get there. Finally, provide a road map to guide behavior and decision making. Leaders must then customize this message for various internal audiences, describing the pending change in terms that matter to the individuals.

    A consumer packaged-goods company experiencing years of steadily declining earnings determined that it needed to significantly restructure its operations — instituting, among other things, a 30 percent work force reduction — to remain competitive. In a series of offsite meetings, the executive team built a brutally honest business case that downsizing was the only way to keep the business viable, and drew on the company’s proud heritage to craft a compelling vision to lead the company forward. By confronting reality and helping employees understand the necessity for change, leaders were able to motivate the organization to follow the new direction in the midst of the largest downsizing in the company’s history. Instead of being shell-shocked and demoralized, those who stayed felt a renewed resolve to help the enterprise advance.


    5. Create ownership. Leaders of large change programs must overperform during the transformation and be the zealots who create a critical mass among the work force in favor of change. This requires more than mere buy-in or passive agreement that the direction of change is acceptable. It demands ownership by leaders willing to accept responsibility for making change happen in all of the areas they influence or control. Ownership is often best created by involving people in identifying problems and crafting solutions. It is reinforced by incentives and rewards. These can be tangible (for example, financial compensation) or psychological (for example, camaraderie and a sense of shared destiny).

    At a large health-care organization that was moving to a shared-services model for administrative support, the first department to create detailed designs for the new organization was human resources. Its personnel worked with advisors in cross-functional teams for more than six months. But as the designs were being finalized, top departmental executives began to resist the move to implementation. While agreeing that the work was top-notch, the executives realized they hadn’t invested enough individual time in the design process to feel the ownership required to begin implementation. On the basis of their feedback, the process was modified to include a “deep dive.” The departmental executives worked with the design teams to learn more, and get further exposure to changes that would occur. This was the turning point; the transition then happened quickly. It also created a forum for top executives to work as a team, creating a sense of alignment and unity that the group hadn’t felt before.

    6. Communicate the message. Too often, change leaders make the mistake of believing that others understand the issues, feel the need to change, and see the new direction as clearly as they do. The best change programs reinforce core messages through regular, timely advice that is both inspirational and practicable. Communications flow in from the bottom and out from the top, and are targeted to provide employees the right information at the right time and to solicit their input and feedback. Often this will require overcommunication through multiple, redundant channels.

    In the late 1990s, the commissioner of the Internal Revenue Service, Charles O. Rossotti, had a vision: The IRS could treat taxpayers as customers and turn a feared bureaucracy into a world-class service organization. Getting more than 100,000 employees to think and act differently required more than just systems redesign and process change. IRS leadership designed and executed an ambitious communications program including daily voice mails from the commissioner and his top staff, training sessions, videotapes, newsletters, and town hall meetings that continued through the transformation. Timely, constant, practical communication was at the heart of the program, which brought the IRS’s customer ratings from the lowest in various surveys to its current ranking above the likes of McDonald’s and most airlines.

    7. Assess the cultural landscape. Successful change programs pick up speed and intensity as they cascade down, making it critically important that leaders understand and account for culture and behaviors at each level of the organization. Companies often make the mistake of assessing culture either too late or not at all. Thorough cultural diagnostics can assess organizational readiness to change, bring major problems to the surface, identify conflicts, and define factors that can recognize and influence sources of leadership and resistance. These diagnostics identify the core values, beliefs, behaviors, and perceptions that must be taken into account for successful change to occur. They serve as the common baseline for designing essential change elements, such as the new corporate vision, and building the infrastructure and programs needed to drive change.

    8. Address culture explicitly. Once the culture is understood, it should be addressed as thoroughly as any other area in a change program. Leaders should be explicit about the culture and underlying behaviors that will best support the new way of doing business, and find opportunities to model and reward those behaviors. This requires developing a baseline, defining an explicit end-state or desired culture, and devising detailed plans to make the transition.

    Company culture is an amalgam of shared history, explicit values and beliefs, and common attitudes and behaviors. Change programs can involve creating a culture (in new companies or those built through multiple acquisitions), combining cultures (in mergers or acquisitions of large companies), or reinforcing cultures (in, say, long-established consumer goods or manufacturing companies). Understanding that all companies have a cultural center — the locus of thought, activity, influence, or personal identification — is often an effective way to jump-start culture change.

    A consumer goods company with a suite of premium brands determined that business realities demanded a greater focus on profitability and bottom-line accountability. In addition to redesigning metrics and incentives, it developed a plan to systematically change the company’s culture, beginning with marketing, the company’s historical center. It brought the marketing staff into the process early to create enthusiasts for the new philosophy who adapted marketing campaigns, spending plans, and incentive programs to be more accountable. Seeing these culture leaders grab onto the new program, the rest of the company quickly fell in line.

    9. Prepare for the unexpected. No change program goes completely according to plan. People react in unexpected ways; areas of anticipated resistance fall away; and the external environment shifts. Effectively managing change requires continual reassessment of its impact and the organization’s willingness and ability to adopt the next wave of transformation. Fed by real data from the field and supported by information and solid decision-making processes, change leaders can then make the adjustments necessary to maintain momentum and drive results.

    A leading U.S. health-care company was facing competitive and financial pressures from its inability to react to changes in the marketplace. A diagnosis revealed shortcomings in its organizational structure and governance, and the company decided to implement a new operating model. In the midst of detailed design, a new CEO and leadership team took over. The new team was initially skeptical, but was ultimately convinced that a solid case for change, grounded in facts and supported by the organization at large, existed. Some adjustments were made to the speed and sequence of implementation, but the fundamentals of the new operating model remained unchanged.

    10. Speak to the individual. Change is both an institutional journey and a very personal one. People spend many hours each week at work; many think of their colleagues as a second family. Individuals (or teams of individuals) need to know how their work will change, what is expected of them during and after the change program, how they will be measured, and what success or failure will mean for them and those around them. Team leaders should be as honest and explicit as possible. People will react to what they see and hear around them, and need to be involved in the change process. Highly visible rewards, such as promotion, recognition, and bonuses, should be provided as dramatic reinforcement for embracing change. Sanction or removal of people standing in the way of change will reinforce the institution’s commitment.

    Most leaders contemplating change know that people matter. It is all too tempting, however, to dwell on the plans and processes, which don’t talk back and don’t respond emotionally, rather than face up to the more difficult and more critical human issues. But mastering the “soft” side of change management needn’t be a mystery.