Search

1 to 9 of 9
Sort by

Blog Entry
Borderless ECM: Addressing the Fragmentation Problem (My AIIM Webinar)

You do it by developing and then executing 4 pieces: The Defensible Disposition Policy (which is the design specification that states very clearly the objectives that your methodology will fulfill

Richard Medina's profile image

Blog Entry
Will We Ever Get This Right

I don't normally cross-post but a short week and a medical issue has me focused on design vs. production and the value of the things we do and don't do

Daniel Antion's profile image

Blog Entry
Runaway Trains

We start projects that are designed to support a specific business process...” If we think about the broader uses of information as we design systems, we can build better systems

Daniel Antion's profile image



Blog Entry
The Good News is that We Can Probably Solve the RM Problems of 1998

Be clear about what problems any “Best Practices” were designed to solve and were actually successful in solving. For a first approximation, we might divide history into five problem periods: Pre-1998 (predominately paper RM) 1998 (the 4 problems I outline above; also “EDMS”) 2003 (the magnification of the 4 problems, plus the internet; also “ECM”) 2013 (the magnification again of the preceding, plus the explosion of “Systems of Engagement” and the digital landfill) 2018 (the magnification of the preceding, plus expected and surprising disruptions) Now ask 3 questions of any information governance “Best Practices” you consider: Which RM problems in which periods was it designed to address?

Richard Medina's profile image

Blog Entry
In Search of the History of Algorithms*

[There is a] general method of algorithm design where we solve a problem by first solving trivial subproblems, then combining those solutions to solve slightly bigger subproblems, etc. until the whole problem is solved

Mimi Dionne's profile image