# Free tools for building from zero By Daniel Ziedins (https://www.danielziedins.com). https://www.agent-six33.com/tools ## Choose your next step ### I have an idea Start by naming one person, the situation they face, and the complete thing you will deliver. The blueprint helps you turn the mission into a testable promise. Leave with one sentence someone else can repeat. Tool: https://www.agent-six33.com/blueprint Read: https://www.agent-six33.com/journal/how-to-build-a-mission-driven-brand-from-zero ### I’m ready to test Take a clear promise through a small, complete delivery. The sprint gives you daily moves and room to record what happened, including confusion, silence, and zero. Leave with a record of delivery and observed behaviour. Tool: https://www.agent-six33.com/sprint#run-the-sprint Read: https://www.agent-six33.com/journal/first-five-customer-interviews ### People have used it Bring your actual counts and their reporting window to the scorecard. Keep delivery, use, return, and change on separate lines so a strong number cannot hide a weak one. Leave with the strongest sentence your current evidence supports. Tool: https://www.agent-six33.com/scorecard#build-scorecard Read: https://www.agent-six33.com/journal/vanity-metrics-vs-impact-metrics ### I need to report Use the proof pack to publish the finding beside its method and limits. End with the decision the evidence earned and the next uncertainty you will test. Leave with a report you can share and a next step you can explain. Tool: https://www.agent-six33.com/proof-pack#build-proof-pack Read: https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust ## The toolkit ### The from-zero blueprint Define who the work serves, what they receive, and the change you hope to support. Seven steps and a ten-question audit give the idea somewhere concrete to land. Leave with: One clear promise. https://www.agent-six33.com/blueprint ### 30-day proof sprint Deliver the smallest complete promise, record use and return, and make a decision. Keep private notes, export the whole sprint, or restore an earlier export. Leave with: A completed test with evidence. https://www.agent-six33.com/sprint#run-the-sprint ### Honest impact scorecard Separate reach, delivery, use, return, and evidenced change. Check your definitions and the strongest claim the evidence can support before publishing a number. Leave with: Five separate evidence signals. https://www.agent-six33.com/scorecard#build-scorecard ### Proof pack builder Put the promise, people, reporting window, findings, method, and limits in one report. Review missing context before sharing, and carry the checklist and warnings into your exports. Leave with: A portable field report. https://www.agent-six33.com/proof-pack#build-proof-pack ## Questions ### Which tool should I start with? Start with the blueprint if your promise is still unclear. Use the 30-day sprint when you are ready to deliver and observe. Use the scorecard when you have signals to classify, then the proof pack when you need to report a finding and decision. ### Are these tools free, and do I need an account? The blueprint, sprint, impact scorecard, and proof pack are free to use without an account. The interactive tools keep working drafts in your browser and offer exports you can keep. ### Do the tools share or combine my project data? The tools keep separate drafts and never combine counts automatically. In the proof pack builder, Review scorecard snapshot lets you inspect a copy from this browser before explicitly replacing the current report. It carries the project, promise, planned change, separate counts, and evidence notes. Reporting dates, findings, limitations, and decisions still need your review. The original scorecard is unchanged. ### How can I move a sprint to another browser? Export the proof pack from the sprint, keep the JSON file, and open Restore a sprint file in the other browser. Review its project, completed days, and note count, then explicitly replace the current sprint. Older version-one SIX33 sprint exports are supported. ### Will my drafts follow me to another device? There is no automatic account sync. Export a JSON backup from the sprint, scorecard, or proof pack, then restore it in the same tool on another browser. Review the backup before explicitly replacing the current draft. Keep backups private: they are readable files, not encrypted. ### Does a completed sprint prove impact? A completed sprint is a record of work and evidence. An impact claim still needs a defined outcome, a stated method, a reporting window, and material limitations. Completing a checklist or exporting a report does not establish that a life changed. # The SIX33 field kit Free project planning and research templates by Daniel Ziedins (https://www.danielziedins.com). https://www.agent-six33.com/field-kit Updated: 2026-10-21 Choose one useful document for the stage you are in. These blank prompts organise the work; they do not validate demand or verify impact. No signup. No private notes or tool drafts are included. ## Working packs ### From an idea to a bounded pilot Four blank worksheets in one editable Markdown file. Clarify the difficulty, choose the uncertainty, agree on the work, and plan a bounded test. Use when: You need to decide what to build before making a larger commitment. Leave with: A clear problem, visible assumptions, an owned brief, and a test plan. Download: https://www.agent-six33.com/field-kit/packs/six33-idea-to-pilot-pack.md Included guides: - Problem statement and evidence worksheet: https://www.agent-six33.com/journal/how-to-write-a-problem-statement - Assumption map and next-test worksheet: https://www.agent-six33.com/journal/how-to-prioritise-assumptions-before-building - One-page project brief: https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief - One-page pilot plan: https://www.agent-six33.com/journal/how-to-plan-a-small-pilot ### 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. Use when: You have a resource or prototype and need to learn from relevant people. Leave with: A recruitment brief, neutral task script, and a source-to-finding record. Download: https://www.agent-six33.com/field-kit/packs/six33-research-session-pack.md Included guides: - Research recruitment brief and coverage worksheet: https://www.agent-six33.com/journal/how-to-recruit-user-research-participants - Usability task script and observation worksheet: https://www.agent-six33.com/journal/how-to-run-a-small-usability-test - Interview synthesis and decision note: https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews ## 01 · Frame: Problem statement and evidence worksheet Use when: A feature request is standing in for a clear account of the person's difficulty. Leave with: A solution-neutral problem statement with evidence, limits, and a next question. Guide: https://www.agent-six33.com/journal/how-to-write-a-problem-statement Download: https://www.agent-six33.com/field-kit/templates/six33-problem-statement-worksheet.md ```markdown # Problem statement and evidence worksheet Version and date: [version / date] Owner and review date: [person / date] Status: [provisional / supported in this context / needs revision] ## Statement Person and relevant situation: [who / when / context] Task they need to finish: [goal in their words, not a feature] Barrier: [specific difficulty] Consequence: [what happens next, at the strength the evidence supports] Working sentence: [person + situation + task + barrier + consequence] ## Evidence boundary Source IDs and dates: [private pointers, not public personal details] Evidence type: [observation / participant account / assumption] Experience or version involved: [context] What the evidence supports: [bounded finding] What it does not establish: [prevalence / cause / demand / other limits] Contradictory experiences and missing perspectives: [details] Possible explanations, kept separate: [assumptions] ## Next learning step Question that could change the statement: [uncertainty] Who or what to learn from: [relevant people / existing material] Method and privacy boundary: [method / access / permission] Two different possible responses, not commitments: [option A / option B] Next decision and owner: [decision / person / date] Revision record: [date / change / reason] A provisional statement is not a validated need. Keep identifying source material private and use appropriate review for higher-risk work. ``` ## 02 · Prioritise: Assumption map and next-test worksheet Use when: The next commitment depends on beliefs you have not examined. Leave with: An important uncertainty, a proportionate learning method, and a decision rule. Guide: https://www.agent-six33.com/journal/how-to-prioritise-assumptions-before-building Download: https://www.agent-six33.com/field-kit/templates/six33-assumption-map-worksheet.md ```markdown # Assumption map and next-test worksheet Project, version, and date: [name / version / date] Next commitment this map could change: [specific decision] Hard-to-reverse part of that commitment: [detail / unknown] Owner and review date: [person / date] ## Assumption — repeat for each important belief ID and clear belief: [A01 / one belief] Category: [person's need / proposed experience / delivery dependency / ongoing care] What fails or changes if this is false: [consequence] Relevant evidence and private source IDs: [source / date / context] Limits, contradictions, and missing perspectives: [details] Current support: [supported in a stated context / weakly supported / unknown] Why investigate this before another commitment: [reason, not an invented probability] Safety, access, and required review: [constraints / reviewer / resolve before testing] ## Next learning step Question: [specific uncertainty] Method and why it can answer this question: [interview / observation / operational check / review] Experience or version: [version] Decision rule written before the test: [continue / change / stop / investigate conditions] What this method cannot establish: [limits] Evidence access and permission boundary: [who sees what / agreed use] ## Review after the learning step Observed result or account, kept separate from interpretation: [result / source] Interpretation and alternative explanations: [bounded conclusion] Status in this context: [supported / contradicted / unresolved] Next decision, owner, and review trigger: [decision / person / trigger] Revision record: [date / change / reason] This worksheet does not calculate risk or verify demand, causation, or impact. Keep identifying information private and obtain appropriate review for higher-risk work. ``` ## 03 · Recruit: Research recruitment brief and coverage worksheet Use when: You need relevant experience and a clear participation plan, not just encouraging feedback. Leave with: A recruitment brief with criteria, arrangements, and missing perspectives. Guide: https://www.agent-six33.com/journal/how-to-recruit-user-research-participants Download: https://www.agent-six33.com/field-kit/templates/six33-research-recruitment-worksheet.md ```markdown # Research recruitment brief and coverage worksheet 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. ``` ## 04 · Observe: Usability task script and observation worksheet Use when: You have a resource or prototype and need to see someone attempt a real task. Leave with: A neutral task script and a record that keeps assistance and limits visible. Guide: https://www.agent-six33.com/journal/how-to-run-a-small-usability-test Download: https://www.agent-six33.com/field-kit/templates/six33-usability-test-worksheet.md ```markdown # Usability task script and observation worksheet 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. ``` ## 05 · Understand: Interview synthesis and decision note Use when: You have interview notes but need a traceable finding and a next decision. Leave with: A source-linked finding, its limits, and one next test. Guide: https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews Download: https://www.agent-six33.com/field-kit/templates/six33-interview-synthesis-template.md ```markdown # Interview synthesis and decision note 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. ``` ## 06 · Align: One-page project brief Use when: The idea is clear to you, but a collaborator needs a bounded piece of work. Leave with: One person, one complete promise, scope, owner, and a decision gate. Guide: https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief Download: https://www.agent-six33.com/field-kit/templates/six33-one-page-project-brief.md ```markdown # One-page project brief Project name, version, and date: [name / version / date] Owner: [person responsible] Decision-maker or reviewer: [person / role] ## Person and problem Who, in what situation: [specific person and context] Task they need to complete: [task] Current difficulty: [problem, not a preselected feature] Evidence and source links: [dated findings / private source pointers] Assumptions: [not yet established] Unknowns that could change the approach: [unknown / owner / check date] ## Complete promise After this delivery, the person can: [one useful action] In scope: [minimum complete contents or behaviour] Out of scope for this version: [explicit exclusions] Accessibility and assisted alternatives: [needs / formats / gaps to resolve] ## Delivery and care Available time and resources: [confirmed / unknown] Dependencies and permissions: [requirements / owner] Review date: [date] Readiness checks: [accuracy / functional checks / required review] Maintenance and correction route: [owner / update trigger / contact] Privacy and safety boundary: [what is not collected / required review] ## Decision gate Next decision: [continue / change / stop / investigate] Evidence needed for that decision: [method and limits] Separate pilot plan, if needed: [link / version] Claims this delivery does not establish: [outcomes / prevalence / causation] Revision record: [date / what changed / reason] A working brief, not a contract or professional approval. Do not publish private source material or unresolved sensitive details. ``` ## 07 · Test: One-page pilot plan Use when: A promise needs a small, real test before a bigger commitment. Leave with: A test question, observation plan, limits, and a decision rule. Guide: https://www.agent-six33.com/journal/how-to-plan-a-small-pilot Download: https://www.agent-six33.com/field-kit/templates/six33-one-page-pilot-plan.md ```markdown # One-page pilot plan Project and version: [name] Owner and review date: [person / date] Decision this pilot will inform: [continue, change, stop, or another specific decision] One uncertainty: [what we do not know] Participant situation and recruitment route: [who / how invited] Complete promise: [what the recipient will receive or be able to do] Task and scope: [included / explicitly not tested] Observation method and window: [source / observer / dates] Completion categories: [independent / assisted / not completed / not observed] Assistance to record: [what help is allowed and how it will be logged] Decision rule and rationale: [what would change the next decision, and why] Protection and permission: [minimum data / voluntary participation / separate publishing permission] Limits to publish beside the finding: [sample / selection / missing data / timing] After the pilot: [finding / unresolved question / decision / owner / date] This is a planning template, not evidence that a result occurred. Do not put identifiable participant information in a public copy. ``` ## 08 · Learn: Pilot follow-up invitation and evidence note Use when: The experience has been delivered and you need to understand what happened next. Leave with: An optional invitation and a private evidence note, not a request for praise. Guide: https://www.agent-six33.com/journal/how-to-follow-up-after-a-pilot Download: https://www.agent-six33.com/field-kit/templates/six33-pilot-follow-up-template.md ```markdown # Pilot follow-up ## Invitation — adapt before sending Hi [name], you tried [experience] on [date]. We are learning what happened afterward, including what did not work. Would you be willing to spend [realistic time] telling us what you did next? This is optional, and declining will not affect [access to help/support]. Notes will be used for [purpose] and seen by [people]. This is not a request for a testimonial or permission to publish your story. You can decline or ask questions by [simple method]. ## Private evidence note Participant code: [not a public name] Experience version and date: [version / date] Follow-up date and method: [date / conversation or other source] Original intended next step: [action] What happened afterward, in the participant's words: [account] Observation versus self-report: [distinguish sources] What did not happen, or remained difficult: [detail] Other influences and alternative explanations: [detail] Assistance or prompting: [detail] Unknown or missing information: [detail] Interpretation, kept separate from the account: [limited conclusion] Next decision, owner, and date: [decision / person / date] Publication permission: [separate permission or do not publish] Keep the original eligible group, invitations, reached participants, responses, and usable observations on separate lines in the overall report. Non-response stays unknown. ``` ## Questions ### Are these templates free and do I need an account? The blank templates are free to download without an account, email address, or payment. Each is an editable Markdown text file. Open it in a text editor or copy the text into your own working document. ### Which template should I start with? Use the problem worksheet to clarify a difficulty and the assumption map to choose what to investigate. Use the recruitment brief and usability script to prepare task-based research, the synthesis note to organise findings, the brief to agree on the work, the pilot plan before a delivery test, and the follow-up note after delivery. You do not need every template. ### Can I download several worksheets in one file? Yes. The idea-to-pilot pack combines four blank worksheets; the research-session pack combines three. Each editable Markdown file includes companion-guide links and update dates. These are optional working aids, not a requirement to complete every section, and they contain no saved notes or tool drafts. ### Will a download include my private notes or tool drafts? No. Downloads contain public blank prompts and source information only. They do not read or export your journal notes, reading list, sprint, scorecard, or proof-pack drafts. Completed copies stay wherever you choose to edit and save them. ### Do I need JavaScript to read or download the templates? No. The field kit's guide links, template previews, and Markdown downloads work without JavaScript. The copy buttons inside individual articles are an optional convenience; you can also select the preview text manually. ### Does a completed template verify demand or impact? No. A template organises thinking and evidence; completing one does not establish demand, usability, causation, or impact. Use methods and professional review appropriate to the actual decision, claims, and risks.