Skip to Main Content

insightsarticles

MESC 2022: Reflections from 30,000 feet

08.24.22

Read this if you are a Medicaid agency or attended MESC 2022.

As I depart Charlotte and fly home and MESC 2022 closes out, I understand why Charlotte is referenced as the Queen City. The people make it so, as we were welcomed with open arms in this beautiful place. Our appreciation and gratitude go out not only to Charlotte, but also to NESCSO for providing us with a place to meet, share ideas, get inspired, and deepen our relationships.

In the coming months, our team can sift through what we learned during our four days at MESC. It will be up to us to transform the ideas spawned from presentations and conversations into tangible action, and grow the new relationships we developed. Here are my key takeaways and themes from the conference that I will continue to ponder:

  • The conference is in full swing on the other side of the pandemic. MESC was sold out, as 1,700 people attended.
    • MESC established a new annual award for collaboration. This year the award went to the Public Sector Technology Group's (PSTG) Medicaid Information Technology Architecture (MITA) workgroup. CMS is optimistic that the MITA workgroup's efforts will help improve Medicaid and that the resulting toolkit will be the future of MITA. Thank you to this group, and congratulations on a well-deserved award!
  • Modernization efforts:
    • The reality of managing modernization efforts is settling in. States and territories are beginning to get clear on their approach, acknowledging that each has unique needs, and consequently, can customize their approach. It will be a long haul requiring good upfront strategizing, planning and execution.
    • Many states and territories recognize a need to examine and adjust their internal structures to manage multiple procurements and strategies.
    • Data and data governance is foundational to the modularization and modernization effort.
  • Unwinding is weighing on everyone's mind, but participants discussed other forward-looking topics. 
  • CMS continues to solicit input from states, territories, and vendors
    • This was CMS' first in-person conference since the pandemic's start—it was so great to have their energy and participation.
    • It was fantastic to be in sessions where CMS asked: How can they do better? 
    • Efforts on outcomes, streamlining certification, consistency, and accountability continue to be CMS themes
    • Brent Weaver, CMS' new Data and Systems Group Director, outlined four of CMS' goals at MESC:
      • Strengthen state and territory partnerships
      • Get input from vendors on unwinding
      • Identify ways to improve data quality
      • Find ways that will help CMS become better partners
  • Ensuring health equity and leveraging social determinants for health is a priority for states and territories.
  • New solution vendors are coming into the Medicaid space, and want to learn about Medicaid and the broader enterprise as they look for ways to adapt their systems.  
  • There continues to be mergers and re-shuffling of the more established vendors as they look to adapt to and serve the needs in the Medicaid space.
    • This was BerryDunn's 17th conference. We have broadened our services and maintained our values. I'm grateful that BerryDunn continues to have a stable presence at the conference.  
  • Our Medicaid Practice Group mission statement (see below) aligns with the CMS Data and Systems Group Director's reason for being in his role. 

Additional thoughts: Asking "why," change, and education

I also appreciated conversations within our Medicaid community based on the “why": Why are we doing what we do? Why focus on modernization? Health equity? Social determinants of health? 
The "why" drives what we do by providing us with our North Star, helping us with strategy, and giving us our roadmaps for proceeding. By starting with the purpose and outcome we strive for, we can align the changes we need to make.  

Change can be a source of fear, and there is a risk of venturing into the unknown. Medicaid leaders understand that the work they are responsible for is critical to their members, providers, and taxpayers. Lives depend upon our work, and the potential of "change" can have positive or negative consequences. Effective planning can mitigate the risks and help alleviate staff, member, and provider fears about change. 

Education also plays a big part in the mitigation equation. After tying the purpose to the vision, roadmap, and phased plans to modernize our programs, there needs to be an education plan to bring everyone up to speed and build confidence in those who will be impacted.

Conclusion

