By Jett Alcock at November 16 2018 05:18:26
They are more difficult to implement through discipline than administrative human-centric processes (although some discipline is needed). It is better to focus on obtaining buy-in from the people affected by the processes through early involvement, communication and expectations management. It is a known fact that knowledge workers are reluctant to change their habits. Some say knowledge workers don't like following procedures because they feel it limits their creativity; but most of the time they will be happy to follow a procedure as long as they see value in it, perceiving that it helps them work better and produce a better process output.
For a technical writer a flowchart can be a very useful tool to illustrate various operations and processes. Before you start your next project, see if you can illustrate the process via a flowchart. It will make life easier for you and your manager or client. The end result will be a better project which is good for your target audience. Note: Microsoft Visio is a good software for creating flowcharts. If you can write a simple sentence in English and organize your thoughts then technical writing may be a rewarding field. You can easily make it a second income stream in your spare time.
It is usual that knowledge processes take the form of projects to manage their execution. If the output of the process is a unique product, managing work as a project will result in obvious advantages. There are certain guidelines that can help an organization willing to improve their knowledge processes: Provide process description on how to approach work Try to figure out the best way to carry out a knowledge process, by making the best practices existing in your organization (or in your industry) explicit. Publish process definitions in a format that is easy to consult and understand. Provide tools that facilitate and standardize work Decide which tools are best to help knowledge workers carry out their work. Involving all affected knowledge workers in the process of deciding which tools will be used is very convenient, in order to obtain user buy in.
In the last years some organizations have emerged with the aim of creating professional communities around specific disciplines such as Software Development (SEI, ESI, etc...), Project Management (PMI), Business Process Management (BPMI), IT Service Management (ITSMF), etc... One of the objectives of these groups is to develop a body of knowledge that compiles the discipline's best practices in the form of reference frameworks, methodologies and maturity models. These assets should be considered by any organization interested in knowledge process management.