The document discusses the design of an interactive witness tool, including maintaining a social media presence to supplement traditional news coverage, designing an interface that feels physical and allows for exploration, and using a story map to define the project scope. It also outlines an agile development process using live wireframing, minimum viable products, and beta testing with several major news publications.

10. Social Media Editors
• Maintaining editorial presences on social media services
• Educating news reporters about using social media
in their coverage
• Using social media as a research tool to feed information
to reporters
• Creating social media-centered packages to supplement
traditional coverage

17. Designing iWitness
• Should feel physical, like a tool, not software
• Exploration and discovery, not “search” and “results”
• Human and friendly, not cold and technological
• Balancing both time and place
• Balancing both content and functionality

26. The Story Map
in scope
out of scope

29. Q: When is the
best possible time
to make a mistake?
A: When it
costs the least
to fix it.

30. The UX Philosophy:
Code is expensive.
Drawings are cheap.

31. The Agile Philosophy:
Drawings can be expensive,
if you get too attached to them.
Code can be cheap,
if you don’t do too much at once.

32. Live Wireframing!

33. Iteration 1

35. Iteration 2

37. Iteration 3

38. Minimum
Viable
Product

39. Minimum
Viable
Documentation

41. Beta

42. Beta Testing
• The New York Times
• The Wall Street Journal
• The Washington Post
• The Seattle Times
• The Palm Beach Post
• The Sacramento Press