Thinking in Maps | Thinking in Packages | Thinking in Stories | |
---|---|---|---|
Use it for | solving hard problems | absorbing new information fast, when "deep" understanding is not needed | explaining stuff |
exploring new problems or even new domains | having easily communicable information at hand | selling | |
out-of-the-box non-linear reasoning | giving easy to follow instructions | convincing | |
making sense of LARGE amounts of highly distilled information | first-phase of learning something new, if speed matters more than deeper understanding | manipulating people | |
learning new and complicated stuff | small volumes of information | ||
exploring an un-familiar domain | un-distilled information that needs to be conveyed in its current form | ||
Bad for | guiding people along a most efficient predetermined path | solving hard problems | transmitting information unambiguosly |
manipulating people towards a pre-determined destination | creative problem solving | avoiding less-than-rational thinking | |
explaining stuff to people unfamiliar with the domain (they can easily get lost because there are too many paths on the map) | large quantities of information (can't find the right stuff because there are too many packages) | large quantities of information (the story becomes too long and confusing) | |
figuring out high-level design mistakes (you can miss the forest because of the talking trees) | |||
highly distilled information (the story's details can obscure the main point) |
Last active
August 29, 2015 14:26
-
-
Save NeuronQ/bf3aa764378f8907a1c1 to your computer and use it in GitHub Desktop.
Mapping vs. Packing vs. Story thinking
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment