Showing posts with label Communication Management Strategy (CMS). Show all posts
Showing posts with label Communication Management Strategy (CMS). Show all posts

Wednesday, 4 April 2018

Mobilizing a Business for Turning Strategy into Action

Six Sigma Tutorials and Materials, Six Sigm Learning, Six Sigma Certifications

Developing a strategy is critical for any organization, and equally important is having a mechanism to translate that strategy into action. However, given the complexities of the European market, there is a special need for a business implementing its strategy to allow its local business unit leaders to adjust the tactics to local needs and requirements. This needs to be done while at the same time providing for feedback on local opportunities that could impact the company’s overall direction.

In short, the challenge is to find a mechanism that engages and commits to action while allowing flexibility for local differences when justified.

Developing a business strategy is the act of aligning operations and improvements with business goals and objectives. Research and experience has illuminated three primary considerations that must be taken into account when determining how to mobilize a business for implementing its strategy.

Processes


Processes are the primary vehicles for propelling strategy into action. Though most businesses organize themselves around functions and departments (R&D, operations, finance, sales and marketing), the products and services their customers receive are produced by processes that require coordination between these functional lines. These are often called value delivery or core business processes. Like “new product development” and “order generation,” for example, these core processes strongly impact a customer’s perceptions of the business.

Businesses in the same industry tend to have basically the same core processes. But how a business performs these processes often determines its competitive advantage, or disadvantage, in the marketplace and ultimately determines its prosperity or failure.

No matter what strategies a business decides to pursue, achieving many of them requires making targeted improvements in those processes that are inherently linked to strategic goals. For every business, some aspects of its operation will be more critical to a particular strategy than another. Identifying where the process-to-strategy relationships are strongest – and what needs to be done differently within those processes – helps a business to prioritize its improvement efforts, focus on those that will have the greatest strategic impact, and translate the strategy into operational terms that everyone can understand and act upon.

Once these improvement opportunities are identified, the leaders of the business can then create detailed action plans and equip high-powered teams to recommend and implement changes in strategically critical areas. In many cases, these changes will require that new capabilities be developed (or existing ones improved) in core business processes. But they also may involve changes in non-core, or what are sometimes called “enabling” processes (such as “information management” and “talent acquisition”). These processes often provide vital services internally and support core processes in delivering value to customers.

Defining and visualizing processes is the critical first step to translating strategy into action. But it is through effective analysis and intelligent, data-based decisions that a business can understand the role which various processes play in achieving strategic goals. This then leads to an understanding of which process capabilities are necessary, where improvement and development resources can best be directed, and the appropriate tools and technologies to be applied.

Measurements


Visibility and improvement of business performance requires the development of the measurement systems and data which illustrate the linkage between process behavior and the business and customer objectives for the business. Every strategic goal should be accompanied by the quantification of that goal, and no goal should be established without its associated measures. This includes outcome measures to see how well a business is performing against its strategic goals, and also the internal process measures that provide visibility to the causal factors that either enable or disable the business from achieving its goals. When these measures are lacking, it is impossible for a business to understand the cause-and-effect relationship between the actions it takes and the goals it hopes to achieve.

Reliable data is needed to align improvements with strategy and to understand precisely the processes which the business needs to develop. This involves collecting information on how processes are currently performing and then identifying the most significant gaps between “baseline” and “targeted” performance levels. To establish these targets – and determine what levels of performance the strategy calls for – requires a comprehensive measurement system which not only takes time and effort to validate and build, but needs to be frequently updated to reflect customer, market and technological changes.

Once a business has determined the appropriate performance levels for the process areas considered key to the strategy, it is then prepared to focus on developing the process capabilities that are critical to meeting the new targets. A process capability is any performance characteristic or attribute of a process which is required if the process goal is to be consistently achieved. Identifying, evaluating and collecting data on these “required process capabilities” help a business to concentrate on making changes that will have real strategic impact and to make smart investments of its limited improvement resources.

A number of tracking tools (such as process management charts and dashboards) can be used to monitor process capabilities and measure their impact on performance over time. These measures serve as “leading” indicators or predictors of process, and hence business, performance. They enable the business to make decisions and adjustments on a much shorter horizon, assess whether and how well process performance targets will be met, and determine the extent of the gains made as a result of improvement investments.

