How do I do that?
Posted: Thu Jan 30, 2025 7:08 am
I have noticed that these types of books or internal libraries are most often created in the context of company procedures.
So that we know how to fire people, how to hire them or onboard them , i.e. introduce new employees to their tasks, how to close a project and report it, etc.
And these are of course very important issues, but this is not the type of document I am talking about at the moment. In this case, I mean a file that is purely substantive, i.e. one that will explain:
how to optimize campaigns,
how to set up ad accounts,
how to report something to a client,
how to interpret certain statistics etc.
It is therefore about the exchange of knowledge.
I have been planning to create such a document for a very long time.
I had an ambitious plan that either one of the team members would do it or I would build it myself. And for months, it didn't work out.
That's why I'm talking about it. Because if you're hoping to find that magical free time saudi arabia rcs data where you can do it, spoiler alert! That's definitely not going to happen.
You have to find another way to approach creating such a knowledge base. And I think I've already figured it out. And I even managed to finish a few of the first projects that way.
Ask your team to record what they are doing while performing a task. If it is, for example, campaign optimization, you can record your screen and use the built-in microphone to comment on all the steps as they go.
What does that give?
First, the employee must think about what their work process looks like, and second — all information collected in this way can then be written down, transcribed or uploaded in the form of short videos to a single repository. In this case, it will be our DIGIBOOK.
This allows many people to share their practices, and it is not a separate job.
And yes, I am aware that completing such a task, and at the same time thinking about it and commenting on it, will extend its implementation time.
So that we know how to fire people, how to hire them or onboard them , i.e. introduce new employees to their tasks, how to close a project and report it, etc.
And these are of course very important issues, but this is not the type of document I am talking about at the moment. In this case, I mean a file that is purely substantive, i.e. one that will explain:
how to optimize campaigns,
how to set up ad accounts,
how to report something to a client,
how to interpret certain statistics etc.
It is therefore about the exchange of knowledge.
I have been planning to create such a document for a very long time.
I had an ambitious plan that either one of the team members would do it or I would build it myself. And for months, it didn't work out.
That's why I'm talking about it. Because if you're hoping to find that magical free time saudi arabia rcs data where you can do it, spoiler alert! That's definitely not going to happen.
You have to find another way to approach creating such a knowledge base. And I think I've already figured it out. And I even managed to finish a few of the first projects that way.
Ask your team to record what they are doing while performing a task. If it is, for example, campaign optimization, you can record your screen and use the built-in microphone to comment on all the steps as they go.
What does that give?
First, the employee must think about what their work process looks like, and second — all information collected in this way can then be written down, transcribed or uploaded in the form of short videos to a single repository. In this case, it will be our DIGIBOOK.
This allows many people to share their practices, and it is not a separate job.
And yes, I am aware that completing such a task, and at the same time thinking about it and commenting on it, will extend its implementation time.