I am grateful that the BerryDunn Medicaid Practice Group's mission complements the goals of CMS and the direction in which states and territories are moving. We are honored to participate in this vital work and join all in the Medicaid community as we work on the initiatives before us. I leave you with our mission statement and invite you to share your organization's mission with us.

BerryDunn's Medicaid Practice Group helps Medicaid agencies improve the health and lives of individuals by empowering, inspiring, and partnering with our clients—we innovate, share deep expertise, and provide an independent perspective to resolve challenges. We are the success partner for Medicaid agencies, building healthier communities and stronger futures.

I look forward to seeing you all again next time in Denver! Let's make it a great year!

Topics: Medicaid, CMS, MESC

Related Industries

Related Professionals

Principals

BerryDunn experts and consultants

Do we now have the puzzle pieces to build the future?

As I head home from a fabulous week at the 2018 Medicaid Enterprise Systems Conference (MESC), I am reflecting on my biggest takeaways. Do we have the information we need to effectively move into the next 12 months of work in the Medicaid space? My initial reaction is YES!

The content of the sessions, the opportunities to interact with states, vendors, and the Centers for Medicare and Medicaid Systems (CMS) representatives were all rich and rewarding.

The underlying message from Julie Boughn, the CMS Director Data and Systems Group? This is “The Year of Data Quality” and the focus will be migrating to outcomes-based projects. CMS indicated they would like their regional representatives and state agencies to be aware of their top three priorities, focus on those, and be able to exhibit measurable progress in the next year.

Here are three ways states can focus their efforts in "The Year of Quality":

  1. Fix identified areas that have issues (every state has T-MSIS areas they can correct)
  2. Maintain data quality over time, especially through system enhancements
  3. Be aware of CMS plans to use and share T-MSIS data

CMS’ overall goals and vision for improvement include:

  • Creating faster delivery of well-functioning capabilities
  • Improving user experience for all users: produce timely, accurate, and complete data
  • Better monitoring and reporting on business process outcomes

I interpret Julie Boughn’s message and direction to be: keep our efforts realistic, focus on tangible results/outcomes, and realize that CMS is approachable.

While we work on outcomes, there may be some additional changes coming to the certification approach—even beyond the most recent updates from CMS. I think there is general understanding that the work we do in the Medicaid space is iterative, and we will always be improving and changing to adapt to the shifting environment and needs of our beneficiaries, stakeholders, and administration.

As I commuted on Portland’s MAX rail line between my hotel, the conference venue, and other events, I remembered Portland’s 2010 conference (then known as the MMIS Conference) and how the topics covered then and now are evidence of just how much we have evolved.

First, we were the MMIS Conference—now there is a much broader view of the Medicaid arena and our attention is on the Medicaid Enterprise—which includes the MMIS.

Second, in 2010 the nation was coming out of the Great Recession and there was a significant amount of energy spent on implementing initiatives on the American Recovery and Reinvestment Act (ARRA). With it came a host of initiatives: meaningful use, as it related to incentives for providers to utilize electronic health records, states were subsequently updating their Medicaid IT and information exchange plans, and ICD-10 implementation readiness was a hot topic.

Fast forward to 2018, where session topics included modularity, re-use, health outcomes, coordinated care, data quality measures, programs to improve and enhance care, the opioid epidemic, long-term care, care delivery systems, payment, and certification measures. The general focus has migrated to include areas far beyond technology and the MMIS.

As we move into the next 12 months of work in the Medicaid space and look forward to gathering in Chicago for the 2019 MESC, the answer is YES, we have a clear direction and vision for moving forward. And we know things will continue to change in coming years. Are you ready to reassemble the pieces to fit and build the evolving picture of Medicaid?

Article
MESC 2018 reflections–Portland, Oregon

The MESC “B’more for healthcare innovation” is now behind us. This annual Medicaid conference is a great marker of time, and we remember each by location: St. Louis, Des Moines, Denver, Charleston… and now, Baltimore. The conference is not only a way to take stock of where the Medicaid industry stands. It is a time to connect with the state and vendor community, explore challenges and best-practice solutions, and drive innovation with our respective projects.

