Best-Practices Feedback Loop
Turn every correction into a documented rule the team must rediscover.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
The Best-Practices Feedback Loop converts routine managerial feedback into reusable organizational knowledge. A team maintains a platform- or task-specific guide containing standards, examples, and the reasoning behind recurring preferences. When a manager finds a problem, the contributor is not merely told what to change. Instead, the contributor searches the guide, identifies the violated rule, explains why it applies, and then corrects the work. If the guide does not cover the issue, the team adds a new rule. This creates a closed loop in which mistakes strengthen both individual judgment and the shared system. Codie Sanchez uses this approach to train social-media staff to reproduce her tone instead of depending indefinitely on line-by-line edits.
Origin
Extracted from The Jasmine Star Show through Codie Sanchez's description of platform-specific best-practices documents.
Core principles
- 01Corrections should improve the system, not only the current deliverable.
- 02People learn more when they identify the governing rule themselves.
- 03A living guide makes subjective preferences teachable.
- 04Repeated feedback reveals where documentation is incomplete.
How to run it
- 1
Create the Guide
Document the rules, examples, tone decisions, and quality standards for a recurring task. Make the guide easy for contributors to search.
Pro tip Pair each subjective rule with a concrete positive and negative example.
Watch out A vague style guide will not support reliable self-correction.
- 2
Flag the Problem
Identify the problematic output without immediately rewriting it for the contributor. Direct attention to the relevant type of issue.
Pro tip Describe the impact of the problem without supplying the full answer.
Watch out Do not turn discovery into humiliation or an artificial obstacle.
- 3
Require Rule Discovery
Ask the contributor to locate and explain the rule that the output violates. This forces active retrieval rather than passive compliance.
Pro tip Have the contributor cite the exact guide section in the revision.
Watch out Do not insist on finding a rule that was never documented.
- 4
Correct and Update
Revise the deliverable according to the rule. Add or clarify documentation when the mistake exposes a genuine gap.
Pro tip Record why the rule exists, not only what it requires.
Watch out Adding a rule for every isolated preference can make the guide unusably complex.
- 5
Check for Recurrence
Monitor future work for the same issue and review whether the guide is producing better judgment. Simplify or strengthen the rule if mistakes continue.
Pro tip Track repeated corrections by category.
Watch out Persistent recurrence may indicate a training or role-fit problem rather than a documentation problem.
In the wild
A new Instagram manager writes a caption filled with expressions that do not match the founder's voice. Rather than silently editing them out, the founder asks the manager to consult the Instagram Best Practices Guide and identify why the language is wrong.
→ The caption is corrected and the manager learns a reusable brand-voice rule for future posts.
A support lead flags an overly defensive response and asks the agent to find the applicable tone and escalation rules in the team's guide. The agent identifies the mismatch, rewrites the response, and adds a new example to clarify an ambiguous rule.
→ The immediate reply improves while the guide becomes more useful for the whole team.
Common mistakes
Fixing Without Teaching
Silently rewriting work resolves the immediate defect but leaves the contributor unable to prevent it next time.
Documenting Rules Without Reasons
Rules are harder to transfer to new situations when contributors do not understand the intended effect.
Blaming People for Missing Rules
A contributor cannot retrieve a standard that the organization never documented or taught.
Is it for you?
Best for
It is best for recurring creative or operational work where quality depends on learnable preferences and standards.
Not ideal for
It is not ideal for novel work where no stable standard exists or for emergencies requiring an immediate correction.
From the transcript
“We have one of those for all platforms.”
“Go to the document and tell me why I don't.”
“Whereas if I just tell them I don't like this, they don't really learn.”
From the episode
Building Boring Businesses, Embracing Questions, and Doing Hard Things with Codie Sanchez
Codie Sanchez