map the existing work on a problem

[iangilman]

I don't know if this is outside the scope of this project, but I thought I'd throw it out there:

Many big problems are already being tackled from a number of angles. One helpful thing that can be done is to map out all of the existing efforts (and counter-efforts) going into addressing a problem. By creating an overarching information structure, weak points and synergies can be identified, and it'll be easier for new people to figure out how best they can fit in.

See Blessed Unrest: http://en.wikipedia.org/wiki/Blessed_Unrest

cc @eldang @rgilman

[dsernst]

100% within scope. Didn't know about the Blessed Unrest book but I have
found myself thinking exactly along those lines.

On Sun, Jul 13, 2014 at 7:41 PM, iangilman notifications@github.com wrote:

I don't know if this is outside the scope of this project, but I thought
I'd throw it out there:

Many big problems are already being tackled from a number of angles. One
helpful thing that can be done is to map out all of the existing efforts
(and counter-efforts) going into addressing a problem. By creating an
overarching information structure, weak points and synergies can be
identified, and it'll be easier for new people to figure out how best they
can fit in.

See Blessed Unrest: http://en.wikipedia.org/wiki/Blessed_Unrest

cc @eldang https://github.com/eldang @rgilman
https://github.com/rgilman

—
Reply to this email directly or view it on GitHub
#29.

[dsernst]

Part of my thinking on how to approach this is that the common thread
between all of these groups is the problems they are attacking. Does that
make sense?

On Sun, Jul 13, 2014 at 7:43 PM, David Ernst david@dsernst.com wrote:

100% within scope. Didn't know about the Blessed Unrest book but I have
found myself thinking exactly along those lines.

On Sun, Jul 13, 2014 at 7:41 PM, iangilman notifications@github.com
wrote:

I don't know if this is outside the scope of this project, but I thought
I'd throw it out there:

Many big problems are already being tackled from a number of angles. One
helpful thing that can be done is to map out all of the existing efforts
(and counter-efforts) going into addressing a problem. By creating an
overarching information structure, weak points and synergies can be
identified, and it'll be easier for new people to figure out how best they
can fit in.

See Blessed Unrest: http://en.wikipedia.org/wiki/Blessed_Unrest

cc @eldang https://github.com/eldang @rgilman
https://github.com/rgilman

—
Reply to this email directly or view it on GitHub
#29.

[iangilman]

Indeed. And many groups are attacking multiple problems, so it's an overlapping tapestry of interlocking circles. This is a very rich data set, and a powerful one at that.

[dsernst]

My current thinking on how to approach this:

Index by problems. So you might have: letsfix.net/group-affected/problem/ .

Then that page lays out:

1. What's the problem?
2. Why is it a problem?
3. What can I do about it?

That third section is a list of "possible solutions" for you, as an individual. So could be groups already working on the problem, i.e. the Blessed Unrest perspective. Or independent actions you can take to make a difference. For example, if the problem is a drought, it would help for you to take shorter showers.

And all of this is collaboratively editable, so everyone can contribute to map [problems] -> [solutions].

Yeah?

[rgilman]

I would encourage you to also include a section for "What's upstream from this problem." My impression is that people spend a lot of energy on symptoms that could be more effectively spent on leverage points in other parts of the system that can have broader and more lasting effects.

[dsernst]

Great point, @rgilman. Nice to see you here! 😃

I had been thinking about a sort of "related problems", but hadn't figured out this specific schema. Thank you-- "upstream" is a great way to think about it. Using a more directed approach invites fantasies of how powerful it would be to see a visual representation, chaining cause & consequence, for all the issues that anyone finds important enough to add. What an impact that could make on strategic planning!

Not to waste time over semantics, but there's also the reverse convention to talk about "the root" of a problem. Fortunately it makes no difference mathematically; easy enough to reverse the orientation. 😃

[iangilman]

I think it's worth noting that, for every problem, one of the things you can do about it is to help fill out the map of that problem and its context. Another thing one can do is help matchmaking people to actions.