weekly proactive-communication tool.

# SUB-014 — Weekly proactive-communication tool

> Paste SUB-014 into chat to context-shift here. > Side-venture subject (NOT main path). Captured 2026-06-01 — Ishai flagged it had been given before but never written down. Exactly the forgetting Subjects exists to fight.

Story

Ishai struggles with the proactive-communication side of the lead-designer role: reaching out to people, pushing things forward, creating meetings, writing emails and notifications. The work piles up because the *initiating* is hard. The idea: a structured tool that makes him more active by doing the structuring for him.

Core mechanic (Ishai's words, lightly cleaned):

• A weekly action that pulls his open questions from the vault / knowledge bank.
• Figures out which people can answer each question (map questions → people).
• Sets up the meetings / drafts the outreach.
• Runs at the start of each week so the week opens with the meetings already arranged.

This turns a chronic weakness (initiating comms) into an automated weekly ritual.

Why it matters

• It's high-leverage: unblocking open questions is how design decisions actually get made.
• It's a known Ishai pain point (communication, meeting creation, follow-through).
• It's off the main path but improves the whole system — the definition of a Studio subject.

How it could work (early thoughts — to develop)

• Source of questions: vault/10-Open-Questions/ (per-role open questions) + vault/07-Recommendations/Open-questions.md + open threads across subjects.
• Question → person mapping: use the stakeholder map / people directory (vault/98-References/) + role files (vault/02-Users/) to suggest who can answer what.
• Output: a weekly digest of "questions to resolve + who to ask," with draft emails / meeting invites ready for Ishai to send.
• Publisher rule applies hard: Claude DRAFTS the emails/invites; Ishai sends. No auto-send (see CLAUDE.md publisher ban).
• Possible home: a recurring Errand (SUB-004 AFK queue) and/or a weekly routine tied to /weekly-review.

Decisions made

• 2026-06-01: Captured as a side-venture subject under Studio Subjects. Maturity: seed.

Open threads

• Where questions are pulled from (which vault sources, exact list).
• Question→person mapping method (manual stakeholder map vs inferred).
• Output format: digest? draft emails? draft calendar invites? all three?
• Trigger: tie to /weekly-review (Sunday) or a separate weekly errand?
• Hard constraint: all sends are DRAFTS only — Ishai is the sole publisher.
• Relationship to SUB-001 F10 "comms gap meter" (this subject likely absorbs/supersedes that deferred feature).

Raw refs

• chat: 2026-06-01 brain dump (Studio Subjects spec session).
• subject: SUB-001 (Studio) listed this as "F10 comms gap meter" but it never became its own subject — lost until now.
• spec: vault/08-Design-specs/studio/_subjects.md (uses this as the worked example).
• people: vault/98-References/ (stakeholder map / directory).

Last activity

2026-06-01 08:29 — Subject created from Ishai's brain dump. Seed stage. Awaiting more detail.