This is already a basis for the procedure, which can be refined later

[sumaiyakhatun26]

However, it will certainly be easier than asking an employee to specially sit down and remember exactly what a process he or she did a week ago looks like.

I heard about this technique once in the context of creating procedures. If you want to create a procedure for onboarding a new employee, write down what you do step by step during the onboarding of people currently in training.



In the context of substantive tasks, you can do exactly the same thing. However, the saudi arabia rcs data difference between our work and optimization or onboarding a new person is that it is not a linear process.

You can do many things at the same time. That is why it is so important to involve many people in the team in this task. This is what will allow you to later confront whether it is better to go this way or another.

Because there is no one perfect process. But it's good to know that if I haven't managed to do something in X way, then maybe Y or Z will be the method that will help me deal with my problem.

So it's about creating scenarios and alternatives, not one ideal pattern that we should follow.

And that's it for today.

I strongly encourage you to develop a mechanism for exchanging knowledge between employees in your company.