Peer Critique Reflection (The Ambiguity Hunt)
Goal
To practice the "Technical Root" skill of identifying linguistic ambiguity. You will act as a strategic editor for your partner, helping them transform vague "fluff" words into actionable design constraints.
Background Context
As we learned in the Technical Root lesson, ambiguity is the enemy of good design. Words like "easy," "fun," or "intuitive" mean different things to different people (The "Tree Swing" Effect). In this assignment, you will review your partner's 10 Point-of-View (POV) statements and help them rigorously define their terms.
Instructions
Step 1: Exchange Work Exchange your list of 10 POV Statements (5 for Persona A, 5 for Persona B) with your assigned partner.
Step 2: The Audit (Identify the Fluff) Review your partner's statements. You are looking for subjective adjectives or "lazy" phrasing that hides the real problem.
Find at least 3 specific concepts or terms that are ambiguous.
Common "Fluff" Suspects: "Simple," "Easy," "Better," "Modern," "Efficient," "Fun," "Intuitive."
Step 3: The Critique & Revision For the 3 concepts you identified, provide specific feedback on why it is ambiguous and offer a concrete suggestion for how to make it measurable or specific.
Ask: "How would we measure this?" or "What does this actually look like?"
The Deliverable
Please submit a single document (PDF or Word) containing the following:
1. Your Partner's Name: [Name]
2. The Source Material: Copy and paste the 3 POV statements you chose to critique from your partner's original list.
3. The Critique (The Audit): For each of the 3 statements, provide the following:
The "Fluff" Word: (e.g., "Seamless")
The Problem: Explain why this word is dangerous. (e.g., "Seamless is vague. Does it mean fast? Does it mean no login required? Does it mean it works offline?")
Suggested Revision: Rewrite the POV or the specific phrase to be an actionable constraint.
Example: Change "Needs a seamless parking experience" to "Needs to find a parking spot without stopping their car for more than 30 seconds."
Please save your file as Lastname_PeerCritique.pdf
Example Entry
Original POV: "Liam needs a super fast way to park because he is stressed."
Critique: "Super fast" is subjective. To a pedestrian, that’s 10 minutes; to a driver, that’s 2 minutes. Also, "stressed" is a generic emotion—what is the root cause?
Suggestion: "Liam needs guaranteed certainty of a spot availability before he leaves home so he can eliminate the variable of 'hunting' from his commute."
Identification (5pts): Spotted 3 ambiguous terms.
Diagnosis (5pts): Explained the risk of the ambiguity.
The Binary Test (10pts): Suggested revisions are strictly measurable (Pass/Fail).
Professionalism (5pts): Constructive tone and correct formatting.
Evaluation
Identification (5pts): Spotted 3 ambiguous terms.
Diagnosis (5pts): Explained the risk of the ambiguity.
The Binary Test (10pts): Suggested revisions are strictly measurable (Pass/Fail).
Professionalism (5pts): Constructive tone and correct formatting.
Criteria Category | Description & Requirements | Grading Check (How to Earn Points) | Points |
1. Identification of Ambiguity | Did the student correctly identify 3 distinct instances of "fluff" or subjective language in their partner's work? | Full Points: Student spotted classic ambiguity traps (e.g., "Easy," "Better," "Fun," "Seamless"). Zero Points: Student critiqued valid, measurable constraints instead of ambiguous ones. | 5 |
2. The Diagnosis (Why it Fails) | Did the student clearly explain why the identified word is dangerous to the project scope or execution? | Look for Risk Analysis: The explanation cites specific risks, such as "The engineer will have to guess" or "This attribute cannot be tested." Reference: "If the instructions are vague, the engineer has to guess." | 5 |
3. The "Binary Test" (Revision Quality) | (Weighted) Did the student’s suggested revision pass the "Technical Root" standard? Is it objective? | The Pass/Fail Check: • Pass: Revision is measurable (e.g., "Must load in under 2 seconds"). • Fail: Revision is still subjective (e.g., "Must load quickly"). Reference: "It is binary: Pass or Fail." | 10 |
4. Professionalism & Tone | Was the feedback delivered in a helpful, collaborative manner? Was the document formatted correctly? | Easy Points: • Did they follow the formatting instructions? • Is the tone constructive (e.g., "We should clarify...") rather than dismissive (e.g., "This is wrong"). | 5 |
TOTAL | 25 |
Locked Message