Showing posts with label Change Management. Show all posts
Showing posts with label Change Management. Show all posts

Saturday, May 19, 2012

Driving Change. Fifteen Years. Five Points.


I’m often asked if Meridian has an official Change Management methodology.  The short answer is No.

I fear methodologies force-fit the same activities on every situation.  That does not work. 

Instead we’ve distilled a set of principles that accelerate the adoption of new methods, processes, and technologies.

1.  People Follow The Path of Least Resistance—So Your Desired Goal Had Better Be On It

People naturally seek the Path of Least Resistance--the pathway that provides the least resistance to forward motion.  A person taking the path of least resistance seeks to minimize personal effort and/or confrontation.

It’s imperative to credibly demonstrate how proposed change(s)  are on the Path of Least Resistance—that is, how a new technology is easier to use or offers more “reward” than current approaches (“reward” in this context has many definitions, not just money). 

Painting the picture that a “new and improved” process or technology is easier to use is a bit of an art.  You can’t just say “this is better, trust me”—people must come to the conclusion themselves.  Hands-on exposure to the new methods or technology is necessary.  Success stories that explain how the new method is easier and better help.  Credible supporters who point out how the new approach is on the right path are a requirement (see my next point). 

Despite your efforts a better approach can struggle to gain traction.  In this case it’s proven effective to directly ask “Why won’t you adopt our new approach?  Why isn’t it better than our current methods?  What will it take to get you to switch?”  It takes some courage to ask these questions—you might find that your next great idea is miles off the Path of Least Resistance—but it’s better to know.

2.       Tap The Power of PEERS

I am very interested in the science of Diffusion—understanding how innovations spread through a population.  A core beliefs in Diffusion science is The Principle of Homophily (Homophily = "Love of the Same").  Homophily is the tendency of individuals to associate and bond with people who are most like them.  Homophily plays a powerful role in the adoption of new practices because we learn best from someone who is like us.

Homophily means it’s imperative to find your experts amongst the population you are trying to change.  It’s important to ensure any and all contractors who are engaged to help you change are most like your own people.  It’s better to actually grow your own Change Leaders, selecting and supporting a sub-group of your people who score high on familiarity to lead your change.

3. There’s PRIORITY & POWER, And They Aren’t Owned By The Same People

Adoption happens when it is clear that acceptance of the new is a real organizational priority and equally that the person who has immediate power over me allows or encourages adoption.  Senior executives foster adoption by lending their personal credibility to programs, deciding which programs control the best resources, and determining the professional gains accruing to contributors.  But “executive priority” alone will not ensure adoption.

It’s rarely acknowledged but true:  Individual contributors who have been asked to change how they work need the permission of their immediate supervisor to make this change.  This ‘permission’ is subtle—I’m not going to ask, “Gee, can I use this new accounting system?” but it will be abundantly clear to me whether use of the new system is what the person who holds power over me wants or does not want.  Mid-management and supervisors thus wield considerable power during times of change.  Every successful change program must understand and manage mid-level support for the program.  

4.       Never Underestimate The Problems of the PAST

Expectations for current success are always based on perceptions of past efforts and outcomes—even if those past efforts and experiences are not directly applicable.

Think of your company’s history: How many projects were regarded as disasters?  How often do people mention these disasters when a new project is introduced?

In our work supporting clients striving for business change skepticism about past efforts has material impact on support at least 80% of the time.

A major study we completed contrasting a sample of successful and unsuccessful corporate initiatives showed that perceptions of past support for projects was the second most important determinant of program success (expectations for rewards was the most important determinant).

Common sense strongly suggests a history of past failures colors future plans, leading people to wonder, “So what’s different this time?”

And that’s precisely the point.  You must understand how people view past projects.  And you must credibly explain what’s different this time. 

Many organizations want to bury the past.  They regard it as ill-mannered to mention past failures.  They fear mentions of past projects will somehow compromise people’s support, as if organizations lack collective memory.

Not advised.  It’s important to allow people to express skepticism about past projects, within bounds.  It’s imperative to credibly and consistently show people how this effort is different, and especially how this program’s results will differ.

5.       Sustain “Offensive” Support

Support equals the people and processes that move people from current practices to better processes.

Support usually happens after a problem occurs, rendering the support reactive or defensive.

Effective support should be “Offensive,” committed and to nipping problems early, often, and before they escalate.

“Offensive” support means telling people what is changing and why, addressing “what this means to me,” allowing errors during adoption, and providing mechanisms for eliminating errors over time.  Support should start early in the program and should sustain well past the formal “completion” or Go Live point.

Some examples of Offensive support include group and individual Information Sessions, Self-Guided Change Discussions, and increasingly online communities and forums.  Change Agents are critical—successful programs always deploy networks of people who are trained and tasked with providing hands-on, grass-root level support and leadership during times of change.

In Summary

Years of work supporting diverse change programs revealed the Five Principles we use to accelerate adoption of new technologies and methods. 

So I encourage you to consider all five when plotting your next organizational initiative.

But remember: While the principles are universal, the actions derived from them are always situational.  One size never fits all.

Thursday, March 1, 2012

Meridian's Services Map: It's What We Do!



