81,898
edits
Meatware: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 28: | Line 28: | ||
'''[[Aesop’s dog]]''': Remember the fable of the dog with the bone: before you spend large, consider the information and the resources you already have. Could you reconfigure them to better present existing information? Could you overlay reporting on existing systems? There are some [[SharePoint|powerful workflow tools sitting idle in many organisations]]. | '''[[Aesop’s dog]]''': Remember the fable of the dog with the bone: before you spend large, consider the information and the resources you already have. Could you reconfigure them to better present existing information? Could you overlay reporting on existing systems? There are some [[SharePoint|powerful workflow tools sitting idle in many organisations]]. | ||
===Humans aren’t perfect=== | |||
Nor should you underestimate the [[meatware]]’s capacity to misunderstand the possibility presented by technology. This is much needed advice for those who write [[playbooks]]. It’s all very well having clever software that can read your confidentiality agreements and mark them up according to a [[playbook]], that is to say, but if the sad sack who wrote the playbook believes — and it is a sad fact of life that many of our learned colleagues do believe this, my friends — that pointless back-and-forths on low-value agreements in the name of procedural perfection ''because you can'' is a good idea, then your clever software will only allow you to waste the organisation’s time and money a little more efficiently and comprehensively than you were already doing by yourself beforehand. | |||
{{sa}} | {{sa}} | ||