4 Amazing Lessons About Changing Processes

Disclaimer: I just wanted to state, what I write are the opinions and recommendations or suggestions of the experiences that happened to me and to share my story. This is not to be rude or to say bad things about a workplace but to share experiences and how I handled them.

This experience is about processes being changed.

A door with an image that says change

Sharing my Story

In my case, a test plan is usually written and presented to various teams including the product manager, product owner, software developers, and UX/UI designers.

When I presented my test plan to the other teams, I thought it went well with me discussing what I was planning to test and what not to test. Wrong! After the meeting was over, my manager sent me a link saying how it should be done with what is going to be tested. After the manager sent the link, I could not understand what I did wrong. I felt like I was not told about this new process change. So, I decided to speak to the manager about this. The manager mentioned that yes, we are trying out a new process and have received feedback from another team/department on how our test plans need improvement. I understand that it is great to always receive feedback to improve our process to become more efficient. There are several things I have learned just from this conversation with the manager and process changes.

Lessons Learned
  1. Try to accept the process change. It might be hard at first to accept the process change because we have been working with this process for a while and it works. It makes me think of the quote by Miles Davis: β€œIt’s not about standing still and becoming safe. If anybody wants to keep creating, they have to be about change.”
  2. Changing the process without knowing prior. If the manager decides to make the change without the team knowing I think it is only fair to inform your team first if possible so the people on your team will not use the old process while presenting in front of other team members and other departments.
  3. Inform the team about an upcoming process. If feedback was given from other teams/departments, I think, if possible, to schedule a time with the team to inform the team what is going on and that we receive feedback from another department on ways to improve our process and moving forward we are going to use this new process and would like your feedback.
  4. Communicate. I think communication with the team is key especially when processes are changed or even thought about being changed.

What are your thoughts about changing processes?

Resources:

Leave a Reply

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