Leadership Blog Series: Every Improvement Involves Change

Written by Sharri Margraves, HR Associate Director for Organization and Professional Development

Change itself isn’t an improvement…but every improvement involves change.

We are experiencing unprecedented (there’s that word again) change on many levels and across many systems, under-resourced in many areas while managing through tremendous pressure for both you and your teams. Learning new ways to make improvements is critical. I invite you to take a fresh perspective on leading change, starting with yourself. You need a deliberate path for leaning into change and bringing your team along with you as you lead improvement measures.

Start with Yourself

To begin, reflect on the following questions while considering your current leadership approach during this time of rapid change. How do you approach problems and lead improvements?

  • Are you treating the symptoms, or are you tackling the root cause of the issues? Imagine the feeling of having your teams think about the root cause of any problems or improvements. Connecting improvements throughout the organization to individuals can increase engagement and build more value for your stakeholders.
  • Does everyone in your organization or on your team know how to participate in improvements? Do they know what is expected of them, or do they have to wait to be told what to do? Imagine empowering and unleashing the potential from your entire team by inviting them to work on what really matters, in a way that is supported by trusting those who know the most about the issues.
  • Do you expect continuous improvement in the daily work? Envision being able to systematically improve even “small” thorny issues, recognize people, and deal with processes that are ineffective, wasteful and redundant.
  • Do you include representation of all your key stakeholders in your efforts? No one wants to feel like they are at the little kids’ table—waiting for scraps and being told what to do. Be holistic in solving problems and making improvements. Not including good representation from across the spectrum to solve issues around change means you are sowing seeds of suspicion or, even worse, sabotage.

Lean into Change

Regardless of an issue’s scope, create a path toward improvement utilizing the following steps:

  1. Define the problem. Create a team to solve the problem that includes those responsible for the activity, process or action. Develop the problem statement in one or two sentences—get to the real root cause by asking the 5 Whys until you get to the bottom of things.
  2. Define the desired state in one to two sentences. If XYZ changes, what is the intended outcome?
  3. Define who needs to be involved and how. Use a RACI chart to help you define roles: who is Responsible, Accountable, Consulted, and Informed. Consider the difference between responsible and accountable: If I am an electrician who is responsible for installing a new outlet and I get sick and can’t complete the job, my manager is accountable to find someone to complete the job.

Lead with Intention

Now you are ready to conduct kaizen, which means to take apart (“Kai”) and put back together (“Zen”). Remember, there is no “bad” information or people—the focus should be on the facts of the problem and not the person. Lead this process with intention using the steps below.

  1. Document the current process with time estimates (or other measures).
  2. Identify areas of improvement. You are likely trying to eliminate wasted time, money or energy. Everything should have a real value—or we shouldn’t be doing it.
  3. Develop new processes that can prevent or improve problems. Document them in Promapp.
  4. Implement (i.e., do the things!) Build in a loop to communicate on the implementation and the results over a period of time. Develop training tools based off your process/actions.
  5. Measure and compare to previous results to verify improvement. Remember, anything that does not add value (time, money, energy) should be eliminated, and measuring improvement is possible—even for what can sometimes feel like Byzantine university processes. This is an important transparency step to all members in the process.
  6. Standardize the new process, system or action. Use visual tools, such as dashboards or posters, to reinforce the processes.

Ongoing steps in the process: Celebrate successes whether big or small, maintain continuous monitoring as situations change, and continue to embark on improvements.

Change Management Strategist, Yvonne Ruke Akpoveta, describes change leadership as “the ability to influence and inspire action in others, and respond with vision and agility during periods of growth, disruption or uncertainty to bring about the needed change.” Approach improvements with intentionality to be an influential leader of change during our current period of transition.

Interested in learning more? Recommended SourceLive articles are listed below, and the Organization and Professional Development department can be reached at prodev@hr.msu.edu for specialized support.

Recommended Reading

Sources

Balzer, W., Francis, D., Krehbiel, T., Shea, N. A review and perspective on lean in higher education. https://www.researchgate.net/profile/William-Balzer/publication/308000035_A_review_and_perspective_on_Lean_in_higher_education/links/5ea32ac6299bf112560c188d/A-review-and-perspective-on-Lean-in-higher-education.pdf (log-in required)

Jenkins, Alison. Advancing lean leadership. https://www.mckinsey.com/business-functions/operations/our-insights/advancing-lean-leadership#

Neumeyer, Adrian. Create a RACI chart so everyone knows their role. https://www.tacticalprojectmanager.com/raci-chart-explanation-with-example

One thought on “Leadership Blog Series: Every Improvement Involves Change

  1. This was a great article. I really liked the idea that change can be about problem solving. I want to remember how to improve with intention using the RACI chart (want to learn more on this) and Kaizen method. New ideas for me to explore. Thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *