If there’s one certainty in our business, it’s that useful, lightweight frameworks turn into bloated, productivity-destroying methodologies.

And so it was with considerable trepidation last week that I suggested we need another methodology, to do for Content Management Systems (CMSs — the technologies we use to manage unstructured information) what normalization and related techniques do for relational database management systems (“Unstructured data design — the missing methodology,” KJR, 5/17/2010).

But we do.

Microsoft has just announced Office 2010. Surprisingly enough, it has genuinely interesting new features, most of them revolving around SharePoint and support for collaboration.

And, of course, The Cloud, where to Microsoft’s credit, alone among major software vendors its product makes serious use of the PC’s processing power instead of limiting its role to running a browser and Citrix client.

But the Office/SharePoint combo is missing something essential: A design methodology for the unstructured data stores it helps you manage.