Having an opportunity to reflect on MESC over the last several years, I’ve discovered that taking stock of how much has changed (or not) is a valuable exercise. 

Changes at CMS

At the federal level, there is the departure of a long time contributor — Jessica Kahn — who is no longer with CMS. Her contributions and absence were marked in both the opening and closing plenary. We are grateful for her dedication and many contributions to the Medicaid space. In this time of change, we look forward to continuing our work with CMS leadership CMS to advance the mission of Medicaid.

Innovation and Collaboration

Many of the sessions this year were updates on modularity, system integration, and certification, and sessions on expanding or maturing innovative approaches to achieving our triple aim. While there did not seem to be any earth-shattering changes, calls for innovation and collaboration continue. This can be difficult to achieve during a time of anticipated change, but necessary, as states strive to realize improvements in their systems and operations.

Data-Driven Decisions

One of the dominating conference themes was a reiteration of the need to access data from broad sources within and outside Medicaid, and to leverage that data for policy and operation-related solutions and decision-making. Key words like “interoperability” and “sustainability” could be heard echoing through the halls. There is no one-size-fits-all solution on how to break out of stove pipes of data, but some new technologies may be viable tools to meet the challenge. 

Strategic Planning for the Future

States remain focused on refining and following their strategic plans and roadmaps in a time of uncertainty — with regard to potential changes coming from the federal level. The closing plenary suggested that states be prepared for “local leadership” opportunities, which further underscores the need for states to continue to prepare themselves and their systems to facilitate changes to their programs.

Maintaining Perspective

As I leave Baltimore to return home and help care for my 88-year-old father, and as I see others who are in clear need of healthcare help, I am reminded that the work we do and the problems we are tackling are important on so many levels. It is a cornerstone of the well-being of our health system and our fellow citizens. Our team will continue to focus our efforts with this perspective in mind, drawing from the lessons, discussions, and best practices shared at this year’s MESC.

Here’s to a year of good health — may you successfully carry out the mission of Medicaid in your state. See you in 2018 in Portland, Oregon!

Article
Reflections on MESC 2017

As your organization works to modernize and improve your Medicaid Enterprise System (MES), are you using independent verification and validation (IV&V) to your advantage? Does your relationship with your IV&V provider help you identify high-risk project areas early, or provide you with an objective view of the progress and quality of your MES modernization initiative? Maybe your experience hasn’t shown you the benefits of IV&V. 

If so, as CMS focuses on quality outcomes, there may be opportunities for you to leverage IV&V in a way that can help advance your MES to increase the likelihood of desired outcomes for your clients. 

According to 45 Code of Federal Regulations (CFR) § 95.626, IV&V may be required for Advanced Planning Document (APD) projects that meet specific criteria. That said, what is the intended role and benefit of IV&V? 

To begin, let’s look at the meaning of “verification” and “validation.” The Institute of Electrical and Electronics Engineers, Inc. (IEEE) Standard for Software Verification and Validation (1012-1998) defines verification as, “confirmation of objective evidence that the particular requirements for a specific intended use are fulfilled.” Validation is “confirmation of objective evidence that specified requirements have been fulfilled.” 

Simply put, verification and validation ensure the right product is built, and the product is built right. 
As an independent third party, IV&V should not be influenced by any vendor or software application. This objectivity means IV&V’s perspective is focused on benefiting your organization. This support includes: 

  • Project management processes and best practices support to help increase probability of project success
  • Collaboration with you, your vendors, and stakeholders to help foster a positive and efficient environment for team members to interact 
  • Early identification of high-risk project areas to minimize impact to schedule, cost, quality, and scope 
  • Objective examination of project health in order for project sponsors, including the federal government, to address project issues
  • Impartial analysis of project health that allows state management to make informed decisions 
  • Unbiased visibility into the progress and quality of the project effort to increase customer satisfaction and reduce the risk and cost of rework
  • Reduction of errors in delivered products to help increase productivity of staff, resulting in a more efficient MES 

