II.
Methodology JSON
Structured · livemethodology:impact-mapping
Impact Mapping json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "methodology:impact-mapping",
"_kind": "Methodology",
"_file": "domain/methodologies/methodologies.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Impact Mapping",
"description": "A strategic planning technique connecting business goals to deliverable features\nthrough a four-level hierarchy: Goal (Why), Actor (Who), Impact (How), and\nDeliverable (What). Prevents scope creep by ensuring every feature decision\ntraces back to a business objective and the behavioral changes needed to achieve\nit. Enables better prioritization by focusing teams on outcomes rather than\noutputs.\n",
"methodologyKind": "design-thinking",
"origin": "Gojko Adzic",
"yearIntroduced": "2012"
},
"outgoingEdges": [
{
"from": "methodology:impact-mapping",
"to": "domain:software-engineering",
"kind": "applies_to"
}
],
"incomingEdges": [
{
"from": "lib-process:shared--impact-mapping",
"to": "methodology:impact-mapping",
"kind": "follows_methodology",
"attributes": {
"weight": 1
}
}
]
}