home / skills / coowoolf / insighthunt-skills / flashtag-communication

flashtag-communication skill

/team-leadership/flashtag-communication

This skill helps teams apply explicit feedback tagging to preserve autonomy while clarifying expectations and required responses.

npx playbooks add skill coowoolf/insighthunt-skills --skill flashtag-communication

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.4 KB
---
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*

Overview

This skill teaches the Flashtag Communication Protocol: a simple tagging system (#fyi, #suggestion, #recommendation, #plea) that clarifies how strongly a sender feels about feedback and what response is expected. It reduces assumptions, prevents informal comments from becoming mandates, and preserves team autonomy. The skill gives practical steps to choose tags, add them to messages, and enforce norms.

How this skill works

The protocol inspects the sender’s intent and maps it to one of four explicit tags that communicate expected weight and response level. Senders decide how strongly they feel, prepend the chosen flashtag to the message, and follow the response rules (no reply for #fyi/#suggestion, explanation required for ignoring #recommendation, rare use of #plea). Teams then respect those tags to avoid escalation and confusion.

When to use it

  • Giving feedback as a leader to a direct report
  • Writing async messages in Slack, email, or docs
  • When offhand comments have previously been treated as directives
  • To preserve decision ownership while sharing opinions
  • During design reviews, roadmap conversations, and PR feedback

Best practices

  • Ask yourself “How strongly do I feel?” before sending any feedback
  • Always prepend the chosen flashtag to the message subject or opening line
  • Treat #fyi and #suggestion as non-actionable—do not follow up aggressively
  • If you ignore a #recommendation, provide a short explanation to close the learning loop
  • Use #plea very sparingly (e.g., 1–2 times per year) and track its usage

Example use cases

  • A PM shares market research with #fyi so the team stays informed without changing priorities
  • An engineer offers an alternative approach with #suggestion—team can consider but not compelled to act
  • A leader proposes a migration plan with #recommendation; if the team declines they explain trade-offs
  • A security incident demands urgent action and the CISO uses #plea to signal high conviction
  • A product review thread where contributors tag items to clarify expected responses

FAQ

What happens if someone ignores the tags?

Establish the norm in a kickoff and call out violations gently. If tags are repeatedly ignored, discuss consequences and reinforce expectations in retrospectives.

Can tags be customized?

Yes, teams can adapt naming, but keep the scale of intent and response clear and limited to avoid dilution.