groom -> refine

.obsidian/workspace.json

@@ -26,20 +26,7 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "crm-anatomy-best-practices.md",
-                "mode": "source",
-                "backlinks": true,
-                "source": false
-              }
-            }
-          },
-          {
-            "id": "00978fead994ccad",
-            "type": "leaf",
-            "state": {
-              "type": "markdown",
-              "state": {
-                "file": "agile-charter-types.md",
+                "file": "ticketing-best-practices.md",
                 "mode": "source",
                 "backlinks": true,
                 "source": false
@@ -60,7 +47,7 @@
             }
           }
         ],
-        "currentTab": 2
+        "currentTab": 1
       }
     ],
     "direction": "vertical"
@@ -89,7 +76,7 @@
             "state": {
               "type": "search",
               "state": {
-                "query": "risk",
+                "query": "groom",
                 "matchingCase": false,
                 "explainSearch": false,
                 "collapseAll": false,
@@ -142,7 +129,7 @@
             "state": {
               "type": "backlink",
               "state": {
-                "file": "agile-charter-types.md",
+                "file": "ticketing-best-practices.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -159,7 +146,7 @@
             "state": {
               "type": "outgoing-link",
               "state": {
-                "file": "agile-charter-types.md",
+                "file": "ticketing-best-practices.md",
                 "linksCollapsed": false,
                 "unlinkedCollapsed": true
               }
@@ -182,7 +169,7 @@
             "state": {
               "type": "outline",
               "state": {
-                "file": "agile-charter-types.md"
+                "file": "ticketing-best-practices.md"
               }
             }
           }
@@ -203,34 +190,35 @@
       "command-palette:Open command palette": false
     }
   },
-  "active": "00978fead994ccad",
+  "active": "690a545b32260114",
   "lastOpenFiles": [
-    "agile-anti-patterns.md",
+    "_site/remote-work.md",
     "ticketing-best-practices.md",
-    "_site/email-engagement-anatomy.md",
+    "remote-work.md",
+    "agile-planning-practices.md",
+    "_site/agile-charter-types.md",
+    "agile-charter-types.md",
+    "agile-anti-patterns.md",
+    "questions-and-answers/personal-inventory.md",
+    "questions-and-answers/eng-leadership-questions-answers.md",
+    "_site/agile-planning-practices.md",
+    "crm-anatomy-best-practices.md",
+    "hiring.md",
     "questions-and-answers/principle - judgement call.md",
+    "email-engagement-anatomy.md",
+    "_site/email-engagement-anatomy.md",
     "prfaq.md",
     "onboarding/NHO-practice-group.md",
     "integration-best-practices.md",
     "ide-anatomy.md",
-    "agile-charter-types.md",
     "agile-configuration.md",
     "web-app-anatomy-best-practices.md",
     "assets/recession-proof-engineering-leadership.pdf",
-    "questions-and-answers/eng-leadership-questions-answers.md",
-    "agile-planning-practices.md",
     "agile-planning-practices~.md",
     "assets/agile/SAFe implementation Roadmap_6.0.png",
     "chilling-effects.md",
-    "hiring.md",
     "career-coaching-training.md",
-    "questions-and-answers/personal-inventory.md",
     "_site/coaching-training.md",
-    "onboarding/NHO-corp.md",
-    "ux-anatomy-best-practices.md",
-    "crm-anatomy-best-practices.md",
-    "README.md",
-    "cybernetic-intervention-layers.md",
-    "org-change.md"
+    "onboarding/NHO-corp.md"
   ]
 }

email-engagement-anatomy.md

@@ -5,9 +5,14 @@
 First Party 
 
 The addition of these services will require the storage and access of data gathered about an email, external to a lead. This database would facilitate campaign (or another microservice) in being able to manage these in an abstract manner and fork updates to relevant subscribers (like ESPs).
-a) Email lookup table (id, email, hash? )
-b) Events Tables (ESP and Suppression-management - add event source to public.events?)
-c) Statuses Table (FA, Suppression-management, etc)
+
+- a) Email lookup table (id, email, hash? )
+- b) Events Tables (ESP and Suppression-management - add event source to public.events?)
+- c) Statuses Table (FA, Suppression-management, etc)
+
+### CDP and CIP repositories
+
+
 
 ## Campaign Management
 

questions-and-answers/personal-inventory.md

@@ -35,4 +35,11 @@ While far from, this inventory has many similarities to what I have already lear
 * Schedule your meetings at a precise time
 * Bring documentation and data to support your points
 * Take time to thoroughly explain your idea
-* Minimize the amount of open-ended questions
+* Minimize the amount of open-ended questions
+
+
+## Personal Mission 
+
+“I will [action] for [audience] by [skills] to [desired result].”
+
+An outline for reflecting on [what a personal mission statement could be composed of](https://www.indeed.com/career-advice/career-development/personal-mission-statement-examples)

remote-work.md

@@ -120,7 +120,7 @@ Async relies on the right tools.  [Use the right one for the context.](https://n
 ### Accountability
 
 * Don't just talk about ideas.  Talk about specific actions, and who will act.
-* Agree on both an action, and a target delivery date.  Or, groom the card for story-point estimation
+* Agree on both an action, and a target delivery date.  Or, refine the card for story-point estimation
 * Break work into 'MVC' pieces - the [Minimum Viable Change](https://about.gitlab.com/handbook/product/#the-minimally-viable-change-mvc) is always easier to validate, debug, rollback, scale, etc.