Based on our experience, when a trusted relationship exists between state governments and IV&V, an open, collaborative dialogue of project challenges—in a non-threatening manner—allows for early resolution of risks. This leads to improved quality of MES outcomes.    

Is your IV&V provider helping you advance the quality of your MES? Contact our team.

Article
Leveraging IV&V to achieve quality outcomes

Editor’s note: If you are a state government CFO, CIO, project or program manager, this blog is for you.

What is the difference in how government organizations procure agile vs. non-agile information technology (IT) services? (Learn more about agile here).

In each case, they typically follow five stages through the process as shown in Figure A:
 

Figure A: Overview of Procurement Process for Agile vs. Non-Agile IT Services

However, there are differences in how these stages are carried out if procuring agile vs. non-agile IT services. 

Unfortunately, most government organizations are unaware of these differences, which could result in unsuccessful procurements and ultimately not meeting your project’s needs and expectations. 
This blog series will illustrate how to strategically adjust the standard stages outlined in Figure A to successfully procure agile IT services.

Stage 1: Plan project
In Stage 1, you define the scope of the project by identifying what your organization wants, needs, and can achieve within the available timeframe and budget. You then determine the project’s objectives while strategically considering their impact on your organization before developing the RFP. Figure B summarizes the key differences between the impacts of agile vs. non-agile services to consider in this stage.


Figure B: Plan Project for Agile vs. Non-Agile IT Services

The nuances of planning for agile services reflect an organization’s readiness for a culture shift to a continuous process of development and deployment of software and system updates. 

Stage 2: Draft RFP
In Stage 2, as part of RFP drafting, define the necessary enhancements and functionality needed to achieve the project objectives determined in Stage 1. You then translate these enhancements and functionalities into business requirements. Requirement types might include business needs as functionality, services, staffing, deliverables, technology, and performance standards. Figure C summarizes the key differences between drafting the RFP for a project procuring agile vs. non-agile services.


Figure C: Draft RFP for Agile vs. Non-Agile IT Services

In drafting the RFP, the scope of work emphasizes expectations for how your team and the vendor team will work together, the terms of how progress will be monitored, and the description of requirements for agile tools and methods.

Stage 3: Issue RFP
In Stage 3, issue the RFP to the vendor community, answer vendor questions, post amendments, and manage the procurement schedule. Since this stage of the process requires you to comply with your organization’s purchasing and procurement rules, Figure D illustrates very little difference between issuing an RFP for a project procuring agile or non-agile services.


Figure D: Issue RFP for Agile vs. Non-Agile IT Services 

Stage 4: Review proposals
In Stage 4, you evaluate vendor proposals against the RFP’s requirements and project objectives to determine the best proposal response. Figure E summarizes the key differences in reviewing proposals for a project that is procuring agile vs. non-agile services.


Figure E: Reviewing Proposals for Agile vs. Non-Agile IT Services 

Having appropriate evaluation priorities and scoring weights that align with how agile services are delivered should not be under-emphasized. 

Stage 5: Award and implement contract
In Stage 5, you award and implement the contract with the best vendor proposal identified during Stage 4. Figure F summarizes the key differences in awarding and implementing the contract for agile vs. non-agile services.


Figure F:  Award and Implement Contract for Agile vs. Non-Agile Services 

Due to the iterative and interactive requirements of agile, it is necessary to have robust and frequent collaboration among program teams, executives, sponsors, and the vendor to succeed in your agile project delivery.

What’s next?
The blog posts in this series will explain step-by-step how to procure agile services through the five stages, and at the series conclusion, your organization will better understand how to successfully procure and implement agile services. If you have questions or comments, please contact our team.  

Article
Procuring agile vs. non-agile projects in five stages: An overview

