This article is one of a series that will focus on the process of running a successful business. It covers business process techniques used at Whitehat SEO and is written by one of our in-house team members.
In current years more and more businesses have started to focus on documentation in their daily business activity. There are several reasons for this which will be explained further in this article.
The question often asked is why do many of the businesses in the UK work without any documentation or checklist? The first reason is clearly the time invested to create the documentations or checklists. A lot of business owners believe it is too much effort and time invested compared to the results achieved with a written documentation. Even though it can be time consuming to create a documentation that everyone can use, the saving of time later on is immense. This is due to the fact that everyone in the business is able to do certain documented processes, since they are explained step by step. This is especially a benefit for the business owner since he/she can focus on the core activities, instead of doing standardized task.
The next main reason why businesses avoid the documentation of processes is that they believe they do not need it in their company, since everyone knows what to do. However important steps can be forgotten (even though it is an expert carrying out the task). A checklist or a documentation makes sure the person carrying out the task knows where to start and that nothing is left out of the process.
Important questions while creating documentations are: How do I create documentations? Gather information. At what time should I implement and make documentations? And how do I get my employees to use the written processes?
These are all major questions which I will try to answer in the next paragraph. First of all we will look closer on the term process.
The first important step, before making a written procedure is to identify the process itself. With having strict rules that set guidelines of how to identify the process it will be difficult to make a written procedure.
A process is a defined course of action that should bring forward a desired outcome or output. It consists of a couple of activities that are supposed to bring a specific outcome like for example adding a new client on to the online accounts system or how a sales person deals with a new customer enquiry.
Organisations have to identify their current objectives and then build up their process upon these objectives.
A procedure is only needed when there is a process. Sometimes there is no need for a documentation when the process is very simple, self- explained or general knowledge. Most employees would even feel that they are been made fun of if there is a procedure for how to turn on the computer (except when it is a very difficult process to turn on the computer).
Try to include the writing of the documentation as early as possible in the business process. It is better to start from day one. In the beginning it will be much easier to identify the processes, since the organisation itself is less complex than after some years of business activity. Later on it will also be easier to identify the evolving processes and include them directly. Also it will be easier to implement a standardised procedure of writing documents. Employees will be less reluctant to write these procedures when they are asked to do so from day 1 instead of doing it after 3 or 4 years of business activity.
When it is decided that there is a need to have a written procedure the organisation has to choose a person to write the documentation. Some businesses might think to assign one person within the organisation that is in charge of writing all the documentations, others might want to outsource the activity to specialised businesses. Usually it is recommended that the person doing the task at the moment or the expert for this task or process writes the procedure. There is no reason why an employee from the production department is writing a documentation for the HR department, or why third parties from outside should explain an activity they never have done before.
If the suitable person is chosen he/she has to select the content for the documentation. The content are all the steps included to fulfill the task in a satisfactory way. The writer should, before writing the final version, first do the activity while taking notes of the most essential steps. Then the author has to use step by step explanation, based on the notes, to explain the purpose of the procedure. There should be a use of bullet points and points should have numbers to form a clear structure. The explanations are supposed to be as short and as precise as possible. If it is a complex procedure, it is recommended to implement examples or pictures which illustrates and help the reader to get a broader understanding.
The purpose of the procedure has to be kept in mind at all points of the creation. It might be interesting for the author to include extra information, but if this does not follow the purpose or support the outcome it should not be in included. This only extends the length of the documentation unnecessary.
The last step and maybe the most important step is to encourage employees to use the documentations. First of all management should show the benefits (named above) of using documentations to employees. An example for a benefit is the time saving for employees. For example it is quicker for a new employee to read the procedure and then ask the remaining questions to a colleague, than asking for everything and maybe waiting for the colleague to have time to explain. This is also a benefit for the existing workforce, since they do not have to spend as much time on explaining and they are able to focus on their main activities. If there is a marketing expert, an seo expert or a marketing department within the company available it is a good suggestion to include them into “selling” the idea of written documentations.
Employees should also actively be engaged in the creation process. A good starting point is to ask them how they would design the layout or the creation of a rotating team (from different departments) testing new written procedures and giving their feedback.
The marketing resource engaged in this process can use the ideas created of employees for example the layout or content. Employees will adapt the ideas much easier when they for example get a small colourful checklist for making good procedures, which they have been contributing to develop.
For more information about how to write procedures that employees actually use, take a look at these five steps: http://www.sweetprocess.com/how-to-create-amazing-non-boring-procedures-that-your-employees-will-actually-use-to-get-tasks-done-correctly/
When I started as an intern at Whitehat, I was told the first day that the business works with written procedures. To be honest I was sceptical if this could work out. In my view it is difficult to include everything needed for a task on one piece of paper or in a Word-document. I also thought that it can be complicated to explain your mind set to another person.
As the first week passed by I realized these written procedures were not a bad idea. I was supposed to be the replacement for the current intern. The current intern was supposed to show me everything she had done until now, so I would be able to take over her task the days she left. The intern mostly showed me what she had been doing by documentations. She told me to read the documentation and then tell me if there was something I did not understand or if I had ideas of how to improve the documentation. Most parts of the documentations were simple and understandable. When I did not understand something I asked the intern what she meant by this. I also had some ideas for improvement. For example extending some of the explanations to tell more in detail of the for instance spreadsheet or cutting down some phrases to make it more simple. When the next intern is coming I will do the same, since I already mentioned continuous improvement of the documentation important.
There are several businesses successfully applying the documentation system to their daily business operations. One of them is Centratel. The company is a telecom company that is located in Oregon (USA). The owner of the business, Sam Carpenter, has written a book about the written procedures in his business. In the book he is explaining the way from no documentation and the struggles the company had until he started to realise that written procedures were needed. The company had these struggles since there were no clear guidelines to employees. Another reason was the CEO himself. He was carrying out major parts of the task, because he was not sure if somebody else could do it or deliver the expected quality. Through the implemented procedures he was able to make sure that employees knew what to do and that the outcome had a set standard. This standardization led to a drop in workload for the CEO and employees felt more motivated since they gained more responsibilities.
To summarize the key aspects of written procedures there should always be an analysis if these are needed for a specific task. When this consideration has taken place and a documentation is needed it is of high importance to do this in a standardized way, following the steps given above. If these guidelines are followed documentations can lead to improvement of performance and make the daily operations easier.
Send us an email now at info@whitehat-seo.co.uk or call us at (+44) 020 8834 4795 and grow your bottom line through our online marketing expertise today.
