Starting with mind maps as a central way of modeling thoughts, the tool is quite like CMap. Allows tagged links and resources from delicious and other tools to be used and attached to each concept or thought node. It also allows “souping” knowledge using a centralized repository on the web that you can host with permission. However, this tool goes beyond in terms of usability and features. First, it is Web 2.0 based. Second it allows fragments or entire concept maps to be “imported” from one user to another. They call these concept maps journeys that can be shared and embedded.
Interesting concept because our project group in CCK08 was trying to get our maps together but could not do so because of disconnected terminology – no way to map nodes and compare because of language or representation (two different terms meaning the same, even typos, inconsistent use of mapping rules etc) problems. IMINDI does not address those problems.
They also have something called a Mindex or mind index which is really putting together the different journeys starting from a single keyword. So they take a keyword/concept term and check their database for all first level associations and so on. The results are pretty powerful at first glance. When quizzed on the business model, the CEO of IMINDI remarked that unlike Google that has to write a search engine to collect thoughts (read “nodes”), they are getting their users to pubish and voluntarily make the connections with what they want to know, some kind of reverse search (if there is such a thing).
The reviewers thought this was, well, a little far fetched and could not relate it to how people would even want to invest time upfront to create a mental map in the first place. They thought the company would do better to focus on the enterprise as a testing ground.
This is an example of a good thought, but no clear articulation of value for the effort.