Law enforcement, courts, prosecutors, and corrections personnel provide many complex, seemingly limitless services. Seemingly is the key word here, for in reality these personnel provide a set number of incredibly important services.

Therefore, it should surprise no one that justice and public safety (J&PS) IT departments should also provide a well-defined set of services. However, these departments are often viewed as parking lots for all technical problems. The disconnect between IT and other J&PS business units often stems from differences in organizational culture and structure, and differing department objectives and goals. As a result, J&PS organizations often experience misperception between business units and IT. The solution to this disconnect and misperception? Defining IT department services.

The benefits of defined IT services

  1. Increased business customer satisfaction. Once IT services align with customer needs, and expectations are established (e.g., service costs and service level agreements), customers can expect to receive the services they agreed to, and the IT department can align staff and skill levels to successfully meet those needs.
  2. Improved IT personnel morale. With clear definition of the services they provide to their customers, including clearly defined processes for customers to request those services, IT personnel will no longer be subject to “rogue” questions or requests, and customers won’t be inclined to circumvent the process. This decreases IT staff stress and enables them to focus on their roles in providing the defined services. 
  3. Better alignment of IT services to organizational needs. Through collaboration between the business and IT organizations, the business is able to clearly articulate the IT services that are, and aren’t, required. IT can help define realistic service levels and associated services costs, and can align IT staff and skills to the agreed-upon services. This results in increased IT effectiveness and reduced confusion regarding what services the business can expect from IT.
  4. More collaboration between IT and the organization. The collaboration between the IT and business units in defining services results in an enhanced relationship between these organizations, increasing trust and clarifying expectations. This collaborative model continues as the services required by the business evolve, and IT evolves to support them.
  5. Reduced costs. J&PS organizations that fail to strategically align IT and business strategy face increasing financial costs, as the organization is unable to invest IT dollars wisely. When a business doesn’t see IT as an enabler of business strategy, IT is no longer the provider of choice—and ultimately risks IT services being outsourced to a third-party vendor.

Next steps
Once a J&PS IT department defines its services to support business needs, it then can align the IT staffing model (i.e., numbers of staff, skill sets, roles and responsibilities), and continue to collaborate with the business to identify evolving services, as well as remove services that are no longer relevant. Contact us for help with this next step and other IT strategies and tactics for justice and public safety organizations.

Article
The definition of success: J&PS IT departments must define services

If you’ve been tasked with leading a high-impact project for your organization, you may find managing the scope, budget and schedule is not enough to ensure project success—especially when you encounter resistance to change. When embarking on large-scale change projects spanning people, processes and technology, appointing staff as “coaches” to help support stakeholders through the change—and to manage resistance to the change—can help increase adoption and buy-in for a new way of doing things.

The first step is to identify candidates for the coaching role. These candidates are often supervisory staff who have credibility in the organization—whether as a subject matter expert, through internal leadership, or from having a history of client satisfaction. Next, you need a work plan to orient them to this role. One critical component is making sure the coaches themselves understand what the change means for their role, and have fully committed before asking them to coach others. They may exhibit initial resistance to the change you will need to manage before they can be effective coaches. According to research done by Prosci®, a leading change management research organization, some of the most common reasons for supervisor resistance in large-scale change projects are:

  • Lack of awareness about and involvement in the change
  • Loss of control or negative impact on job role
  • Increased work load (i.e., lack of time)
  • Culture of change resistance and past failures
  • Impact to their team

You should anticipate encountering these and other types of resistance from staff while preparing them to be coaches. Once coaches buy into the change, they will need ongoing support and guidance to fulfill their role. This support will vary by individual, but may be correlated to what managerial skills they already possess, or don’t. How can you focus on developing coaching skills among your staff for purposes of the project? Prosci® recommends a successful change coach take on the following roles:

  • Communicator—communicate with direct reports about the change
  • Liaison—engage and liaise with the project team
  • Advocate—advocate and champion the change
  • Resistance manager—identify and manage resistance
  • Coach—coach employees through the change

