Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » infoKits » Creating an MLE » embedding-mles-into-institutions » Summary and conclusion

8.8. Summary and Conclusion

Don't think because you got this far that the work is over!

Is your MLE now just part of normal life and being used as a matter of course wherever appropriate? Is its use included seamlessly in all applicable policies, procedures, roles and responsibilities? If so you have made great strides towards embedding, however...

Embedding is not a once and for all process - if it was it would imply that your institution is immune to change and by and large this only applies to the extinct. The whole process is one of continuous evaluation and review.

Your organisation will need to change, both of its own volition and as a response to external pressures. This means that you will have to keep revisiting the make-up and needs of the institution (Understanding your organisation section) and why you have an MLE (Why might you want an MLE section).

Responding to change will mean that your MLE will have new requirements to address (Gathering requirements section). In turn, you will need to re-examine your technology options (Technology options section) in the light of these new requirements and in response to the ever-changing technologies available. This will mean you will need to change your MLE's design (MLE design section) and implement these changes (Implementation section). (In reality all of what has gone before can and will need to happen in various orders.)

Of course, now many of the things you had embedded will be thoroughy uprooted and you will need to address policy. procedure, roles and responsibilities and all the associated cultural change issues yet again.

Having done this - you can evaluate how it went, if it's working, and start all over again...

Good luck!


Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)