Implementing Change Protocol in order to have Continuous Service Improvement(CSI) in DATAAK Company.
First of all, it’s worth mentioning, this is our story so far and this story continues. We spent three months full of experience together and had many achievements in various fields .
Dataak is a young, knowledge-based, technology-based company that, with the help of years of knowledge and experience in the field of metadata and artificial intelligence, offers a variety of services and products to transform distributed data into coherent and practical knowledge. Public relations system, “cyberspace status room” and “Analytical reports” are among Dataak’s products in this field.
Like always we started from “Problem Space”. Detecting real problems in a systems is always challenging and need to understand current company’s culture. Their culture means their employees personas and skills and the way they play their games. We do not speak about process and organizational charts, these did not and do not represent the culture of an organization. We had to play the games and understand each other.
Phase 1: Creating a playground for team to have a better solidarity.
What was the challenges?
In order to understand the real problems, we had to play real games and real players as much as we could. In the first encounter, these people were divided into three groups:
- Some of them constantly resisted change and hid the essence of the problems.
- Another group was interested and accompanied.
- The last group did not react to change, this group or from Previously unsuccessful changes were tired or did not consider themselves members of the company.
*The very important point is that the quality of detecting problems and solving them depends more on the effective communication of all people in all three categories than their relationship with me as a consultant of the organization.**
How did we start?
Step1- We could gather a change team with the key responsibility of detecting real problems regarding DATAAK’s Vision. As I mentioned the most important aspect was related to our team work.
Step2- We needed to look at the organization’s vision in the same way, along with the vision of each product or, better yet, the services that were offered.
In order to create our products vision we have used “Roman Pichler vision board” and it was so useful for us. Roman Pichler
Another useful method for detection our Customer’s Needs and Pains that we have used it was creating Our customer As-IS and To-Be journey.
Step3- Running Design Thinking Framework in 5 Days to detect our first Iteration problems and define related solution.
Phase2:Implementing Ideas and monitoring the outcomes
We were able to define solutions, but we started to implement a few of them.
In the brainstorming sessions and in the retrospective sessions, we had ideas to implement, and really good ideas to implement.
What we learned together was that it is not possible to make these changes overnight. Prioritization through value and Effort solution was not a solution to the implementation of ideas, because the structure of the organization, culture and ability of individuals to implement change has always been limited.
Achievements
- Defining A To-Be structure and break down the tasks to have more self-organized team.
- Improving requirement engineering process.
- Increasing change team collaboration by giving them some protocols and responsibilities.
- Defining long term objectives and increasing concentration for change team.
Thanks to the DATAAK team.
Payam Hoveida, fAeze Rezaee Pooya, Paris Ojaghi , Maryam Zibaie, Ati Mokallahi
To be continued…