One of the initial tasks for your coaches will be to assess the existing level of change resistance and evaluate what resistance you may encounter. Prosci® identifies three types of resistance management work for your coaches to begin engaging in as they meet with their employees about the change:

  • Resistance prevention―by providing engagement opportunities for stakeholders throughout the project, building awareness about the change early on, and reinforcing executive-level support, coaches can often head off expected resistance.
  • Proactive resistance management―this approach requires coaches to anticipate the needs and understand the characteristics of their staff, and assess how they might react to change in light of these attributes. Coaches can then plan for likely forms of resistance in advance, with a structured mitigation approach.
  • Reactive resistance management―this focuses on resistance that has not been mitigated with the previous two types of resistance management, but instead persists or endures for an extended amount of time. This type of management may require more analysis and planning, particularly as the project nears its completion date.

Do you have candidates in your organization who may need support transitioning into coaching roles? Do you anticipate change resistance among your stakeholders? Contact us and we can help you develop a plan to address your specific challenges.

Article
How to identify and prepare change management coaches

Truly effective preventive health interventions require starting early, as evidenced by the large body of research and the growing federal focus on the role of Medicaid in addressing Social Determinants of Health (SDoH) and Adverse Childhood Experiences (ACEs).

Focusing on early identification of SDoH and ACEs, CMS recently announced its Integrated Care for Kids (InCK) model and will release the related Notice of Funding Opportunity this fall.

CMS describes InCK as a child-centered approach that uses community-based service delivery and alternative payment models (APMs) to improve and expand early identification, prevention, and treatment of priority health concerns, including behavioral health issues. The model’s goals are to improve child health, reduce avoidable inpatient stays and out-of-home placement, and create sustainable APMs. Such APMs would align payment with care quality and support provider/payer accountability for improved child health outcomes by using care coordination, case management, and mobile crisis response and stabilization services.

State Medicaid agencies have many things to consider when evaluating this funding opportunity. Building on current efforts and innovations, building or leveraging strong partnerships with community organizations, incentivizing evidence-based interventions, and creating risk stratification of the target population are critical parts of the InCK model. Here are three additional areas to consider:

1. Data. States will need information for early identification of children in the target population. State agencies?like housing, justice, child welfare, education, and public health have this information?and external organizations—such as childcare, faith-based, and recreation groups—are also good sources of early identification. It is immensely complicated to access data from these disparate sources. State Medicaid agencies will be required to support local implementation by providing population-level data for the targeted geographic service area.

  • Data collection challenges include a lack of standardized measures for SDoH and ACEs, common data field definitions, or consistent approaches to data classification; security and privacy of protected health information; and IT development costs.
  • Data-sharing agreements with internal and external sources will be critical for state Medicaid agencies to develop, while remaining mindful of protected health information regulations.
  • Once data-sharing agreements are in place, these disparate data sources, with differing file structures and nomenclature, will require integration. The integrated data must then be able to identify and risk-stratify the target population.

For any evaluative approach or any APM to be effective, clear quality and outcome measures must be developed and adopted across all relevant partner organizations.

2. Eligibility. Reliable, integrated eligibility and enrollment systems are crucial points of identification and make it easier to connect to needed services.

  • Applicants for one-benefit programs should be screened for eligibility for all programs they may need to achieve positive health outcomes.
  • Any agency at which potential beneficiaries appear should also have enrollment capability, so it is easier to access services.

3. Payment models. State Medicaid agencies may cover case management services and/or targeted case management as well as health homes; leverage Early and Periodic Screening, Diagnostic, and Treatment (EPSDT) services; and modify managed care organization contract language to encourage, incent, and in some cases, require services related to the InCK model and SDoH. Value-based payment models, already under exploration in numerous states, include four basic approaches:

  • Pay for performance—provider payments are tied directly to specific quality or efficiency indicators, including health outcomes under the provider organization’s control. 
  • Shared savings/risk—some portion of the organization’s compensation depends on the managed care entity achieving cost savings for the targeted patient population, while realizing specific health outcomes or quality improvement.
  • Pay for success—payment is dependent upon achieving desired outcomes rather than underlying services.
  • Capitated or bundled payments—managed care entities pay an upfront per member per month lump sum payment to an organization for community care coordination activities and link that with fee-for-service reimbursement for delivering value-added services.

