I spent some time today mapping out the similarities and differences between Value Stream Mapping and EventStorming. It's remarkable how similar they seem, and I think the way I've been doing VSM is very close to an EventStorming approach. I don't think you could go wrong with either one, but there are subtle differences. I think the best recommendation I'd have for any organization is to use whichever term and approach seems to resonate best with key sponsors and leadership. Use what will get results!

  Value Stream MappingEventStorming
Data YN
Method Qualitative/QuantitativeQualitative
Delays MeasuredAs queue S/M/L
Symbology ComplexSimple
Orientation Default Left to RightDefault Right to Left
Roles/Actors YY
Quality YN
Lead time YN
Rework YY
Waste YN
Triggers NY
Activity YY
Issue NY
Question NY
Areas identified HotspotsHotspots, Bounded context, Subdomain
Extensions Tools, Artifacts, Data flowRead model, Aggregate, External system, Policy
Core unit ActivityEvent
Focus Value flowSoftware event flow
Sequence Current state, Ideal state, Future stateCurrent state, Issues, Questions
Scope Org to TeamDomain to Application
Levels Ecosystem, Org, Release, Sprint, ProcessBig picture, Process modeling, Software design
Parent Lean Process ModelingDomain-Driven Design
Software design  NY
Market dynamics NY
Resources https://www.isixsigma.com/tools-templates/value-stream-mapping/resource-page-value-stream-mapping/https://github.com/mariuszgil/awesome-eventstorming