Designing a CSTEAM system…
My Amazon author page!!!!

Designing a system that would better support CSTEAM activities isn’t really rocket science. In fact it is something that could be built fairly easily. Today there are applications that can automatically backup your computer (locally and to the cloud). Using that technology and having a specific folder for the concepts and ideas on the computer we could create an automatic upload infrastructure for lessons and ideas.

The problem is going to be value at that point. There are two ways that have been used in the past to create the value of a document or IP. The first is the number of downloads anyone document has.  The highest quality documents get downloaded frequently (due to updates and reuse). But so do bad documents that have really catchy titles.

You could consider uploads and downloads where a document that is modified and then re-shared (parent-child) is of more value than a document that is only downloaded. The problem there is specificity. If a document details a project that is wholly dedicated to a specific area in the world, its less likely to gain mass downloads and uploads than say an activity around a major world event or holiday.

We could develop a taxonomy for uploads that would support a flexible presentation system but again we run the risk of small samplings. A document could be influenced by people or simply by the fact that it is so good people download it and don’t modify it. To start down that path is fairly tough but there are components of what is needed already deployed in various social sites.

Project Upload Date First Download date Author updated Community Updated Regional only downloads overall use cost Monthly download rate


The reality is that today we can capture most of this information. We could add the simple like system (you can either like or choose not to like a document) but in the end that only gets us an awareness rating. We can build a matrix based on the various qualities in the table but again while that opens the door that doesn’t get us all the way through. There are many more considerations we would need to consider. Community updates would need to evaluate the percentage of the original document used and then the matrix for the new document against the original. The new document may be more effectively presented. Or they new upload may have simply added an easy to use slide deck that made it easier to consume the overall activity.

Overall use cost may take a fantastic lesson plan and in the end make it impossible to reproduce because of the cost of building the idea. The monthly download rate tied to the author or community update rate may in effect show us a consistent community structured, managed and continuous development project.

Sadly this is only one small aspect of what would need to be in place just to manage and develop the right IP going forward. It is however while the hardest part of this overall process partly complete today.

A worldwide CSTEAM system would be that hard to implement.


Scott Andersen

IASA Fellow.