There are three trends or “demand drivers” in our Services Map. Meridian is configured to support these trends.

  • Technology: Clients continue to implement Commercial Off-The-Shelf Software (COTS), principally Enterprise Resource Planning (ERP) suites; to develop and implement Custom Software, typically using Agile, Traditional Waterfall, or some blended development approach; and are increasingly considering the cloud—Software as a Service (SaaS) offerings.

  • Process:  Clients will forever need to improve process performance, most often by adopting some elements of the LEAN Process Improvement approach.

  • People:  Clients pursue diverse programmatic change to improve organizational performance and efficiency, including mergers & acquisitions, organizational re-alignments, the creation of shared services centers, and the deployment of new sales, delivery, and support models.

Meridian offers five services that support Technology, Process, and People programs.

Strategic Tech Advisory: Meridian helps organizations create their Strategic Technology Roadmap comprising enterprise, cloud, mobile, and social technologies.  We facilitate your efforts to define business requirements and to choose technology partners.  We offer over twenty years experience planning technology and process improvement programs.

Service Systems: Meridian has the experience and methods to help you measurably improve Services Productivity, especially in CIO, CFO, and HR organizations.  We have an especially powerful approach to understanding services expectations and requirements.  We also offer extensive experience developing Shared Services Centers.

Program Management: Meridian provides experienced Program Managers who can drive your workplan, team, and partners to the success you seek.

Change Management: Meridian offers two decades Change Management experience.  We accelerate your adoption of new technologies, leading the important tasks of streamlining and standardizing business processes and teaching and supporting people’s day-to-day use of your new processes and technologies.

Delivery Assurance:  We've been engaged by clients and vendors to evaluate and turn-around at-risk programs.  Meridian provides expert, experienced analysis of program shortcomings and risks.  We re-plan and re-purpose your program so that it is back on track.  

Our expert resources can be engaged through consulting teams or through individual contract services.

Wednesday, May 18, 2011

Why Choose Meridian?

My previous post, “Meridian’s Services Map, It’s What We Do!” neatly summarized the services Meridian offers to support clients' COTS, Custom, and SaaS initiatives.

With the “What We Do” covered I’d like to address the next fundamental question.

Why Choose Meridian? 

What do we bring to the table that’s unique and valued by partners, prospects, and clients?


To answer I asked a number of partners and clients what they valued about Meridian.  I believe they accurately captured the value we strive to deliver.

Objective
“You guys do the right things for the right reasons,” one client claimed.

Honest
“We really believe the only agenda you had was our agenda,” a partner offered.

Expert
“You understand the services you offer—the fact that you’ve been in business for over 15 years clearly shows,” one Program Manager stated.

Enabling
“Meridian was willing to work with us, to teach us what you know and to ultimately leave when you’ve fulfilled your mandate,” an organizational change lead said.

Meridian's Technology Evolution Map
Click to Enlarge
Meridian’s mission is to master the selection, deployment, and use of technologies to better your business.

We crafted this mission at the very dawn of the COTS/ERP era. 

We’ll pursue our mission in this “New Century,” helping clients and partners navigate their new, very exciting business opportunities.

Saturday, June 5, 2010

Building Real Support For Your Program


Picking up from my previous post, how can you ensure your programs are effectively supported by your leaders and your organization?

I noted earlier that people ask three questions when faced with change in their organizations and work-lives:

  • Is this program credible (will it really happen)?

  • What does this program mean to us?

  • What does this program mean to me!


Examination of a sample of projects Meridian has supported sharply illuminates the key perceptions that differentiate programs that enjoy broad, effective support from programs people oppose.

Strongly Supported Programs
39% of our sample

  • These initiatives are credible—people largely believe their organization is capable of pulling off the program.

  • People are informed—communications are informative and believable.

  • There are concerns about what the program means for “me personally” but the concerns are manageable.  For example personal concerns dogging one ultimately-successful program included the addressable perception “I think my workload will increase significantly as a result of this program.”



Moderately Supported Programs
40% of our sample
  • There are usually holes in program credibility, typically related to past attempts with similar initiatives or questions about the true quality of executive support for the program.

  • Persistent information gaps—people say they do not know what they need to know about this program—are common to virtually all weakly supported programs.

  • There is also very little information about expected program impacts; naturally, given today’s work environment, these impacts are largely assumed to be a net negative to individuals.



Resisted Program
21% of our sample
  • Resisted programs (“Heck no, we won’t go”) are not credible, suffering fundamental questions about program purpose (“Why are we doing this”).

  • Resisted programs are also persistently undermined by deep personal mistrust of what the program means to individuals, usually laced with fear of loss of prestige, power, or jobs.



Take Action!

Taking a step back I’d say the keys to ensuring your programs are really supported include:

  • Credibility is the first gate: you simply must make people believe you can and will complete what you have started, even if this has not been true in the past.

  • The importance of information cannot be over-emphasized—the actionable difference between a moderately and strongly supported program is what people know and believe about your program.

  • Never underestimate how quickly concerns become personal—always keep in mind people naturally need to know “what this means for me” before they consider landing in your corner.



A note about the sample underpinning this post

Measures of support (strongly/moderately supported, resisted programs) are backed by hard data provided by Meridian’s Readiness Quotient.  The sample supporting this post includes over 360 Readiness Quotient sessions with clients undertaking large-scale change programs including acquisitions, technology implementations, shared-services implementation, and other significant organizational consolidations.  Our sample includes direct input for over 23,000 individuals worldwide.