IDE Debugger Usability Benchmark Script Author
Author a structured, moderated usability testing protocol script to evaluate complex developer debugging interfaces.
Use this template when planning and conducting structured user research on developer workflows, IDE debugger UI overhauls, or breakpoint tools. It provides a timed, step-by-step moderator script with objective usability metrics.
Role: Lead UX Researcher focusing on software developer experience and code analysis tooling.
Context
- Debugging interface feature under evaluation: {{ide_debugging_feature}}
- Target participant profile: {{target_developer_persona}}
- Test codebase and synthetic defect: {{complex_bug_scenario}}
- Quantitative UX telemetry to capture: {{telemetry_metrics}}
- Total session allocation: {{session_duration_minutes}}
- Evaluation rubric framework: {{evaluation_rubric}}
Task
Draft an exhaustive, timed moderator script for conducting a 1-on-1 usability benchmarking session evaluating {{ide_debugging_feature}} with a {{target_developer_persona}} as they resolve {{complex_bug_scenario}}.
Method
- Define pre-session technical setup steps, including IDE workspace provisioning and screen recording calibration.
- Write a warm-up introduction that puts the developer at ease, clarifies consent, and sets think-aloud ground rules.
- Formulate baseline pre-task questions probing the participant's mental model of {{ide_debugging_feature}}.
- Script the task handoff for {{complex_bug_scenario}}, giving realistic debugging objectives without providing UI hints.
- Draft explicit moderator prompts, standardized non-leading interventions, and neutral probing cues.
- Structure observation checkpoints to record timestamps and qualitative friction points for {{telemetry_metrics}}.
- Formulate emergency unblocking hints if the participant is blocked past designated threshold times.
- Script the post-task debrief and subjective cognitive workload scoring aligned with {{evaluation_rubric}} within {{session_duration_minutes}}.
Constraints
- The moderator script MUST contain verbatim spoken prompts enclosed in quotation marks.
- You MUST NOT include leading phrasing that reveals UI element locations or keyboard shortcuts.
- Moderator interventions must be strictly conditional based on specific participant failure states.
- Time allocations across sections must sum exactly to {{session_duration_minutes}} minutes.
Output format
- Session Overview & Technical Setup Checklist (5 minutes before session).
- Timed Moderator Script (chronological sections with Verbatim Script, Observer Prompts, and Unblocking Rules).
- Post-Task Debrief & Metric Scoring Form (rubric questions and telemetry collection grid).
Self-review
- Ensure all variables ({{ide_debugging_feature}}, {{target_developer_persona}}, {{complex_bug_scenario}}, {{telemetry_metrics}}, {{session_duration_minutes}}, {{evaluation_rubric}}) are integrated.
- Confirm the time budget strictly adds up to {{session_duration_minutes}}.
- Check that every spoken prompt remains neutral and non-leading.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.