Back to list
Coowoolf

flashtag-communication-protocol

by Coowoolf

105 Product Management Skills extracted from Lenny's Podcast - For use with Claude Code / Cursor / Windsurf

1🍴 0📅 Jan 24, 2026

SKILL.md


name: Flashtag Communication Protocol description: Use explicit tags (#fyi, #suggestion, #recommendation, #plea) in written communication to clarify the expected weight and required response level. Eliminates the "Founder Megaphone" problem.

The Flashtag Communication Protocol

"The challenge is people will take [an opinion] and over-index on what was an opinion... Flashtags are an escalating set of the 'dying on the hill' spectrum." — Dharmesh Shah

What It Is

A system of explicit tags used in written communication (email, Slack) that clearly defines the expected weight of the feedback and the required response level.

When To Use

  • Whenever a leader provides feedback to a subordinate
  • In async communication channels (Slack, email)
  • When there's a history of offhand comments becoming mandates
  • To preserve team autonomy while still sharing opinions

The Four Flashtags

┌──────────────────────────────────────────────────────┐
│  #fyi                                                │
│  "I found this interesting."                         │
│  → No response expected. Go on with your life.       │
├──────────────────────────────────────────────────────┤
│  #suggestion                                         │
│  "A thought I had."                                  │
│  → You don't have to do it. Consider it. No reply.   │
├──────────────────────────────────────────────────────┤
│  #recommendation                                     │
│  "I have researched this. I would do this."          │
│  → If you don't do it, explain why (learning loop).  │
├──────────────────────────────────────────────────────┤
│  #plea                                               │
│  "I beg of you. High conviction. Please do this."    │
│  → Use EXTREMELY rarely (count on one hand).         │
└──────────────────────────────────────────────────────┘

How To Apply

STEP 1: Before Sending Feedback
└── Ask: "How strongly do I feel about this?"
└── Choose the appropriate tag

STEP 2: Add Tag to Message
└── "#suggestion: Have you considered..."
└── "#recommendation: Based on X, I'd do Y..."

STEP 3: Respect the System
└── Don't follow up on #fyi or #suggestion
└── Only expect response for #recommendation+

STEP 4: Track #plea Usage
└── Should be extremely rare (1-2x per year)
└── If overused, loses meaning

Common Mistakes

Overusing #plea (turns into micromanagement)

❌ Following up aggressively on #suggestion (defeats purpose)

❌ Not using any tags (defaults to "founder megaphone")

Real-World Example

Dharmesh uses these daily at HubSpot to give product feedback without disempowering the specific product owners (DRIs).


Source: Dharmesh Shah, Lenny's Podcast

Score

Total Score

55/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

0/5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon