TACS Feedback
Make feedback tactical, actionable, concrete, and specific enough to use.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 98%
TACS Feedback makes direct communication useful by requiring it to be tactical, actionable, concrete, and specific. Instead of issuing a verdict, dropping a vague hint, or forcing an employee to guess the manager's hidden opinion, the reviewer names the problem and explains the logic behind the assessment. This gives the recipient enough context to improve the current artifact and recognize similar issues later. The leader can still ask questions, but should first contribute a real observation—for example, identifying excessive cognitive load before asking where it appears. The recipient then practices solving the problem without having to discover what the manager secretly believes. TACS preserves candor while reducing ambiguity, and it reframes detailed criticism as an investment in the person's craft rather than an emotional attack.
Origin
Wes Kao introduced the TACS acronym while explaining why people often appreciate severe edits when the reviewer supplies care, reasoning, and usable detail.
Core principles
- 01Directness requires explanation, not abrasiveness.
- 02Useful feedback gives the recipient something they can do.
- 03Reasoning helps people generalize beyond one edit.
- 04Specificity demonstrates care and effort.
- 05Questions work best after the leader states the observed problem.
How to run it
- 1
Name the issue
State what you observe without hiding the opinion inside a vague question. Keep the claim focused on the work or behavior.
Pro tip Use a sentence such as “I think there is too much cognitive load here.”
Watch out Do not use directness as permission to say every unfiltered thought.
- 2
Explain the reasoning
Share the logic, evidence, and thought process that produced your conclusion. Clarify why the issue matters to the intended outcome.
Pro tip Describe the audience or business consequence of leaving the issue unchanged.
Watch out A mic-drop verdict leaves the recipient to perform all the interpretive work.
- 3
Make it actionable
Indicate what kind of change would improve the work. Supply enough direction that the recipient can take a meaningful next step.
Pro tip Distinguish essential details from distracting ones.
Watch out Avoid feedback so broad that success remains undefined.
- 4
Let them solve
After stating the problem, ask the recipient to identify where it appears or propose how to fix it. This develops judgment without concealing your own view.
Pro tip Ask, “Where do you see the cognitive load?” after naming it.
Watch out Do not ask soft questions designed only to steer someone toward an undisclosed answer.
- 5
Extract the pattern
Explain why the edit improves the work and identify the reusable lesson. Help the recipient recognize the pattern independently in future projects.
Pro tip Connect the correction to a broader craft principle.
Watch out Fixing the artifact without teaching the pattern creates repeat dependence.
In the wild
A manager reviewing customer email copy states that the draft creates too much cognitive load. Rather than rewriting everything immediately, the manager asks the writer to locate the load. The writer notices that the draft emphasizes too many irrelevant details and spends too long on a minor point.
→ The email becomes clearer, and the writer practices diagnosing cognitive load independently.
A leader marks extensive problems in a piece of work but pairs every major edit with concrete reasoning and a practical improvement. The recipient can see both what changed and why the revised version is stronger.
→ Detailed criticism becomes a coaching artifact that improves future pattern recognition.
Common mistakes
Using directness as an excuse
Unfiltered abrasiveness is lazy because it ignores how the recipient can understand or use the message. Direct feedback still requires framing and restraint.
Hiding the opinion in questions
Repeatedly asking whether something is right forces the employee to guess the manager's preferred answer. State the concern, then invite problem-solving.
Giving only the what
A verdict without the why or how does not teach judgment. The recipient may make the requested edit but repeat the same class of mistake later.
Is it for you?
Best for
It is best for managers, editors, and creative leaders reviewing work where quality depends on nuanced judgment.
Not ideal for
It is not ideal for simple binary corrections that require no explanation or developmental coaching.
From the transcript
“being direct is uh saying what you think sharing your recommendation sharing your observation exactly without mincing words and sharing your logic rationale and thought…”
“feedback that is tactical actionable concrete and specific I call it tax Tacs”
“if you hit those elements the person is able to do something with that feedback they're able to learn from it they're able to pattern…”
From the episode
Everything I Learned From Seth Godin in 50 Minutes - Wes Kao
Wes Kao