photo credit: storebukkebruse via photopin cc
No matter how clean and accessible your business documentation is, it is dead weight if it’s out of date. And this is the sad reality in many organisations today. Your business is growing, optimising, and doing things differently every day. Document maintenance becomes a nightmare. Read More
photo credit: kevin dooley via photopin cc
“We had some great documentation but it is now out of date from all the changes we made in the past years”
Sounds familiar?
How many times do we put the effort into constructing something only for the projects we run to invalidate it. This is especially the case with operational documentation. Organisations get it in place for a whole host of reasons but so many just ignore updating it when they run a project which becomes a false economy as the update job will happen at some time. Once they are established in a job, the organisation forgets that useful asset and ignores it when they make changes to the way they work. Read More
photo credit: kevin dooley via photopin cc
So you are embarking on an operational documentation review. The reasons can vary: an upcoming audit, a standardization mandate from above, or more efficient knowledge transfer. No matter what the case, the task doesn’t exactly scream “sexy” but it needs to be done and it needs to bring solid results. Read More
photo credit: Christmas w/a K via photopin cc
It might not seem straightforward, but the benefits of having an up to date and accurate business process documentation are much more imperative than you may think. The need for a proper operational package can be driven by different organizational triggers and objectives. Some common scenarios include:
Regulatory compliance: Highly regulated industries (e.g. financial services) more than others require strict compliance in terms of documenting your business processes. This task then becomes mandatory and cannot be ignored – it’s not a “nice to have” process. Read More
photo credit: Jeremiah John McBride via photopin cc
Once you decide on the high-level structure of your IT governance (as discussed in Setting up the right IT Governance – Part 1), you must flesh out the committee membership rosters, activities, and most importantly – accountabilities. Read More