archimedes
write

EverythingResilience & Technical Communication

StoryMaps and map inserts

One topic, or a named hazard set, wrapped so a room can actually follow it.

  • One-topic or named set
  • Not-to-exceed
  • GIS via teammate
  • ASG wrap
  • Not a PE seal

A flood, watershed, or energy project often has to explain itself to people who will not open a geodatabase. The StoryMap is the meeting; the insert is the packet.

A named StoryMap package, not a standing GIS program: diagnose the audience and the materials you already have, map one topic or a named hazard set, wrap narrative and accessibility around the drawing, and hand over a file a room can follow. GIS production runs through a named teammate. Not hydrology, not a PE seal, not EPC.

Same method as the rest of the practice: diagnose the operating system, map the risk or workflow, improve the procedure or digital tool, produce evidence and a usable handoff.

What you get

  • A one-topic StoryMap or a named set
  • Accessible narrative wrap
  • Insert-ready exports
  • Handoff notes

How resilience & technical communication runsSee the method

  1. 01Understand the operating system
  2. 02Map the risk or workflow
  3. 03Improve the procedure or digital tool
  4. 04Produce evidence and a usable handoff
  • WCAG 2.1 AA on the wrap
  • Named topic or set
  • Not-to-exceed on the map work
  • Handoff you own

Ask about thisStraight answer, no deck.

More on resilience & technical communication