Accountability


Agreeing on what the strategy of a business should be is the responsibility of senior management. But implementing the strategy requires a business to identify and engage the right people to make accountable for process performance and to equip them with the appropriate reporting tools and disciplines to responsibly evaluate and track the performance of processes.

To achieve its strategy, a business must create an organizational culture which fosters alignment between the strategy itself and the work performed within each department and function. This cannot be accomplished simply by communicating the strategy – no matter how well-chosen the words. A business must translate the strategy into process terms and into specific process goals and outcomes. This makes the strategic plan relevant to everyone in the business and gives each one a clear “line of sight” to the strategy. And it promotes ownership of new business goals by helping everyone understand how their work contributes to the overall objectives, and what skills, knowledge and abilities they must bring to bear to make the strategy succeed.

The three primary ways a business can promote feelings of accountability during strategy implementation are through:

1. The action of its leaders. Leaders serve as valuable role models when they make decisions based on data and processes (rather than gut feelings) and when they continually reinforce the strategic importance of process improvement.

2. Participation in developing the measures and reporting mechanisms that are needed to monitor critical process capabilities. When process owners and those who support them are required to measure, improve and monitor process outcomes on a regular basis, they tend to develop stronger feelings of accountability, as well as a greater commitment to continuous improvement. Of course, this only takes place when those with accountability for process performance are given both the skills and the authority to influence and manage those same processes.

3. Performance management. This is the most effective way to drive accountability. Individuals at all levels of the business should be evaluated based on how well they meet process performance goals. Recognition and rewards, both financial and non-financial, should be based on who contributes the most to making the strategy succeed. Generally, European businesses are organized in such a way that each business unit operating in a different country has is own P&L. This can facilitate the downward assignment of accountability for business performance. A challenge, however, is balancing the efforts to create common, global and best practice standards and disciplines for processes while still allowing country and regional versions to reflect local customer, channel and regulatory requirements.

Together with processes and measurements, accountability plays a key role in implementing business strategy. By linking individual performance to process improvements and outcomes, and by rigorously measuring outcomes against established targets, businesses will have a much higher likelihood of successfully translating strategy into action.

Thursday, 5 October 2017

Communications Management Plan - A Step by Step Guide

One of the best ways to learn is by doing. This applies not only to everyday life, but also to project communications management. This step-by-step guide is meant to be used in conjunction with our Communications Management Plan Template. By following the steps outlined below, and using our communications management plan template you'll find that developing the communications management plan for your project is quite easy and can be accomplished with little stress.

Step 1: Review the PMBOK


Read through section 10.2.3.1 of the PMBOK (Communications Management Plan). Either print this section or make a copy and keep it on your desk - this way you can refer back to it often. The PMBOK is the industry standard for project management and is extremely useful in detailing the requirements for project communication as well as other project areas. A thorough review of the applicable PMBOK section should precede work on any project management process area.

Step 2: Determine Stakeholder Communication Requirements


Refer to the Stakeholder Register and Stakeholder Management Strategy if you have them (these should have been created during the project initiation process). This step requires more than just creating a list of stakeholders. There are several key considerations to account for during this step of the communication management plan. First, you must ensure ALL stakeholders are identified. Many projects fail to do this only to discover it later which results in project gaps, document changes, etc.

Another key part of this step is determining all of the stakeholders’ expectations, interests, and influence within the project. If a stakeholder’s expectation is that this project should not result in any changes to his/her work but you know it will, then this is where discrepancies like this must be identified and resolved. Likewise, stakeholders will have varying degrees of interest and influence on a project. All of these characteristics should be captured and documented in the Communications Management Plan section “Stakeholder Communication Requirements”. Specific communication methods, preferences, and frequencies for each stakeholder should be documented in the project’s Stakeholder Register as an Appendix or attachment to the Communication Management Plan.

Stakeholders include: management, customers, PMO, project team, business partners, program manager, portfolio manager, project sponsor, etc.


Step 3: Determine Level of Detail for the Plan


The Communications Management Plan can be either a stand-alone subsidiary management plan or a section contained within the project management plan. Several determining factors will help you to determine the scope and level of detail for your Communications Management Plan.

