Skip to main content

Mindset Shift: Champion of Change

# Mindset

In the past year, our entire team embarked on a transformative journey, evolving from traditional paper-based processes to embracing the power of digital solutions and data analytics. This transition, while challenging, has been a revelation, uncovering layers of historical inaccuracies that were hidden beneath the surface of our conventional methods.

Our journey has been a testament to the strength and resilience inherent in embracing change, reminding me of a sentiment often attributed to Albert Einstein: "Great spirits have always encountered violent opposition." This quote, while stark, underscores a universal truth about the path of innovation and growth. 

It isn't about the opposition itself but about the courage and determination to move forward together, despite the hurdles. This experience has highlighted the natural human hesitation towards the unfamiliar and the remarkable courage it takes for a team to navigate through these changes. It’s through our collective efforts, understanding, and patience that we push forward, transforming challenges into opportunities for improvement and growth.

There is no human on earth who hasn’t felt the deep resistance to change in one form or another. Change is painful. Modern psychology tells us that we will usually not pursue change until the pain of change is less than the pain of staying the same. When systems blow up so bad that people leave without leave abruptly, the time to change was long passed. Incremental change only works when the system is still functioning, at least a little. When the engine is blown, heroic efforts are required just to get down the road. We began the process of building a new engine as the car was being towed. It was a crazy journey, and the engine still needs a massive overhaul.

Our journey has not been without its struggles. Change is difficult, and it often brings to light discrepancies that were long buried under established routines. Through meticulous analysis and the adoption of new technologies, we've begun to uncover and correct these errors, many of which trace back decades. This process, though met with resistance, is a testament to the power of innovation and the importance of looking forward with an open mind.

I want to extend my gratitude to my colleagues, both new and seasoned, for their dedication during this period of transition. Change can be unsettling, and it's natural to feel protective of familiar ways. Yet, it's through embracing these new methods that we're able to grow and improve, not just as professionals but as an organization.

We listened, even when the concerns were expressed in less than helpful ways. In one recent long-form report, we performed root-cause analysis of every potential issue that was highlighted. We found, without exception, it was the “old” ways and not the “new” ways that were at the root cause of each issue. We found that we can include new audits to look for those issues in the future, as some of the old ways are still in practice and those errors are bound to reoccur. 

It is unfortunate that there was a historical culture of blame, but we refuse to take that tact. We do not seek blame but seek understanding, and innovation. We want to perform root-cause analysis on every issue, look for a better solutions, and implement it. It is hard to push forward through change, but we are pushing forward, because we must. We are looking forward to a future in which data management best practices are the norm, and innovating new ways to use technology to assist the humans is also the norm. There should never be a 12-month period were something hasn’t been innovated. Not 100 years from now, the system will never be perfect, it will always require adaptation.

As one colleague said in the past three years, “we spend all out time struggling to get the data, and don’t have enough time to analyze it.” That is a pain-point we have worked to solve and want to continue to solve. Humans should not be doing data entry if it can be automated. Those things that cannot be automated, can still be partially automated or improved.

Let’s use the best tools available to the best of our ability, and never ever stop innovating. 

As we continue to navigate this path, I'm reminded of the importance of patience, understanding, and perseverance. Change is a journey, not a destination, and it's through collective effort and a shared vision that we can overcome challenges and shape a future that's more accurate, efficient, and transparent.

To everyone embarking on similar journeys of transformation, remember that the road to innovation is often paved with obstacles. Yet, it's these challenges that lead us to improvement and progress. Let's continue to support each other, learn from our experiences, and move forward with an open heart and mind.

I dedicate this post to my first mentor, Sharon, who taught me that nobody can be an asset to any organization without being a “champion of change”.

#ChangeManagement #DigitalTransformation #Innovation #Teamwork #GrowthMindset

Shalom שָׁלוֹם: Live Long and Prosper!
Darrell Wolfe
Storyteller | Writer | Thinker | Consultant | Freelancer

Popular posts from this blog

Learning Coding Fundamentals with Python and SQL

Learning Coding Fundamentals with Python and SQL Learning Coding Fundamentals with Python and SQL Darrell Wolfe ————————————————————— Disclaimers First It is not my intention to steal anyone’s thunder or copyrighted material. I do not believe these seven fundamentals are specific to Dr Hill (below), who was the initial inspiration to start this note file. That beings said, she has a particularly unique method of teaching, and I strongly recommend that if you are someone who needs a good teacher, she’s the one! This is my own process of learning. I take information from as many sources and teachers as possible, synthesis that material, and then practice it until I get good at it. Further, I like to take detailed notes so I can refer back to them when a particular tool starts getting rusty or dusty in my brain after disuse for a time. When I learned .rmd through my Google Data Analytics Certification, I

Becoming a Business Intelligene and Data Analyst

In order to learn SQL, here are the steps I'm using: I'm working through: W3 Schools SQL Tutorials   Coursera: Google Data Analytics Professional Certificate   YouTube's Alex the Analyst FREE " Data Analyst Bootcamp!! "  Google Searching to reference as many articles as I can find on various aspects. Using ChatGPT  to check my syntax and explain concepts to me, answering my questions like a tutor.  I've also joined/downloaded/am using: GitHub My Repository:  https://github.com/darrellwolfe/toposcreative SQL Quick Reference notes Trello SQL Server  Express: SQL Server 2022 Express is a free edition of SQL Server, ideal for development and production for desktop, web, and small server applications. Visual Studio 2022 Power BI Tableau &  Tableau Public TBC... Shalom  שָׁלוֹם : Live Long and Prosper! Darrell Wolfe Storyteller | Writer | Thinker | Consultant | Freelancer

Using INDIRECT to obtain a VLookup with a variable array reference

Case Study for using INDIRECT to obtain a VLookup with a variable array reference *For reference: I did not build this workbook, it came this way and I'm stuck with it until I can rebuild it correctly next year.* The Problem: I have a legacy workbook that I have to rebuild for next year, but his year I'm stuck with.  This workbook has at or near 100 tabs that need to be referenced on a Totals and Subtotals set of pages. There are a thousand better ways to do that, especially using Power Query and Power Pivot, but here we are. These sub-totals pages were for specific sub-sets of the data that could be found on any given page (Ex: One sub-totals page looks for all properties with a PC Code "548"). On the sub-totals pages, the previous builder had simply linked the cells to the various pages; resulting in over a thousand rows of data that looked like this: //='2001'!$A$20// However, when the end-user filtered the data on the origin pages, the data on the sub-tota