This is great - FreeMind I mean, and the suggestion of how to use it
with wiki and email. FreeMind is very snappy in action. (01)
One consideration re using this as part of helping work on wicked
problems: (02)
run the nodes backward
ie, rather than fanning out from general to particular,
how do you map, and help enable, the process of discovering the new
general that maps the then newly understood particulars? (03)
FreeMind runs left to right; nodes to the left bind nodes to the right
what about running so that nodes to the left are bound through a node
to the right (which I would see, re another thread here, as their
call by future). (This also relates to the Victoria Livschitz
discussion re "recursively build higher-level metaphors from lower-
level ones".) (04)
The suspension state is when the nodes are in flux, appearing,
disappearing, being edited, some thrown out, some thrown in, since
we're not sure what's relevant, and won't know what was relevant till
after the fact. This is the state of work, processing. Then, the
nodes are bound - we know what's relevant, relative to the new
binding, and the work re-begins, with progess aka newly minted bound
(at least interimly) nodes. (05)
The discuss via email stage may well correspond to the chaotic flux
stage. It seems to still be the de facto way most of us carry this
out. Thank goodness these e-mails here have their purple numbers, so
we can turn what's relevant into nodes. (06)
Within relatively limited contexts - and necessity / urgency forces
limited contexts (ie, staying on the point, trying to be relevant)
(http://webseitz.fluxent.com/wiki/ConText) - this could actually be
surprisingly powerful. It accords with ideas I/we have been nurturing
about shared mission-oriented carrels. (07)
Face to face meeting, open space style, or U-process style, also fit
into the "discuss via..." slot. A bit of "downloading", a bit of
opening up, but then at some point something needs to be concretized.
This is the small grokkable set of ideas we've been working on: how
do we now bind them? Jumping out of the linear overlapping flow of
emails into a 2D picture concretizes, which is helpful. A new form of
periodic digest, as a mind map: that's great! (08)
A contributory pattern would be playfulness: I can see FreeMind
helping with that. (09)
On Jan 11, 2006, at 12:26 PM, Bill Seitz wrote: (010)
> Without much elaboration, here's another "simplest" approach:
>
> * do some integration of FreeMind with Wiki, so a MindMap is stored
> as the contents of a wiki page
> * discuss via email
> * update the MindMap/WikiPage following IBIS conventions to corral
> the email threads
>
> http://webseitz.fluxent.com/wiki/MindMapping
> http://webseitz.fluxent.com/wiki/FreeMind
> http://webseitz.fluxent.com/wiki/EmailDiscussionBesideWiki
>
> Aleksander Slominski wrote:
>
>> Eric Armstrong wrote:
>>
>>> --which raises the question: If it's so well-targeted
>>> for carrying on a remote discussion, preserving an
>>> "organizational memory", and reaching a resolution,
>>> why hasn't the Yak group moved to it, and left email
>>> messaging behind?
>>
>>
>> in the spirit of Agile Development and http://xp.c2.com/
>> DoTheSimplestThingThatCouldPossiblyWork.html
>> i keep wondering what is the simplest thing could be done and
>> achieve the goals for such collaborative tool as it is discussed?
>>
>> it looks to me that email is not going away any time soon (!) so
>> maybe we could look what can be done to improve it to be more like
>> IBIS-yak?
>>
>> we have already email archives for yak so maybe they can be used
>> to mine for IBIS-like discussion maps?
>>
>> maybe some conventions can be used in emails to indicate AGREE.
>> DISAGREE, SUPPORTS, etc (or whatever it is called in IBIS) and add
>> some support for linking threads of email discussions to topics/
>> subject proxies (with metadata carried in X-Mail headers)?
>>
>> thanks,
>>
>> alek
>>
>> ps. in my opinion no collaborative software can replace email as a
>> collaborative tool (just because of email ubiquity and network
>> effect) - instead i think the way is to integrate such
>> collaborative software with email infrastructure and hope users
>> will find value in added capabilities such as IBIS (maintaining
>> relevant subject lines in emails or keeping threads is hard ...)
>>
>
> --
> This message is archived at:
>
> http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?
> a=yak&i=43C531C4.7020304@fluxent.com (011)
--
This message is archived at: (012)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=592E3769-C01D-43AE-AFD7-3591223FE94F@well.com (013)
|