Conversation for action

First draft (attached). It's a cacoo diagram. Shared with @lynnfoster and @ahdinosaur so far. Let me know if you want to edit.

P.S....and then we need to detail out all of those messages...

P.P.S....and after Lynn and I go for a walk-and-talk, I'll write up some of the limitations of that first draft...and, second draft with Lynn's improvements coming up. [Aside: how do I delete an attachment to a Loomio comment?]

Limitations of first draft:
First it's limited in scope: in terms of the stages identified by ISO - “planning, identification, negotiation, actualization and post-actualization”, this only covers negotiation and actualization. (And everybody who has looked seriously at the question has similar stages, maybe with different names, boundaries and definitions, but close enough.)

And then, it's limited to one CfA pattern: the diagram depicts a requester and a performer. What about collaboration, do-it-together?

In terms of project the assembled multitudes here might know about, that diagram covers the scope that might live within our NRP software. Hylo might cover the identification (matching of needs and abilities). And Netention went even farther and deeper into the direction of "what happens before you are ready to start a conversation for action".

And then a lot of stuff happens in what ISO calls "post-actualization": like, let's evaluate that action. How did it work out? Should we do something like that again? What should we do different, how can we improve, the next time?

And then these actions form networks. I did something with you, and then I did something else with some other people, and so did you, and we could all come together in something else altogether. (In other words, this spins into the person-and-organization stuff, where organizations form from engagements.)

From another angle, as Fred writes about, in the real world, everything is negotiable, including the vocabulary and message flow.

I'm happy to start with a limited scope and assume we can all come to some agreements on vocabulary, but even that is a conversation for action.

Feel free to suggest other limitations and suggest other improvements or directions...

Second draft attached. Lotsa improvements from Lynn.

Still more to go (for another day and after more feedback): message details, maybe some explicit timeouts here and there?

Let's create a community that you guys can use.

(You'll find the flow we use to be highly simplified-- It is, strictly speaking, not CfA, but it is influenced by CfA)

To set up a community, here's what we'll need:

Community Name:

The Community's Core Intention: (1-2 sentences)

Logo: (image, square, at least 300x300)

Banner Image: (something that your community will recognize or resonate with, at least 1200 pixels wide by 500 high)

Invite Code: (Something like: openapp-hylo)

URL: (Something like http://www.hylo.com/c/openappcommunity)

Bob-- I can make you a moderator

Let's create a community that you guys can use.

(You'll find the flow we use to be highly simplified-- It is, strictly speaking, not CfA, but it is influenced by CfA)

To set up a community, here's what we'll need:

Community Name:

The Community's Core Intention: (1-2 sentences)

Logo: (image, square, at least 300x300)

Banner Image: (something that your community will recognize or resonate with, at least 1200 pixels wide by 500 high)

Invite Code: (Something like: openapp-hylo)

URL: (Something like http://www.hylo.com/c/openappcommunity)

@bobhaugen -- I can make you a moderator

@edwardwest - I think either @ahdinosaur or @simontegg or @derekrazo or somebody else who is more part of the nucleus should be the moderator. (Derek is already a member of Hylo and presumably knows the ropes.) I could copy and paste something lame about the core intention but have no ideas for logo or banner.

And I understand about CfA. Our diagrams are simplified, too. Helene probably has the broadest scope. Flores' version is simplified compared to Helene's.

Great-- and @bobhaugen -- you asked if I knew about Netention-- I had heard the name, but I didn't have any sense of it-- upon reviewing their slideshare: http://www.slideshare.net/helenefinidori/introduction-to-netention it is clear there is some convergent evolution going on -- or, perhaps more correctly, we're all blind men and women feeling the same elephant--

@edwardwest - so how can we get connected and start feeling up the same elephant?

(Afterthough: I'm not sure how the elephant is gonna feel about that...)

:)

Right now, I have a small team and we've got a thesis of a good first step toward light-weight CfA-as-social-media-like-tool for "communities of purpose" in Hylo-- I'd welcome any thoughts/suggestions/support with this specific project, and I would welcome the opportunity to build flows that include Loomio and CoBudget and other apps

@edwardwest - we understand the heads-down-on-a-project feeling. But then there's this other part of the conversation for action that we have not touched on yet, which is, do we match? Do we have compatible goals and values? Are we to some extent trying to accomplish some shared purpose in the world?

And even if we do match in some abstract sense, how exactly do we connect in some useful and practical way? Do we find each other in our own adjacent possibilities?

I don't know your answers to any of those questions. Lynn and I are still heads-down on part of our current project, but our real goals are not to create a product but to be part of an ecosystem. So we'll be happy to tear everything we have done so far into little pieces and distribute them among a bunch of OpenApps, assuming that can be done. Might not suit you...?

I'm sure there's also other ways to connect, between Hylo, Loomio and CoBudget as they are now. I can't speak for them.