Task Library
Flag every moment worth public gratitude – milestones, referrals, reviews, advice, problem-solving – into a running log so no thank-you-worthy event slips by unrecorded.
Category: Thank You Machine
Use this when running the weekly gratitude scan, or the moment something thank-you-worthy happens – the machine starts with noticing.
Inputs
- Access to the week's surface area: closed projects, CRM notes, inbox, DMs, review platforms, social mentions, meeting notes
- The running trigger log (sheet or doc): person · what they did · why it mattered · where it happened · social handle
- The five trigger classes from /thank-you-machine
Steps
- Know the five trigger classes: milestones (client results, anniversaries, launches), referrals, reviews, advice received, and problems someone solved for you.
- Walk the week's surface area class by class – projects closed, CRM activity, inbox, DMs, review platforms, social mentions, meeting notes. Gratitude hides inside ordinary operations.
- Apply the two-part test: would naming this person and what they did make them feel genuinely seen – and would it teach your audience something about how you work? Both yes = trigger.
- Log each trigger the same day it's spotted: person, the specific deed, why it mattered, where it happened, their social handle. Specificity now is the script later.
- Prioritize: recency beats backlog (gratitude has a half-life), and referrals plus unprompted reviews jump the queue.
- Queue the top triggers for the week's recording session – a logged trigger that never becomes a video is a leak in the machine.
- Review the log weekly: recurring trigger types (e.g., every project completion, every referral) graduate into the post-project checklist via the systematize skill.
Definition of done (QA checklist)
- Trigger log current, with person / deed / why / location / handle per row
- All five trigger classes scanned for the week
- Top triggers queued for recording; nothing thank-you-worthy older than a week unaddressed
- Recurring trigger types flagged for the post-project checklist
- Linked back to the definitive article and relevant siblings
- Complies with Blog Posting Guidelines (if it publishes content)
Example(s)
- Worked example to document: a referral from a partner like Cam Hazzard logged same-day and queued for a thank-you video. Example needed – run the Meta-Article Prompt after first real run.
File in the zip: skills/thank-you-machine/identify-thank-you-triggers.md. Download the Task Library zip.
Index: Task Library. Article guidelines.