---
id: int.critique_injected_on_script_in_the_collaborative_exercise
type: intervention
title: "Critique injected on script in the collaborative exercise"
lang: en
registry: 1.1.0
canonical: https://hoba.work/interventions/int.critique_injected_on_script_in_the_collaborative_exercise
json: https://hoba.work/api/v1/interventions/int.critique_injected_on_script_in_the_collaborative_exercise.json
---

# Critique injected on script in the collaborative exercise

The collaborative round carries a written script: the same objection is raised at the same point for every candidate, and the panel records what was said in response rather than how the room felt.

## At a glance

- Actor: hiring manager
- Scope: team
- Cost: low
- Evidence: supported

## What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

**The script, and the line it produces** — *reconstruction*

```
> 00:18  Scripted at minute 18, verbatim for every candidate: "I think this design is wrong — you have put the queue in the wrong place."
  00:19  Recorded: asked which failure the objection was about; restated the trade-off; proposed moving it and named what that would cost.
  00:31  Not recorded: tone, warmth, whether the room enjoyed it. The rubric has no column for it, so no column carries it.
```

*What to notice* Friction in a collaborative exercise is a real signal, and this does not deny it — it makes it comparable. Unscripted, the objection arrives when an interviewer happens to feel like raising it, in words chosen for that candidate, and what comes back is scored against a memory of how other rounds went. Scripted, the same prompt produces answers that can be set side by side.

## From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

### Hiring manager

- **What reaches them:** A one-page script with the objection, the minute it lands, and the three things the answer is scored on.
- **What it means from there:** What the panel disagreed about was never the candidate — it was which objection each interviewer raised and how hard. Fixing the prompt leaves only the answer to disagree about.
- **What happens next:** Writes the script once per role, and holds the panel to scoring the response rather than the room.

### Candidate

- **What reaches them:** An objection that arrives as part of the exercise, and a rubric that names what the answer is being read for.
- **What it means from there:** The pushback is the test, not a reaction to something already gone wrong — so it can be answered on the merits instead of managed.
- **What happens next:** Answers the objection rather than reading the room for what caused it.

### Recruiter

- **What reaches them:** Panel write-ups that name a scripted moment and quote the response, instead of arriving as impressions.
- **What it means from there:** A write-up quoting a common prompt is the only kind that can be compared between candidates or defended after the fact.
- **What happens next:** Returns the quoted exchange as the feedback, and refuses write-ups that score the room.

## Expected effects

- mech.communication_or_working_style_friction is measured against a common prompt rather than inferred from an interviewer's chosen one
- Interviewer variance stops entering the verdict as if it were candidate behaviour

## What to measure

- `scripted_prompt_coverage`
- `panel_inter_rater_agreement`

## Related entries

- targets — [mech.communication_or_working_style_friction](https://hoba.work/mechanisms/mech.communication_or_working_style_friction) — Communication or Working Style Friction
- targets — [bar.recruiter_screening_call](https://hoba.work/barriers/bar.recruiter_screening_call) — Recruiter Screening Call
- targets — [bar.team_cross_functional_panel](https://hoba.work/barriers/bar.team_cross_functional_panel) — Team & Cross-Functional Panel

---

hoba — a public, versioned atlas of hiring obstacles. Content CC BY-SA 4.0. This document is generated from the registry; the canonical page is linked above.