By focusing on upstream prevention, comprehensive service delivery, and alternative payment models, the InCK model is a promising vehicle to positively impact children’s health. Though its components require significant thought, strategy, coordination, and commitment from state Medicaid agencies and partners, there are early innovators providing helpful examples and entities with vast Section 1115 waiver development and Medicaid innovation experience available to assist.

As state Medicaid agencies develop and implement primary and secondary prevention, cost savings can be achieved while meaningful improvements are made in children’s lives.

Article
Three factors state medicaid agencies should consider when applying for InCK funding

Most of us have been (or should have been) instructed to avoid using clichés in our writing. These overstated phrases and expressions add little value, and often only increase sentence length. We should also avoid clichés in our thinking, for what we think can often influence how we act.

Consider, for example, “death by committee.” This cliché has greatly — and negatively — skewed views on the benefits of committees in managing projects. Sure, sometimes committee members have difficulty agreeing with one another, which can lead to delays and other issues. In most cases, though, an individual can’t possibly oversee all aspects of a project, or represent all interests in an organization. Committees are vital for project success — and arguably the most important project committee is the steering committee.

What Exactly is a Steering Committee?
It is a group of high-level stakeholders that provides strategic direction for a project, and supports the project manager. Ideally, the group increases the chances for project success by closely aligning project goals to organizational goals. However, it is important to point out that the group’s top priority is project success.

The committee should represent the different departments and agencies affected by the project, but remain relatively small in size, chaired by someone who is not an executive sponsor of the project (in order to avoid conflicts of interest). While the project manager should serve on the steering committee, they should not participate in decision-making; the project manager’s role is to update members on the project’s progress, areas of concern, current issues, and options for addressing these issues.

Overall, the main responsibilities of a steering committee include:

  1. Approving the Project Charter
  2. Resolving conflicts between stakeholder groups
  3. Monitoring project progress against the project management plan
  4. Fostering positive communicating about the project within the organization
  5. Addressing external threats and issues emerging outside of the project that could impact it
  6. Reviewing and approving changes made to the project resource plan, scope, schedules, cost estimates, etc.

What Are the Pros and Cons of Utilizing a Steering Committee?
A group of executive stakeholders providing strategic direction should benefit any project. Because steering committee members are organizational decision-makers, they have the access and credibility to address tough issues that can put the project at a risk, and have the best opportunities to negotiate positive outcomes. In addition, steering committees can engage executive management, and make sure the project meshes with executive management’s vision, mission, and long-range strategic plan. Steering committees can empower project managers, and ensure that all departments and agencies are on the same page in regards to project status, goals, and expectations. In a 2009 article in Project Management Journal, authors Thomas G. Lechler and Martin Cohen concluded that steering committees are important to implementing and maintaining project management standards on an operational level — not only do steering committees directly support project success, they are instrumental in deriving value from an organization's investments in its project management system.

A steering committee is only as effective as it’s allowed to be. A poorly structured steering committee that lacks formal authority, clear roles, and clear responsibilities can impede the success of a project by being slow to respond to project issues. A proactive project manager can help the organization avoid this major pitfall by helping develop project documents, such as the governance document or project plan that clearly define the steering committee structure, roles, responsibilities and authority.

Steer Toward Success!
Steering committees can benefit your organization and its major projects. Yet understanding the roles and responsibilities — and pros and cons — is only a preliminary step in creating a steering committee. Need some advice on how to organize a steering committee? Want to learn more about steering committee best practices? Together, we can steer your project toward success.

Article
Success by steering committee