Flash Tags for Calibrated Feedback
Tag every piece of feedback FYI, Suggestion, Recommendation, or Plea so teams know how hard to weigh it.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 90%
A shared four-level vocabulary that tells the receiver exactly how much to weight a piece of feedback, using a 'hill to die on' metaphor. It stops teams from over- or under-interpreting input and prevents every comment from being treated with equal, velocity-killing weight.
Origin
Created by Dharmesh Shah (co-founder/CTO of HubSpot), who presented it at one of Coda's rituals dinners. Shackleton adopted it at Coda, where it's now used inside Coda docs and in meetings.
Core principles
- 01Uncalibrated feedback gets over- or under-interpreted
- 02Feedback should be weighted, not treated uniformly
- 03A senior leader's superpower is knowing which of their inputs are FYIs vs pleas
- 04Shared language forces the giver to decide how strongly they actually feel
How to run it
- 1
Adopt the four tags
Establish the ladder: FYI ('a thought, take it or leave it — no hill in sight'), Suggestion ('a hill I'm not going to die on, this is what I'd do'), Recommendation ('I'm climbing the hill, I've thought hard about this, don't ignore it'), Plea ('trust me, this really matters — used rarely').
Pro tip The escalating 'hill to die on' metaphor makes the levels intuitive and memorable.
Watch out A Plea should be rare; overuse destroys its signal.
- 2
Tag each piece of feedback as you give it
In a feedback table, attach one of the four tags via a select list next to your comment, including the description so you must consciously choose your intensity.
Pro tip Choosing the tag forces you to ask whether you really feel that strongly.
Watch out Without the tag, every comment reads as equally urgent.
- 3
Triage by tag
Sort the feedback and spend your time where it matters: if 100 pieces come back with one Plea, focus there; a pile of FYIs can be left alone.
Pro tip In live meetings just ask 'is that a recommendation or a plea?' to force the caller to calibrate.
Watch out Skipping triage means drowning in a flat list of 100 equal-looking comments.
In the wild
A teammate gave a lightning talk at a Coda offsite on how valuable flash tags had been: 'we got 100 pieces of feedback and there's like one Plea — okay let's spend our time on that.'
→ The team could quickly triage a large feedback pile to the few items that truly mattered, protecting velocity.
Common mistakes
Treating all feedback the same
When every comment carries equal weight, teams feel they must address all 100 pieces, which slows everything down; distinguishing importance makes sorting fast.
Overusing the Plea tag
A Plea signals 'really trust me on this'; if it's used often it loses meaning and the calibration collapses back to a flat list.
Is it for you?
Best for
Teams and leaders drowning in feedback where seniority makes offhand comments get over-actioned
Not ideal for
Very small teams with tight trust where feedback weight is already obvious
From the transcript
“so he outlines four flash tags”
“recommendation is like I'm climbing the hill I'm not going to die here but like I've thought about this a lot so like don't ignore…”
From the episode
What sets great teams apart
Lane Shackleton (CPO of Coda)