◉ Size of Project - larger projects which span a longer timeframe tend to have more communication requirements.
◉ Complexity of Organization - for instance, a highly political environment within the organization has very specific communication needs for the project to be successful.
◉ Number and Location of Stakeholders – project’s with a high number of stakeholders and/or stakeholders from a wide geographic area may require more detailed planning of communication management.

If you have a small project and your organization isn't very complex in its communication requirements then your communications management plan can be a section within your project plan. If you go this route be sure at a minimum to include:

◉ Communications management approach
◉ Stakeholder communication requirements
◉ Stakeholder register (from project initiation)
◉ Roles and responsibilities
◉ Project team directory
◉ Communication matrix
◉ Guidelines for meetings

Most large and complex projects will require that the communications management plan be developed as a subsidiary management plan which can stand on its own. Because of the size and complexity, these communications management plans often require more detailed planning and documentation. If you require a more detailed subsidiary communications management plan, you should include the following at a minimum:

◉ Communications management approach
◉ Communication constraints
◉ Stakeholder communication requirements
◉ Roles and responsibilities
◉ Project team directory
◉ Communication matrix
◉ Communication flowchart
◉ Guidelines for meetings
◉ Standardization of communication
◉ Communication escalation process
◉ Glossary of communication terminology
◉ Sponsor acceptance of the plan as a subsidiary/stand-alone plan

The level of detail for the communications management plan can be discussed or summarized in the “Introduction” section. Information pertaining to the level of detail will also be present in the “Stakeholder Communication Requirements” section of the plan as well as the Stakeholder Register.


Step 4: Determine Communication Constraints


All projects are subject to various constraints which must be identified and managed effectively to ensure project success. The communication management plan is no exception as often times a project’s communications are subject to various constraints. These constraints may be financial (i.e. project’s budget allocated for communication), time-dependent (i.e. adhering to schedule regarding project communications), or deal with other factors. Other communication constraints may include what types of technology are available for communications, any internal or external regulations and policies, or legislation that may require communications to be handled in a certain manner.

Communication constraints should be identified during the project’s planning phase and every effort must be taken to ensure all constraints are identified and documented. If any constraints are missed then it is likely that they will become evident later in the project’s lifecycle and impact the project’s triple constraint (time, cost, and scope). All identified communication constraints should be contained in the “Communication Constraints” section of the Communication Management Plan.

Step 5: Determine Information to be Communicated


This step may seem simple and self-explanatory, but on many projects, there are either significant gaps or overlaps in information being communicated. There are many questions that need to be answered such as, “who needs the information?”; “how often do they need it?”; and “what information do they need?”. Small projects allow for more simplified communication without having to provide extreme detail in the planning. However, large and complex projects, which usually have many stakeholders with differing interests and influences, require very thorough and detailed planning.

For large and complex projects it is usually helpful for an organization to provide standard documents and templates for use in formal communications because it simplifies the communication process and provides a level playing field and promotes understanding of what is being communicated. There may be standard status reports, meeting agendas, meeting minutes, gate reviews, or other documents which provide consistent format and content. Depending on the complexity of the project and the stakeholder communication requirements the standard documents may need slight modification and a determination of the level of detail communicated must be made. However, the organizational standards should contain most of the key information that needs to be communicated for the project.

Determining the information that needs to be communicated is the result of determining stakeholder communications requirements as well as what the organization’s internal communications requirements are. This should provide what needs to be communicated, to whom, and how often. This information is then documented and presented in the “Communication Matrix” and “Standardization of Communication” sections of the Communication Management Plan.


Step 6: Determine Methodology for Communications


Now that we know what needs to be communicated, to whom, and how often, we must determine how we are going to communicate the project information. Much like the other steps in completing the communications management plan, this step largely depends on the size and complexity of the project. Small project communications with few stakeholders may only require periodic meetings, emails, and phone calls. Large and complex projects again require much more detailed planning. Different types of communications may also require different methods of communication. For instance, project status meetings may be most effective in a face-to-face environment. However, some stakeholders may be located in different geographic regions so the result may be a face-to-face meeting with a video-teleconference capability where distant stakeholders have the capability of seeing briefing charts and participating in the conversation. Communication methodology is dependent on the technology available to stakeholders as well.

