Ever tried to give feedback and felt like you were juggling a dozen loose‑ended ideas at once?
One minute you’re praising a project, the next you’re warning about missed deadlines, and before you know it you’ve left the conversation feeling… well, a little flat.
What if there was a simple, tasty‑sounding shortcut that kept every feedback session balanced, clear, and actually useful?
Enter the Burrito mnemonic—a five‑step recipe for performance feedback that sticks in your mind (and maybe even your stomach).
What Is the Burrito Mnemonic
Think of the word burrito as a checklist, not a food order. Each letter stands for a core component of effective feedback:
| Letter | Meaning | Quick reminder |
|---|---|---|
| B | Behavior – what the person actually did | Observe, don’t assume |
| U | Impact – the effect of that behavior | Why it matters |
| R | Result – the outcome, good or bad | Data, not drama |
| R | Request – what you’d like to see change or continue | Clear next steps |
| I | Inquire – ask for their perspective | Two‑way conversation |
| T | Timing – when to discuss and follow‑up | Right moment, right frequency |
| O | Outcome – the agreed‑upon plan and accountability | Close the loop |
It’s not a random string of letters. The sequence mirrors how a conversation naturally unfolds: you start with the facts, explain why they matter, discuss the result, propose a move forward, invite the other person’s view, set the timing, and seal the outcome.
In practice, the Burrito mnemonic works for any setting—annual reviews, quick check‑ins, or even peer‑to‑peer coaching. The beauty is that you can mentally “unwrap” the steps in real time, keeping the talk focused and constructive.
Why It Matters / Why People Care
Feedback is the lifeblood of growth, but it’s also the most dreaded HR buzzword. When delivered poorly, it can demotivate, breed resentment, or simply be ignored That's the part that actually makes a difference. But it adds up..
Here’s the short version: the Burrito framework eliminates ambiguity. It forces you to separate what happened from why it matters, and from what should happen next. That separation does three things:
- Reduces defensiveness – People hear “I saw X behavior” instead of “You’re terrible at Y.”
- Boosts clarity – Both giver and receiver know exactly what the next steps are.
- Creates accountability – With a clear outcome and timing, follow‑up becomes a given, not an afterthought.
Turns out, most feedback failures stem from skipping one of those steps—usually the “Impact” or the “Request.” The Burrito mnemonic makes sure you never leave those gaps.
How It Works
Below is the step‑by‑step guide to using Burrito in a real conversation. Feel free to adapt the language to your style; the skeleton stays the same.
B – Behavior
Start with observable actions, not interpretations.
- Do: “In the last sprint, you committed code to the repo at 10 p.m. without running the unit tests.”
- Don’t: “You’re always careless with quality.”
The key is specificity. Mention the when, what, and where so the other person can’t dispute the fact.
U – Impact
Explain why that behavior matters to the team, project, or business.
- Do: “When code lands untested, it caused the build to break for the whole team, delaying our release by two days.”
- Don’t: “Your sloppiness is hurting us.”
Link the behavior to tangible outcomes. That connection turns a simple observation into a meaningful conversation Not complicated — just consistent..
R – Result
Distinguish the result from the impact when needed. Sometimes the impact is the result, but often you want to highlight metrics or data.
- Do: “Our defect rate rose from 2% to 5% that week, and we logged an extra 8 hours of rework.”
- Don’t: “We’re all suffering because of you.”
Numbers keep the talk grounded and prevent it from feeling like a personal attack Easy to understand, harder to ignore..
R – Request
Now tell them what you’d like to see change—or continue. Be concrete and actionable Small thing, real impact..
- Do: “Going forward, could you run the full test suite locally before pushing, and flag any failures in the pull request?”
- Don’t: “Just be more careful next time.”
Specific requests give the receiver a clear target to aim for.
I – Inquire
Open the floor. This is where you turn a monologue into a dialogue.
- Do: “How do you feel about the current testing workflow? Anything that’s getting in the way?”
- Don’t: “That’s it, I’m done.”
Listening shows respect and often uncovers hidden obstacles—maybe the test suite is slow, or the developer lacks proper tooling.
T – Timing
Agree on when you’ll revisit the topic. Timing can be a single follow‑up meeting or a recurring check‑in.
- Do: “Let’s touch base in two weeks to see how the new process is working.”
- Don’t: “I’ll just assume it’s fixed.”
Setting a timeline signals that you’re serious about the change and that you’ll hold both parties accountable.
O – Outcome
Wrap up with a concise summary of what was agreed upon. Write it down if possible.
- Do: “So, you’ll run tests before pushing, we’ll meet on the 15th, and I’ll share a quick guide on optimizing the test suite.”
- Don’t: “Okay, good talk.”
A clear outcome prevents the conversation from evaporating into “we said we’d do something” later on.
Common Mistakes / What Most People Get Wrong
-
Skipping the Impact – Jumping straight from behavior to request leaves the why vague. The receiver wonders, “Why does this matter?” and may dismiss the request.
-
Being Vague on the Request – “Do better” is a dead‑end. Without a concrete action, there’s nothing to measure Small thing, real impact..
-
Forgetting the Inquire Step – Feedback is a two‑way street. Ignoring the other person’s perspective can breed resentment and miss systemic issues.
-
Overloading the Conversation – Trying to cover multiple behaviors in one Burrito session turns it into a buffet of criticism. Stick to one main point per meeting.
-
Neglecting Timing – If you don’t set a follow‑up, the feedback becomes a one‑off comment that quickly fades from memory.
By being aware of these pitfalls, you can keep your Burrito feedback tight, tasty, and effective It's one of those things that adds up..
Practical Tips / What Actually Works
- Prep a mini‑script – Jot down B‑U‑R‑R‑I‑T‑O bullets before the meeting. It’s okay to glance at them; it keeps you on track.
- Use “I” statements – “I noticed…” sounds less accusatory than “You always…”.
- Pair with a visual – A quick whiteboard sketch of the process can reinforce the steps for visual learners.
- Keep it brief – Aim for a 5‑minute Burrito for routine feedback; 15‑20 minutes for performance reviews.
- Document the outcome – A one‑sentence email recap ensures everyone remembers the agreed next steps.
- Practice with low‑stakes scenarios – Try the Burrito on a coffee break chat before using it in a formal review.
These tricks turn the mnemonic from a mental note into a habit that sticks.
FAQ
Q: Can I use Burrito for negative feedback only?
A: No. The same structure works for praise—just flip the tone. “Behavior: you delivered the client deck early; Impact: it gave us extra time to refine; Result: the client was thrilled; Request: keep sharing drafts early; Inquire: any tools you need?; Timing: next project; Outcome: we’ll continue this cadence.”
Q: What if the person reacts defensively?
A: Lean heavily on the Behavior and Impact steps. Stick to facts, pause, and invite their view with the Inquire step. It diffuses tension.
Q: Is the order fixed?
A: Generally yes, because each step builds on the previous one. You can loop back—e.g., after Inquire you might need to clarify Impact—but keep the core sequence Simple as that..
Q: How long should the “Timing” step be?
A: Whatever feels right for the issue. For a minor tweak, a week may suffice; for a major behavior change, a month or a series of check‑ins works better.
Q: Can I use Burrito in written feedback?
A: Absolutely. Structure the email with bolded headings for each letter (just not as H2/H3) to guide the reader through the same flow.
So there you have it—a full‑flavored, easy‑to‑remember framework that turns a dreaded feedback session into a clear, constructive conversation.
Next time you’re gearing up to talk performance, just think: Burrito. Grab a mental wrap, fill it with the right ingredients, and serve it up. Your team will thank you, and you’ll finally feel like you’re feeding growth—not just criticism.
