# Prepare a useful research round Three blank worksheets in one editable Markdown file. Plan relevant participation, observe a realistic task, and organise the evidence without overstating it. Blank working pack by Daniel Ziedins (https://www.danielziedins.com). Updated: 2026-10-21 Library: https://www.agent-six33.com/field-kit#working-packs Use only the sections that help the decision. Save a private working copy before adding answers. This file contains public blank prompts, not your journal notes, tool drafts, participant records, or proof of demand or impact. The recruitment worksheet is not a consent form. ## Your working copy Project and version: [name / version] Owner and review date: [person / date] Next decision: [specific decision] ## Included guides 1. How to recruit research participants who can change what you learn. — https://www.agent-six33.com/journal/how-to-recruit-user-research-participants 2. How to run a small usability test without coaching the answer. — https://www.agent-six33.com/journal/how-to-run-a-small-usability-test 3. How to synthesise customer interviews into a useful decision. — https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews --- ## 01 · How to recruit research participants who can change what you learn. Guide: https://www.agent-six33.com/journal/how-to-recruit-user-research-participants Guide updated: 2026-10-21 Project, brief version, and date: [name / version / date] Research question and next decision: [question / decision] Method and proposed activity: [interview / observed task / other] Owner and required review: [person / appropriate review before recruiting] ### Relevant experience Required recent experience or likely task: [plain criteria / why relevant] Different contexts to explore: [channels / familiarity / access methods / other task-relevant differences] Exclusions and reasons: [appropriateness / avoid convenience-only restrictions] Who this plan may miss: [perspectives / recruitment limitations] ### Invitation and participation arrangements Approved recruitment channels and permission: [where / owner / permission] Neutral invitation purpose: [what you want to learn, not praise for a solution] Activity, expected commitment, and prototype limits: [details] Contact, questions, declining, and stopping process: [clear arrangements] Information and consent process: [reviewed material / recording choices / agreed use] Requested format, communication, or device arrangements: [arrange privately] Compensation or expense terms, if offered: [process / not conditional on favourable answers] Minimum screening information needed: [each field / reason] Access, handling, and retention arrangements: [approved process / owner / review date] ### Recruitment review Participant code: [private ID, contact details stored separately where practical] Relevant experience and channel: [bounded context] Status: [invited / opted in / confirmed / cancelled / no response / other] Arrangements confirmed: [yes / unresolved action] Coverage gaps and changed criteria: [gap / revision / reason] ### Reporting boundary What this group can help investigate: [bounded question] Who or what it does not represent: [missing perspectives / frequency limits] Next recruitment decision and owner: [action / person] This is a planning aid, not a consent form, legal compliance checklist, or safeguarding process. Do not publish completed screening or contact details, and do not treat non-response as an opinion about the idea. --- ## 02 · How to run a small usability test without coaching the answer. Guide: https://www.agent-six33.com/journal/how-to-run-a-small-usability-test Guide updated: 2026-10-21 Project, version, and date: [name / tested version / date] Decision this session could change: [specific decision] Question: [what you need to observe] Relevant participant experience: [criteria, not identifying details] Moderator / note-taker: [owners] ### Prepare the boundary Starting point and device context: [page / device / access method] Prototype limits and sandbox checks: [unavailable steps / no real submissions] Participation and recording arrangements: [agreed process / pause or stop option] Support or format requested: [arrange privately] Source-record access and review date: [who / date / handling process] ### Task — repeat as needed Participant-facing scenario: [realistic context and goal, no control labels] Moderator-only research question: [uncertainty] Visible endpoint agreed before the session: [what completion would mean] Assistance or stopping boundary: [when and how to intervene] ### Observation record Participant code and task ID: [private code / task] What happened, in sequence: [actions / words / relevant context] Questions, prompts, or assistance given: [exact intervention / when] Outcome: [unassisted / assisted / unfinished / chose to stop / prototype blocked / other] Unexpected result or disagreement: [details] Interpretation, separate from observation: [candidate explanation] Alternative explanations and limits: [what is not established] ### Review Candidate issue and consequence: [finding / source IDs] Change or operating dependency: [action / owner] Next observation after the change: [task / version / question] What remains unknown: [demand / wider frequency / conformance / long-term outcomes] Decision and review trigger: [proceed / change / investigate / stop] This is a planning aid, not a consent form, accessibility certification, or proof of demand or impact. Keep completed copies and participant records private. --- ## 03 · How to synthesise customer interviews into a useful decision. Guide: https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews Guide updated: 2026-10-18 Decision this round informs: [one decision] Research question: [uncertainty] Round dates and method: [dates / method] Participants and recruitment limits: [codes / relevant context / missing perspectives] Experience or version discussed: [experience / version] ### Source-linked observations — repeat as needed Observation ID: [O01] Participant code: [P01] Source pointer: [private note ID or permitted timestamp] Evidence type: [observed behaviour / participant account / other] What was said or done: [exact quote or labelled paraphrase] Prompting, assistance, and context: [details] Interpretation, kept separate: [tentative meaning] ### Finding — repeat as needed Finding ID and short statement: [F01 / bounded finding] Supporting observation IDs: [O01, O02] Distinct participants represented: [count / context; not market prevalence] Contradictions and alternative explanations: [details] Unknowns and missing perspectives: [details] Why this matters for the task: [consequence] ### Decision Decision and reason: [investigate / change / retain / stop] Next test and what it can establish: [bounded test] Owner and review date: [person / date] Brief or prototype version: [link / version] Sharing boundary and retention plan: [who may see what / when to review or remove] Remove participant identifiers from any public summary. Do not infer population rates, causation, or publication permission from this note. --- Keep completed copies and participant details private. Review methods, permissions, missing perspectives, and limitations before relying on or publishing a finding.