Thanks to @Nurturegirl for listening, inspiration and prodding to write this up.
Writing procedures for a preferably lean management system is like writing lean code, only it is not to instruct computers. Procedures instruct people, or better help them to follow a defined, proven process to achieve some of the purposes of the organization more efficiently. Of course, people can do so much more than computers, they can improve instructions and reject faulty ones, where a computer would just bug out.
Future of writing
According to Robert Horn in What Kinds of Writing Have a Future?
The seven kinds of information came to be called “information types.” They are:
• Structure
• Concept
• Procedure
• Process
• Classification
• Principle
• Fact
Structured writing
Indenting and tables are an essential element of structure. An example. So sorry this typepad blog refuses to let me control tables in a straightforward way.
D R A F T
| Purpose | We made and maintain this document to
|
| Principles | Compile or reference appplicable definitions, requirements, analyses, declarations, and contractual conditions for staff and subcontractors (free agents). Analyze relationships with risks, indicate checks and balances. |
| Process | Draft, usually as a structured table. Collaborate on Wiki version, export to Word as formatting template. Get approval signatures from responsible executives. Store pdf scan as approval record. |
| Content |
Scope
Requirement Potential threats against impartiality (mitigation) Approval Attachments |
Why structured writing
Information Mapping Inc. who happen to sell solutions (no affiliation) offer an interesting test. Based on your own reading habits, their demo will show you how much time you could save your readers.
If more writers used structure, would that be enough to call it progress?
Recent Comments