There are many means for communicating project information. Some of these include email, phone calls, face to face meetings, data bases, web/internet portals, video-teleconferences, organizational shared drives, or various other technologies and applications. The project team must consider what methods are available to all stakeholders and plan appropriately so pertinent project information can be communicated to everyone involved.

Communication methodology is included in the “Communications Management Approach”, “Stakeholder Communication Requirements”, and Communication Matrix” sections of the Communications Management Plan. Additional detail may be included in the project’s Stakeholder Register.


Step 7: Develop Flow Charts for Information Flow


It should be clear by now that large and complex projects require detailed planning to avoid communication gaps and overlaps and to ensure that project information is distributed in a timely and effective manner. A common tool which helps illustrate and describe how project communications should work is the flow chart.

The communication flowchart should describe the paths of both formal and informal communications. These paths should include any necessary reviews or authorizations which must occur prior to information being distributed (i.e. sensitive or classified information). The flowchart should also include any events which may trigger or result in communications. For example, a monthly project status meeting may trigger and agenda or presentation to be distributed beforehand and meeting minutes or changes in documentation to be communicated afterward. As projects grow larger and more complex, the flowchart helps manage communication by providing a visual diagram of communication flows.

The flowchart should be included in the “Communication Flowchart” section of the Communications Management Plan.

Friday, 5 May 2017

3 Common Pitfalls to Avoid with PRINCE2

Although project success rates are growing, project managers still struggle with many common pitfalls. Here are some of the ways PRINCE2 can prepare you for them.

PRINCE2 Guide, Prince2 Tutorials

1. Unclear scope


Every good project has a clear goal. It’s easier to assign work and correct problems when you know the end goal. Along with a clear scope, it also makes it easier to define project success. Even small changes like changing the colour of a logo create delays. When these little changes go unchecked, they can ruin projects. Here are some of PRINCE2’s tools for staying on scope:
  • Project Initiation Document (PID) – As the name suggests, this document is part of the Initiation stage. A complete PID will outline the project’s objectives, scope and exclusions. With these three documented, you can not only define the scope, but also manage scope creep.
  • Change control – PRINCE2 uses the term ‘issue’ to describe unplanned events that require management intervention. You can’t stop issues from arising, but you can control how they’re handled. PRINCE2 has five steps to handling issues and keeping projects on-scope. This process is abbreviated to CEPDI:
    • Capture: Determine type of issue
    • Examine: Assess the impact of the issue on the project objectives
    • Propose: Propose actions to take
    • Decide: Someone decides to approve or reject the recommended solution
    • Implement: Put the recommended solution in action

2. Micromanagement


Micromanagement tends to be more prevalent among budding managers. However, managers at every level are susceptible to it, and the results are never good. Project teams should be able to get immersed in their work. Instead of fostering a ‘babysitting’ corporate culture, consider this:
  • Manage by exception – One of PRINCE2’s 7 core principles. It means senior managers are only alerted to major process deviations. This not only gives the project team more breathing room, but it also helps senior managers prioritise their time.
  • Communication Management Strategy (CMS) – This document on how you’ll communicate with stakeholders was brought up in the previous blog, in reference to sponsors. Since everyone in the project team is also a stakeholder, the CMS should account for them. With regular meetings, the project team and team manager won’t have to spend as much time updating you. Instead, they can raise issues without disruption.

3. Unrealistic timelines


Project managers are eager to make clients happy with a quick product delivery, but this often leads to overambitious estimates. It’s easier to form and stick to a realistic deadline with these tools:
  • Project Plan – Part of the Project Initiation Document (PID). It details the start and end points of the project’s milestones/stages, and control points for these. By breaking the stages down, it’s easier to judge the length of the project. It will be less tempting to underestimate the project length when the stages are laid out in front of you.
  • Project Assurance – This is where manage by exception and Change Control come in. After the first delivery stage, you may no longer agree with your original timeline. You can save a new version of your Project Plan with new information and estimates. Project Assurance can help devise these new estimates. Better yet, senior managers and sponsors can lend their support to get the project back on track.
If you’d like to keep projects on track, PRINCE2 has so much more to offer. For the easiest way to get qualified, we offer an accredited Foundations course with a guaranteed pass.