diff --git a/find-it/iterative-ux-d4d-outline.md b/find-it/iterative-ux-d4d-outline.md
index 01de8d5..e3bbccd 100644
--- a/find-it/iterative-ux-d4d-outline.md
+++ b/find-it/iterative-ux-d4d-outline.md
@@ -8,6 +8,22 @@ Main challenges:
 
 * Listening to the client more than the citizenry
 
+Make sure to cover:
+* Define iterative UX. Brief description of iterative UX/iterative testing/validation, and how this approach is ideal for any project, particularly this project
+* Describe the research that Cambridge had done before engaging Agaric, and explain how/why that helped so much
+    * Clients and Leo conducted research on sites with similar functionality "took great notes on what worked well and what didn't" -- did this include interviewing owners of the similar sites and/or cambridge clients' personal assessments of what worked well?
+        * Cambridge had some graduate students conduct interviews with other website owners -- a whole semester project
+    * Domain research: they found that people expected more useful information from .org domains than from .gov domains
+    * Comparative analysis: Cambridge staff evaluated similar sites and came up with critiques and questions about look/feel/functionality
+        * Discovered that site needs to be mobile friendly
+
+Findings
+* Automatic translation doesn't work well - give example of Google Translate button vs automatic machine pre-translation
+    * 
+
+For iteration section of presentation:
+* when discussing iterating on what someone else has built, focus on what works well and what you want to change
+
 
 What's next: