Notes from Scott Kubie’s (@scottrocketship) session at PSU Web, "Defrag Your Brain with a Concept Diagram".
Working at Wolfram
Is versus Ought: "Minding your isness"
Pages aren’t stories.
Websites aren’t products.
Wireframes and mockups only do so much. What if you’re missing something? How are things connected?
If someone assigns something to you, do the research to truly understand where they’re coming from. What they want. Their perspective.
Concept modeling is a process to develop a concept map/diagram.
Concept diagrams are graphical tools for organizing and representing knowledge.
Concept diagrams are made up of nouns and verbs. Nouns = concepts. Connected by verbs (link).
What they are NOT:
- Sketch notes
- Affinity diagrams
Five steps to building diagrams:
- Ask a question (you need to know what you want to understand)
- Do research (materials, competitive, interviews with experts, mind mapping)
- Make a list (parking lot, brain dump, big freaking list – nouns and verbs, interactive words for UX)
- Arrange the pieces (allow yourself to move around, shuffle – stickies, notecards, omnigraffle)
- Create links (trust your gut, your understanding)
Then, refine, refine, refine…or don’t.
Start with basics, then introduce size, color variations. What happens if you pull out the central concept? Can someone understand what your diagram is describing? Introduce larger circles, then you have Venn diagrams. Introduce icons or visuals that represent things. People, especially. Personas, etc.
- Use content diagramming to do some Gap analysis
- Concept model plus content model for strategy
- Stakeholder meetings: can be tricky. But these are your propositions, not theirs. Remember that.
- Tell a story with one or more diagrams
- Works really well as a suggestive device
Other thoughts: Concept maps are never finished. Start with something you know well.