performance-feedback-author

Overview

Most performance feedback fails on the same axis: it describes the manager's impression ("not detail-oriented enough", "great team player") instead of the person's behavior, so the recipient can neither verify it nor act on it. The Center for Creative Leadership's SBI model fixes the shape: clarify the Situation with a precise time and place rather than a vague window ("this morning at the 11 am team meeting", not "last week"); describe the specific observable Behaviors without judgment (someone "interrupted me while I was telling the team about the monthly budget", not someone "was rude"); explain the Impact the behavior had, including the genuine effect on you ("impressed", "frustrated", "troubled"). CCL extends it to SBII by adding an Intent inquiry - asking "What were you hoping to accomplish with that?" - which turns delivery into a two-way conversation and replaces negative assumptions about motive. CCL's claim for the format is practical: it "reduces anxiety around giving feedback" and decreases defensiveness in recipients. (All of the above: CCL, "Closing the Gap Between Intent vs. Impact: SBII", fetched 2026-06-10.)

This skill adds the QA-specific half: in a testing team, the Behavior component should come from work artifacts, which are abundant and citable - bug reports, test cases, automation PRs, review comments, charter logs, CI history. Feedback built on artifacts survives challenge; feedback built on recollection does not.

When to use

• A tester did something this week that deserves specific feedback, positive or corrective, and the manager wants it in deliverable shape before the next 1:1.
• Review season: the manager owes written review input per tester and wants it evidence-based rather than adjective-based.
• A promotion case needs assembling against the ladder's evidence list.
• Peer-feedback requests arrive and the team needs a format that keeps them concrete.

Do not use this skill to:

• Plan the meeting where feedback is delivered - that is tester-one-on-one-planner.
• Update the team capability map - that is skill-matrix-author; mixing performance judgments into the matrix corrupts it as a planning tool.
• Run disciplinary or termination processes - those are HR-owned with legal constraints outside this marketplace's scope.

Step 1 - Capture the inputs

Step 2 - Mine the artifacts for Behavior candidates

For each feedback theme, locate the artifact before writing a word. QA work leaves a wide evidence trail:

Rule: no Behavior statement without a linkable artifact or a first-person observation with date and place. Secondhand reports ("people say...") are not Behavior; either observe directly, collect the reporter's own SBI, or drop the theme.

Step 3 - Draft each item as SBI(I)

Worked example, corrective, artifact-backed:

**Situation:** In Tuesday's triage meeting (2026-06-02), reviewing bug #4821,
the payment-retry failure you filed on Friday.

**Behavior:** The report had a one-line description, no reproduction steps, and
no environment block. Dev returned it as cannot-reproduce, and you re-filed it
with full steps on Monday (#4838) - those steps reproduced first try.

**Impact:** We lost two working days on a P2 in the payment path, and the
developer's first hour went into guessing context your Monday version supplied
in full. When your reports carry reproduction steps, like #4838 or #4640 from
May, they typically clear triage in one pass. I want that to be the default.

**Intent (ask, then listen):** What was happening on Friday when you filed the
first version - what were you trying to get done?

Worked example, positive, same discipline:

**Situation:** During the 2026-Q1 charter sessions on checkout (your session
log, weeks 3 - 14).

**Behavior:** You logged 31 charter-based sessions and your session notes
flagged the cart-merge timing issue that became P1 #4512 before it shipped,
including a recorded repro.

**Impact:** Two of the quarter's three would-be P1 escapes were caught in your
sessions; the cart-merge catch alone avoided a production incident in the
revenue path. I used your session notes as the example in the team's charter
workshop - I was genuinely impressed by the audit trail.

The positive example follows the identical Situation/Behavior/Impact discipline (CCL); vague praise ("great quarter!") wastes signal exactly the way vague criticism does. The Intent step is most valuable on corrective items: per CCL it surfaces the gap between what the person intended and the impact that landed, instead of assuming motive.

Step 4 - Assemble into the purpose-shaped output

• Immediate feedback: one SBI(I) item, delivered in the next 1:1's feedback segment (the tester-one-on-one-planner agenda reserves 5 minutes). Feedback delivered within a week of the event beats a stockpile at review time; The Manager's Path (Camille Fournier, O'Reilly 2017, ISBN 978-1491973899) frames this as building a culture of continuous feedback, with the written review as a summary of conversations already had, never a surprise.
• Review input: 4 - 8 SBI items spanning the window, grouped by the ladder axes, each citing its artifact, plus a one-paragraph synthesis. Strengths and growth areas both artifact-backed.
• Promotion case: the level's observable-evidence list from career-ladder-author, with one artifact-cited SBI item per evidence line, and explicit gaps marked [NO EVIDENCE YET] rather than papered over.

Anti-patterns

Limitations

• Artifacts do not cover everything. Mentoring, meeting behavior, and cross-team communication often leave thin trails; those items rest on dated first-person observation, clearly marked as such.
• Outcome metrics are confounded. Escape counts depend on area risk, not only on the tester; use outcome data to find themes, never as a verdict by itself.
• Calibration is out of scope. Cross-team rating fairness is a management-chain process; this skill makes one manager's input evidence-based, which is the precondition, not the whole.
• Not an HR instrument. Performance-improvement plans, disciplinary records, and termination documentation have legal requirements this skill does not address.

Hand-off targets

• Deliver it → tester-one-on-one-planner (the feedback segment of the next 1:1).
• Promotion case against level criteria → career-ladder-author.
• Theme is a skill gap, not a performance issue → skill-matrix-author and a growth thread instead of corrective feedback.

References

• Center for Creative Leadership, "Closing the Gap Between Intent vs. Impact: SBII" - the Situation / Behavior / Impact model, the Intent extension, precision guidance and the anxiety/defensiveness claims used throughout: https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-vs-impact-sbii/ (fetched 2026-06-10).
• Camille Fournier, The Manager's Path, O'Reilly 2017, ISBN 978-1491973899 - continuous-feedback culture, writing and delivering performance reviews ("Managing People" chapter).
• tester-one-on-one-planner, career-ladder-author, skill-matrix-author - sibling skills in the delivery, promotion, and capability paths.