Carol says "That is the fundamental different between governance or framework and implementation. One is guiding principles according to a Strategy, the other is a project plan." The difference in what we're saying is that I agree with what she said -- but I also believe: 
1) What the quote implies: the EDRM is not the "Strategy" -- so an E-D initiative needs a Strategy in addition to the EDRM. So when Carol says "I'll stick with the EDRM framework!", she needs more -- a Strategy that's outside the framework. The methodology I suggested (along with other methodologies out there) provides a way to get this "Strategy"
2) Even if the EDRM includes a "Strategy", a good E-D initiative needs more "guiding principles" and "Strategy" than is covered by the EDRM -- so a good E-D initiative not only needs one or more sets of guiding principles and the Strategy to imply them, but also a covering, comprehensive "Strategy" to organize the specialized "Strategies" and "guiding principles". So again, sticking with the EDRM framework is necessary but not sufficient for a good E-D initiative. I designed the methodology to include the other necessary "Strategies" into a comprehensive uber "Strategy" that rules them all.
3) As Carol would agree, any E-D initiative needs an implementation plan, which EDRM doesn't address because it's a "framework". So finally, sticking with the EDRM framework is not sufficient for reaching the target desired E-D future state. The methodology addresses (as one aspect) the implementation plan.

The program methodology may be insufficient or overly complex but to confuse it with the EDRM is just a category mistake. A program methodology usually has several smaller "frameworks" and "implementation plans" within it and should provide a comprehensive "framework" that incorporates all of them and rules them all. The EDRM is one of the "sub-frameworks", and as such should not be confused with the comprehensive "framework" or any implementation plans. It differs from both of them. I provided a comprehensive framework which includes the EDRM framework (and several others -- in their well-defined roles), and which also addresses implementation. 

The R and M in EDRM stand for Reference Model. A "model" with lots of slots -- variables or questions that need to be determined or answered -- is a framework. But it isn't a framework that covers everything you need to decide and do for E-D. And it doesn't tell you how to decide and execute the items it does cover. So if you have the EDRM in hand, you need more. 

Achieving the objective -- a happy target state of litigation readiness in harmony with the organization's overall prioritized objectives -- requires a specification of your "ends" and your "means" and a structured way to organize them in importance, dependency, and how you will carry them out. A framework is a way to organize what's important and what needs to happen. An implementation plan tells you how and when to do it. Any program methodology should do all of this, and may include several "frameworks" and "implementation plans". The one I suggested does -- and there are others that also do so. 

The list of missing items (the "checklist for implementation") from the EDRM points to the categories in a program "framework" that must be addressed but are either not addressed by the EDRM (because it was not designed to address them), or are addressed by it but not adequate for implementation (because that's not the EDRM's job). To see exactly how the EDRM fits into the methodology, and what (I believe) it addresses and doesn't address, take a look at the methodology itself, where the EDRM plays an important (and well-defined) role. http://www.richardmedinadoculabs.com/1/post/2013/04/how-to-develop-and-implement-your-discovery-readiness-program.html



-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On Behalf Of Carol E.B. Choksy
Sent: Tuesday, April 16, 2013 9:45 AM
To: [log in to unmask]
Subject: Re: RAINdribble: How to Develop and Implement Your Discovery Readiness Program

Rich Medina says:
"That misses the point by a rather wide margin."

Actually, it doesn't. It's a framework. What you have listed is a checklist for implementation. That is the fundamental different between governance or framework and implementation. One is guiding principles according to a Strategy, the other is a project plan.

Best wishes,
Carol

Carol E.B. Choksy, PhD CRM PMP
CEO
IRAD Strategic Consulting, Inc.
[log in to unmask]
317-294-8329

Adjunct Lecturer
School of Library and Information Science Indiana University, Bloomington [log in to unmask]

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]