diff --git a/docs/design/analysis.md b/docs/design/analysis.md
index c9efecf..7015666 100644
--- a/docs/design/analysis.md
+++ b/docs/design/analysis.md
@@ -12,6 +12,7 @@
 1. For all **events**:
    - Determine whether the event requires an explicit queue with durability guarantees.
    - If an external system consumes the event, design the API.
+   - Determine whether to use a notification event or event-carried state transfer @@Fowler2017.
 1. For all **commands**:
    - If a human issues the command, design the user interaction that allows the user to do that.
    - If an external system issues the command, design the API that allows the system to do that.
diff --git a/docs/references.bib b/docs/references.bib
index acc4e4e..fb278e0 100644
--- a/docs/references.bib
+++ b/docs/references.bib
@@ -186,6 +186,13 @@ @book{Ford2017
     year = {2017},
 }
 
+@online{Fowler2017,
+    author = {Fowler, Martin},
+    title = {What do you mean by "Event-Driven"?},
+    year = {2017},
+    url = {https://martinfowler.com/articles/201701-event-driven.html},
+}
+
 @book{Gilb2005,
     title={Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage},
     author={Gilb, Tom},