Processing Feedback

When feedback arrives, don't react — process it:

1. Separate signal from tone. Extract the actionable content regardless of how it's phrased.
2. Restate the core issue in one sentence to confirm understanding.
3. Classify it: factual error, stylistic preference, missed requirement, or misunderstanding.
4. Act: fix, ask, or push back with reasoning — never argue defensively.

Example response pattern:

"Got it — the issue is [X]. That happened because [brief reason, not excuse]. Fixing by [concrete action]."

Progress:

• Step 1: Read/listen to feedback fully before responding
• Step 2: Identify the underlying issue (not just the surface complaint)
• Step 3: Classify feedback type
• Step 4: Check for patterns across past feedback
• Step 5: Apply the fix or clarify if ambiguous
• Step 6: Confirm resolution, don't over-apologize

Step 1: Absorb fully Read/listen to the entire critique before formulating a response. Don't start defending mid-way through.

Step 2: Identify the real issue Feedback is often imprecisely worded. "This feels off" might mean tone, structure, or a factual gap. Dig for the specific, actionable core.

Step 3: Classify

• Factual/objective error → fix immediately, no debate needed
• Stylistic/subjective preference → adapt to it, it's the stakeholder's call
• Missed requirement → check if it was stated; if yes, correct and note; if no, clarify scope
• Misunderstanding of the work → clarify without being defensive, provide context once

Step 4: Pattern-check Is this the second time this type of issue has come up? If so, address the root cause (e.g., a checklist item to prevent recurrence), not just this instance.

Step 5: Apply Make the fix. If feedback conflicts with other requirements, surface the tradeoff explicitly rather than silently picking one side.

Step 6: Close the loop Confirm the fix addresses the concern. One acknowledgment is enough — excessive apology or self-flagellation adds noise, not value.

Example 1: Input: "This analysis is too shallow, you barely scratched the surface." Output: "Understood — the depth issue is likely in [specific section], which only covers the surface metric without root-cause analysis. I'll add a breakdown of contributing factors and quantify their impact. Will have the revised version in [timeframe]."

Example 2: Input: "I don't like how this is written." (vague, no specifics) Output: "To fix this precisely — is the concern more about tone (too formal/casual), structure (ordering of points), or content (missing/extra info)? I want to target the actual issue rather than guess."

Example 3: Input: Critique turns out to be based on a misunderstanding — reviewer missed a section that already addresses their concern. Output: "That's covered in [section/line] — want me to make it more prominent so it's easier to spot, or is there something that section doesn't address?" (No "you didn't read it" — assume the miss is a legibility problem, fix the legibility.)