Take the 2-minute tour ×
Writers Stack Exchange is a question and answer site for authors, editors, reviewers, professional writers, and aspiring writers. It's 100% free, no registration required.

In your experience, are sections on risk and risk management typically part of technical standards documentation?

For example, in a document that describes how the Network Time Protocol is implemented and deployed throughout a network, does it make sense to talk about organizational risk?

Do people usually create a single "risk" document, with sections for each technology? (As opposed to splitting the Risk and Risk Management sections throughout a myriad of documents.)

The documentation must be in Microsoft Word, so a wiki solution is not possible (at this time).

Thank you for your opinions!

share|improve this question
add comment

3 Answers 3

up vote 1 down vote accepted

You should give mention risks in your technical document but leave risk management to "Single Risk Document" if it exists. What I mean is : RISK: If we fail to use NTP workstations and servers may be out of sync. Therefore some reports will use their computer's time instead of using common time.

RISK Management: This is not a big problem. We publish our reports enterprise only and we can bear this cost. Maintaining NTP enterprise wide will more costly.

You may agree or disagree with Risk Management but it is prerogative of management to decide this issues.

Also I object to this line. "The documentation must be in Microsoft Word, so a wiki solution is not possible (at this time)." MS Word has ability to link documents. Since I assume you can use network shared documents, you can link to this document.

share|improve this answer
add comment

I haven't found it common for technical standards documentation to say much about risk and risk management. The folks who negotiate standards generally care about risk, and spend a lot of time discussing risk in their deliberations. Perhaps in the end they presume that their standards themselves mitigate the relevant risks (assuming, of course, that they are implemented correctly).

share|improve this answer
add comment

Risk management is often in a section just devoted to the topic. In large organization RM is the task of designated personnel. The tech folks don't care about RM they just want to implement and maintain. RM folks want to know what issues might mandate procedures.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.