Wednesday, March 21, 2007

A Framework that works

The last month I've been so busy with my consulting work, that I didn’t have time to do my posts. Off course, there isn’t such a thing as “no time”, just “not taking the time”. Having realized that, here’s a short update.

I’ve made my first yards in the development of the framework. These yards include making a selection of the main pillars on which, we at YNNO believe, a digitization project must rest, such as: Taxonomies, Metadata structures, Authorization schemas, Document Lifecycle, Registration and Inheritance, Search and Retrieval, Archival and Durability, Processes and Workflow, Conversion and Migration, Interfaces, Social Network Analysis (SNA), User interfaces.

Furthermore, I’m also trying to incorporate aspects of Enterprise 2.0 into the framework, with pillars the likes of: Ease of Use and the Rich User Experience, Perpetual Beta, Innovation in Assembly, Freeform versus Control, Emergent, Social and Collaborative.

And last but not least, the first “main beliefs” of the pillar “taxonomies” are already made explicit from tacit knowledge and experience . Mine, to be exact.

If you’re an ECM consultant and have just read the summary of pillars, you’re probably thinking: “so what, that’s nothing special?” Correct. The framework in it self is nothing special. I’ve become conscious of the fact that making the framework work what’s special.

I realized this during a meeting I had with a colleague of mine in which we discussed a project approach he was writing. We discussed the contents, approach, scope and ambitions and I realized that I was already using the framework as a common vocabulary to talk from and to distill my assumptions from. The result was not “well, you could do this and that, probably”, but instead it was “you should this and not do that, because past experience has shown that it works like that", and so forth. And that’s the result only after walking a couple of yards! I’m being optimistic, as always, but the potential of filling the “hollow framework” with working knowledge (made explicit) was suddenly crystal clear to me.

At present I’m busy organizing and preparing an interactive session with my colleagues operating in the field of digitization projects at knowledge intensive organizations. In this session we’ll present our main beliefs and use them the lighten up a discussion and to, ultimately, fill the hollow framework and make it work.

I’m being too optimistic when I say that one session will be enough. Maybe enough for the next couple of yards. That’s not a problem. The other thing I realized during the discussion with my colleague was that the value is not just in the destination, the journey is just as important.

In the next post I'll give some examples of "main beliefs".

No comments: