Process-Focused Feedback¶
Method — instantiates Self-Handicapping Disruption
Responds to effort, strategy, revision, and next action rather than global labels about talent, character, or worth.
Process-Focused Feedback is a way of talking about someone's work whose whole grammar is about the work and its trajectory, never the person. The one idea that makes it this mechanism: it refuses global labels — "brilliant," "careless," "not cut out for this" — and instead names what was attempted, which strategy was used, what the evidence shows, and the single next move. It is not a diagnosis of why the person struggled and it is not a scheduled forum; it is the content of the response itself. Its job is to make being evaluated survivable, so that showing effort stops being a wager on one's worth and becomes just a way to find the next correction.
Example¶
A senior engineer is reviewing a junior developer's first substantial pull request. The junior has been opening PRs late and only when they are "perfect," because a critical review feels like a verdict on whether he really belongs on the team. Rather than "this is sloppy" or the equally unhelpful "great instincts," the senior comments on process: "The retry logic doesn't handle the timeout path — add a test that forces the timeout, and the fix falls out of that." Every note points at a code path and a next action; none point at the developer. Over a few reviews the pattern shifts: he starts opening draft PRs early, because the feedback attaches to lines of code and their revision, not to a judgment about whether he is a "real" engineer.
How it works¶
- Target one of five process objects. Effort, strategy, evidence, revision, or next action — pick the one the moment needs and speak to it specifically.
- Strip the global adjective. Remove person-nouns and trait words; if a sentence would survive being said about the code instead of the coder, keep it.
- End on one next move. Every response closes with a single, doable revision, so the feedback opens a path rather than delivering a score.
Tuning parameters¶
- Specificity — how granular the process object is; finer notes are more actionable but can overwhelm and read as nitpicking.
- Affirm-to-correct ratio — how much confirming vs. redirecting; too much affirmation hollows out, too little re-threatens.
- Latency — immediate vs. batched feedback; immediate is more usable, batched is calmer but staler.
- Channel privacy — one-to-one vs. in front of the team; privacy lowers threat, visibility spreads the learning.
When it helps, and when it misleads¶
Its strength is that it makes revision safe: a person who hears their approach discussed, not their worth, can afford to show unfinished work. Its failure mode is process praise curdling into empty positivity — cheering "effort" on a strategy that is quietly failing, so the feedback stops telling the truth about whether the approach works.[n1] The classic misuse is praising hard work on a doomed method to protect feelings, which teaches the recipient that effort and results are unrelated. The guarding discipline is that process feedback must still be honest about whether the strategy is getting there — it separates identity from performance without suspending judgment of the work.
How it implements the components¶
identity_performance_separation— its defining move: the response speaks about work and trajectory, keeping the person out of the sentence.process_accountability— it holds the actor to attempted strategy, effort, and revision rather than to the raw outcome.revision_path— every response ends pointing at the next attempt, so a setback reads as a step, not a verdict.
It does not diagnose why the obstacle arose in the first place — probing what a delay protects and whether it reflects a real_constraint_check on top of the protective_obstacle is the work of its method-twin obstacle_function_review, not this feedback. Nor is it the discrete post-setback partition protocol that sorts causes via real_constraint_check once an outcome has already failed — that is failure_debrief_without_global_label; this feedback is instead the continuous grammar of response to work still in progress.
Related¶
- Instantiates: Self-Handicapping Disruption — supplies the identity-safe response content the pattern depends on.
- Consumes: low_stakes_draft — feedback needs a piece of visible early effort to respond to.
- Sibling mechanisms: obstacle_function_review · safe_accountability_check_in · low_stakes_draft · private_commitment_window · effort_tracking_rubric · failure_debrief_without_global_label · low_stakes_rehearsal
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Process-Focused Feedback operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it responds to effort, strategy, revision, and next action rather than global labels about talent, character, or worth.
Independent corroboration: The frozen evidence defines Process-Focused Feedback as 'Responds to effort, strategy, revision, and next action rather than global labels about talent, character, or worth', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Education & Pedagogy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Process-Focused Feedback is most plausibly rooted in the education_pedagogy tradition because its characteristic form depends on instruction, learning progression, assessment, and scaffolded practice. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Related originating lineages:
- Psychology — The psychology tradition materially shaped Process-Focused Feedback through its own practice of individual cognition, motivation, judgment, and behavior.
Review resolution: Both blind reviewers agree that education pedagogy is the primary origin. Explicit reconciliation resolves origin mode disagreement, domain reach disagreement. Formative alternate lineages are retained as psychology; later breadth of use is recorded separately as domain_reach=universal, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In Carol Dweck's research on praise, feedback aimed at process — strategy, effort, choices — supports persistence, whereas praise aimed at fixed ability ("you're so smart") leaves learners more fragile after failure. Process-Focused Feedback generalizes the distinction to correction as well as praise. ↩