I think folks are notorious for discovering the speck in another individual’s eye. In my own situation, it is helping people identify and optimize Business Processes. I understand the theory, and work consistently with partners who’ve Business Procedure design tools. But I discovered that I have really lax standards with my own private processes, like checking my next day program before leaving work, or setting all my out-of-office helpers when going on a business trip or holiday.
1 alibi I hear for not recording processes is the procedure is very creative to be documented.
If you believe a procedure can’t be documented, that implies that the human is dynamically re designing the procedure every time it’s performed. That represents a real risk to your company, because that individual might not be here tomorrow.
Anything that is done over once, or by several people, needs to be documented, if for no other grounds than uniformity.
Once a procedure is documented, it might be monitored, managed, and improved. Running processes without procedure instruction manual is like running applications without the source code. Who can even discover what went wrong?
Great process management can be enabled by computers, or else they can obstruct with it. The temptation is to start using it before you really understand how to use it effectively, when you get a cool new applications application. When it’s good applications, it should provide procedure instruction manual for how to effectively use it. Genuinely good applications would provide really good procedure instruction manual, with graphical diagrams, and tracking/management interfaces built in.
Popular new applications using SOA are being created using Business Process modeling tools to make the process framework, hence the composite pc software that is created from the procedure definition is precisely related to the operating manual. These kinds of applications already are instrumented for administration reporting and optimization. You can also discover what the IT dependences are, and what company processes are affected when these IT dependences fail.
Nicely official and optimized processes can make the dissimilarity between good business and also an excellent firm, or even between earnings and losses. When recording existing or new processes, make sure to use app that supports Model Driven Architecture and Enterprise Architecture frameworks. This will let you build high-level abstract models which can be realized in distinct re usable contexts. Also, make sure that the procedure models can be integrated with CMDB, so the procedure dependences can be used to create Business Support Impact Versions (Service Models for short). Service Models can then be used to automate problem and event management processes, and improve your support desk responsiveness.
You may also want to consider this; http://www.ebizq.net/blogs/service_oriented/2012/12/how_much_we_save_on_minimising_business_process_documentation.php