Collection

Turn feedback into one behavior that can actually change

Design, give, receive and follow up on performance feedback as an evidence-to-behavior loop: observable events, proportionate impact, one next action, barriers, rehearsal and short-cycle verification.

16 elements · Explore in any order.

2 heuristics · 4 principles · 9 protocols · 1 question

Narrow your search

16 elements

Protocol

Define the behavior before opening the feedback conversation

Feedback cannot change a noun.

Read the idea
Principle

Separate the observation from the story about the person

The observation is shareable evidence; the motive is usually a hypothesis.

Read the idea
Protocol

Name the work impact without inflating it

Impact connects behavior to the shared task, not to moral judgment.

Read the idea
Principle

Ask for one next behavior, not a personality renovation

A change request should fit inside the next real opportunity to use it.

Read the idea
Protocol

Make the receiver reconstruct the message

Sent is not the same as understood.

Read the idea
Question

Ask what makes the better behavior hard

A behavior gap may be a skill, tool, priority or system gap.

Read the idea
Heuristic

Choose a source that actually saw the work

More opinions do not automatically mean more information.

Read the idea
Protocol

Move feedback close enough to the event to keep the evidence

Delay converts examples into impressions.

Read the idea
Principle

Separate coaching from the formal judgment

People seek less useful feedback when every question becomes evidence against them.

Read the idea
Principle

Do not hide the corrective point inside a praise sandwich

Kindness is useful; ambiguity is not.

Read the idea
Protocol

Turn feedback into a rehearsal before the real repeat

Agreement is not yet performance.

Read the idea
Protocol

Track the next two opportunities, not the next six months

Early repetition tells you whether the change is becoming operational.

Read the idea
Heuristic

Aggregate repeated signals before turning them into an identity

Patterns are stronger than anecdotes, but labels can still overreach.

Read the idea
Protocol

Facilitate multisource feedback before demanding an action plan

A pile of ratings is data, not yet an improvement plan.

Read the idea
Protocol

Receive feedback in two passes: signal first, verdict later

You can extract information without surrendering judgment.

Read the idea
Protocol

Close the feedback loop by reporting the change

Feedback systems improve when outcomes return to the source.

Read the idea