HARBOR | Usability Test Coding Sheet
Prompt
Use the current VIFE Lite to generate a real, editable XLSX, "HARBOR | Usability Test Coding Sheet", as a public Example. HARBOR is a fictional collaboration product and every record is a constructed demo sample; label every sheet "Simulated data · Not real participants". Build 12 anonymous IDs P01–P12 × 5 tasks, 60 rows in total, with the fields Participant, Task, Completion status, Time (seconds), Error count, Issue tag and Observation notes; no real names or personal information. At least four sheets: (1) Observation detail, with frozen panes, filters and data validation; (2) Coding dictionary, defining the statuses and issue tags; (3) Task summary, using COUNTIFS/AVERAGEIFS for completion rate, average time and error count, with charts; (4) Findings and next steps, with 5 sample findings ranked by severity and frequency, each explicitly needing validation in real testing. Use deep-sea blue, sky blue and warm white. Use the existing xlsxwriter to write the formulas together with independently precomputed cached values, so the public preview shows the KPIs without recalculation; then read it back with openpyxl in both formula and data_only modes to check the 60 rows, formulas, dropdown validation, charts, completeness of key values and that the file opens. Deliver only one final XLSX; do not install software or renderers. Write all content, headings, labels, sheet names and file names in English.
Result
Here is the finished, editable workbook — one XLSX, built with xlsxwriter and read back with openpyxl.
What is inside
- Observation detail — 60 rows (P01–P12 × T1–T5), fields Participant, Task, Completion status, Time (seconds), Error count, Issue tag, Observation notes. Frozen panes at A4, autofilter A3:G63, six data-validation rules: dropdowns for participant, task, status (4 options) and issue tag (6 options), plus 0–3600 s and 0–20 error bounds. Status values are colour-coded.
- Coding dictionary — defines the four completion statuses and six issue tags (what to look for, typical severity, how to code), a task reference with scenario prompts, and the coding conventions. Its counts are live COUNTIF / AVERAGEIFS formulas.
- Task summary — headline metrics, the per-task table using COUNTIFS for completion and AVERAGEIFS for average time and errors, an overall row, a status mix, and three charts (completion rate, average time, status doughnut) in deep-sea blue, sky blue and warm white.
- Findings and next steps — five sample findings ranked by severity × frequency (27, 12, 10, 8, 3), each with evidence, a recommended next step and an explicit "Yes — needs validation in real testing" line.
Every sheet carries the banner "Simulated data · Not real participants", the HARBOR name is fictional, and no real names or personal data appear anywhere.
Verification (122 checks, all passed)
- Container: zip integrity clean, charts present in the package, opens in openpyxl in both formula and data_only modes.
- Data: exactly 60 rows, no blanks, 5 rows per participant, 12 per task, all statuses/tags within the dictionaries.
- Formulas: 91 formula cells (COUNTIFS, AVERAGEIFS, COUNTIF, IFERROR, priority score), every one carrying a cached value so the preview shows the KPIs without recalculation — overall completion 85.0%, average time 124.65 s, average errors 1.47.
- Independent recomputation: per-task attempts, completed, completion rate, average time, average errors, abandoned and the status mix were recalculated from the raw 60 rows and matched the cached values exactly (tolerance 1e-9). No error tokens, no external links.
- Validation/charts: 6 data validations confirmed with their sqref ranges and option counts; 3 charts confirmed with their category and value ranges.
- Layout: explicit widths on every used column of every sheet, plus a width/height audit for clipping (no unwrapped overflow; only short section and total rows are under 30 pt by design).
Limits to note
- No renderer or office suite was installed, so I could not produce a pixel rendering; visual coverage is the deterministic width/row-height audit plus the checks above, not a rendered preview.
- The file name uses a hyphen ("HARBOR - Usability Test Coding Sheet.xlsx") because "|" is invalid in Windows filenames; the exact title "HARBOR | Usability Test Coding Sheet" is preserved in the banner of every sheet and in the document properties.
- The findings are hypotheses from constructed records, not measured prevalence.
How it was made
- Mode
- Spreadsheet
Related spreadsheet prompts
Online Course | Production Tracker
Spreadsheet
Juniper & Oak Café | Inventory Replenishment Model
Spreadsheet

WORKSHOP | Event Execution Checklist
Spreadsheet
City Bike Stations | Operations Dashboard
Spreadsheet
Creative Projects | Budget vs. Actuals
Spreadsheet
TIDE | Clothing Repair Service Capacity Plan
Spreadsheet
OPEN | Shared Kitchen Cash Flow
Spreadsheet
Content Team | 8-Week Publishing Plan
Spreadsheet

