Maintain private, chronological field notes for employees in Notion. Field notes track
patterns of concern (missed deliverables, communication problems, repeated feedback) and
record evidence over time. They serve two audiences: Alex (coaching decisions) and
leadership (escalation).
CRITICAL: Access Rules
NEVER search Notion. Alex always provides the URL. No exceptions.
NEVER create Notion pages. Alex creates them manually, then hands the URL.
NEVER write to Slack. Read-only Slack access. The only write targets are Notion and Obsidian.
NEVER share, export, or link field note content to anyone. No Slack posts, no email drafts, no shared links.
Append only. Never edit or delete existing entries in the Notion page.
Always show draft before writing. Never write to Notion without Alex's explicit approval.
Workflow
Verwandte Skills
Step 1: Fetch the Notion page
Use mcp__claude_ai_Notion__notion-fetch with the provided URL. Parse to understand:
Person's name from the page title.
Current tl;dr (if one exists).
Most recent entry date (to maintain chronological order).
Document structure the page already uses.
If the page is empty (Alex just created it):
Confirm the person's name from the title.
Ask: "What triggered this note?"
Write the tl;dr and first entry together.
Set up Obsidian cross-links.
Step 2: Gather source material
Process whatever Alex provides in the conversation:
URLs (Slack, GitHub, Asana): Fetch content using the appropriate MCP tool or CLI.
For Slack threads, use mcp__slack__slack_get_thread_replies. Resolve display names
with mcp__slack__slack_get_user_profile (always use real_name, never display_name).
Free text: Treat as Alex's direct observations or analysis.
Mixed input: Separate evidence (fetched content, quotes, links) from Alex's interpretation.
If a Slack URL fails to fetch, say so and ask Alex to paste the content manually. Don't
silently skip evidence.
Step 3: Check for recent 1:1 context (Granola)
Automatically look for recent meeting context with this person:
Check today's daily note (journal/daily/YYYY-MM-DD.md) for meeting notes mentioning
the person. Granola notes are pulled there by an existing automation.
If local notes exist, use them as context. No need to call Granola.
If no local notes, use mcp__granola__list_meetings to find recent meetings with the
person, then mcp__granola__get_meeting_transcript to pull the transcript.
Granola rules:
Granola content is supporting context, not the entry itself. Use it to enrich Alex's
observations, not to auto-generate entries.
Always surface what was pulled from Granola so Alex can verify accuracy.
Never quote Granola transcripts verbatim without Alex's confirmation (transcription
errors are common).
Step 4: Auto-detect entry type
Examine the input and classify using these priority rules:
Explicit request wins. If Alex says "structure this as O/I/A" or names a format, use it.
Feedback language ("observed," "impact," "I gave feedback," "I need to give feedback")
produces an O/I/A Feedback Block.
Multiple URLs or multiple dated events tied to the same problem produce an
Evidence-Heavy Incident Entry.
Sensitive content (tears, personal problems, mental health, family, medical) produces
a Personal/Sensitive Entry.
Otherwise, produce a Journal Observation.
When uncertain, ask: "This looks like [type]. Should I format it that way, or did you have
something else in mind?"
Step 5: Draft the entry
Present the draft to Alex showing:
The date header that will be used.
The entry content, formatted according to type.
Any proposed tl;dr update (if applicable).
Wait for approval before proceeding.
Step 6: Write to Notion
Use mcp__claude_ai_Notion__notion-update-page to append the entry. Append only.
Step 7: Cross-link in Obsidian
See Obsidian Cross-Linking section below.
Step 8: Propose tl;dr update (if warranted)
See tl;dr Management section below.
Entry Types
1. Journal Observation
Format:
### Mar 24
[Narrative in Alex's voice. First-person, direct, uses contractions.]
Status: [open | resolved | monitoring]
2. Evidence-Heavy Incident Entry
Format:
### Mar 24 - [Short incident label]
**tl;dr** [One sentence summarizing the incident pattern.]
- **[Date]:** [Event description] [link or quote]
- **[Date]:** [Event description] [link or quote]
- **[Date]:** [Event description] [link or quote]
3. O/I/A Feedback Block
Format:
### The Feedback (by Alex) - Mar 24
**Observed:** [Specific, factual description. No judgment. Dates, actions, quotes.]
**Impact:** [Concrete consequence on team, project, or business. No emotional language.]
**Ask:** [Clear behavioral change. Forward-looking expectation. "Going forward, I need you to..." not "It would be great if you could..."]
If Alex describes how the conversation went, add below the O/I/A block:
#### How it landed
[Narrative: Alex's voice. How the person received it, what they said, next steps agreed.]
4. Personal/Sensitive Entry
Same format as Journal Observation, but:
Use more careful, human language.
Don't summarize emotions reductively.
Capture emotions factually ("she burst into tears," "he was visibly frustrated") without editorializing.
Include what options were discussed and decisions made.
Include what support was offered.
If the content seems like it might create legal exposure (promises about employment,
medical accommodations), surface a brief caution without playing lawyer.
Writing Voice
Field notes use a hybrid voice. Load the alex-writing-at-work skill guidelines for
the full reference. Key points per entry type:
Journal entries and narrative sections (including "How it landed")
Use alex-writing-at-work document style:
First-person singular ("I noticed," "I gave feedback," "I validated").
Direct, earnest, warm without being casual.
Contractions freely ("didn't," "wasn't," "I'm").
Medium-length sentences, mix of lengths for rhythm.
No corporate jargon. Plain language.
No hedging unless genuine uncertainty exists.
Active voice throughout.
O/I/A blocks
More structured and evidence-grounded:
Observed: Purely factual. No interpretation. Specific dates, actions, quotes.
Impact: Concrete consequences. Connect to team, project, or business outcomes. No emotional language.
Ask: Clear, forward-looking. Framed as expectation: "Going forward, I need you to..."
Sensitive entries
Same voice as journal, plus:
More space for the other person's perspective.
Capture emotions factually without editorializing.
Include support offered and decisions made.
tl;dr Management
The tl;dr sits at the top of the field note, immediately after the title. It summarizes
the overall situation, not just the latest entry.
Rules:
Propose, never auto-replace. Draft an updated tl;dr and present it for confirmation
before writing.
Material change means: a new pattern emerged, a previous concern was resolved,
escalation happened, or the overall trajectory shifted.
Not every entry warrants an update. A single observation reinforcing an existing
pattern doesn't change the tl;dr.
Format: Bold **tl;dr** (lowercase, no colon) followed by dense 1-2 sentence summary.
Example lifecycle:
Initial:
**tl;dr** Filipe has a pattern of not reading shared documentation before asking
questions. Three incidents in February, feedback given March 1.
After feedback lands well:
**tl;dr** Filipe had a pattern of not reading shared documentation (three
incidents in Feb). Feedback given March 1, received well. Monitoring.
After resolution:
**tl;dr** Filipe had a pattern of not reading docs (Feb). Addressed in March 1
feedback. No recurrence since. Resolved.
Obsidian Cross-Linking
Field notes are sensitive. Cross-links must be maximally discreet.
Person file
Location:people/@FirstName LastName.md
Add a single line to the Log section:
- [Private notes](https://notion.so/...)
Generic label "Private notes." No year, no context, no description.
Link points to the Notion page URL.
Only add once per field note document. Check if the link already exists before adding.
If the person's name (from the Notion page title) doesn't match any file in people/,
ask Alex to confirm the correct file name. Don't create a new person file.