# The SIX33 journal Field notes by Daniel Ziedins (https://www.danielziedins.com). Scripture first. The build log keeps the numbers. https://www.agent-six33.com/journal ## Guided reading paths https://www.agent-six33.com/journal#reading-paths ### Build a useful first promise For an idea that needs a first real test. About 27 minutes across 3 articles. Move from a broad mission to one person, one complete promise, and one small delivery. Listen before adding features, then keep a record of what actually happened. 1. [How to build a mission-driven brand from zero — without faking impact.](https://www.agent-six33.com/journal/how-to-build-a-mission-driven-brand-from-zero) — Name the person, promise, and evidence gate before designing the presentation. 2. [Your first five customer interviews: questions that change what you build.](https://www.agent-six33.com/journal/first-five-customer-interviews) — Learn from a recent experience instead of asking people to approve your idea. 3. [How to plan a small pilot: a one-page test plan.](https://www.agent-six33.com/journal/how-to-plan-a-small-pilot) — Turn the strongest uncertainty into a bounded test and write its decision rule before delivery. Leave with a promise you can explain and a test you can deliver. Next: [Turn the promise into a proof sprint](https://www.agent-six33.com/sprint#run-the-sprint) ### Make the evidence useful For work that has been delivered and needs an honest report. About 22 minutes across 3 articles. Separate shipping from use and outcomes. Classify the signals, write down how you know, and make the next decision without upgrading a count into an unsupported impact claim. 1. [Vanity metrics vs impact metrics: how to tell them apart.](https://www.agent-six33.com/journal/vanity-metrics-vs-impact-metrics) — Keep reach, delivery, use, return, and evidenced change on separate lines. 2. [How to follow up after a pilot: questions, script, and evidence.](https://www.agent-six33.com/journal/how-to-follow-up-after-a-pilot) — Ask what happened afterward without leading the answer or guessing what silence means. 3. [How to write an impact report people will actually trust.](https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust) — Put the finding beside its method and limitations, then review before sharing. Leave with a finding, its method and limits, and a next decision. Next: [Build and review a proof pack](https://www.agent-six33.com/proof-pack#build-proof-pack) ### Take the next faithful step For a day that needs a clearer priority. About 21 minutes across 3 articles. Begin with seek first as a lived priority, distinguish today's responsibility from tomorrow's worries, and choose one concrete act of faithfulness in the place you already are. 1. [Seek first is not a slogan.](https://www.agent-six33.com/journal/seek-first-is-not-a-slogan) — Start with the priority that gives the rest of the work its order. 2. [Tomorrow is not your assignment.](https://www.agent-six33.com/journal/tomorrow-is-not-your-assignment) — Name today's responsibility without pretending to own tomorrow. 3. [There is grace for the next faithful hour.](https://www.agent-six33.com/journal/grace-for-the-next-faithful-hour) — Choose the next available act of obedience instead of waiting for the whole plan. Leave with one faithful action for this hour, not a promise to control every outcome. Next: [Explore the foundation in Matthew 6:33](https://www.agent-six33.com/matthew-6-33) ### Reading and private notes **Where should I start in the SIX33 journal?** Choose Build a useful first promise if you are shaping an idea, Make the evidence useful if you need to report a result, or Take the next faithful step for a clearer daily priority. Each path has three articles in a suggested order and one practical next step. All articles are by Daniel Ziedins. **Do I have to finish a reading path in one sitting?** No. Read one article, write one useful next step, and return when you need the next part. The displayed reading time is an estimate from the individual articles, not a deadline or a measure of progress. **How can I find notes for an article I did not bookmark?** Choose My notes in the journal. It lists articles with a saved note, whether or not Save for later is selected. Open a card to return to its reading tools. Unsaved text stays only in the open article until you choose Save my note. **How do I move my SIX33 reading notes to another browser?** In My notes or Saved for later, open Back up or restore my reading library and download a JSON backup. In the destination browser, choose that file, review the preview, and select Merge backup; keep existing notes. Missing notes and bookmarks are added, but existing notes are never replaced and entries are never deleted. A Markdown download is a readable copy, not a restorable backup. Unsaved article text is not included. **What happens if a backup contains a different note for the same article?** The preview shows the conflict and lets you compare both private notes. The note already saved in this browser is kept. The other note remains in your backup file; it is not copied over your current note. You can cancel without changes. If the library changes after the preview, choose the file again to review a fresh merge. **Are my reading notes public or included in search-engine content?** No. Saved notes stay in local storage in this browser and are not added to the public page source, sitemap, feeds, search index, or AI-readable copies. Search filters the article text, not your private notes. Download a copy before clearing browser storage; the Markdown export is readable, not encrypted. ## Explore the journal by topic - Research and testing: What should I learn before I build more? https://www.agent-six33.com/journal/topics/research-and-testing — Markdown: https://www.agent-six33.com/journal/topics/research-and-testing/guide.md - Evidence and honest impact reporting: What can I honestly say changed? https://www.agent-six33.com/journal/topics/evidence-and-impact — Markdown: https://www.agent-six33.com/journal/topics/evidence-and-impact/guide.md ## Free templates Download planning worksheets, recruitment briefs, usability scripts, and follow-up templates: https://www.agent-six33.com/field-kit Choose an idea-to-pilot or research-session working pack in one editable file: https://www.agent-six33.com/field-kit#working-packs Public blank templates only. No private reading notes or tool drafts are included. --- # How to run a small usability test without coaching the answer. Watch someone attempt a realistic task, record where help was needed, and make a bounded improvement decision. Includes a task script, worked example, and worksheet. ## The direct answer Run a small usability test by choosing a realistic task, preparing a specific version, and observing relevant participants attempt it with neutral instructions. Record what happened, including assistance, errors, and unfinished tasks. Keep observations separate from interpretation, then choose a change or another test. A small session can reveal a usability issue; it cannot establish wider demand, accessibility conformance, or long-term impact. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 21, 2026 - Updated: Oct 21, 2026 - Scripture: James 1:19 - Read: 7 min - URL: https://www.agent-six33.com/journal/how-to-run-a-small-usability-test > Let every person be quick to hear, slow to speak, slow to anger. > — James 1:19 A person can like your idea and still be unable to use it. A helpful-looking page can hide the one detail somebody needs before acting. Asking whether the design is clear gives you an opinion; watching a person attempt a meaningful task gives you a different kind of evidence. Both may be useful, but they should not be mistaken for each other. The working method below is for a small, low-risk resource or prototype. It is an original practical structure informed by the sources below, not a formal research standard. Do not test an unreliable service by asking people to depend on it for essential help. Resolve safety, permission, and operating responsibilities first. Use a sandbox when a task could send a message, spend money, publish information, or change a real record. ## 1. Choose a task and a decision, not a tour. Write the decision the session could change: whether to rewrite arrival instructions, move a confirmation detail, or remove a confusing step. Then state what you want to observe. Can a first-time visitor find a suitable session and explain what happens after choosing it? This is more useful than a broad request to explore the website and say what you think. Freeze or identify the version being tested. Record the page, prototype link, device context, starting point, and any unavailable parts. If the prototype cannot complete a step, say so in the record rather than turning that technical limit into a participant failure. Decide what counts as completion before the session, while leaving room to record an outcome that does not fit your expected categories. ## 2. Write the goal without naming the controls. GOV.UK's moderated-testing guidance recommends believable tasks that do not reveal the route to the answer. Keep that principle short and concrete in your script. Compare find the Contact tab and click Volunteer with you want to ask whether a role fits your available time; show what you would do next. The second instruction leaves the navigation open to inspection. Prepare a moderator-only note with the research question, the visible endpoint, and the assistance boundary. Do not read that note as part of the task. A scenario can provide necessary circumstances without supplying the right label. If a participant needs a different but equally relevant scenario, record the variation so you do not later imply that every session used identical conditions. ## 3. Prepare the participant and the test setting. Explain that the resource is being examined, not the person's ability. Set out the activity and agreed recording arrangements before beginning. Offer a way to pause or stop, and check that the person can use the materials and equipment. Do not assume that a familiar video platform, a desktop browser, or a spoken think-aloud instruction will work equally well for everyone. Use invented task details in a prototype that does not need personal information. Remove real submission destinations, or make the sandbox boundary unmistakable. A note-taker needs only the information relevant to the question. Keep a participant code beside observations and store contact details separately where practical. If you cannot provide an appropriate setting or review for the people involved, change the plan before recruiting them. **Recruit for the task, not for agreement:** Choose relevant experience and participation arrangements before scheduling a session. https://www.agent-six33.com/journal/how-to-recruit-user-research-participants ## 4. Observe first, and make assistance visible. Give the task, then leave enough space for the participant to act. Do not convert each pause into a hint. If you ask a clarifying question, record it when it could influence the next action. A useful note says the participant reopened the schedule twice and asked whether confirmation was immediate; an interpretation such as the page creates anxiety belongs on a separate line. Stopping or helping can be the responsible choice. Decide how you will respond to distress, a technical block, or a task that is going nowhere. Record the prompt or intervention and describe any later completion as assisted. You can continue learning after assistance; you simply cannot report that path as an unassisted success. Preserve the difference between did not finish, chose not to continue, and could not proceed because the prototype ended. ## 5. Turn a hypothetical session into a bounded finding. Imagine a draft community-workshop page. This is a hypothetical example, not a SIX33 result. The task is to choose a session the person could attend and explain how they would know their place was confirmed. In the scenario, the page offers a time and a request button, but the confirmation process is buried in a separate paragraph. One participant finds the time, requests a place, and assumes the request is a booking. Another asks whether a reply is needed; the moderator points to the confirmation paragraph. Record those sequences separately. Do not compress them into both users completed booking, because the prototype did not establish a booking and the second path included help. Do not infer how often this issue occurs across all visitors. A candidate finding is that the tested version left the confirmation boundary unclear in these sessions. A reasonable next change is to state beside the request what is and is not confirmed, then observe the revised task with relevant people. The record should retain the original wording, the observations, the intervention, and the alternative explanation that the scenario itself may have implied an immediate booking. ## 6. Make one decision and keep the limits beside it. After the session, connect the task note to a candidate issue and its consequence. Distinguish a wording improvement from an unresolved service dependency. Clearer text cannot repair a coordinator who has not agreed to confirm places. Give the next action an owner and define what you will observe after the change, rather than treating the redesigned screen as a successful result on its own. Report the number of sessions, the relevant version and conditions, and which paths involved help. Do not turn a small convenience group into a reliable population success rate. Testing with people who use different access methods can reveal valuable barriers, but a small usability round does not replace a specialist accessibility audit or establish conformance. Likewise, successful task completion says nothing by itself about repeated use or lasting change. Keep a review record when the next version is ready. Which issue was addressed, which remains, and what would make you revisit the decision? An honest usability report can end with unresolved questions. Its value is in making the next change more accountable, not in giving a finished design a research-shaped seal of approval. **Keep the evidence traceable:** Adapt the source-to-finding discipline without treating interviews and observed tasks as interchangeable methods. https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews ## Usability task script and observation worksheet Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** A completed task is only useful evidence when the conditions and the help remain visible. ## Questions ### What is the difference between an interview and a usability test? An interview explores an account of an experience. A usability test observes someone attempting a task with a particular version of a resource or service. You may use both, but an opinion about ease of use is not the same as an observed task outcome. ### What makes a usability task leading? A task becomes leading when it supplies the label, sequence, or answer you want to inspect. Give a believable situation and goal instead. Keep the expected route in the moderator's notes, and record any hint or assistance that influences the attempt. ### Can I help a participant who gets stuck? Yes, when that is appropriate to the session and the person's wellbeing. Record when and how you helped, and describe any later completion as assisted. Help can allow further learning, but it must not disappear from the reported result. ### Does a small usability test prove that a website is accessible? No. It can reveal barriers experienced by the participants with the tested version and conditions. It does not establish accessibility conformance or replace an appropriate audit. Keep access methods, support, missing perspectives, and limits visible in the record. ## Sources - GOV.UK Service Manual: moderated usability testing: https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing — Reference for observing realistic tasks and avoiding instructions that reveal the answer. The worksheet and workshop-page example are original illustrations, not a reported study or government endorsement. - GOV.UK Service Manual: finding research participants: https://www.gov.uk/service-manual/user-research/find-user-research-participants — Further reading on relevant participants and participation arrangements. A small task observation is not a representative survey. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-run-a-small-usability-test --- # How to recruit research participants who can change what you learn. Write a recruitment brief around the real task, include missing perspectives, and invite participation without asking for praise. Includes a hypothetical example and reusable worksheet. ## The direct answer Recruit user research participants by defining the experience relevant to your question, writing clear selection criteria, and choosing channels that can reach those people. Plan participation arrangements before invitations, keep screening proportionate, and record who your recruitment method misses. A useful group can challenge a design; it does not automatically represent the whole audience or prove how common a need is. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 21, 2026 - Updated: Oct 21, 2026 - Scripture: James 1:19 - Read: 7 min - URL: https://www.agent-six33.com/journal/how-to-recruit-user-research-participants > Let every person be quick to hear, slow to speak, slow to anger. > — James 1:19 The people easiest to ask are not always the people best placed to answer the question. A supportive colleague may know the website too well to reveal a first-visit problem. A follower who enjoys your writing may never have needed the service you are investigating. Recruiting only encouragement can leave a team with warm feedback and the original uncertainty intact. This guide offers an original recruitment-planning aid for low-risk work with adults. It is not a legal compliance checklist, a consent form, or a safeguarding process. Work involving children, vulnerable circumstances, sensitive subjects, or essential services needs appropriate expertise and review. A small project is not exempt from treating a person's time, choices, and information with care. ## 1. Start with the experience that matters. Write your research question before writing an invitation. If you need to understand how newcomers prepared for a first session, recent first-time participants are relevant in a way that long-standing organisers may not be. If you are investigating an unfinished task, people who abandoned it may know something that completed registrations cannot explain. The relevant experience should determine the brief, not the size of an existing mailing list. Describe the experience in terms a person can recognise. Avoid requiring someone to agree that your proposed solution would help before they can participate. That would filter for your conclusion. Also distinguish a task condition from a personal characteristic. Ask only for information that helps answer the question or arrange participation; a detailed biography is not a substitute for a clear reason to include somebody. ## 2. Write criteria, exclusions, and missing perspectives. GOV.UK's participant guidance emphasises actual or likely users and attention to different access needs. Use that as a starting boundary, then explain your own selection decisions. Record which experience is required, which differences you want to explore, and any condition that makes the proposed session inappropriate. Keep the reason beside each criterion so a convenient restriction cannot quietly become a claim about the audience. Maintain a missing-perspectives line from the beginning. A session offered only during working hours may miss people whose schedules differ. A web-only invitation may miss those who rely on another person or channel. You may not resolve every gap in one round, but you can stop the report from saying users when it really means people who saw this invitation and could attend under these conditions. ## 3. Choose recruitment channels that fit the question. Compare channels for the experience you need, not just response speed. An opt-in invitation to recent participants might suit a preparation question; an approved community notice might reach people who have never registered. A gatekeeper's opinion can help you understand the setting, but it is not automatically an account from the people using the service. Keep the two source types separate. Ask permission before posting in a group or approaching people through an organisation. Describe the research accurately and make declining uncomplicated. If a colleague helps arrange introductions, agree what information is actually necessary to share. Do not add people to a marketing list because they expressed research interest, and do not imply that giving a positive answer is the price of being helpful. ## 4. Make participation understandable before scheduling. Draft a plain invitation with the purpose, activity, expected commitment, contact method, and how to ask questions or decline. State whether the session concerns a prototype or a working service. Explain any planned recording and who would see the material through your agreed information and consent process. This worksheet helps you notice those decisions; filling it in does not itself establish informed consent. Ask about participation arrangements in a way that does not demand an unnecessary diagnosis or personal history. A person might need a different format, communication method, device setup, or time. Arrange what you can support before confirming the session. If compensation or expenses are offered, state the terms through the appropriate process and do not make favourable feedback a condition. Keep the invitation separate from a request for a testimonial. **Prepare the observed task:** Give people a clear goal and make the assistance boundary visible. https://www.agent-six33.com/journal/how-to-run-a-small-usability-test ## 5. Work through a hypothetical recruitment brief. Imagine a team trying to understand confusing arrival information for a community workshop. This is a hypothetical example, not a SIX33 study. The first draft asks enthusiastic supporters to review our improved welcome page. That wording selects for goodwill and points attention toward the proposed page before establishing how people prepared for the session. A better brief names adults who recently prepared to attend for the first time, including people who asked for clarification or did not complete the arrival process where an appropriate invitation route exists. The question is how they found the time, place, and contact information. Prior experience with the team and the channel used for preparation are context to record, not reasons to manufacture a balanced-looking group. Suppose the eventual sessions include only people who successfully arrived after a direct message from the coordinator. The team can learn from those experiences, but it cannot describe the findings as the experience of every newcomer or of people who never reached the venue. The next recruitment decision might deliberately seek a different preparation route. The useful output is a visible limitation and a better next question, not an unsupported claim of representativeness. ## 6. Review who took part, not just how many. Before the first session, check the achieved group against the question and the participation arrangements. Keep a cancellation or non-response as a recruitment status, not an opinion about the service. A person who did not reply has not rejected your idea. If a criterion changes, record the reason and the version of the brief so the final account can explain how the group was assembled. Afterward, report the channels, relevant experience, exclusions, and gaps alongside the session count. Avoid presenting a convenience group as a population estimate. The method and question determine what further research is appropriate; there is no universal participant number that certifies a need, a product, or an impact claim. Repeated sessions with highly familiar people may answer a different question from a first encounter. Finally, follow the agreed handling and retention arrangements for contact and screening material. Keep the recruitment record separate from public findings, using private source pointers where needed. A public report usually needs to explain why a participant's experience was relevant, not reveal who they are. Recruitment has done useful work when it makes the eventual claim narrower, clearer, and more open to being challenged. **Ask about the recent experience:** Use neutral questions once the relevant participants and arrangements are clear. https://www.agent-six33.com/journal/first-five-customer-interviews ## Research recruitment brief and coverage worksheet Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** Recruit for a relevant experience and an honest challenge, not for the answer you hope to hear. ## Questions ### Who should I recruit for a small user research project? Choose people with the actual or likely task experience relevant to your question. Record the contexts you need to explore and who your recruitment channels may miss. Supportive followers, colleagues, and gatekeepers are not automatically substitutes for the people doing the task. ### Can I use friends or colleagues in a usability test? They can help rehearse the script and identify obvious technical problems. If they genuinely match the research criteria, their session may provide relevant evidence, but familiarity can change how they use the resource. Record that context and do not present a rehearsal as research with unfamiliar users. ### Does a small research group represent my whole audience? Not automatically. Recruitment channels, availability, selection criteria, familiarity, and missing perspectives limit what a group can establish. Explain those limits beside the findings rather than converting a small set of sessions into population percentages. ### Is a recruitment worksheet a consent form? No. It helps a team plan the information, participation arrangements, review, and handling decisions that need attention. It does not establish informed consent or replace the appropriate process for the people, subject, risks, and jurisdiction involved. ## Sources - GOV.UK Service Manual: finding research participants: https://www.gov.uk/service-manual/user-research/find-user-research-participants — Reference for actual or likely users, participation arrangements, and recruitment limitations. The brief and workshop example are original working aids, not a reported study. - GOV.UK Service Manual: moderated usability testing: https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing — Further reading on the task-based sessions a recruitment brief may support. No endorsement or universal participant-count rule is implied. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-recruit-user-research-participants --- # How to write a problem statement before choosing a solution. Name the person, situation, task, barrier, and consequence without hiding a feature request inside the problem. Includes a worked example and a practical worksheet. ## The direct answer Write a problem statement by naming a specific person, the situation they are in, the task they need to finish, the barrier, and the consequence. Attach the evidence behind the statement and label what is still assumed. Keep your proposed solution outside the sentence so you can compare different responses. Revise the statement when research changes what you understand. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 20, 2026 - Updated: Oct 20, 2026 - Scripture: James 1:19 - Read: 6 min - URL: https://www.agent-six33.com/journal/how-to-write-a-problem-statement > Let every person be quick to hear, slow to speak, slow to anger. > — James 1:19 We need an app is a decision about a response. It is not yet a description of a person's problem. Starting there can make the work feel productive while leaving the most important question unanswered: what is somebody trying to do, and what is actually preventing it? A problem statement is a small discipline of listening. It gives a team something precise enough to investigate without pretending the answer is already known. The format below is an original working aid for a low-risk project, resource, or service. It is not a diagnostic assessment, an eligibility rule, or permission to experiment with somebody's safety or access to essential help. ## 1. Put a person in a real situation. Describe the relevant situation rather than inventing a personality. First-time volunteers preparing for their first session is a more useful starting point than busy people who care. The first phrase tells you when the difficulty occurs and whose experience to investigate. The second could describe almost anyone and cannot guide a useful conversation. Be explicit about whose experience is missing. Someone with a slow connection, a different language preference, or an assisted way of completing the task may encounter a different barrier. Do not add personal details simply to make the statement vivid. Include a circumstance only if it helps explain the task or changes what a useful response would need to support. ## 2. Describe the task without prescribing the channel. GOV.UK's user-needs guidance separates the person's goal from a proposed solution. Make that distinction visible in your document. A person might need to confirm where to arrive and whom to contact; a notification, printed sheet, phone conversation, or clearer page could each help in different circumstances. Needing an app assumes a channel before establishing the task. Write the task as something the person would recognise. Avoid an internal department's objective such as increase engagement when the person's job is choose a suitable role. A team can care about engagement, but the statement should first explain what the person is trying to accomplish. Otherwise you risk improving a dashboard while leaving the actual handoff confusing. ## 3. Separate the barrier from your explanation of it. Record the difficulty and its consequence at the strength your source supports. If a participant says they contacted a coordinator because the page did not identify a meeting point, that is an account of what happened. It is not yet an observed test of the page, proof of the only cause, or a count of everyone affected. Keep an explanation such as the wording is too technical on an assumptions line until you have investigated it. The issue might instead be outdated information, a broken link, an unfamiliar place, or a mismatch between the page and the invitation. A statement that leaves these possibilities open makes it easier to compare responses without defending the first idea somebody suggested. ## 4. Attach a short evidence note and an uncertainty. Beside the statement, record the source, date, context, and whether it is observation, a participant account, or a team assumption. Use private source IDs rather than copying identifying material into a widely shared brief. Preserve contradictions too: a person who completed the task easily may have had information or assistance that another person lacked. If there is no direct evidence yet, call the statement provisional. That is a useful status, not a reason to dress it up as a validated insight. Decide what would change your understanding and whom you should learn from next. A statement can guide initial research before it is supported, provided the team does not quietly treat that provisional wording as an established fact. **Investigate the recent experience:** Use neutral questions and a concrete story to learn what actually happened. https://www.agent-six33.com/journal/first-five-customer-interviews ## 5. Rewrite a solution request as a bounded problem. This hypothetical example is not a SIX33 research result. A team starts with we need a volunteer app. Its only evidence is two recent messages from first-time volunteers asking where to meet and whom to contact. Those messages support investigating arrival information. They do not establish demand for an app or show how common the difficulty is. A provisional statement could be: before their first session, some first-time volunteers cannot confirm the meeting point and contact person from the information they received, so they need another exchange with the team before they can plan their arrival. The evidence note identifies the two messages, the invitation version, and the unanswered question of whether the information was missing, hard to find, or out of date. A next learning step is to review the invitation and ask people about their latest preparation experience. If you later observe people finding the details successfully but still being unsure about transport, revise the problem instead of forcing the new evidence into the arrival-information explanation. A solution-neutral statement should make a changed understanding possible, not merely make an old feature request sound more thoughtful. ## 6. Use the statement to choose a learning step, then a brief. Ask a colleague to name two materially different responses that could address the statement. If the only possible answer is the feature you already wanted, check whether the wording has smuggled in that feature. Also ask whether the person, moment, barrier, and consequence can be understood without an explanation from the author. Do not promise an improvement the statement has not tested. Fewer clarification messages, for example, might reflect clearer information, fewer participants, or people deciding not to ask for help. Decide what you need to learn before choosing a measure. Once the task and uncertainty are clear enough, turn the proposed delivery into a brief with an owner, scope, exclusions, and an appropriate evidence gate. Keep the earlier version and the reason for any revision. A short record of what changed prevents a team from remembering that it knew the answer all along. The goal is not a perfect sentence that survives forever. It is a precise, revisable description that helps people spend their next effort on a real difficulty rather than on the most attractive imagined solution. **Give the work a clear boundary:** Turn a supported problem and a proposed response into a complete, owned piece of work. https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief ## Problem statement and evidence worksheet Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** A useful problem statement leaves room for the answer to surprise you. ## Questions ### What are the parts of a useful problem statement? Name the person, situation, task, barrier, and consequence. Keep a short evidence note beside the sentence, including source dates, limits, assumptions, and missing perspectives. The statement should describe a difficulty without requiring one particular solution. ### What is the difference between a problem statement and a project brief? A problem statement describes the difficulty to understand. A project brief agrees on a proposed piece of work: its promise, scope, owner, constraints, and decision gate. A brief can refer to a problem statement, but a completed brief does not prove the original problem or proposed solution. ### Can a problem statement be written before research? Yes, as a clearly labelled provisional statement. Use it to choose questions and relevant participants, then revise it from evidence. Do not present an initial assumption as an established need simply because it has been written in a structured format. ### How do I know if my problem statement already contains a solution? Ask whether it requires a particular feature or channel and whether two genuinely different responses could address it. A person needing to confirm an arrival time leaves options open; a person needing an app notification may prescribe an answer before the context is understood. ## Sources - GOV.UK Service Manual: learning about users and their needs: https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs — Reference for distinguishing a person's goal from a proposed solution. The worksheet and volunteer-arrival example are original practical illustrations. - GOV.UK Service Manual: how the discovery phase works: https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works — Further reading on understanding the problem and constraints before committing to build. This article is not a formal discovery process or an endorsement by GOV.UK. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-write-a-problem-statement --- # How to prioritise assumptions before building your next idea. Find the belief that could change your next commitment. A practical assumption map for a small mission-driven project, with an example, evidence boundaries, and a worksheet. ## The direct answer Prioritise assumptions by writing each belief clearly, asking what would fail if it were wrong, and checking what relevant evidence you actually have. Investigate important, weakly supported assumptions before committing to a larger build. Choose a method that can answer the specific question, define its limits and decision rule in advance, and record the result without treating a completed test as proof of demand or impact. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 20, 2026 - Updated: Oct 20, 2026 - Scripture: Luke 14:28 - Read: 7 min - URL: https://www.agent-six33.com/journal/how-to-prioritise-assumptions-before-building > For which of you, desiring to build a tower, does not first sit down and count the cost > — Luke 14:28 An idea can have a compelling mission, an elegant design, and a long feature list while depending on one unexamined belief. Perhaps people cannot access the format you chose. Perhaps the person who would maintain the information has no capacity to do so. More polished delivery will not repair a promise that depends on something untrue. An assumption map makes those dependencies discussable before a bigger commitment. The method here is an original planning aid for a small, low-risk project. It is not a numerical risk model, a formal evaluation, or a way to bypass legal, safety, safeguarding, or professional review. Some uncertainties must be resolved through qualified review, not through an experiment with people who could be harmed. ## 1. Name the next commitment you might change. Start with a concrete decision: whether to build an account system, print a first batch, recruit a pilot group, or ask a coordinator to maintain a resource. A broad question such as will this mission succeed is too large for a useful assumption map. You need a decision that could reasonably change when new evidence arrives. Write what the commitment would require in time, effort, money, or responsibility, without inventing precise figures you do not know. Then name the part that is hard to reverse. You may learn something with a draft before ordering a full print run, or confirm an operational owner before promising weekly updates. The map should influence an actual choice, not become another document that sits beside an unchanged plan. ## 2. Turn a broad belief into specific assumptions. GOV.UK's alpha guidance focuses attention on the assumptions that could prevent a service from working. Use that principle without importing a government delivery timetable into a small project. Ask what must be true about the person's need, the proposed experience, the delivery arrangements, and the conditions for keeping the promise over time. Separate people need help choosing a role from people will use our new page and the team can keep the page current. Each is a different belief and may need different evidence. Avoid combining them into people want our solution. One interview account cannot automatically support all three, and a working prototype cannot confirm that someone has accepted an ongoing maintenance responsibility. ## 3. Compare the consequence of being wrong with the evidence available. For each assumption, ask what would change if it were false. Would you adjust wording, change the format, stop a planned feature, or withdraw the promise? Then record the most relevant evidence you have and its limits. A dated observation with likely users is different from a colleague's confident opinion; an old observation in a different context may still leave the current question open. You can discuss importance and support in plain language rather than multiplying invented scores. For example: important because the promise fails without current information; weakly supported because no maintenance owner has agreed to it. Keep the reason beside the judgement. A low-looking score must never be used to wave away a safety or access concern that requires specialist attention. ## 4. Match the learning method to the uncertainty. Use an interview to understand a recent experience, an observed task to examine whether someone can use a proposed version, and an operational check to confirm a dependency with the people who own it. These methods answer different questions. Asking whether a page looks helpful is not the same as watching someone use it; a friendly reaction does not establish a future purchase or repeated use. Write the question, method, decision rule, and limitations before the test. Keep the effort proportionate, but do not make a promise incomplete simply to make a test small. If a person would rely on information that has not been checked, resolve that dependency before inviting them to act on it. Choosing another method, asking for qualified review, or stopping can each be the right next step. **Define the small test before running it:** Keep the question, observations, decision rule, and limits together. https://www.agent-six33.com/journal/how-to-plan-a-small-pilot ## 5. Work through a hypothetical assumption map. Imagine a team considering a searchable volunteer-role directory. This is a hypothetical example, not a SIX33 result. The proposed directory depends on three beliefs: people need help finding a suitable role, a searchable list helps them choose, and coordinators can keep availability accurate. The team has recent accounts about unclear options but no observed use of a directory and no agreement about maintenance. The maintenance assumption matters before a public pilot: stale availability would make the promise unreliable even if search worked perfectly. A first action is to ask the responsible coordinators what updating would involve and whether anyone can own it. That is an operational dependency check, not evidence that the directory has demand. If nobody can maintain the information, the team may need a smaller, dated resource or a different service arrangement. If the dependency can be resolved, the next uncertainty is whether the proposed list helps people complete the task. A bounded prototype session can investigate selection and confirmation, recording assistance and confusion. It cannot establish long-term participation, the size of the wider market, or impact on the community. The map has earned its place if it changes the order or scope of the work before a costly commitment. ## 6. Record what changed, including what remains unknown. After the learning step, keep the result and interpretation separate. Record which version was involved, what happened, who or what the evidence describes, and whether the original decision rule was met. If you change the rule afterward, retain the original and explain why. Otherwise an ambiguous result can be quietly rewritten as the answer the team hoped for. Update the assumption's status in bounded language: supported for this context, contradicted in this test, or still unresolved. Do not mark an assumption permanently proven. A different audience, a larger delivery, or a new operating arrangement may change what is relevant. Give unresolved assumptions an owner and a review trigger so uncertainty stays visible rather than disappearing from the document. Finally, state the next decision: proceed with a limited commitment, change the response, gather different evidence, or stop. A completed map is not the outcome. The useful result is a better sequence of responsible commitments, with fewer unsupported beliefs hidden inside a public promise. Keep completed worksheets private when they refer to participants, internal constraints, or material that was not agreed for publication. **Revise the brief from what you learned:** Change the scope, owner, or promise when the evidence calls for it. https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief ## Assumption map and next-test worksheet Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** Test the belief that could change the commitment, not the one that is easiest to make look successful. ## Questions ### What is an assumption map? It is a record of the beliefs a proposed commitment depends on, the consequence if each is wrong, and the evidence currently available. Its purpose is to choose a responsible next learning step, not to give a speculative plan a scientific-looking score. ### Which assumption should I test first? Start with an important, weakly supported belief that could change the next commitment. Resolve dependencies that make a test unsafe or the promise unreliable before inviting people to rely on it. The right order depends on the actual decision, context, and required reviews. ### Is an assumption map the same as a risk register? No. This worksheet organises learning about beliefs behind a proposed project. A formal risk register may have different governance, assessment, and control requirements. Do not use a simple assumption map to replace a required safety, legal, safeguarding, or professional review. ### Does a successful prototype validate the whole idea? No. A prototype can provide evidence about a particular task with a particular version and group. It does not automatically establish wider demand, long-term use, operational feasibility, causation, or impact. State what the method could and could not answer. ## Sources - GOV.UK Service Manual: how the alpha phase works: https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works — Reference for investigating consequential assumptions with proportionate prototypes. The worksheet, prioritisation questions, and directory example are original illustrations, not a government risk model. - GOV.UK Service Manual: how the discovery phase works: https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works — Further reading on understanding a problem and its constraints before committing to a solution. No endorsement of SIX33 is implied. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-prioritise-assumptions-before-building --- # How to write a mission statement for a faith-based business. Who you serve, what you do for them, why it matters to you before God, and what you will never claim. A four-part template, two tests, and how to root it in Scripture without turning it into a slogan. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 20, 2026 - Updated: Oct 20, 2026 - Scripture: Habakkuk 2:2 - Read: 4 min - URL: https://www.agent-six33.com/journal/how-to-write-a-mission-statement-for-a-faith-based-business > Write the vision; make it plain on tablets, so he may run who reads it. > — Habakkuk 2:2 God told Habakkuk to write the vision down and make it plain — plain enough that someone could read it and run. That is the whole job of a mission statement. Not to sound impressive. To be clear enough that the people doing the work know which way to run. Most faith-based businesses either skip this or overdo it. Skipped, the business drifts toward whatever sells. Overdone, the statement becomes a paragraph of spiritual language nobody can act on: “to glorify God and transform lives through excellence in everything we do.” True, maybe. But it cannot tell you what to say yes or no to on Monday morning. Here is a simple way to write one that can. I use the same approach for SIX33, whose foundation is one verse — Matthew 6:33 — and one sentence the brand uses to describe itself. ## 1. Use four parts: who, what, why, and what you won't claim. A useful mission statement answers four questions. Who do you serve? What do you do for them? Why does it matter — to them, and to you before God? And the one most statements leave out: what will you refuse to claim until you can prove it? That last part is what keeps a faith-based business honest when growth is slow. Deciding in advance that you will not call sales “lives changed” protects your integrity at exactly the moment it is under pressure. - Who: a specific group of people, not “everyone.” - What: the concrete thing you do or make for them. - Why: the conviction underneath — the reason you would keep going if it were hard. - Won't claim: the overstatement you are ruling out now. ## 2. Start from a one-sentence template. Write a first draft with this template, then cut every word that does not help someone make a decision: “We [do what] for [whom] so that [what changes for them], because [our conviction]. We will not claim [overstatement] until we can show it.” A hypothetical example: “We make durable, well-designed workwear for tradespeople so that the clothes outlast the job, because work done heartily is worship. We will not claim social impact until we can show it.” Plain enough to run with. **Build a mission-driven brand from zero:** How to turn the sentence into one useful promise and the smallest complete version of it. https://www.agent-six33.com/journal/how-to-build-a-mission-driven-brand-from-zero ## 3. Root it in Scripture without turning it into a slogan. A verse can anchor a mission without decorating it. The test is whether the verse changes decisions. SIX33 is built on Matthew 6:33 — “seek first the kingdom of God and his righteousness, and all these things will be added to you” — and the brand describes the principle in one line: get the first thing right and everything else falls in order behind it. That is a decision rule, not a tagline. It tells you what comes first when priorities collide. Pick the verse that actually governs how you work, not the one that looks best on a wall. Then ask: what would we do differently if we took this seriously? **What Matthew 6:33 means:** The verse behind SIX33, and why it is a decision rule rather than decoration. https://www.agent-six33.com/matthew-6-33 ## 4. Run two tests: the stranger test and the Monday test. The stranger test: read the statement to someone who does not know your business. Can they repeat back who you serve and what you do? If not, it is too abstract. The Monday test: take a real decision you face this week — a new product, a partnership, a price. Does the statement point to an answer? If every option fits it equally, it is not guiding anything yet. - Stranger test: can someone repeat it back after one reading? - Monday test: does it settle a real decision this week? - Honesty test: is every claim in it already true, or clearly framed as an aim? ## 5. Publish it, then let your record prove it. Put the statement where customers can see it — and then let the work, not the wording, make the case. Report what you actually did against it, including the seasons when the honest answer is small. A mission statement is a promise; your public record is the evidence. **Write an impact report people trust:** How to report against your mission without inflating the result. https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust > **The short version:** Write the vision and make it plain: who, what, why, and what you won't claim. Root it in the verse that actually governs your decisions, test it on a stranger and on Monday, then let your record prove it. ## Questions ### How do you write a mission statement for a faith-based business? Answer four questions in one or two sentences: who you serve, what you do for them, why it matters (including your conviction before God), and what you will not claim until you can prove it. Then test it on a stranger and on a real decision. ### Should a Christian business put a Bible verse in its mission statement? Only if the verse actually governs decisions. A verse that changes what you say yes or no to anchors the mission; one used as decoration turns it into a slogan. ### What is a good mission statement template? “We [do what] for [whom] so that [what changes for them], because [our conviction]. We will not claim [overstatement] until we can show it.” ### What is the difference between a mission and a vision statement? A mission statement says what you do now and for whom. A vision statement describes the future you are working toward. Both should be plain enough to act on. ### What is SIX33's mission? SIX33 is a Christian lifestyle and performance culture brand built on Matthew 6:33 — seek first the Kingdom of God. Its principle is to get the first thing right so everything else falls in order behind it. It has not launched, and its published verified impact is zero. ## Sources - Straight answers — SIX33.World: https://www.six33.world/answers — SIX33's own description and Matthew 6:33 foundation — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-write-a-mission-statement-for-a-faith-based-business --- # How to choose a brand name with meaning: the story behind SIX33. Meaning before cleverness, short enough to say, available everywhere it needs to be, and a story worth telling. Plus how Seek First Brand became SIX33 — and why renaming is allowed. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 20, 2026 - Updated: Oct 20, 2026 - Scripture: Proverbs 22:1 - Read: 4 min - URL: https://www.agent-six33.com/journal/how-to-choose-a-brand-name-with-meaning > A good name is to be chosen rather than great riches, and favor is better than silver or gold. > — Proverbs 22:1 Proverbs says a good name is worth more than great riches. That is about reputation first — but it is also a useful brief for naming a brand. The name is the first promise people hear. It should carry meaning you can live up to, not hype you will have to explain away. SIX33's name is a reference: Matthew 6:33, “seek first the kingdom of God and his righteousness, and all these things will be added to you.” The brand began in 2014 as Seek First Brand and is being rebuilt in 2026 as SIX33 — the same foundation with a much bigger vision. Same meaning, shorter name, more room to grow. Here is the process I would recommend to anyone naming a brand, ministry, or business from zero. ## 1. Start with meaning, not cleverness. Write down the one idea the brand stands for before you brainstorm a single name. For SIX33, that idea is seeking first — getting the first thing right so everything else falls in order behind it. A name that points back to the core idea gives you a story you can tell for years. A clever name with no meaning has to be propped up by marketing forever. - Write the one idea the name should carry. - List words, references, and images connected to it. - Prefer a name that invites the question “what does that mean?” ## 2. Make it short, sayable, and spellable. People will hear your name before they read it, and type it after hearing it. Say each candidate out loud to five people and ask them to spell it. If most cannot, it will cost you in every conversation. Numbers and references can work — SIX33 is short and memorable — but test that people understand how to write it. - Two syllables to four is the comfortable range. - Spell test: say it, ask people to type it. - Avoid names that only work when explained in writing. ## 3. Check it is available everywhere it needs to be. Before you fall in love with a name, check the domain, the main social handles, and whether anyone already uses it in your space. Trademark rules differ by country, so for anything you plan to grow, search your national trademark database and get proper advice before you print stock. Finding a conflict after launch is far more expensive than finding it now. - Domain: the .com or your country's main extension. - Handles on the platforms you will actually use. - Existing businesses using the name in your category. - Trademark search — and professional advice before scaling. ## 4. Make sure the story is true and worth telling. The best names come with a short true story: where the name came from and what it commits you to. Write that story in three sentences. If it only works with exaggeration, choose a different name. A name is a promise, and Proverbs is right that the reputation behind it is worth more than the money it might make. **Write a mission statement for a faith-based business:** The sentence that should sit behind the name — who, what, why, and what you won't claim. https://www.agent-six33.com/journal/how-to-write-a-mission-statement-for-a-faith-based-business ## 5. Renaming is allowed when the vision outgrows the name. Seek First Brand was a fine name for what it was in 2014. The vision has since grown into a whole world — apparel, Motor, Fight, Outpost, Legends — and the brand is being rebuilt in 2026 as SIX33, with the same Matthew 6:33 foundation. If your name no longer fits what you are building, keep the meaning and change the name. Tell people why; the honesty is part of the brand. **The SIX33 world, as it stands:** The mark, the worlds, and the live front door — observed and dated. https://www.agent-six33.com/brand > **The short version:** A good name is chosen, not just invented: meaning first, short and spellable, available, with a true story behind it — and renamed without shame when the vision outgrows it. ## Questions ### How do you choose a brand name with meaning? Write the one idea the brand stands for, brainstorm names connected to it, keep the candidates short and easy to say and spell, check domain, handles, existing use and trademarks, and choose a name with a true story you can tell in three sentences. ### What does SIX33 mean? SIX33 refers to Matthew 6:33 — “seek first the kingdom of God and his righteousness, and all these things will be added to you.” It began in 2014 as Seek First Brand and is being rebuilt in 2026 as SIX33 on the same foundation. ### Should I trademark my brand name? For anything you plan to grow, search your national trademark database and get professional advice before you invest in stock or signage. Rules differ by country. ### Is it okay to rename a brand? Yes. When the vision outgrows the name, keep the meaning and change the name, and explain the reason openly. Seek First Brand being rebuilt as SIX33 is an example. ### Can a brand name be a Bible reference? Yes — SIX33 is one. A Scripture reference works best when the verse genuinely governs how the brand operates, so the name carries a commitment rather than decoration. ## Sources - Straight answers — SIX33.World: https://www.six33.world/answers — What SIX33 means; Seek First Brand (2014) rebuilt as SIX33 (2026) — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-choose-a-brand-name-with-meaning --- # How to synthesise customer interviews into a useful decision. A practical way to move from interview notes to traceable findings, an honest uncertainty, and one next test — with a worked example and research synthesis template. ## The direct answer Synthesise interviews by separating what each person said or did from your interpretation, grouping related observations, checking disagreements, and writing findings that point back to their sources. Choose a decision and a next test for each important finding. Keep the limits visible: a small interview round can reveal problems worth investigating, but it cannot establish how common they are across a market. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: James 1:19 - Read: 6 min - URL: https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews > Let every person be quick to hear, slow to speak, slow to anger. > — James 1:19 The interviews are finished. Your notes contain a difficult story, several suggestions, and one sentence that would look excellent above a launch button. None of that tells you what to build next until you distinguish the evidence from the story you want to tell about it. This is a practical synthesis method for a founder or small team learning about a low-risk product, resource, or service. It is not a formal qualitative analysis protocol or a substitute for specialist research where decisions affect safety, eligibility, or access to essential support. Its output is modest: a short, inspectable decision note, not a declaration that the market has been validated. ## 1. Write the question and the boundaries of this round. Start the synthesis document with the decision you were trying to inform. For example: should the next prototype help first-time volunteers choose an available role, or help them contact a coordinator? Those are different jobs. Without a question, the most memorable comment can become the priority simply because it is memorable. Record whom you spoke with, how you found them, the experience you asked about, and what you did not investigate. Use participant codes in the working summary rather than names. If all participants came through your own network, say so. If nobody used an earlier version, do not describe their accounts as feedback on that version. A clear boundary makes the eventual recommendation easier to challenge constructively. **Prepare a better interview round:** Start with recent experiences and neutral questions before analysing the answers. https://www.agent-six33.com/journal/first-five-customer-interviews ## 2. Separate an observation, an interpretation, and an idea. GOV.UK's analysis guidance distinguishes observations, findings, and actions. Keep that separation in your own notes. An observation records something you heard or saw; a finding explains a pattern; an action proposes what to do. These should be connected, but they should not silently become interchangeable. Consider three deliberately invented notes. Observation: P02 said they sent a message because the page did not say which roles were still available. Interpretation: uncertainty about availability may delay choosing. Idea: add an availability label. The first statement is a participant's account, not an observed delay. The second is a tentative explanation. The third is one possible response, not a requirement handed down by the interview. Give each observation an ID and a pointer to the source note or permitted recording timestamp. Distinguish exact quotations from paraphrases. If you cannot check the wording, remove quotation marks. If an interviewer supplied an answer or showed a solution, retain that context beside the response rather than polishing it away. ## 3. Group related observations, then look for the awkward cases. Place observations about the same difficulty together. You might use a document, spreadsheet, or physical cards; the tool matters less than keeping each source attached. Start with practical labels such as choosing a role, finding the meeting place, or asking for help. Rename a group if its contents no longer fit. A theme is a working container, not proof that everyone has the same need. Then deliberately search for contradictions. Who completed the task without that difficulty? Did a person have prior experience, a helpful friend, a different device, or information the others lacked? Keep an isolated but consequential barrier visible too. A concern affecting access or safety should not disappear because it was mentioned only once. Do not use the largest pile of notes as an automatic voting system for the roadmap. ## 4. Write a finding with enough context to be challenged. Use a simple structure: in this situation, these participants described or demonstrated this difficulty; the consequence appears to be this; here is the evidence and here is what remains uncertain. Avoid broad labels such as people hate forms. A narrower finding about a specific question, task, or handoff gives you something you can change and examine. Count participants rather than quotations when describing how many people raised a topic. One talkative participant might generate ten notes. Do not turn those into ten independent votes. Counts from a small, selected interview group describe that group; they are not population percentages, and silence is not evidence that a problem was absent. If the topic was not asked consistently, state that before making any comparison. ## 5. Work through one finding without inflating the conclusion. Here is a hypothetical synthesis, not reported SIX33 research. Four first-time volunteers describe their latest attempt to choose a role. P01 and P02 say they contacted a coordinator because availability was unclear. P03 says an experienced friend explained the options. P04 chose directly from a recently updated list. These are accounts of past events, not observations of the four people using a prototype today. A supportable finding is that two interviewees described needing extra contact to resolve availability, while the other accounts suggest that timely information or personal help may matter. An unsupported headline is that half of all volunteers abandon signup. Nobody established that population rate, and contacting a coordinator is not the same thing as abandoning a task. The next decision could be to prototype a clearly dated list of available roles before building a larger matching system. The next test would observe whether new participants can choose an appropriate role and identify how to confirm it, recording assistance and misunderstandings separately. That test still needs its own scope and decision rule. The interviews suggested the uncertainty; they did not settle the solution. ## 6. Close with a decision, an owner, and a checkable next step. For each important finding, write whether you will investigate, change something, leave it unchanged for a stated reason, or stop a proposed direction. Name who owns the next step and when the decision will be revisited. Keep a link to the prototype or brief version so a later team member can understand what the recommendation actually changed. Share the smallest useful summary with the people who need it. Keep raw notes and identifying details within the access and retention arrangements agreed with participants. Permission to discuss an experience privately is not permission to publish a quotation, identifiable story, or recording. A public update can describe the decision and its limits without exposing the people whose experiences helped you make it. **Turn the decision into a one-page brief:** Name the user, promise, scope, owner, and evidence gate before adding a feature list. https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief ## Interview synthesis and decision note Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** A useful synthesis does not make the interviews sound unanimous. It makes the next decision traceable. ## Questions ### What is customer interview synthesis? It is the process of connecting source-linked interview observations to bounded findings and decisions. A useful synthesis preserves context, separates evidence from interpretation, includes contradictions, and identifies what to test next instead of simply collecting favourable quotes. ### Is affinity mapping the same as research synthesis? No. Affinity mapping groups related observations and can help reveal themes. Synthesis also requires interpreting those groups, checking source material and disagreements, acknowledging limits, and making a reasoned decision. A wall of clustered notes is not the finished finding. ### Can I report percentages from five interviews? Counts can describe the people interviewed if the question and denominator are clear. They do not establish population prevalence when participants were not sampled for that purpose. Prefer a precise account such as two of the five interviewees described this difficulty, alongside recruitment and questioning limitations. ### What if interviewees disagree? Keep the disagreement. Compare the task, prior experience, assistance, and circumstances before combining accounts. Different experiences may point to different needs, an unclear question, or an uncertainty that needs another test. Do not remove an inconvenient account to make the finding sound cleaner. ## Sources - GOV.UK Service Manual: analyse a research session: https://www.gov.uk/service-manual/user-research/analyse-a-research-session — Reference for distinguishing observations, findings, and actions. The decision-note structure and four-volunteer example here are original practical illustrations. - GOV.UK Service Manual: sharing user research findings: https://www.gov.uk/service-manual/user-research/sharing-user-research-findings — Further reading on making research useful to the people deciding what to improve. No endorsement of SIX33 is implied. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews --- # How to write a one-page project brief that makes the next step clear. Turn a mission into a bounded piece of work: one person, one problem, one complete promise, and a decision gate. Includes a worked example and a downloadable brief template. ## The direct answer A useful one-page project brief names whom the work serves, the problem and evidence behind it, the smallest complete promise, what is in and out of scope, the owner and constraints, and how the next decision will be made. It aligns people before detailed planning. Keep assumptions labelled, give unknowns an owner, and link to a separate pilot plan when the promise needs testing. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: Luke 14:28 - Read: 7 min - URL: https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief > For which of you, desiring to build a tower, does not first sit down and count the cost > — Luke 14:28 A mission can be true and still be too broad to assign. Help our community, build a better resource, and make the experience easier express intention. They do not yet tell a collaborator what they are responsible for delivering, what they should leave alone, or when the work is ready for a decision. A brief is the bridge between the intention and the work. This guide offers an original working format for a small, low-risk initiative, not a contract, funding application, safeguarding process, or professional approval. A page is a useful constraint, not a virtue in itself: link to essential detail instead of making safety, accessibility, or important dependencies disappear to fit a layout. ## 1. Name a person, a situation, and a job to finish. Write who needs help, when the difficulty occurs, and what the person is trying to accomplish. For example: a first-time volunteer needs to identify an available role before contacting the team. That sentence is more useful than we need an improved portal because it leaves room to discover whether a portal is needed at all. GOV.UK's discovery guidance recommends understanding the problem and questioning a preselected solution before committing to build. Apply that distinction to your brief: keep the user's task on one line and your proposed response on another. Include people who may need a different format or support route. Do not define the audience only as the people most convenient for your team to recruit. ## 2. Put evidence, assumptions, and unknowns on separate lines. Evidence might be a dated support request, a source-linked interview finding, or an observed difficulty with the current version. Record what the source actually supports. A request for a printable sheet supports investigating that format; it does not prove that every visitor wants print or that a sheet will improve the outcome you care about. Write assumptions explicitly. We assume the role list can be kept current is operationally important, not embarrassing. Then assign a person to check the unknowns that could change the approach. If nobody knows who owns the information, that unanswered question may be the first piece of work. A polished brief is not permission to convert an untested assumption into a public claim. **Create a traceable research finding:** Keep source observations, interpretations, and the resulting decision connected. https://www.agent-six33.com/journal/how-to-synthesise-customer-interviews ## 3. Define the smallest complete promise and its boundaries. Describe what a person will be able to do with the delivery. Then state the minimum contents or behaviour needed for that promise to be real. A role sheet might need available options, the date checked, a clear way to confirm a place, and an alternative contact method. A beautiful title without usable information is not a complete delivery. Put exclusions beside inclusions. For this version, perhaps no accounts, automated matching, public directory of volunteers, or collection of personal stories. An exclusion should protect focus without quietly excluding people: no account needed is different from no assisted option offered. If an essential access need cannot be met, record the gap and resolve it before calling the delivery ready for those users. ## 4. Assign ownership, constraints, and a real handoff. Name one person responsible for the delivery and another, if needed, who can approve its factual accuracy or operational use. State the time and resources actually available, the review date, and dependencies that could block release. Use an explicit unknown rather than inventing a budget or deadline to make the document look finished. Agree how the delivery will stay useful after the first handoff. Who updates changed information? What happens if that person is unavailable? Where can a reader report a mistake? A brief for a small resource does not need a large governance system, but it does need someone who accepts the maintenance task. Otherwise a successful launch can become an unreliable promise a week later. ## 5. Read a worked example with a deliberately limited claim. This is a hypothetical example, not a SIX33 project result. A community team wants first-time volunteers to choose a suitable role before the next session. Its evidence is a source-linked finding from a small interview round: some participants described needing extra contact to understand which roles were available. The team still does not know whether unclear wording, stale information, or another issue caused the difficulty. The first delivery is one dated, mobile-readable and printable role list with an accurate confirmation route. Accounts and automated matching are out of scope. A named coordinator checks the information before sharing and owns updates. The release gate is that the information is checked, the contact route works, and the required formats are reviewed. Passing that gate establishes delivery readiness, not improved volunteering outcomes. A separate pilot then observes whether people can select a suitable role and identify the next step without assistance. The brief points to that test rather than declaring a success threshold after seeing results. If people still need help, the next decision is to investigate the remaining barrier. Neither publishing a sheet nor receiving praise is counted as a life changed. ## 6. End with the next decision, not an endless feature list. Distinguish a delivery check from a learning check. Delivery checks ask whether the agreed work exists and functions. Learning checks ask whether the intended person can use it or whether a proposed explanation deserves more investigation. A longer-term outcome claim needs an appropriate method and follow-up beyond either checklist. Before beginning, ask collaborators to restate the promise and the exclusions in their own words. If they describe different projects, fix the brief first. Put a version and date on the agreed document. When new evidence changes the scope, keep the reason beside the revision rather than silently rewriting the original intention. The goal is not to freeze learning; it is to make changed decisions visible. Keep a list of attractive extras outside the brief. Revisit them only if they serve the task and fit the next decision. You can have a large vision and still give today's work a clear edge. A brief earns its space when another person can take responsibility for a complete, useful step without needing to guess what you meant. **Write the pilot plan separately:** Specify the test, observations, limits, and decision rule before delivery. https://www.agent-six33.com/journal/how-to-plan-a-small-pilot ## One-page project brief Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** Keep the mission large and the next promise precise enough for somebody to own. ## Questions ### What should a one-page project brief include? Include the person and problem, the evidence and assumptions, one complete promise, scope and exclusions, an owner, constraints, review and maintenance arrangements, and the evidence needed for the next decision. Link to essential detail instead of omitting it to fit a page. ### What is the difference between a project brief and a project plan? The brief aligns people on why the work matters, what it includes, and who owns it. The plan details tasks, dependencies, timing, and delivery. A pilot plan additionally specifies the question, observations, limits, and decision rule for testing a promise. ### Can I write a project brief before doing interviews? Yes, as a provisional brief with assumptions clearly labelled. Use it to identify what you need to learn rather than to claim that demand is established. Revise it when relevant evidence changes the person, problem, scope, or proposed approach. ### Does completing the brief mean the project is validated? No. A brief records an agreed intention and a decision process. Completing it does not demonstrate demand, usability, impact, safety, or professional approval. Those require evidence and reviews appropriate to the claim and the risks of the actual work. ## Sources - GOV.UK Service Manual: how the discovery phase works: https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works — Further reading on understanding a problem, constraints, and assumptions before committing to a solution. The brief format and volunteer-role example are original illustrations, not a government template. - GOV.UK Service Manual: learning about users and their needs: https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs — Reference for keeping a person's task distinct from a proposed feature. This small-project aid does not replace a formal discovery process. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief --- # How to plan a small pilot: a one-page test plan. Turn an uncertain idea into a small, inspectable test: one question, one complete promise, clear observations, and a decision you define before the results arrive. ## The direct answer A useful pilot tests one important uncertainty with a small, bounded delivery. Define the person, promise, question, observation method, time window, and decision rule before starting. Record assistance, missing responses, and limitations. A completed pilot can justify a next test; it does not automatically prove demand, causation, or lasting impact. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: Luke 14:28 (excerpt) - Read: 7 min - URL: https://www.agent-six33.com/journal/how-to-plan-a-small-pilot > For which of you, desiring to build a tower, does not first sit down and count the cost… > — Luke 14:28 (excerpt) A pilot should make the next decision clearer. It is not a miniature launch designed to produce a flattering screenshot. You are choosing a small enough setting to notice where the promise breaks, while keeping enough of the real experience to learn something useful. If the result could not change what you build next, the activity may be a demonstration rather than a test. The one-page plan below is for low-risk tools, workshops, community experiences, and services. It is not a substitute for specialist oversight where health, safety, safeguarding, significant money, or regulated decisions are involved. Start with a question you can investigate responsibly. A smaller pilot does not make an unsafe intervention acceptable. Planning is a form of stewardship, not a promise that every outcome can be controlled. Write what you hope to learn, what would count against your preferred answer, and what you will do if the test cannot answer the question. That makes an inconclusive result useful instead of embarrassing. ## 1. Choose the decision before choosing the activity. Begin with the decision that is currently blocked. Should you simplify the worksheet, offer a guided session, or stop building this particular solution? Then write the uncertainty underneath it. “Do first-time founders understand the promise without an explanation?” is narrower and more observable than “Does our mission resonate?” Keep a learning question separate from a growth target. An attendance target can help you organize an event, but reaching it will not tell you whether the experience worked. A pilot question should name what you intend to observe and the decision that observation could inform. The GOV.UK Service Manual similarly connects service purpose, hypotheses, and meaningful measurements; the planning format here is an original SIX33 worksheet, not a government certification. - Decision: what might we continue, change, or stop? - Uncertainty: what do we not yet know? - Question: what observation could reduce that uncertainty? - Disconfirming signal: what would challenge our preferred explanation? **Listen before designing the pilot:** Use recent customer experiences to choose a question worth testing. https://www.agent-six33.com/journal/first-five-customer-interviews ## 2. Make the scope small, but keep the promise complete. Choose a tightly described participant group and the simplest experience that can still deliver the promised value. A promise worksheet might be one page and a short session. If the promise includes choosing a first test, the participant needs to leave with a test, not merely receive a PDF. Cut decorative features before cutting the part that makes the experience useful. Write what is outside the pilot. You may be testing whether someone can complete a planning task, not whether their business will succeed. Do not let a convenient short-term measure stand in for that larger outcome. Also record the delivery conditions: a founder-led session, a self-guided page, and a workshop with peer support are different versions of the experience. - For whom: a specific situation and relevant recent experience. - Complete means: the recipient can do a named thing. - Included: the smallest materials, support, and follow-up needed. - Not tested: the larger claims this pilot cannot answer. **Define one complete promise:** Use the blueprint before turning your promise into a pilot. https://www.agent-six33.com/blueprint ## 3. Decide how to observe the task before running it. Choose what you will record, when, and by whom. For a worksheet, this could be whether the participant identifies a person, writes a complete promise, and chooses a dated next action. Record whether each step was completed independently, completed after assistance, not completed, or not observed. Those categories are more useful than a single “successful” checkbox. GOV.UK describes moderated usability testing as observing people attempting realistic tasks. Apply that principle by describing the goal without explaining the answer. If you intervene, help the person, but record the intervention. Assistance is part of the evidence, not a failure you must hide. Keep observed actions, participant reports, and your interpretations in separate fields. - Task and observable completion definition. - Evidence source: direct observation, participant report, or another named record. - Assistance provided and where it was needed. - Date, setting, version of the experience, and missing observations. ## 4. Write a decision rule, not a claim of statistical proof. A decision rule helps a small team avoid moving the goalposts after seeing the results. For example, you might decide that any repeated misunderstanding of the core promise triggers a wording revision before another round. That is an operational choice. It is not a validated threshold, an industry benchmark, or proof that a particular sample represents a wider population. Use a threshold only if you can explain why it is appropriate to your decision. Keep the underlying counts and case notes even when you use a rate. Two completions out of three observations should remain “2 of 3,” with the context attached. A percentage alone can make a very small convenience sample look more conclusive than it is. - Continue when: the evidence is sufficient for the next limited test. - Change when: a defined problem or uncertainty remains. - Stop or pause when: the promise is not useful, delivery is unsafe, or the question cannot be answered responsibly. - Inconclusive when: missing evidence or changed conditions prevent the intended decision. ## 5. Work through a hypothetical pilot before inviting anyone. This example is hypothetical and is not a SIX33 result. A builder wants to test whether a one-page promise worksheet is understandable without live coaching. They invite four first-time founders who recently struggled to choose an initial delivery. The task is to name one recipient, describe the complete promise, and choose a dated first test. The version, invitation route, and assistance policy are written down before the sessions. Suppose two participants complete the task independently, one completes it after the builder explains a phrase, and one does not finish. The useful record is two independent completions, one assisted completion, and one non-completion among four participants. The next decision could be to rewrite the confusing phrase and run another round. “Three of four completed with differing support” may describe the task result; “our worksheet makes founders successful” is not supported by this test. The sample is small and self-selected, the task is short, and business outcomes have not been followed. Keep those limits beside the finding. If the plan changes midway, record which participants saw which version instead of silently treating them as one identical group. **Keep signals on separate lines:** Use the scorecard to avoid adding delivery, use, return, and change into one total. https://www.agent-six33.com/scorecard ## 6. Protect the people and close the learning loop. Explain the purpose, what you will record, how it will be used, and that declining or leaving will not affect access to help. Collect only what the test needs. An anonymous participant code is often enough for an internal learning record. Keep identifiable notes out of public build logs, shared screenshots, and templates. Ask separately before recording, quoting, or publishing a person's story. At the end, compare the result with the original question. Record what changed, what remains unknown, and the next decision with an owner and a date. A pilot that exposes an unsuitable promise can save months of building. That is useful learning, not a transformation claim. If the question concerns later behaviour, plan a proportionate follow-up instead of treating a positive exit comment as an outcome. **Plan an honest follow-up:** Use neutral questions and an explicit response record after the pilot ends. https://www.agent-six33.com/journal/how-to-follow-up-after-a-pilot ## One-page pilot plan Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** A pilot earns its value by improving the next decision, not by making the launch story sound certain. ## Questions ### What should a one-page pilot plan include? Include the decision, uncertainty, participant group, complete promise, task, evidence source, time window, assistance rules, decision rule, privacy boundaries, and limitations. After delivery, add the finding and next decision without changing the original question to fit the result. ### How many people do I need for a pilot? There is no universal number that makes a pilot valid. Choose a scope suited to the question, risk, participant diversity, and observation method. A small learning round can reveal problems, but it cannot by itself establish population-level demand or a causal impact estimate. ### Is a pilot the same as an MVP? Not necessarily. An MVP describes a minimal product version; a pilot is a bounded test of an experience in a particular setting. A manual service or workshop can be piloted without building software. In either case, keep the useful promise complete. ### What if the pilot result is inconclusive? Publish what was observed and what could not be determined. Missing responses, changed conditions, or an unsuitable observation method may justify another test, not a success label. Do not convert a blank outcome into zero or assume a silent participant had a positive result. ## Sources - GOV.UK Service Manual: setting performance metrics: https://www.gov.uk/service-manual/measuring-success/how-to-set-performance-metrics-for-your-service — Purpose-led measurement and combining metrics with user research. The worksheet, thresholds, and worked example here are original and illustrative. - GOV.UK Service Manual: moderated usability testing: https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing — Task-based observation and realistic, non-leading task design. Not an endorsement of this guide or its example. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-plan-a-small-pilot --- # How to follow up after a pilot: questions, script, and evidence. Find out what happened after delivery without turning compliments into outcomes. Use a neutral follow-up script, record non-response, and separate reported change from attribution. ## The direct answer Follow up at a time matched to the behaviour you want to understand. Ask what the participant did, when, what got in the way, and what else influenced the result. Record how many were invited, reached, and responded. Keep non-response unknown, distinguish reports from observation, and ask separately for permission to publish a quote. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: James 1:19 - Read: 7 min - URL: https://www.agent-six33.com/journal/how-to-follow-up-after-a-pilot > let every person be quick to hear, slow to speak, slow to anger; > — James 1:19 A warm comment at the end of a session tells you how someone answered at that moment. It does not tell you what happened when they returned to their day. Follow-up closes that gap. The aim is not to collect a testimonial for the launch; it is to understand use, friction, later behaviour, and the limits of what you can honestly report. This guide is for a low-risk project, tool, workshop, or community experience where a voluntary conversation is appropriate. It is not a clinical outcome instrument or a substitute for specialist evaluation. The question list and message below are original working templates. Adapt them to the experience and make disagreement easy, especially when the interviewer also delivered the help. Being quick to hear means leaving room for an answer that changes the plan. A person may have used the resource differently, forgotten it, disliked it, or benefited from something else. Those are all possible findings. Your mission is better served by an inspectable record than by a sentence that requires the participant to keep encouraging you. ## 1. Match the timing to the behaviour, not the posting calendar. Choose the follow-up point when you design the pilot. If the promised next step is scheduling one conversation, a short interval may be enough to ask whether it happened. If the intended change needs a longer period to become observable, a next-day message cannot answer the question. Write the rationale and actual dates rather than assuming one interval fits every project. Separate immediate experience, later action, and sustained change. You can ask about clarity immediately after delivery, action at the first follow-up, and persistence in a later round if justified. If you change the timing or only reach participants who are easy to contact, record that. The missing part belongs in the report, not outside the denominator. - Immediate question: could the person understand and use the experience? - Later question: what did they actually do afterward? - Persistence question: did the intended behaviour continue, if this was observed? - Limit: what does this time window leave unanswered? **Put follow-up in the original plan:** Decide the question and observation window before the results arrive. https://www.agent-six33.com/journal/how-to-plan-a-small-pilot ## 2. Make the invitation voluntary and separate from promotion. Say who is asking, which experience you are discussing, what you want to learn, and how long the conversation should take. State that a negative answer is useful and that participation does not affect access to support. Offer a simple way to decline. Agree on follow-up during the original experience instead of surprising people with repeated messages. Do not ask for a public testimonial in the same opening request. Research participation and publication permission are different decisions. A person who agrees to tell you what happened has not automatically agreed to appear on your website. Keep recording, attribution, and quotation permissions separate and use an appropriate process for your setting. - Name the experience and why you are following up. - Give a realistic time commitment and an easy decline. - Explain how notes will be used and who can see them. - Do not make care, belonging, or further help depend on a favourable response. ## 3. Ask for a sequence of events before asking for an opinion. Begin with the participant's own account: “Since the session, what happened with the next step you chose?” Ask for a concrete recent example, then explore the sequence. If they say nothing happened, ask what got in the way without treating the answer as a failure they must defend. Keep the conversation focused on their experience rather than your hopes for the project. The GOV.UK interview guidance supports open, neutral questions and concrete examples. Use the menu below as an original discussion guide, not a survey you must finish at speed. Follow the relevant detail and avoid supplying the explanation. “How much did the worksheet improve your confidence?” assumes an improvement; asking what changed, if anything, leaves the direction open. - What did you do after the session or after opening the resource? - Can you walk me through the last time you tried that next step? - What, if anything, was different from how you handled this before? - What got in the way, or made you decide not to continue? - What else helped or influenced what happened? - Did you use any part of the resource again? Which part, and when? - Is there an example you can describe without sharing someone else's private information? - What have I misunderstood, or not asked, about your experience? ## 4. Keep a response record without guessing what silence means. Keep the original eligible group, invitations sent, people reached, responses received, and relevant usable observations on separate lines. A response can be valuable without answering every question. Record the date and why information is missing when known. Do not repeatedly contact someone until you get a favourable answer; respect their preference and the contact plan you agreed. A non-response is not a positive result. It is also not automatically proof that no action occurred. Leave the outcome unknown. Do not reduce the denominator to respondents without saying so, and do not combine results from different follow-up windows as though everybody had the same chance to act. These distinctions keep the report useful to somebody who was not in the room. - Eligible for this follow-up: [count and definition]. - Invited / reached / responded: [separate counts]. - Usable observation for this question: [count and source]. - Missing or partial information: [what is unknown and why, if known]. - Method and timing: [who asked, when, and whether prompting occurred]. **Keep unknown different from zero:** Use separate signals without converting missing follow-up into an impact number. https://www.agent-six33.com/scorecard ## 5. Write the strongest narrow sentence, not the biggest one. This example is hypothetical and does not describe SIX33 results. Six participants are eligible for a seven-day follow-up after a planning workshop. All six are invited, four respond, and two respondents report completing the next action they chose. One respondent reports no action and one gives an answer that does not establish completion. Two participants do not respond. The completion reports are self-reported, not independently verified. An inspectable sentence is: “At seven-day follow-up, four of six invited participants responded; two reported completing their chosen next action. Two outcomes were unknown because of non-response, and one response did not establish completion. These reports were not independently verified.” Keep the no-action response in the underlying record as well. Do not rewrite this as “our workshop changed a third of participants' lives” or assume the workshop caused the actions. Ask what else might explain the result: prior plans, another resource, a helpful friend, or the person's own effort. An account can support a reported sequence without isolating a cause. For higher-stakes impact claims, get evaluation expertise appropriate to the question; a brief follow-up is not a substitute for a design that can support the inference you want to make. **Put the method beside the finding:** Carry the response record, limitations, and next decision into an honest report. https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust ## 6. Close the loop with the participant and the next version. Thank the person for the actual detail they shared, not for confirming the mission. Explain what you will do next and honour the boundaries you stated. Keep a direct quote distinct from a paraphrase. If a story could identify somebody indirectly, removing a name may not make it safe to publish; choose a less identifying summary or leave it out. Translate the findings into one change you can inspect. For example: participants understood the first question but did not know how to choose a date, so the next version adds a concrete scheduling example. Keep the old and new versions identifiable. A useful follow-up ends with a clearer product or a better question, not merely another paragraph of praise. **Review the report before sharing:** Use the proof pack to keep the finding, method, limitations, and decision together. https://www.agent-six33.com/proof-pack#build-proof-pack ## Pilot follow-up invitation and evidence note Copy this blank template into your private working document. It contains no journal notes or tool drafts. ```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. ``` > **The short version:** Follow up to understand the person's next chapter, not to recruit their words into your preferred story. ## Questions ### What questions should I ask after a pilot? Ask what the person did afterward, what changed if anything, what got in the way, whether they used the experience again, and what else influenced the result. Request a specific example. Avoid questions that assume improvement, gratitude, or a causal effect. ### When should I send a pilot follow-up? Choose timing suited to the behaviour you want to understand and agree on contact during the pilot. There is no universal interval. A short window may capture an immediate next action but cannot establish that a longer-term change lasted. ### How should I report people who do not respond? Report the eligible group, invitations, people reached, responses, and usable observations separately. Leave non-respondents' outcomes unknown. Do not count silence as success or failure, and state when a finding describes respondents rather than everyone invited. ### Can I use follow-up answers as testimonials? Not automatically. Agree separately on recording, attribution, quotation, and publication. Participation in a learning conversation is not blanket permission to publish a person's words or story. A positive quote also does not establish typical results or causation. ## Sources - GOV.UK Service Manual: using in-depth interviews: https://www.gov.uk/service-manual/user-research/using-in-depth-interviews — Open, neutral interviewing and concrete examples. The invitation, question menu, and six-person example are original and illustrative, not reported research. - HM Treasury: The Magenta Book: https://www.gov.uk/government/publications/the-magenta-book — Broader evaluation guidance on design and interpreting findings; use specialist evaluation methods when the claim or risk requires them. This article is a practical learning aid, not an impact evaluation. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing - Evidence and honest impact reporting: https://www.agent-six33.com/journal/topics/evidence-and-impact — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-follow-up-after-a-pilot --- # How to start a Christian clothing brand that lasts. A mission you can say in one sentence, designs people would wear even if they disagreed, small runs instead of a warehouse, honest giving, and a list of people waiting before the first shirt is printed. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: Colossians 3:23 - Read: 5 min - URL: https://www.agent-six33.com/journal/how-to-start-a-christian-clothing-brand > Whatever you do, work heartily, as for the Lord and not for men. > — Colossians 3:23 There are a lot of Christian clothing brands, and most of them sell the same thing: a verse in a nice font on a blank shirt. That is not wrong. But it is not a brand, and it rarely lasts. A brand is a reason people come back — a point of view, a standard of quality, and a promise they can see you keep. Colossians 3:23 sets the bar: whatever you do, work heartily, as for the Lord. Not “put the Lord on whatever you make.” The faith shows up first in the work itself — the fabric, the fit, the honesty of the claims, the way you treat the people who buy from you. The verse on the chest comes second. This is the path I would take from zero, and the one I am taking with SIX33 — a brand that has not launched yet, which is exactly why every step below is something you can do before you have a single customer. ## 1. Say the mission in one sentence before you design anything. Write one sentence that a stranger could repeat: who the brand is for, what it stands for, and what it does beyond selling shirts. If you cannot write it, more designs will not fix it. SIX33's version is built on Matthew 6:33 — seek first the Kingdom, and let everything else fall in order behind it. Then write the sentence you will not say. Not “we are changing the world.” Not “every purchase saves a life.” Decide now which claims you will refuse to make until you can prove them. That decision protects you later, when sales are slow and the temptation to overstate is strongest. - Who it is for — specifically, not “all Christians.” - What it stands for — the conviction under the designs. - What it does beyond the sale — and only what you can actually show. **Build a mission-driven brand from zero:** The longer guide to defining one useful promise and keeping reach separate from real change. https://www.agent-six33.com/journal/how-to-build-a-mission-driven-brand-from-zero ## 2. Design for people who might not share your faith yet. The strongest faith apparel starts conversations instead of ending them. Ask of every design: would someone who disagrees still think it is well made? Would a believer wear it somewhere other than church? Clever beats preachy; quality beats quantity; one strong idea beats ten weak ones. Invest in the basics people actually feel — fabric weight, fit, print durability — before you invest in a logo animation. A shirt that falls apart after five washes preaches something too. - Order samples of every blank you are considering and wash them. - Show three designs to people outside your church and listen. - Launch with fewer, better pieces rather than a full catalogue. ## 3. Choose your production model: print-on-demand or small runs. Print-on-demand means no inventory: a supplier prints each item when it is ordered. It is the lowest-risk way to start and test designs, at the cost of lower margins and less control over quality. Small limited runs mean buying a set quantity up front: better margins, better control, and a reason for people to act — but you carry the risk of unsold stock. Many brands start with print-on-demand to learn what sells, then move proven designs to small runs. SIX33 has chosen intentional limited drops instead of an endless catalogue: when a drop sells through, it moves into a permanent archive rather than being quietly restocked. - Print-on-demand: lowest risk, lowest margin, test freely. - Limited runs: higher margin and control, real inventory risk. - Whichever you choose, say plainly on the product page how it is made. ## 4. Build the list before you print the first shirt. The most valuable asset a new brand can have on launch day is not stock — it is a list of people who asked to hear from you. An email list (not just followers) means you can launch to people who already said yes. SIX33 does this with an Inner Circle: members get first access to the first drop before the public. Give people a real reason to join early, and keep whatever you promise them. Early access, a name on a founding list, a behind-the-scenes look — all good, as long as they are true. **How to build a waitlist before you launch:** The step-by-step guide to growing a list of people who actually want the thing. https://www.agent-six33.com/journal/how-to-build-a-waitlist-before-you-launch ## 5. If you promise giving, make it specific and keep receipts. Many faith brands promise to give. Few say exactly what, to whom, and when — and fewer still show that it happened. Be specific: name the organization, name the amount or percentage, name when you will report. SIX33 names its intended giving publicly — a big part of its heart is raising funds for Love on The World — and has not claimed any giving yet, because it has not launched. **How a business can give — and say so honestly:** Pledges, percentages, and the line between a giving plan and a giving claim. https://www.agent-six33.com/journal/how-a-business-can-give-honestly ## 6. Launch small, report honestly, and let the work speak. Your first drop is a test, not a verdict. Launch to your list, watch what sells and what people say, and write down what you learned. Report your numbers honestly — orders are orders, not “lives changed.” The brands that last are the ones customers trust, and trust is built by saying exactly what happened. **Run the free 30-day proof sprint:** Thirty daily moves from a defined promise to delivery, observed use, and an honest decision. https://www.agent-six33.com/sprint > **The short version:** Work heartily, as for the Lord: a clear mission, wearable designs, small honest runs, a list before launch, and specific giving you can prove. The verse on the shirt comes second. ## Questions ### How do I start a Christian clothing brand? Write a one-sentence mission, design a few strong pieces people would wear even if they do not share your faith, choose print-on-demand or small limited runs, build an email list before launch, make any giving promise specific, and launch small to that list. ### Should a Christian clothing brand use print-on-demand? Print-on-demand is the lowest-risk way to start because there is no inventory, though margins and quality control are lower. Many brands test designs with print-on-demand and move proven designs to small limited runs. ### How do I make a faith brand stand out? Lead with a clear point of view and real quality. Designs that start conversations, durable blanks, and honest claims stand out more than another verse on a blank shirt. ### Is it okay for a Christian brand to make a profit? Yes. Work done heartily and honestly can be worship (Colossians 3:23). What matters is the integrity of the work and the claims — including being specific and truthful about any giving. ### What is SIX33? SIX33 is a Christian lifestyle and performance culture brand built on Matthew 6:33, founded by Daniel Ziedins in Hamilton, Ontario. It plans limited apparel drops with Inner Circle first access and names Love on The World as its intended giving. It has not announced a launch date. ## Sources - Straight answers — SIX33.World: https://www.six33.world/answers — SIX33's limited drops, Inner Circle first access, and named giving to Love on The World — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-start-a-christian-clothing-brand --- # How to build a waitlist before you launch — without fake scarcity. One clear promise, one simple signup, a real reason to be early, regular honest updates, and a launch that keeps every promise you made to the people who waited. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: Luke 14:28 - Read: 4 min - URL: https://www.agent-six33.com/journal/how-to-build-a-waitlist-before-you-launch > For which of you, desiring to build a tower, does not first sit down and count the cost, whether he has enough to complete it? > — Luke 14:28 Jesus asked a practical question: who builds a tower without first counting the cost? A waitlist is how a new brand counts the cost before it builds. It tells you whether anyone actually wants the thing — before you spend money making it. But waitlists have a reputation problem. Fake countdowns, “only 3 spots left” on a list with no limit, and launch dates that slide forever have taught people to distrust them. The good news: an honest waitlist outperforms a manipulative one over time, because the people on it still believe you on launch day. This is how to build one from zero. SIX33 is doing the same thing right now — no launch date announced, no fake countdown, an Inner Circle that walks in first. ## 1. Make one clear promise about what people are waiting for. A waitlist for “something amazing coming soon” grows slowly because nobody knows what they are signing up for. Say what it is, who it is for, and what joining gets them. If you do not have a date, say so. “No launch date yet — members hear first” is more trustworthy than a countdown you might miss. - What it is, in one sentence. - Who it is for. - What joining early actually gets you. - When — or honestly, that there is no date yet. ## 2. Keep the signup to one field and one honest sentence. Ask for an email address and nothing else at first. Every extra field costs signups. Under the button, say exactly what you will send and how often, and make leaving easy. Protect the list from bots with simple checks so the number you report means people, not scripts. - Email only; ask for more later, once people trust you. - State the frequency: “about once a month,” “only at launch.” - One-click unsubscribe in every message. - A hidden honeypot field to filter obvious bots. ## 3. Give a real reason to join early — and only a real one. Early access, a founding name, first pick of a limited run, a behind-the-scenes view of the build — these are real reasons, as long as they are true. SIX33's Founding 633 is an example: the first 633 people to join the Inner Circle become part of the brand's foundation and get the earliest access. A real limit is fine. An invented one is not. Scarcity is honest when it is real and stated: a numbered founding list, a single production run, a date that will not move. It is manipulation when the number is made up. ## 4. Send updates that build trust, not hype. A list goes cold if it hears nothing for months, and it burns out if it hears hype every week. Send short, honest updates when something real happens: a sample arrived, a design changed, a date was set. Building in public works here — people who watched the work are far more likely to buy the result. **How to build in public:** What to share, what to keep private, and how to stay honest when the numbers are small. https://www.agent-six33.com/journal/build-in-public-guide ## 5. Measure the list honestly. A big list is reach, not demand. The numbers that matter are the ones that move: how many people open your updates, how many reply, how many come back. Before launch, a small engaged list beats a large silent one — and it predicts launch day far better. **Vanity metrics vs impact metrics:** How to tell which list numbers can actually change a decision. https://www.agent-six33.com/journal/vanity-metrics-vs-impact-metrics ## 6. Launch to the list first — and keep every promise. On launch day the people who waited go first, exactly as promised. If you said they would get early access, give them real time before the public. If something slips, tell them before anyone else. The way you treat the people who trusted you before there was anything to buy is the brand. **How to start a Christian clothing brand:** The full path from one-sentence mission to a first limited drop. https://www.agent-six33.com/journal/how-to-start-a-christian-clothing-brand > **The short version:** Count the cost before you build: one clear promise, a one-field signup, real reasons to be early, honest updates, and a launch that keeps every promise to the people who waited. ## Questions ### How do you build a waitlist before launch? Make one clear promise about what people are waiting for, use a one-field email signup that says exactly what you will send, give a real reason to join early, send short honest updates, measure engagement rather than size, and launch to the list first. ### Should a waitlist have a launch date? Only if you can keep it. “No launch date yet — members hear first” builds more trust than a countdown that slips. ### Is creating scarcity on a waitlist dishonest? Real, stated limits are honest — a numbered founding list or a single production run. Invented limits, like “3 spots left” on an unlimited list, are manipulation and cost trust. ### How often should you email a waitlist? When something real happens, and at the frequency you promised at signup. Short honest updates keep a list warm without burning it out. ### What is the SIX33 Inner Circle? The SIX33 Inner Circle is the brand's pre-launch list: members get first access to the first apparel drop before the public. The first 633 members are the Founding 633. SIX33 has not announced a launch date. ## Sources - Straight answers — SIX33.World: https://www.six33.world/answers — Inner Circle, the Founding 633, and "no fake countdowns" — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-build-a-waitlist-before-you-launch --- # How a business can give — and say so honestly. A giving plan is not a giving claim. Name the recipient, the amount, and the reporting date; report what actually went out; and never let a promise to give do the work of proof. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 18, 2026 - Updated: Oct 18, 2026 - Scripture: 2 Corinthians 8:21 - Read: 3 min - URL: https://www.agent-six33.com/journal/how-a-business-can-give-honestly > For we aim at what is honorable not only in the Lord's sight but also in the sight of man. > — 2 Corinthians 8:21 When Paul carried a large gift from the churches to Jerusalem, he did something unusual: he arranged for others to travel with it, so nobody could question how it was handled. His reason is 2 Corinthians 8:21 — “we aim at what is honorable not only in the Lord's sight but also in the sight of man.” Generosity was not enough. It had to be visibly trustworthy. Businesses that give face the same test today. “A portion of every sale goes to charity” is one of the most common lines in marketing, and one of the least checked. Customers have learned to tune it out. The way through is not to give less — it is to be specific, report what actually happened, and never let the promise do the work of proof. SIX33 names Love on The World as its intended giving. It has not launched, so it has given nothing yet — and it says so. That distinction is the whole guide. ## 1. Know the difference between a giving plan and a giving claim. A giving plan is a statement about the future: “we intend to give 10% of profit to this organization.” A giving claim is a statement about the past: “we gave $1,240 to this organization last quarter.” Both are fine. Confusing them is not. Before you have given anything, only the plan is true — so present it as a plan. - Plan: “We intend to give…” — honest before launch. - Claim: “We gave…” — only after money actually moved. - Never: “Every purchase changes a life” — unless you can show it. ## 2. Be specific: who, how much, and when. Vague giving language hides the details customers need to trust it. Name the organization. Say whether the amount is a percentage of revenue, a percentage of profit, or a fixed amount per item — these are very different numbers. Say when you will report. - Who receives it — named and linked. - Revenue, profit, or per-item — say which. - How often you give and when you report. - What happens if there is no profit yet. ## 3. Report what actually went out — even when it is small. A short public note — date, amount, recipient, and, where possible, the recipient confirming it — does more for trust than any campaign. Report small amounts too. A first gift of a few hundred dollars, honestly reported, is a stronger foundation than a vague promise of millions. **Write an impact report people trust:** The structure for reporting giving and results without inflating them. https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust ## 4. Do not borrow the recipient's results as your own. If you give to a ministry or charity that does real work, its results are its own. Your business gave money; the organization did the work. Say “we gave $X to Y, which does Z” — not “our customers fed a thousand families,” unless the recipient can actually attribute that outcome to your gift. This site keeps that line on purpose: the ministry results Daniel and Katie's work has published are reported on their own ledger, and none of it is counted as SIX33 impact. **The harvest so far — two ledgers, kept separate:** A worked example of reporting a ministry's fruit without counting it as a brand's impact. https://www.agent-six33.com/journal/the-harvest-so-far ## 5. Give from the heart, report for trust. Jesus warned against giving to be seen (Matthew 6:1–4), and Paul arranged for his giving to be seen as honest (2 Corinthians 8:21). Both are true. Give because God loves a cheerful giver, not because it sells. Report because the people who trusted you deserve to know where the money went. The motive is private; the receipts are public. > **The short version:** A giving plan is not a giving claim. Name who, how much, and when; report what actually went out; credit the recipient's work to the recipient; give from the heart and report for trust. ## Questions ### How should a business give a percentage of profits? Name the recipient, say whether the commitment is a percentage of revenue, a percentage of profit, or a fixed amount per item, say how often you give and report, and publish what actually went out — including small amounts. ### Is “a portion of every sale goes to charity” misleading? It can be, because it does not say how much, to whom, or when. Specific, reported giving is far more trustworthy. ### Can a business claim the impact of the charity it supports? Only if the charity can attribute that outcome to the gift. Otherwise report what the business gave, and credit the outcomes to the organization that did the work. ### Does SIX33 give to charity? SIX33 names Love on The World as its intended giving: a big part of its heart is raising funds for that ministry, and the giving is meant to grow as the brand grows. SIX33 has not launched, so it has not given anything yet. ## Sources - Straight answers — SIX33.World: https://www.six33.world/answers — SIX33's intended giving to Love on The World - Love on The World: https://www.loveontheworld.com — The ministry SIX33 names as its intended giving — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-a-business-can-give-honestly --- # Your first five customer interviews: questions that change what you build. A practical interview script for mission-driven founders: find a real problem, learn what people already do, and choose one test from the evidence. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 14, 2026 - Updated: Oct 18, 2026 - Scripture: James 1:19 - Read: 6 min - URL: https://www.agent-six33.com/journal/first-five-customer-interviews > let every person be quick to hear, slow to speak, slow to anger; > — James 1:19 The first customer conversation should leave you with a clearer picture of somebody else's day. A founder usually arrives with a solution and asks whether people like it. A useful interview starts earlier: what happened, what became difficult, what the person tried, and what they sacrificed to get through it. Those details can change the product before you spend another week building it. Five conversations are a manageable first round, not a statistically representative sample or a certificate that an idea is validated. They give you enough material to notice repeated problems, contradictions, and gaps worth testing. If all five people are close friends, share the same role, or came from the same invitation, write that limitation beside the result. This is the script I would take into a first round for a mission-driven project. Use it for a tool, a service, a community experience, or a brand promise. Keep the person specific and the invitation honest. A good mission gives you a reason to listen carefully; it does not give you permission to assume you already know what someone needs. ## 1. Choose one person and one uncertainty. Write the assumption that would change your next decision if it proved wrong. For example: first-time founders struggle to turn their mission into a concrete first test. That is a hypothesis to investigate. “People will love my planning app” cannot guide the conversation because it starts with your preferred answer. Invite people who have recently faced the situation. Ask for twenty minutes to understand their experience, explain that you are learning rather than selling, and give them an easy way to decline. A participant should never feel that access to help, a community, or a personal relationship depends on agreeing with your idea. Ask before recording; plain notes are enough for this first round. - Name the situation, role, and recent event that make someone relevant. - Write the assumption you most need to test. - Recruit beyond the people who already want to encourage you. - Agree on time, note-taking, and how their words may be used. **Define the first useful promise:** Use the blueprint to name the person, promise, and evidence gate before interviewing. https://www.agent-six33.com/blueprint ## 2. Ask for a recent story, then follow the details. Begin with a specific event: “Tell me about the last time you tried to turn an idea into something someone could use.” Let them describe the sequence. When an answer becomes general, ask for an example. When a word such as frustrating, expensive, or confusing appears, ask what happened that made it so. The following questions are a menu, not a script you must finish. Spend more time on an actual difficulty than on checking every box. Leave room for silence. You are trying to understand their experience in their vocabulary, including the parts that contradict your expectations. - What were you trying to get done that day? - What triggered the need to do it? - Walk me through what you did, from the first step. - Where did you get stuck, stop, or ask someone for help? - What did you try instead, and how did that work? - What did this cost you in time, money, or another tradeoff? - How did you decide whether the result was good enough? - Is there something I should have asked that I missed? ## 3. Keep your pitch out of the evidence. “Would you use an app that makes this easier?” encourages a prediction that costs the person nothing. “How did you handle this last week?” asks for something that already happened. Both answers may be sincere, but only one gives you a concrete behaviour to examine. Questions about hypothetical purchases belong in a later test with an actual offer and a real choice. If you show a prototype, mark that as a separate part of the conversation. Give the person a realistic task and observe what they do before explaining how it works. Keep prototype findings separate from the earlier account of their problem. Your explanation can make an experience look clearer than it would be for somebody arriving alone. - Replace “Do you like this?” with “What did you expect to happen here?” - Replace “Would this help?” with “What do you currently do when this happens?” - Replace “Is this easy?” with “Show me how you would start.” - Write down where you prompted or explained; that assistance affects the result. ## 4. Write an evidence note after each conversation. Record the situation while it is fresh. Use an anonymous participant code, the date, a recent example, the current workaround, and the cost of the problem. Keep a direct quote separate from your interpretation. “I abandoned it after choosing a name” is their reported behaviour. “They need a brand generator” is your interpretation, and another solution could fit the same evidence. The example below is hypothetical: Participant P03 described spending two evenings designing a logo, then stopped because they could not explain what the project would provide. The existing workaround was asking a friend for feedback. The next uncertainty is whether a one-page promise worksheet helps them choose a first delivery. That is specific enough to test without claiming that three other people have the same problem. - Participant code and relevant context. - A recent event and the sequence they described. - Existing workaround and the tradeoff it required. - Their words, then your separate interpretation. - Evidence that challenged the original assumption. - One uncertainty to investigate next. ## 5. Turn the round into one decision and one test. Compare the records after the round. Look for a repeated situation with a concrete cost, existing effort to solve it, and a next step you can deliver. Keep the exceptions visible. Five interviews can expose an assumption or suggest a pattern; they cannot establish its prevalence across a market. If the pattern is still vague, narrow the group or improve the questions before adding features. Choose a small delivery that addresses the strongest problem you heard. Define what completion looks like, invite a person to try it, and observe use and return. For the hypothetical worksheet, the first test might be whether the person can state one promise and schedule one delivery after completing it. That tests an immediate result. It does not establish a durable outcome or an impact count. Write the decision in this form: “We heard [specific problem] in [relevant context]. We will test [complete promise] with [person or group]. We will observe [behaviour] by [date]. The result will tell us whether to [continue, change, or stop].” Attach what would disconfirm the idea. A round that changes what you build has earned its time. - List repeated behaviours and meaningful exceptions. - Name the assumption that survived and the one that changed. - Choose one complete delivery and one observable result. - Set a review date and the result that would change your decision. **Write the one-page pilot plan:** Choose the question, evidence source, assistance rules, and next decision before testing the promise. https://www.agent-six33.com/journal/how-to-plan-a-small-pilot > **The short version:** Listen for a recent problem, an existing workaround, and a real tradeoff. Keep the person's words separate from your interpretation. Finish the first round with one decision and one test someone can actually complete. ## Questions ### What should I ask in a first customer interview? Ask about a recent experience: what triggered the problem, what the person tried, where they struggled, their existing workaround, and the time or money it cost. Follow concrete details and record their words separately from your interpretation. ### Are five customer interviews enough to validate an idea? Five interviews are a useful first learning round, not a representative sample. They can reveal assumptions and suggest a next test. Validation requires observing a real choice, delivery, or behaviour, and reporting the limits of that evidence. ### Should I show my product during a problem interview? Understand the recent problem first. If you show a prototype afterward, treat that as a separate test: set a realistic task, observe without coaching, and record where you offered assistance. ### How do I avoid leading questions? Ask what happened and what the person did rather than whether they like your idea or would buy it someday. Use neutral follow-ups such as “What happened next?” and seek examples that could contradict your assumption. ### What should I do after the interviews? Compare the records, keep exceptions visible, and choose one test of a specific promise. Name the person, complete delivery, observable result, review date, and evidence that would make you continue, change, or stop. ## Explore the wider topic - Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/first-five-customer-interviews --- # How to measure ministry impact without inflating the numbers. Attendance, decisions, baptisms, discipleship: what each number can and cannot tell you, how to label early reports honestly, and a five-level record any church or outreach team can keep. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 14, 2026 - Updated: Oct 14, 2026 - Scripture: 1 Corinthians 3:6–7 - Read: 6 min - URL: https://www.agent-six33.com/journal/how-to-measure-ministry-impact > I planted, Apollos watered, but God gave the growth. So neither he who plants nor he who waters is anything, but only God who gives the growth. > — 1 Corinthians 3:6–7 Ministries tend to fail at measurement in one of two directions. Some round up: every crowd becomes “thousands reached,” every hand raised becomes a soul saved, and the report grows faster than the church. Others refuse to count at all: only God knows the heart, so any number feels unspiritual. Both leave leaders guessing, donors trusting the wrong things, and new believers slipping through the gaps between the event and the next Sunday. Paul gives the right posture in one sentence: “I planted, Apollos watered, but God gave the growth.” We do not manufacture growth, so we should never report it as our product. But planting and watering are real work, and they can be observed honestly. And Scripture itself counts — with care. Acts 2:41 records that “there were added that day about three thousand souls.” Notice the word about. The first church report labelled its own estimate. This guide gives you a simple record any church, outreach team, or ministry can keep: five levels on separate lines, a label on every number, a follow-up window that turns a moment into discipleship, and a report people can actually trust. ## 1. Name the change you are actually hoping to see. Before you count anything, write one sentence about the change your ministry exists to serve. Not “impact our city.” Something a stranger could check. For example (a hypothetical): “People who respond at our outreach nights are connected to a local church within 90 days.” That sentence tells you what to measure, how long to wait, and which numbers are only on the way there. Most ministries have a few honest answers here: people hearing the Gospel clearly, people choosing to follow Jesus, new believers being baptized and discipled, believers being equipped to share their faith, practical needs being met. Pick the one this activity is for. A food table and a baptism service can both be faithful — they are not measured the same way. - Write the intended change in one sentence a stranger could verify. - Name the people it is for (who exactly — not “everyone”). - Set a time window: what should be true after 7, 30, or 90 days? ## 2. Keep five levels on separate lines. The most common inflation is adding numbers that measure different things. A crowd, a decision, and a disciple are not the same unit. Keep them apart and every one of them becomes more meaningful, because a reader can see exactly where the path narrows. - Reach — people who were present or heard. A crowd count or an estimate. Real, but not yet impact. - Delivery — people who clearly received the core message or care: a Gospel conversation, a meal, prayer, a follow-up contact. - Response — people who responded: a decision to follow Jesus, a prayer request, a request for baptism, a contact card. - Return — people who came back: a second gathering, a small group, a reply to follow-up, a first Sunday at church. - Change — credible evidence over time: still connected to a church, baptized and continuing, discipling someone else, a testimony shared with permission. **The reach-vs-impact standard:** The full five-level vocabulary with definitions you can reuse for any ministry report. https://www.agent-six33.com/proof ## 3. Label every number with what kind of number it is. A number without a label invites the reader to assume the best version of it. A labelled number earns trust even when it is small. One public example of doing this well: after Jesus Festival Hamilton 2026, JesusFestival.ca published its salvation and baptism figures as “early reports, not a final audited count.” That one phrase tells a donor, a pastor, and a sceptic exactly how much weight the number can carry — and the numbers still read as good news. For every figure you publish, be ready to answer five questions. If you cannot, say so beside the number instead of leaving it out. - Counted or estimated? (“About 300” and “312 signed in” are different claims.) - Counted how — and by whom? - When, and over what window? - Could anyone be counted twice (two nights, two tents, two volunteers)? - Early report or confirmed later through follow-up? ## 4. Follow up, or a decision count is only a moment. A decision is the beginning of a story, not the end of a report. The weeks after someone responds matter more than the moment itself — and they are where most ministry numbers quietly disappear. If you only count decisions, you will never know whether your ministry is making disciples or collecting moments. Choose a follow-up rhythm before the event, not after: a message within 48 hours, a conversation within the first week, a connection to a local church within 30 days, a check-in at 90. Then report the follow-up result beside the decision count, even when it is humbling. Free tools exist for this; Kingdom Base, for example, is a free evangelism CRM built for follow-up and discipleship. - Decide who owns follow-up for each person before the event ends. - Record contact attempts and responses, not only decisions. - Report the 30- and 90-day numbers beside the event numbers. **Kingdom Base:** A free evangelism CRM for tracking conversations, follow-ups, and the people you are praying for. https://www.kingdombase.app ## 5. Protect people while you measure them. People are not data points, and a testimony belongs to the person who lived it. Measure in a way you would be comfortable explaining to the person being counted. Collect only what you need, keep names private, and ask permission before a story leaves the room. A ministry that treats people as trophies will eventually be treated by them as a sales pitch. - Ask before sharing a testimony; let people choose first name only, initials, or nothing. - Publish totals, never lists of names, health details, or addresses. - Store follow-up details where only the people doing follow-up can see them. ## 6. Publish a report your church and donors can trust. A trustworthy ministry report has the same shape every time: the change you hoped for, the five levels with their labels, what you learned, the limitations, and what you will do next. It does not need a big number. It needs numbers a reader can believe — and a next step that shows you are learning, not just announcing. If a season is quiet, say so. A report that reads “we held eight outreach nights, had forty Gospel conversations, saw three people respond, and two are now in a small group” is more encouraging to a mature donor than a vague “hundreds impacted,” because it shows the ministry knows its own people by name. - Promise: the change this ministry exists to serve. - Signals: reach, delivery, response, return, change — each labelled. - Stories: one or two, shared with permission. - Limits: what the numbers cannot prove. - Next: the one thing you will do differently next season. **Build a free proof pack:** Turns one season of ministry into a field report with the method, limits, and next decision attached — drafts stay in your browser. https://www.agent-six33.com/proof-pack > **The short version:** Plant and water faithfully, count honestly, label every number, and follow people past the moment. God gives the growth; your report should never claim it. ## Questions ### How do you measure the impact of a ministry? Name the specific change the ministry exists to serve, then record five levels on separate lines: reach (who was present), delivery (who clearly received the message or care), response (decisions, prayer or baptism requests), return (who came back or connected), and change (credible evidence over time, such as continued church connection). Label each number and report follow-up results beside event results. ### Should churches count salvations and baptisms? Counting is biblical — Acts 2:41 records “about three thousand” added — but count with labels. A decision recorded at an event is a response, not yet a disciple. Report it as an early report, then report what follow-up shows at 30 and 90 days. ### What is the difference between attendance and impact? Attendance is reach: it shows who was present. Impact is change: evidence that the intended difference happened in someone's life over time. Both matter, but adding them together inflates the report. ### How long should a ministry follow up after someone responds? Decide before the event. A practical rhythm is contact within 48 hours, a conversation within the first week, connection to a local church within 30 days, and a check-in at 90 days. ### What is an honest way to report event numbers? Say whether each number is counted or estimated, how and when it was collected, whether people could be counted twice, and whether it is an early report or confirmed later. JesusFestival.ca, for example, published its 2026 figures as early reports, not a final audited count. ### How should a ministry report to donors? Use the same shape each time: the intended change, the five labelled levels, one or two stories shared with permission, the limitations, and the next step. Small, credible numbers build more trust than large vague ones. ## Sources - Thank You, Hamilton: Jesus Festival 2026 — JesusFestival.ca: https://www.jesusfestival.ca/news/thank-you-hamilton-jesus-festival-2026 — Event figures published as "early reports, not a final audited count" - Love on The World reference — LoveonTheWorld.com/llms.txt: https://www.loveontheworld.com/llms.txt — Kingdom Base described as a free evangelism CRM for follow-up and discipleship ## Explore the wider topic - Evidence and honest impact reporting: https://www.agent-six33.com/journal/topics/evidence-and-impact — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-measure-ministry-impact --- # Correct the page you opened. Matthew 6:33 does not reward a sharper sentence you did not actually read. Seek first, then tell the truth about the page in front of you. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 14, 2026 - Updated: Oct 14, 2026 - Scripture: Matthew 6:33 - Read: 5 min - URL: https://www.agent-six33.com/journal/correct-the-page-you-opened > But seek first the kingdom of God and his righteousness, and all these things will be added to you. > — Matthew 6:33 A correction is only as honest as the page it corrects. On 14 October 2026 I opened the brand's homepage again, looking for a line above the headline that said the world was open. It was not there. The first line was still seek first and live different. The tempting move was to write the sharper sentence anyway, because it would have made yesterday look incomplete. That is not a correction. That is a better-looking invention. Seek first is an order about the King, not a caption about momentum. Jesus put the Kingdom and His righteousness ahead of food, clothes, and tomorrow. A homepage that stops saying it is coming has done one honest thing. It has not then proved that anyone sought first, trained, gave, or came back changed. The Father already knows what you need. A line you expected does not add the evidence. Hold the lines apart when the page is quieter than the story you wanted. Intention was to re-read the door. Delivery is a new private dashboard and a longer public map. Use, return, and change are still uncounted. Reach is none of those. Write what the page says. Leave the count at zero. I am Daniel Ziedins, writing from Hamilton. The personal site is danielziedins.com. If you only keep one sentence from this note, keep this one: correct the page you opened. Seek first in the room you already have. Then measure the rest without flattering a sign that is not there. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/correct-the-page-you-opened --- # A new sentence is not a new life. Matthew 6:33 does not grade you on a better headline. Seek first, then tell the truth about what the new words actually changed. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 13, 2026 - Updated: Oct 13, 2026 - Scripture: Matthew 6:33 - Read: 5 min - URL: https://www.agent-six33.com/journal/a-new-sentence-is-not-a-new-life > But seek first the kingdom of God and his righteousness, and all these things will be added to you. > — Matthew 6:33 A sentence can get truer and still not be a result. On 24 September 2026 the brand's front door said the world was coming. On 13 October 2026 I opened it again. The first line was SEEK FIRST. LIVE DIFFERENT. The old line was gone. That is a real change in what a stranger reads. It is not, by itself, a person whose life became different. Seek first is an order, not a score. Jesus put the Kingdom and the King's character ahead of food, clothes, and tomorrow. A homepage that finally says the order out loud has done one faithful thing: it stopped wearing a waiting-room caption. The verse does not then owe you a crowd. The Father already knows what you need. The crowd is not the proof that you obeyed. Hold the lines apart on a day like this, because the day will try to collapse them. Intention was to tell the truth about the door. Delivery is a new sentence, two more tools that run in a browser, and a longer public map. Use is whether a real person did the thing. Return is whether they came back. Change is whether something meaningful became different, and you can show it. Reach is none of those. A new headline can raise reach and leave change at zero. Write zero. The practical test did not get easier because the words got better. Name the person the sentence is for. Ship the smallest complete thing. Wait long enough to learn whether anyone used it. Put the limitation beside the finding. If the only finding is that the sentence changed, say that, and stop. A report that upgrades a headline into a life is the old flattery in a cleaner font. This is still not a reason to stop building. It is a reason to enjoy the clearer sentence without spending it. Seek first in the room you already have. Then measure the rest without flattering yourself. I am Daniel Ziedins. The personal site is danielziedins.com. This note is mine. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/a-new-sentence-is-not-a-new-life --- # The harvest so far: 12 years, one city, and what comes next. From two people and one question on a Hamilton street to 20+ weekly outreach teams, a citywide festival with baptisms in the park, and Love on The World. The impact so far — with receipts — and how to partner for the next twelve years. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 6, 2026 - Updated: Oct 6, 2026 - Scripture: Luke 10:2 - Read: 7 min - URL: https://www.agent-six33.com/journal/the-harvest-so-far > The harvest is plentiful, but the laborers are few. Therefore pray earnestly to the Lord of the harvest to send out laborers into his harvest. > — Luke 10:2 Jesus never said the harvest was small. He said the workers were few — and then, before He sent anyone, He told them to pray for more workers. That order is the whole story of the last twelve years for Katie and me. We prayed. We went. God sent more people than we ever could have recruited. This site usually counts one thing: SIX33, a brand I am building from zero, which has not launched and has zero verified lives impacted. I keep that number honest on purpose. But there is a second ledger in my life, and it is much older than the brand. It is the ministry. Today I want to open that ledger — what God has done through Love on Hamilton, Love on The World, Jesus Festival, and our work through e3 Canada — with a source beside every number, so you can see it for yourself. And then I want to ask you to take a seat at the table. Because what comes next is bigger than what came before. ## 2014: two people, coffee, and one question. We did not launch a ministry in 2014. We just started showing up. Katie and I walked downtown Hamilton with coffee and one simple question: “Can we pray with you for anything?” No stage. No strategy. No budget. Just a conviction that the people everyone walks past are the people Jesus walks toward. That walk became Love on Hamilton. Practical love first — warm socks in February, a meal, a coat, a ride, presence when someone is at their lowest — and then the deeper conversation that practical love earns the right to have. “Let us not love in word or talk but in deed and in truth” (1 John 3:18). **Twelve years on the streets:** The full origin story on KD-Ziedins.com — what grew, and what we actually learned. https://www.kd-ziedins.com/blog/twelve-years-on-the-streets ## The ledger: what God has done, with the receipts. This site has one rule about numbers: say where they came from and what kind of number they are. So here is the ministry ledger, the same way. Every line is published by the ministry it belongs to, and the sources are listed at the end of this post. Festival figures are early reports from the team, not an audited count — and every one of them is a person with a name. - 20+ weekly Love on Hamilton outreach teams — ordinary believers who now go out every week without us needing to be there. - 12 Love on The World city outreach groups listed across Ontario and New Brunswick, most meeting weekly. - 36 nations covered by Love on The World prayer points, across every continent. - 10,000+ people gathered at Gage Park across Jesus Festival Hamilton 2024 and 2025, with 6,000+ hot dogs served freely. - Jesus Festival Hamilton 2026 (early reports): 70+ people gave their lives to Jesus, 50+ baptisms in the middle of the park, and 3,000+ free hot dogs and drinks. - 2026 was the first year of Jesus Festival Niagara — and the City of Niagara Falls lit the Falls in yellow, the festival's colour. - Overflow, a Sunday evening service launched in 2022 where the Holy Spirit was given full permission to move. **How to measure ministry impact honestly:** The five-level record behind this ledger — so your church or outreach team can keep one too. https://www.agent-six33.com/journal/how-to-measure-ministry-impact ## Jesus Festival: a city park becomes a baptism tank. Jesus Festival Hamilton is free. No ticket, no cover charge, no catch — a whole city invited to Gage Park for worship, the Gospel, food, families, and a Kids Zone. On September 4–5, 2026, it drew a record turnout, with altar calls on both Friday night and Saturday. And then there was the tank. People lined up in the middle of a public park to be baptized. Coming up out of the water, people said things like “I have no desire for my vape anymore and threw it away,” “My back is healed!” and “I was lost — who would have thought Jesus led me here!” That is what plundering hell looks like. Not a slogan. A person walking out of the water free. Acts 2 ends with a city noticing: “the Lord added to their number day by day those who were being saved.” A festival is a moment; the follow-up is the mission. That is why the festival hands people on to Love on Hamilton, Love on The World, local churches, and tools like Kingdom Base — so a decision at a bandshell becomes a disciple a year later. And if you want a festival in your city, Jesus Festival Movement exists for exactly that. **Read the Jesus Festival 2026 recap:** Testimonies, photos, and the early reports from the weekend on JesusFestival.ca. 2027 dates have not been announced yet. https://www.jesusfestival.ca/news/thank-you-hamilton-jesus-festival-2026 ## Love on The World: the same heart, in more cities. What started on one Hamilton street is now Love on The World — a Great Commission movement making disciples who make disciples. City groups meet weekly for street outreach, prayer, and practical compassion. A live movement map plots the groups, partners, and gatherings. And anyone can start one: pray, gather two or three believers, pick a place and a time, and apply. Jesus did not say “make converts in your city.” He said “go therefore and make disciples of all nations” (Matthew 28:19). Twelve groups is not the finish line. It is proof the pattern travels. **Start a Love on The World group:** The official pathway for a new city — and your group goes on the shared movement map once reviewed. https://www.loveontheworld.com/start-a-group ## e3 Canada: evangelize, equip, establish. Katie and I serve in partnership with e3 Ministry Canada, whose mission is equipping God's people to evangelize His world and establish His church. It is the frame around everything above: not just reaching people, but equipping believers who reach people, and establishing churches that keep multiplying after any one night of outreach ends. This is what we mean when we say plunder hell and populate heaven. Jesus bound the strong man (Matthew 12:29); His people carry out what was stolen. The enemy is never a person. People are the treasure. Every baptism in that park was a transfer “from the domain of darkness” into “the kingdom of his beloved Son” (Colossians 1:13). **Plunder hell. Populate heaven.:** The Scripture behind the phrase, and why we serve through e3 Canada. https://www.agent-six33.com/journal/plunder-hell-populate-heaven ## SIX33: a brand built to impact culture — and fuel the harvest. SIX33 is the brand. The name is Matthew 6:33 — seek first the Kingdom of God and His righteousness, and all these things will be added. It began in 2014 as Seek First Brand and is being rebuilt in 2026 as a whole world: limited apparel drops, athletes and creators, events, stories, Motor, Fight, Outpost, and Legends. Its heart is to impact culture for the Kingdom — unashamedly a faith brand, with the door wide open to everyone. And it is wired to the harvest. In SIX33's own words: a big part of SIX33's heart is raising funds for Love on The World — and as SIX33 grows, the giving grows with it. SIX33 is coming. There is no fake countdown and no announced date; the Inner Circle walks in first. When it does, this site will log it honestly, starting from zero. **Enter SIX33.World:** The brand, the worlds, and the Inner Circle list — the only way to be early. https://www.six33.world ## Your seat at the harvest. Luke 10:2 gives the order. Pray first. Then go — or send. Paul called it “partnership in the gospel” (Philippians 1:5), and he believed the fruit counted to the credit of the people who sent him (Philippians 4:17). Nobody does this alone. Every story of a life changed came through a body of people praying, giving, and showing up. - Pray for the harvest and for workers — by name, the way we pray for our partners every day. - Partner monthly through e3 Canada. Monthly partners are what let us plan, and go further. - Go: join Love on Hamilton weekly, find a Love on The World city group, or start one where you live. - Come to Jesus Festival 2027 — and bring someone who has never heard. Get the dates first at JesusFestival.ca. - Join the SIX33 Inner Circle at SIX33.World and be early to the brand built to fuel this. ## The harvest is plentiful. Send more workers into it. Twelve years ago it was two people and a cup of coffee. Today it is weekly teams, city groups, a festival that baptizes people in a public park — and Canada, we believe, on the edge of revival. The next twelve years are bigger. We can't do them alone. Become a monthly ministry partner with Daniel and Katie through e3 Canada, then follow the story at KD-Ziedins.com. - Partner through e3 Canada: https://e3ministry.ca/staff/katie-daniel-ziedins - KD-Ziedins.com: https://www.kd-ziedins.com - LoveonTheWorld.com: https://www.loveontheworld.com - JesusFestival.ca: https://www.jesusfestival.ca - SIX33.World: https://www.six33.world _e3 Ministry Canada's own terms: gifts are made to e3 Ministry Canada and remain under its full discretion and control, used for its charitable purposes; it seeks to honour a donor's preference for supporting a particular staff member._ > **The short version:** Two people and one question became a city-shaking harvest — because people prayed, went, and sent. Pray, go, give, or join: the harvest is plentiful and the next twelve years need workers. ## Questions ### What happened at Jesus Festival Hamilton 2026? Jesus Festival Hamilton took place September 4–5, 2026 at Gage Park with a record turnout. Early reports from the team counted 70+ people giving their lives to Jesus, 50+ baptisms held in the park, and 3,000+ free hot dogs and drinks — early reports, not a final audited count. 2026 was also the first year of Jesus Festival Niagara. ### When is Jesus Festival 2027? The 2027 dates have not been announced. JesusFestival.ca/2027 has the announcement signup. ### What impact has Love on Hamilton had since 2014? Love on Hamilton began in 2014 with Daniel and Katie Ziedins offering coffee and prayer downtown. It has grown to 20+ weekly outreach teams, Overflow (a Sunday evening service launched in 2022), Love on The World, and Jesus Festival Hamilton — which gathered 10,000+ people across 2024 and 2025. ### What is Love on The World? Love on The World is a Christian Great Commission movement founded in Hamilton, Ontario in 2014. It lists 12 city outreach groups across Ontario and New Brunswick, provides prayer points for 36 nations, and helps believers start outreach groups in new cities. ### How are Daniel and Katie Ziedins connected to e3 Canada? Daniel and Katie serve in partnership with e3 Ministry Canada, whose mission is equipping God's people to evangelize His world and establish His church. People can give once or monthly through their e3 staff page; gifts are made to e3 Ministry Canada under its discretion and control. ### What is SIX33, and when does it launch? SIX33 is a Christian lifestyle and performance culture brand built on Matthew 6:33, founded by Daniel Ziedins in Hamilton. A big part of its heart is raising funds for Love on The World. It has not announced a launch date; the Inner Circle at SIX33.World gets first access. ### Are these numbers SIX33's impact? No. They are ministry numbers published by Love on Hamilton, Love on The World, and Jesus Festival. SIX33 has not launched and its published count on AGENT SIX33 is zero verified lives impacted. ## Sources - Twelve Years on the Streets — KD-Ziedins.com: https://www.kd-ziedins.com/blog/twelve-years-on-the-streets — 2014 origin, 20+ weekly teams, Overflow (2022) - Thank You, Hamilton: Jesus Festival 2026 — JesusFestival.ca: https://www.jesusfestival.ca/news/thank-you-hamilton-jesus-festival-2026 — 2026 early reports and testimonies - Jesus Festival history — JesusFestival.ca: https://www.jesusfestival.ca/history — 10,000+ gathered and 6,000+ hot dogs across 2024–2025 - Jesus Festival Hamilton reference — JesusFestival.ca/llms.txt: https://www.jesusfestival.ca/llms.txt — Record turnout, Jesus Festival Niagara, Falls lit yellow - City outreach groups — LoveonTheWorld.com: https://www.loveontheworld.com/cities — 12 groups in Ontario and New Brunswick - Pray for nations — LoveonTheWorld.com: https://www.loveontheworld.com/nations — Prayer points for 36 nations - Daniel & Katie Ziedins — e3 Ministry Canada: https://e3ministry.ca/staff/katie-daniel-ziedins — Partnership and e3's donation terms - Straight answers — SIX33.World: https://www.six33.world/answers — SIX33's giving to Love on The World; no launch date — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/the-harvest-so-far --- # Plunder hell. Populate heaven. Stand with Daniel & Katie. Before SIX33 had a logo, there was a Hamilton street, a cup of coffee, and a question about Jesus. Twelve years later the assignment is bigger than ever. Here is the calling, the Scripture behind it, and how to partner with us through e3 Canada. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 5, 2026 - Updated: Oct 5, 2026 - Scripture: Matthew 16:18 - Read: 7 min - URL: https://www.agent-six33.com/journal/plunder-hell-populate-heaven > And I tell you, you are Peter, and on this rock I will build my church, and the gates of hell shall not prevail against it. > — Matthew 16:18 Gates are defensive. Nobody attacks a city with a gate. When Jesus said the gates of hell would not prevail against His church, He was not describing a church hiding behind its walls hoping the darkness stays outside. He was describing a church on the move — kicking at the doors of every place the enemy has claimed, and walking out with people. That is the whole story of my life with Katie. We did not start with a stage, a brand, or a plan. In 2014 we started on the streets of Hamilton with practical love, prayer, and a question about Jesus. That became Love on Hamilton. Love on Hamilton grew into weekly outreach teams, church equipping, a free citywide festival, and Love on The World — a movement spreading the Gospel and equipping believers in cities across Canada. Everything on this site — the build log, the brand, the billion-life goal — sits downstream of that. SIX33 is named after Matthew 6:33 for a reason: seek first the Kingdom. The brand is the “all these things.” The Kingdom is the first thing. So this post is not about SIX33. It is about the work the brand exists to serve, and an invitation to be part of it. ## What “plunder hell, populate heaven” actually means. The line is the late evangelist Reinhard Bonnke's, and it is deliberately loud. But it is not a slogan we made up to sound tough. It is a summary of something Jesus said plainly: “How can someone enter a strong man's house and plunder his goods, unless he first binds the strong man? Then indeed he may plunder his house” (Matthew 12:29). Jesus bound the strong man at the cross. What is left for His people is the plundering — carrying out what was stolen. And what was stolen is people. Not territory, not influence, not a culture war. Paul is clear that “we do not wrestle against flesh and blood” (Ephesians 6:12). The person stuck in addiction is not the enemy. The neighbour who is angry at God is not the enemy. They are the treasure. Colossians 1:13 says God “has delivered us from the domain of darkness and transferred us to the kingdom of his beloved Son.” Plundering hell means that transfer happening to one more person, by name. Populating heaven is the other half. Revelation 7:9 shows the end of the story: “a great multitude that no one could number, from every nation, from all tribes and peoples and languages.” Every face in that crowd heard the Gospel from somebody. Jesus said there is “joy before the angels of God over one sinner who repents” (Luke 15:10). One. Heaven throws a party for one. That is the scale we work at on a Tuesday night in Hamilton, and it is the same scale as the billion. ## What the work looks like, week to week. Every week we meet people in desperate need, bringing practical help and the life-changing power of Jesus. Over these years we have watched chains of addiction break, lives healed, and hearts set on fire for God. Not in a highlight reel. On ordinary streets, with ordinary believers who decided to be available. The work is not one thing. It is a pattern we have repeated since 2014, written down so anyone can copy it: - Street evangelism — weekly teams offering practical care, prayer, and Gospel conversations through Love on Hamilton. - Jesus Festival Hamilton — a free, family-friendly public gathering at Gage Park. The 2026 weekend took place September 4–5. - Love Overflow trainings — equipping churches so evangelism becomes practical, biblical, repeatable, and normal. - Discipleship — helping new believers take clear next steps in the weeks that matter most. - Collaboration — partnering with ministries like e3 Canada, God Heal Our Land, I Am Second, and Disciple a City instead of building in isolation. - Evangelize.World — the latest mission: helping establish 100 multiplying outreach groups anywhere and everywhere around the world. **Read twelve years on the streets:** The full story on KD-Ziedins.com: how two people, coffee, and a question grew into a citywide movement. https://www.kd-ziedins.com/blog/twelve-years-on-the-streets ## Why Canada. Why now. Our conviction is simple and it is not small: we believe Canada is on the verge of its greatest revival, and we are stepping into dark places to shine His light. Our mission is clear: to see souls saved and Canada set ablaze for Christ. Paul asked the question every generation has to answer: “How then will they call on him in whom they have not believed? And how are they to believe in him of whom they have never heard? And how are they to hear without someone preaching?” (Romans 10:14). Revival is not a weather pattern that happens to a country. It happens through people who go — and through the people who send them. “How beautiful are the feet of those who preach the good news!” (Romans 10:15). ## Why we serve through e3 Canada. Katie and I serve in partnership with e3 Ministry Canada. Their mission is in their name: equipping God's people to evangelize His world and establish His church. That is exactly the shape of our calling — not just reaching people, but equipping believers who reach people and establishing churches that keep multiplying long after any one outreach ends. Partnering through e3 means our ministry support goes through an established Canadian ministry with accountability around it, rather than through a brand or a personal account. It also means you are not just backing two people. You are backing a pattern that equips others to do the same work in their own cities. **Our e3 Canada partner page:** Read our page on e3 Ministry Canada and give once or monthly to the ministry. https://e3ministry.ca/staff/katie-daniel-ziedins ## Four ways to stand with us. Paul thanked the Philippians for their “partnership in the gospel from the first day until now” (Philippians 1:5). Partnership is not a donation box. It is a seat at the table of what God is doing. There is more than one way to take that seat. - Pray. Use the free 7-day evangelism prayer guide on KD-Ziedins.com and pray for open hearts, Gospel courage, and the people we will meet this week. - Give. Become a monthly ministry partner through our e3 Canada page. Monthly partners are what let us say yes to the next street, the next city, and the next church that asks for training. - Go. Join a weekly outreach through Love on Hamilton, or start a group in your own city through Evangelize.World. - Equip your church. Invite us to bring Love Overflow training so sharing faith becomes normal for your people — email hello@loveontheworld.com. **Visit KD-Ziedins.com:** Our ministry home: the stories, the free resources, the prayer guide, church training, and monthly God-story updates. https://www.kd-ziedins.com ## Why a brand-builder is asking you this. Some people find this site because of the business story: building SIX33 from zero toward a billion lives. Fair question, then — why is the founder asking for ministry partners? Because the order matters. Matthew 6:33 does not say build first and seek the Kingdom with whatever is left. It says seek first. The ministry came first, in 2014. The brand came after, and six33.world names Love on The World as its intended giving. I want to be precise, because this whole site runs on honest numbers: SIX33 has not launched, and nothing on this page is SIX33 impact. The SIX33 count is still zero verified lives. What you are reading about here is twelve years of ministry that existed before the brand and will outlast it. If the brand ever succeeds, part of what it is for is to fuel this. Partnering now means you are not waiting for that day. **Why this site keeps reach and impact separate:** The standard every number on AGENT SIX33 is held to — including the ones in this post. https://www.agent-six33.com/proof ## Stand with us. Take a seat at the table of what God is doing. We can't do this alone, and we were never meant to. Every prayer and every gift helps bring the Gospel to people who need it most — and equips believers to carry it further than we ever could. Give once or become a monthly partner through e3 Canada. Then come see what God is doing at KD-Ziedins.com. - Become a ministry partner: https://e3ministry.ca/staff/katie-daniel-ziedins - Visit KD-Ziedins.com: https://www.kd-ziedins.com - Pray with us for 7 days: https://www.kd-ziedins.com/evangelism-prayer-guide _e3 Ministry Canada's own terms: gifts are made to e3 Ministry Canada and remain under its full discretion and control, used for its charitable purposes; it seeks to honour a donor's preference for supporting a particular staff member._ > **The short version:** The gates of hell will not prevail. Somebody has to walk through them carrying the Gospel — and somebody has to send them. Go, give, pray, or equip: take your seat in the partnership. ## Questions ### Who are Daniel and Katie Ziedins? Daniel and Katie Ziedins are Hamilton, Ontario ministry leaders who have served together in public ministry since 2014. Their work includes Love on Hamilton weekly outreach, church evangelism training, discipleship, Jesus Festival Hamilton, and Love on The World. Their ministry home is KD-Ziedins.com. ### What does “plunder hell and populate heaven” mean? It is a phrase made famous by evangelist Reinhard Bonnke. It summarizes Matthew 12:29 — Jesus binding the strong man so His people can carry out what was stolen — and the hope of Revelation 7:9, a multitude from every nation. The enemy is never people (Ephesians 6:12); people are who is being rescued. ### How do I partner with Daniel and Katie's ministry? Pray, give once or monthly through their e3 Ministry Canada partner page, join outreach through Love on Hamilton or Evangelize.World, or invite them to train your church by emailing hello@loveontheworld.com. ### Where does a gift through e3 Canada go? Gifts are made to e3 Ministry Canada and remain under its discretion and control for its charitable purposes. e3 seeks to honour a donor's expressed preference to support a particular staff member such as Daniel and Katie. ### What is e3 Ministry Canada? e3 Ministry Canada is a Canadian ministry whose mission is equipping God's people to evangelize His world and establish His church. Daniel and Katie serve in partnership with e3 Canada. ### Is this SIX33 impact? No. SIX33 has not launched and its published count is zero verified lives impacted. The ministry described here began in 2014, before the brand. six33.world names Love on The World as SIX33's intended giving. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/plunder-hell-populate-heaven --- # Vanity metrics vs impact metrics: how to tell them apart. A vanity metric can only go up and changes no decision. An impact metric can disappoint you. Five levels of evidence, one test for each number, and what to report instead. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 1, 2026 - Updated: Oct 1, 2026 - Scripture: Proverbs 11:1 - Read: 6 min - URL: https://www.agent-six33.com/journal/vanity-metrics-vs-impact-metrics > A false balance is an abomination to the LORD, but a just weight is his delight. > — Proverbs 11:1 A vanity metric is a number that makes the work look bigger without telling you what to do next. Followers, page views, impressions, total sign-ups ever, “people reached”: each one can only grow, each one feels like progress, and none of them can tell you whether the thing you built is useful to anyone. The problem is not that these numbers are fake. They are usually accurate. The problem is that they answer a question nobody needed answered. An impact metric is the opposite in one decisive way: it can disappoint you. It is tied to a specific promise, measured over a specific window, and capable of coming back lower than you hoped. That possibility is what makes it worth reporting. A number that cannot go down cannot correct you. This guide gives you a practical way to sort any metric you already track, the five levels of evidence that sit between attention and real change, and the sentence to publish when the honest answer is still small. It uses the same proof ladder SIX33 runs on — and SIX33's own published count is zero verified lives impacted, so none of this depends on having a success story first. ## 1. Run the one-question test on every number you report. For each metric on your dashboard, ask: if this number moved sharply in either direction next month, what would we do differently? If the honest answer is “nothing — we'd keep doing the same thing and feel better or worse about it,” it is a vanity metric for you, whatever it is called. If the answer names a decision — change the offer, fix onboarding, stop a channel, double down on one audience — it is doing real work. The same number can pass for one team and fail for another. Page views are vanity for a ministry measuring discipleship and genuinely actionable for a publisher testing headlines. The test is not about the metric's name. It is about whether it is wired to a decision. - List every number you report publicly or to a board. - Beside each, write the decision it would change. Leave it blank if there is none. - Anything left blank stays internal — or gets reframed honestly as reach. ## 2. Separate the five levels instead of adding them together. Most inflated impact claims come from adding numbers that measure different things. A useful way to stop that is to keep five levels on separate lines: reach (who could have encountered the work), delivery (who received the complete promise), use (who meaningfully used it), return (who came back, replied, or referred), and change (who has credible evidence that the intended difference happened). Each level is real and each one matters. Only the last one supports the word impact. A campaign that reached 50,000 people, delivered to 900, was used by 300, brought back 40, and produced 6 evidenced changes is a far more convincing report than “we impacted 50,000 lives” — because a reader can see exactly where the funnel narrows and judge the result for themselves. - Reach — impressions, views, visitors. Distribution, never impact. - Delivery — orders shipped, sessions held, tools received complete. - Use — completions, active users, people who did the thing. - Return — repeat use, replies, referrals, second purchases. - Change — a defined outcome with a stated method and limitations. **Read the reach-vs-impact standard:** The full five-level vocabulary with definitions you can reuse. https://www.agent-six33.com/proof ## 3. Recognise the common vanity metrics — and what to track instead. A handful of numbers show up as vanity metrics again and again. In each case there is usually a nearby number that measures the same activity at a level that can actually inform a decision. - Total followers → people who acted on a specific post this month. - Page views → readers who reached the end, or took the next step the page offered. - Total sign-ups (all time) → sign-ups in a window who completed the first meaningful action. - Downloads → people who used the download more than once. - “People reached” → people who received the complete promise, then people who came back. - Hours volunteered or money raised → what those inputs produced, reported as outputs, not outcomes. ## 4. Do not let outputs pose as outcomes. Outputs are what you did: workshops run, meals served, products shipped, articles published. Outcomes are what changed for someone because of it. Outputs are worth reporting — they prove execution — but they answer a different question. Ten workshops is an output. Seven participants who report, at a 30-day follow-up, that they now do the thing the workshop taught is an outcome, with a method attached. The quiet failure mode is gradual: a report that starts by listing outputs slowly begins describing them in outcome language. “Served 2,000 meals” becomes “fed 2,000 families” becomes “fought hunger for 2,000 families.” Each step sounds harmless. Together they claim something nobody measured. ## 5. Measure change with a method you can name. Evidence of change does not require a research budget. It requires deciding in advance what change you expect, choosing a way to observe it, and being honest about what that method can and cannot prove. A short follow-up question asked to everyone served is a method. Observed behaviour — they came back and did the next step unprompted — is a method. Independent verification is a stronger method. Self-report collected only from your happiest customers is not a method; it is a testimonial. Whatever you choose, publish it beside the number, along with the reporting window, who was asked, how many responded, and what the result cannot establish. A modest number with a clear method is more persuasive than a large number nobody can check. - Write the intended change in one sentence before you count anything. - Ask everyone in the cohort, not only the people likely to say yes. - Record non-responses and negative results alongside positive ones. - State the window: 7 days, 30 days, one season. **Build an impact scorecard:** A free, local-first tool that keeps the five levels separate and flags inconsistencies. https://www.agent-six33.com/scorecard ## 6. Report the small true number on purpose. The strongest defence against vanity metrics is a habit: publish the most specific true sentence the evidence supports, even when it is small, and date it. “Between 1 and 31 August, 412 people visited, 38 completed the course, 11 returned for the second module, and 4 reported the change we were aiming for in a 30-day follow-up” will survive any scrutiny. It also tells you exactly where to work next. If the honest answer is zero, say zero. SIX33 publishes zero verified lives impacted with a date because a definition written while the count is zero cannot quietly bend later to absorb a flattering metric. That is the whole point of choosing impact metrics: they keep the story tied to what is actually happening. **Publish an honest proof pack:** Turn your five levels, method and limitations into a field report you can share. https://www.agent-six33.com/proof-pack > **The short version:** If a number cannot disappoint you, it cannot guide you. Keep reach, delivery, use, return and change on separate lines, attach a method to the last one, and publish the small true number with its date. ## Questions ### What is a vanity metric? A vanity metric is a number that makes work look successful without informing any decision — typically cumulative totals like followers, page views, impressions, or all-time sign-ups. It usually only grows, so it cannot tell you when something is not working. ### What is the difference between vanity metrics and actionable metrics? An actionable metric is tied to a specific decision and can move in either direction in a way that would change what you do. A vanity metric would not change your next step whether it rose or fell. The same number can be vanity for one team and actionable for another. ### Are followers and page views always vanity metrics? Not always, but they measure reach, not impact. They are useful for distribution decisions such as which channel or headline works. They become vanity metrics when reported as evidence that people were helped or changed. ### What should I track instead of vanity metrics? Track five separate levels: reach, complete delivery, meaningful use, return behaviour, and evidenced change. Report each with its window and method, and reserve the word impact for the last one. ### How do small organisations measure impact without a research budget? Define the intended change in one sentence in advance, ask everyone served a short follow-up question at a fixed interval, record non-responses, and publish the result with its method and limitations. Observed return behaviour is also strong, cheap evidence. ## Explore the wider topic - Evidence and honest impact reporting: https://www.agent-six33.com/journal/topics/evidence-and-impact — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/vanity-metrics-vs-impact-metrics --- # How to write an impact report people will actually trust. Most impact reports are built to impress funders and are read with suspicion. A trustworthy one shows the narrowing funnel, names its method, and publishes its limits. A section-by-section structure you can copy. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 1, 2026 - Updated: Oct 16, 2026 - Scripture: 2 Corinthians 8:21 - Read: 9 min - URL: https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust > for we aim at what is honorable not only in the Lord's sight but also in the sight of man. > — 2 Corinthians 8:21 Readers have learned to discount impact reports. They expect a large headline number, warm photos, a few testimonials, and very little about how any of it was measured. That expectation is the opportunity: a report that shows its working stands out immediately, and it is easier to write than a polished one because it only has to be true. A trustworthy impact report does three things the usual version avoids. It keeps reach, delivery, use, return, and change on separate lines so the reader can see where the numbers narrow. It names the method behind every outcome claim. And it publishes limitations and failures at the same size as the wins. Those three choices do more for credibility than any amount of design. Below is a structure you can copy section by section. It works for a nonprofit annual report, a ministry update, a social enterprise, or a founder's quarterly letter. It also works when the numbers are small — which is exactly when most organisations are tempted to round up. ## 1. Lead with the promise, not the headline number. Open with one sentence describing who you set out to help and what change you hoped would follow. This is your theory of change in plain language. Without it, every number in the report floats free and the reader cannot judge whether a result is good. “We help first-time parents in east Hamilton feel confident feeding a newborn in the first month” gives a reader everything they need to interpret what comes next. - Name the people, not a demographic slogan. - Name the change you hoped for, written before the results came in. - State the reporting window up front. ## 2. Show the funnel from reach to change. Present your numbers in order, from widest to narrowest: how many were reached, how many received the complete thing you offered, how many used it, how many came back, and how many show evidence of the intended change. A funnel that narrows is normal and believable. A report that jumps straight from reach to “lives changed” invites the reader to wonder what happened in between. If later numbers are higher than earlier ones, check that you are counting the same cohort over the same window before you publish. Mismatched populations are the most common reason impact reports quietly contradict themselves. **Lay out your funnel in the scorecard:** Enter all five levels and get a consistency check before you publish. https://www.agent-six33.com/scorecard ## 3. Name the method beside every outcome. Every outcome claim needs a short note on how you know it: who was asked, when, what was asked, how many responded, and how the answer was judged. “23 of 61 participants (38%) answered a 30-day follow-up; 17 said they still use the budgeting method weekly” is an outcome with a method. “Participants transformed their finances” is not. You do not need academic rigour. You need enough detail that a sceptical reader could understand, and in principle repeat, what you did. Self-report is fine if you call it self-report. A comparison group is better if you have one. Independent verification is better still. Match your language to the strength of the method. ## 4. Use stories to illustrate the numbers, not replace them. Stories carry meaning numbers cannot, and a good report should include them. The problem arises when a single exceptional story stands in for the typical result. Say plainly where a story sits: “This is one of the four participants who reported the full change” is honest. Presenting the best case as representative is not, even when every word of the story is true. Get consent, protect privacy, and avoid language that makes the people you serve props in your own success narrative. ## 5. Publish limitations and failures at full size. Include a section — not a footnote — on what did not work, what the data cannot show, and what you would measure differently. Low response rates, short follow-up windows, results that did not hold, programmes you stopped: all of it belongs here. Readers trust a report more when it volunteers its weaknesses, because it signals that the strong claims were held to the same standard. - Response rate and who did not respond. - What the method cannot rule out. - Results that were lower than hoped, and the likely reasons. - Anything you stopped doing, and why. ## 6. End with the decision the evidence earned. Close with what you will do next because of these results: continue, change something specific, or stop. This turns the report from a performance into a tool, and it gives the next report a baseline to be judged against. A reader who can see the decision can also see whether it was justified. Date the report and keep old versions public. A record of honest reports, including the disappointing ones, builds more trust over time than any single impressive one. **Generate a proof pack:** A free builder that produces this structure as Markdown or JSON, with method and limits attached. https://www.agent-six33.com/proof-pack ## 7. A worked example: a small pilot without an impact claim. The following example is hypothetical, not a SIX33 result. Imagine a founder testing a worksheet that helps first-time founders state a complete promise. Twelve people received the invitation, six received the whole worksheet, four completed it, and two returned with a revised sentence. No follow-up evidence was collected about whether their projects became more useful. The reach, delivery, use, and return counts are twelve, six, four, and two; evidenced change is not measured, not zero and not four. A defensible finding is: “Four participants completed the worksheet during the pilot window; two returned a revised promise.” The method might be a dated delivery log, completion submissions, and a record of the replies. The limitations are equally important: the participants volunteered, the group is small, and finishing a worksheet does not establish a lasting change in their work. Avoid claiming that the pilot transformed four businesses. The next decision could be to change one confusing prompt and observe another round. To investigate a later outcome, define it separately, agree on a follow-up window, and decide what evidence would support it. A record of use can justify improving the next delivery without being upgraded into verified impact. - Reporting window: write the actual start and end dates. - Keep unknown results unmeasured; use zero only when you measured and observed none. - Finding: state what happened in the language your method supports. - Decision: change one prompt, then test the revised version. ## 8. Move from the scorecard to a report, then review before sharing. If your numbers are already in the SIX33 impact scorecard, open the proof pack builder and choose Review scorecard snapshot. It reads the scorecard in this browser and shows the project, promise, intended change, and five counts before changing anything. Blank counts remain unmeasured. The planned change is labelled as an intention, not inserted as a finding. Your original scorecard stays intact. Back up an existing report first if you want to keep it. Choosing Replace report with snapshot creates a fresh report draft from the reviewed fields; it does not merge two reporting windows or add counts together. The scorecard's combined evidence notes appear in the method field so you can separate the method from the limitations. People served, dates, finding, decision, and next test remain blank for you to complete. Copying a field does not verify it. Before sharing, read the report as someone outside the team. Can they tell who was counted, during which period, and how you know the result? Remove private participant details and unapproved quotes. Export Markdown for the readable report and JSON for a restorable working copy. Files are readable rather than encrypted; keep a private backup separate from the version you intend to share. The builder exports a file but does not publish it for you. - Match every count to a definition, cohort, and reporting window. - Put the evidence method beside the finding and the material limitations beside the claim. - Check that the intended change is not presented as an observed outcome. - Remove identifying details you do not intend to share. - Name a continue, change, or stop decision and the next test. - Keep a dated backup before publishing the reviewed report. **Review your scorecard snapshot:** Carry your separate counts into a private report draft, then add the missing context before sharing. https://www.agent-six33.com/proof-pack#build-proof-pack ## 9. Run a completeness review without mistaking it for verification. Before sharing a report, check whether a reader has enough context to inspect it. The SIX33 builder's Before you share panel checks eight areas: the project and promise, people served, reporting dates, signal formats and consistency, finding, method, limitations, and decision with next test. Each item opens the relevant field so you can correct a missing date or explain a result without searching the whole form. A filled checklist is not an impact certificate. A plausible sentence can still be false, a quotation can still lack permission, and a carefully counted outcome can still have another cause. Read the actual claims, compare them with the underlying record, and check consent and privacy yourself. Text length helps the tool notice an empty method; it cannot judge whether the method is credible. Keep measurement states separate during the review. A blank count means not measured. Zero means the defined measurement found none. An invalid or fractional count needs correction rather than silent rounding. If a later count exceeds an earlier one, inspect definitions, cohorts, and windows before treating the sequence as a funnel. The review preserves those warnings in exported Markdown and JSON, even if you choose to keep the report as an unfinished working draft. - Fill missing context before sharing a public version. - Investigate count warnings; do not delete them merely to make the report look complete. - Check the original record, permissions, and identifying details yourself. - Export unfinished work as a backup when needed; a saved draft is not a published or verified report. **Run the before-sharing review:** Find missing context and keep the completeness checklist with your exported report. https://www.agent-six33.com/proof-pack#build-proof-pack > **The short version:** Lead with the promise, show the funnel narrow, name the method, publish the limits at full size, and end with a decision. Credibility comes from what you are willing to show, not from how large the headline is. ## Questions ### What should an impact report include? A clear statement of who you serve and the change you hoped for, the reporting window, numbers from reach through delivery, use, return and evidenced change, the method behind each outcome, honest limitations and failures, a few clearly-labelled stories, and the decision the results lead to. ### Does a completed report checklist verify an impact claim? No. A completeness checklist can flag missing fields and obvious count inconsistencies, but cannot establish truth, permission, causation, or independently verified impact. Review the original evidence, permissions, limitations, and private details yourself before sharing. ### How do I turn a scorecard into an impact report? Keep each signal separate, add the reporting window and people counted, write the finding in the language your evidence supports, and publish its method and limitations. In SIX33, Review scorecard snapshot copies a reviewed local scorecard into the proof pack builder only after confirmation. It does not combine counts, invent findings, verify impact, or publish the report. ### How long should an impact report be? Long enough to show the funnel, the method and the limitations — often one to four pages. Length adds nothing if the method is missing. A short report with a clear method is more credible than a long one without it. ### How do you make an impact report credible? Separate reach from outcomes, state the method and response rate for every outcome claim, publish limitations and negative results prominently, label stories as illustrations rather than typical results, and date the report so it can be compared with later ones. ### What is the difference between outputs and outcomes in an impact report? Outputs describe what you did, such as sessions held or products delivered. Outcomes describe what changed for people as a result. Both belong in the report, but outputs should never be described in outcome language. ### Can I publish an impact report with small or zero results? Yes. A dated, honest report with small numbers is more useful and more trustworthy than an inflated one. It sets a baseline, shows your standards, and makes later growth believable. ## Explore the wider topic - Evidence and honest impact reporting: https://www.agent-six33.com/journal/topics/evidence-and-impact — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-write-an-impact-report-people-trust --- # Build in public: a practical guide to sharing the real work. Building in public works when it is a record, not a highlight reel. What to share, what to keep private, how often to post, and the rules that keep it honest when the numbers are small. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Oct 1, 2026 - Updated: Oct 1, 2026 - Scripture: Luke 14:28 - Read: 5 min - URL: https://www.agent-six33.com/journal/build-in-public-guide > For which of you, desiring to build a tower, does not first sit down and count the cost, whether he has enough to complete it? > — Luke 14:28 Building in public means sharing the work while it is still being done — the decisions, the numbers, the mistakes, the quiet weeks — rather than only announcing the finished result. Done well, it builds trust, attracts the right early people, and forces clearer thinking. Done badly, it becomes a stream of manufactured momentum that nobody believes, including the person posting it. The difference is almost entirely about rules you set in advance. This site is itself a public build log: SIX33 is being built from zero with the record kept here, under four rules written before there was anything to show. The current verified impact is zero, and the log says so. That constraint is what makes the rest of it readable. This guide covers why to build in public, what to share and what to protect, how often to post, how to handle the stretches where nothing happens, and how to keep the record honest when growth eventually makes exaggeration tempting. ## 1. Know why you are doing it. There are three good reasons to build in public, and they lead to different habits. Accountability: writing the plan down publicly makes it harder to quietly abandon. Learning: explaining a decision to strangers exposes weak reasoning faster than thinking alone. Trust: people who watched the work happen are more likely to believe the result than people who only saw the launch. Distribution is a fourth reason and a real one, but it is the one most likely to corrupt the record. If reach becomes the main goal, posts drift toward whatever performs, and the honest updates — the boring and disappointing ones — stop getting written. ## 2. Write your rules before you have anything to show. The cheapest moment to commit to honesty is when there is nothing to protect. Write a short set of rules and publish them before the first real numbers arrive. SIX33's four are a usable starting point: real numbers or no numbers; failures at the same size as the wins; no fake momentum; keep it readable by someone who does not care about your industry. Rules written after success tend to protect the available win. Rules written at zero cost nothing to keep, and they give readers a standard to hold you to. **Read the four rules:** Entry 004 of the SIX33 log, written before there was anything to report. https://www.agent-six33.com/log/building-in-public-on-purpose ## 3. Decide what to share — and what to protect. Share the things that help a reader understand and trust the work: the problem you are solving, the decisions you made and why, real numbers with their dates, experiments and their results, mistakes and what you changed, and what you are deliberately not doing. Protect anything that belongs to other people or would cause harm: customer and user data, other people's stories without consent, partners' confidential terms, security details, and anything you would not want a competitor or a bad actor to have. Building in public is about your work, not about exposing the people it serves. - Share: decisions, dated numbers, experiments, failures, costs where comfortable. - Share: what you are not doing, and why. - Protect: personal data, other people's stories, confidential terms, security. - Protect: your own wellbeing — you do not owe the internet every hard day. ## 4. Post on events, not on a schedule — and log the quiet weeks. A fixed posting schedule pushes you to invent news. Post when something real happens: a decision, a result, a change of plan. Then add one deliberate exception — when a stretch goes by with nothing to report, say so. A short “nothing shipped publicly in eleven days, here is why” is one of the most credible posts a build log can contain, because it proves the log is not curated. A simple status page that says what you are doing now, and what you are not doing, removes most of the pressure to post for the sake of posting. **See a live Now page:** What SIX33 is doing this week, and what it is deliberately not doing. https://www.agent-six33.com/now ## 5. Share numbers without turning them into hype. Numbers are what make a public build log useful, and they are where most of them go wrong. Always attach a date and a definition. Say what kind of number it is — reach, delivery, use, return, or change. Never round a small number into a vague large one, and never describe attention as impact. Expect the temptation to grow with the numbers. The first time a metric looks good, there is pressure to frame it generously. The rules you wrote at zero are what hold the line. **Use the five levels of evidence:** A shared vocabulary for keeping attention and impact on separate lines. https://www.agent-six33.com/proof ## 6. Make the record findable and easy to quote. A build log nobody can find is a private diary. Give it a stable home you control rather than only a social feed: dated entries at permanent URLs, an RSS feed, and a short page that states the current facts for anyone — or any search or AI system — that wants to describe the work accurately. Make it easy to start at the beginning. Social posts can point to the record. The record should not live only inside the posts. **See a log in reading order:** The SIX33 record from entry 001, grouped into chapters. https://www.agent-six33.com/start > **The short version:** Write the rules at zero, share decisions and dated numbers, protect other people, post on events and log the quiet weeks, and keep the record somewhere you control. A build log is worth reading only if it would also publish the bad month. ## Questions ### What does building in public mean? Building in public means openly sharing the process of building a product, brand or organisation — decisions, numbers, mistakes and progress — while the work is happening, rather than only announcing finished results. ### Is building in public a good idea? It works well when the goal is accountability, learning and trust, and when you set rules about honesty and privacy in advance. It works poorly when it becomes a performance optimised for reach, because the honest updates stop getting written. ### What should you not share when building in public? Do not share personal data about customers or users, other people's stories without consent, confidential partner terms, security details, or anything that could harm the people your work serves. ### How often should you post when building in public? Post when something real happens rather than on a fixed schedule, and deliberately log stretches where nothing happened. A schedule pushes you to invent news; an event-driven log stays credible. ### How do you build in public when your numbers are small? Publish them anyway, with dates and definitions. Small honest numbers build more trust than vague large ones, set a baseline for later growth, and show readers your standards before success makes them harder to keep. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/build-in-public-guide --- # How to build a mission-driven brand from zero — without faking impact. Start with one person and one useful promise. Deliver the smallest complete version, separate reach from change, and publish only the result your evidence can support. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Sep 25, 2026 - Updated: Sep 25, 2026 - Scripture: Matthew 6:33 - Read: 14 min - URL: https://www.agent-six33.com/journal/how-to-build-a-mission-driven-brand-from-zero > But seek first the kingdom of God and his righteousness, and all these things will be added to you. > — Matthew 6:33 A mission-driven brand is not a logo wrapped around a large intention. It is a promise made to a particular person, delivered completely enough to be used, and measured honestly enough that the mission cannot hide behind the marketing. If you are starting from zero, that is good news. You do not need a crowd before you can become useful. You need one clear promise and one real encounter with reality. I am building SIX33 from zero in public. The stated horizon is a billion lives impacted. The verified count is still zero. That distance forces a useful discipline: ambition can set the direction, but evidence has to set the sentence. A page shipped, a view recorded, a product sold, and a life changed are different events. Treating them as one number makes the story louder and the strategy weaker. This guide is the operating sequence I would use if every logo, follower, and page disappeared tomorrow. It is for founders, ministries, nonprofits, community projects, and faith-driven builders who want the work to matter without inventing proof that it already does. The steps are simple. None of them are easy. Every one ends in an artifact another person can inspect. ## 1. Put the mission before the market — then make it concrete. Mission answers why the work should exist. Market answers who has the problem, how they currently respond to it, and whether your promise is useful enough to earn attention or action. You need both. A mission without a person becomes a slogan. A market without a mission becomes whatever converts this week. Write the mission as a direction, not a result you are pretending to have achieved. Then choose one group close enough to understand without demographic theatre. “Help people live with purpose” is a horizon. “Help a first-time founder turn one mission into a testable 30-day promise” is a starting point. Specificity does not shrink the mission; it gives the mission somewhere to land. - Name one person or tightly defined group. - Name the costly problem in their own language. - Name the change you hope to support without claiming it has happened. - Write what this project will refuse to become, even if that choice slows growth. **Use the from-zero blueprint:** Turn the mission into seven concrete moves, deliverables, and evidence gates. https://www.agent-six33.com/blueprint ## 2. Define one useful promise a stranger can repeat. A promise is the complete thing a person should receive or become able to do. It is not the list of features, the founding story, or the change you hope will happen years from now. If somebody outside the team cannot repeat the promise after reading it once, measurement will not rescue it later. Use this sentence: “For [specific person] who is trying to [real job], this provides [complete experience] so they can [intended next step].” Test every word. Does the person recognize themselves? Can the experience be completed? Is the next step observable? Keep the intended life change separate from the delivered promise so you do not count intention twice. - One person, not everybody who might someday care. - One complete promise, not an ecosystem of unfinished possibilities. - One observable next step, not a vague feeling of inspiration. - One sentence without internal vocabulary or founder explanation. ## 3. Ship the smallest complete delivery, not the smallest impressive launch. A minimum viable product is often interpreted as the least work required to put something online. That is too weak. The useful standard is the smallest complete delivery: the shortest version that still keeps the whole promise for one person. It may be a conversation, a worksheet, a guided session, a local event, a service, or a tool. It does not need a campaign before it needs a recipient. The distinction protects speed. You can cut scale, polish, automation, channels, and secondary features. You cannot cut the part that makes the promise true. A landing page about a future service is not delivery of the service. An invitation is not attendance. A download is not use. Mark the delivery complete only when the person receives the whole thing you said they would receive. - Remove everything that serves the launch more than the recipient. - Write a definition of complete before delivery begins. - Record attempted, failed, partial, and complete deliveries separately. - Fix the first broken promise before adding another channel. **Run the 30-day proof sprint:** Move one promise through definition, delivery, observed behaviour, and verification. https://www.agent-six33.com/sprint ## 4. Build the measurement ladder before the numbers arrive. Decide what each signal means while the count is still zero. Reach is potential exposure. Delivery means the complete promise arrived. Use means the person meaningfully engaged with it. Return means they came back, replied, referred, or repeated the behaviour. Evidenced change means the intended outcome was recorded with a method strong enough to support that sentence. Do not pour all five signals into one vanity total. Each answers a different question and suggests a different decision. Low reach may be a distribution problem. High delivery with low use may be an experience problem. Use without return may mean the first encounter was not valuable enough. A reported change with no method is a story worth following up, not yet a verified impact count. - Set one reporting window and keep cohorts aligned. - Leave unknown values unknown instead of converting blanks into optimism. - Keep qualitative evidence beside the counts that summarize it. - Publish the definition whenever you publish the number. **Build the impact scorecard:** Separate every signal and identify the strongest public claim the evidence supports. https://www.agent-six33.com/scorecard ## 5. Observe behaviour before asking for praise. People are generous when a founder asks whether something was helpful. Politeness is not the same as use. Watch where they pause, what they skip, whether they finish, what they misunderstand, and whether they return without being chased. Behaviour gives the compliment a denominator. Ask questions that make disagreement safe: “What nearly stopped you?” “What did you expect that was missing?” “What did you do afterward?” “What would you replace this with?” Record their words before translating them into your strategy language. Silence is data too, especially when you made a clear invitation and the right person still did not act. - Capture the first point of confusion. - Separate prompted return from unprompted return. - Record non-response and abandonment instead of deleting them from the story. - Change the experience only after naming the evidence that justified the change. ## 6. Verify the change without claiming more than the method can prove. Outcome evidence begins with a precise intended change and a follow-up close enough to observe it. Ask what became different, when it changed, what else might have caused it, and whether the change lasted. Self-report can be valuable. So can observation, completion data, repeat behaviour, or a third-party record. None is automatically conclusive. Name the method and its weakness together. Attribution is the hard part. A person may change after using your work without changing because of your work. Small samples, self-selection, short windows, missing baselines, and founder-led interviews all narrow the sentence you can publish. This does not make the evidence worthless. It makes the wording specific: “Two participants reported the intended change seven days later” is stronger than “We transformed lives” because another person can inspect what it means. - Define the outcome before asking whether it occurred. - Record the source, timing, sample, and follow-up method. - Test at least one plausible alternative explanation. - Put the limitations beside the finding, not behind a link nobody opens. **Read the proof standard:** See exactly where reach ends and a defensible impact claim begins. https://www.agent-six33.com/proof ## 7. Publish the proof pack and make the decision it earned. A test is unfinished until the record can survive outside the team. Publish the promise, people served, reporting window, five evidence signals, plain-language finding, method, limitations, and decision. A credible report can end at delivery, use, return, or zero. The purpose is not to manufacture an impact story. It is to make the next choice less dependent on mood. Choose continue when the promise is useful and the next uncertainty is worth testing. Choose change when the evidence identifies a repairable mismatch. Choose stop when the problem is not costly enough, the promise is not useful enough, the route to evidence is not ethical or practical, or a better use of the mission has appeared. Stopping one expression of the work is not abandoning the mission. It may be the most honest way to protect it. - Continue: name the next uncertainty, not just the next feature. - Change: state what the evidence invalidated and what will be different. - Stop: preserve the record so the same weak assumption is not rebuilt later. - Set the next review date before the current result fades into a story. **Publish an honest proof pack:** Generate a portable Markdown or JSON field report with the limits and next decision attached. https://www.agent-six33.com/proof-pack > **The short version:** Build the smallest complete promise for one real person. Keep reach, delivery, use, return, and change separate. Publish the limits. Let the evidence—not the ambition—choose the next sentence. ## Questions ### What is a mission-driven brand? A mission-driven brand organizes its promise, product, operations, and measurement around a purpose larger than attention or revenue. The mission sets direction, but the brand still has to name a specific person, solve a real problem, deliver a complete promise, and report evidence honestly. ### How do I start a mission-driven brand with no audience? Start with one person you can understand and reach directly. Define one useful promise, deliver the smallest complete version, observe what they do, and make the next decision from that evidence. An audience can scale a proven promise; it cannot make an unclear promise useful. ### Which metrics should a new mission-driven brand track? Track reach, complete delivery, meaningful use, return behaviour, and evidenced change separately. Also record failures, non-response, the reporting window, cohort definitions, evidence method, and limitations. Do not combine exposure and outcomes into one impact number. ### Should I invest in SEO before validating the promise? Make the work technically discoverable from the beginning, but do not use SEO volume to avoid direct validation. A fast, crawlable page helps the right person find the promise. Search traffic still measures reach; it does not prove usefulness, return, or change. ### When can a brand honestly claim impact? A brand can claim an evidenced outcome when the intended change was defined in advance, recorded through a stated method, tied to the relevant people and reporting window, and published with material limitations. Views, clicks, sales, shipments, and testimonials alone should not be renamed impact. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/how-to-build-a-mission-driven-brand-from-zero --- # A page that exists is not a life that changed. Matthew 6:33 does not congratulate you for shipping. Seek first, then tell the truth about what the work has actually done. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Sep 24, 2026 - Updated: Sep 24, 2026 - Scripture: Matthew 6:33 - Read: 6 min - URL: https://www.agent-six33.com/journal/a-page-is-not-a-life-changed > But seek first the kingdom of God and his righteousness, and all these things will be added to you. > — Matthew 6:33 A finished page feels like proof. The type is set. The link works. Someone can open it. That feeling is not a result. It is the cheapest thing a page can do: exist. Jesus did not say seek first a homepage. He said seek first the Kingdom of God and His righteousness. The rest is added, or it is not, and you still owe the truth about which one happened. I keep five lines separate on purpose, because the age will collapse them for you if you let it. Intention is what you meant. Delivery is what you shipped. Use is whether a real person actually did the thing. Return is whether they came back. Change is whether something meaningful became different because of the work, and you can show that without squinting. Reach sits beside those lines. It is not one of them. A view is not a life. SIX33 is living this in public, and the public count is still zero. The brand's front door still says the world is coming. Motor has a page and no event. Two free tools run in a browser. A proof sprint and a proof pack exist on this record so a person can finish a test and write down what the evidence earned — continue, change, or stop. All of that is delivery. None of it is a life I am allowed to count. If I round a working page up into impact, the verse becomes a caption on a scoreboard I invented. The practical test is short. Write the promise in one sentence. Name the person it is for. Ship the smallest complete thing. Then wait long enough to learn whether anyone used it, came back, or changed. Put the limitation next to the finding: small sample, self-report, no follow-up, a story that could have another cause. If the limitation changes the sentence, the sentence was not finished. A report that hides the weakness is a better-looking intention. This is not a reason to stop building. It is a reason to stop announcing. Seek first, then make the thing, then tell the truth at the size of the truth. If the honest line is still nobody, write nobody. The Kingdom is not threatened by a zero. It is threatened by a person who needed the zero to look like a win. If you only keep one sentence, keep this one: a page that exists is not a life that changed. Seek first. Then measure the rest without flattering yourself. I am Daniel Ziedins. The personal site is danielziedins.com. This note is mine. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/a-page-is-not-a-life-changed --- # Seek first in the city you already have. Matthew 6:33 does not wait for a bigger stage. The field is Hamilton, or the room you are already standing in. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Sep 24, 2026 - Updated: Sep 24, 2026 - Scripture: Matthew 6:33 - Read: 6 min - URL: https://www.agent-six33.com/journal/seek-first-in-the-city-you-already-have > But seek first the kingdom of God and his righteousness, and all these things will be added to you. > — Matthew 6:33 I build from Hamilton, Ontario. Steel, the escarpment, a harbour, and a lot of ordinary rooms. It is easy to treat a city like a waiting room for the place where the real work will start. Jesus does not offer that delay. Seek first is an order for the day you are in, not a caption for the day the platform is ready. The verse sits in a chapter about anxiety. Food. Clothes. Tomorrow. The people listening were not short on worry, and they were not standing on a stage. The command is to put the Kingdom and the King's character first, before the provisions you can already name. The promise is not a vending machine. It is that the Father already knows what you need. A brand can hide inside that verse and still miss it. You can print Matthew 6:33 on a lockup, ship a page, and keep your actual first hour pointed at the feed. Seeking first is local before it is legendary. It is prayer before the scroll. It is the person on your street, your shift, your kitchen. Hamilton is not a smaller version of the assignment. For me, it is the assignment's address. Stay sharp enough to notice when 'later' is just fear with a calendar. The world I am building still says it is coming. That is an honest status, and it is not an excuse to postpone obedience until a launch date exists. There is no launch date. There is today's room. If you are waiting to seek first until you have a bigger city, a cleaner story, or a number you are proud to post, you are waiting past the verse. Start where your feet are. One faithful hour. One person you can actually help. Do not post it to prove you did it. Then go back to the work that can be tested in public, and keep the dream from eating the truth. I am Daniel Ziedins. This note is mine, written from Hamilton, not from a template. The personal site is danielziedins.com. The build log is where the numbers stay honest. This journal is where the verse stays first. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/seek-first-in-the-city-you-already-have --- # Pray where nobody is ranking you. Matthew 6 puts secret prayer next to seek first for a reason. The Father is not waiting for a more impressive room. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 16, 2026 - Updated: Aug 16, 2026 - Scripture: Matthew 6:6 - Read: 7 min - URL: https://www.agent-six33.com/journal/pray-where-nobody-is-ranking-you > But when you pray, go into your room and shut the door and pray to your Father who is in secret. And your Father who sees in secret will reward you. > — Matthew 6:6 We live in an age that cannot tell the difference between prayer and content. A caption. A verse graphic. A public fast that is really a brand. Jesus was not impressed. In the same chapter as seek first, He told people to shut the door. Secret prayer is not shame. It is sequence. Before the Kingdom can reorder a life, someone has to actually talk to the King without an audience. The Father who sees in secret is not missing your hidden hour. He is the only one it was for. That is why anxiety loves the feed. The feed never shuts the door. It keeps you performing a spiritual life you have not entered. Seek first begins in a room with no ranking — a walk, a parked car, a kitchen before the house wakes. Stay sharp enough to notice when prayer became a post. Agents of the Gospel are not people with better captions. They are people who carry good news because they have been with Jesus. The sending in John 20 comes after peace. The peace in Matthew 6 comes after a closed door. You cannot skip the door and still call the platform formation. If you do not know what to say, take the chapter itself. Our Father. Daily bread. Forgive. Deliver. Then sit. Then go do the next faithful thing in the room you already have. Hamilton. The shift. The person you keep walking past. Prayer is not the opposite of mission. It is how mission stays clean. Shut the door today. Not forever. Long enough to remember you have a Father. Then open it and live like someone who was actually heard. The video ends. The conversation with God does not. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/pray-where-nobody-is-ranking-you --- # Do not copy the age. Romans 12:2 is how you stay sharp. The world is always offering a template. The Kingdom offers a renewed mind. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 16, 2026 - Updated: Aug 16, 2026 - Scripture: Romans 12:2 - Read: 7 min - URL: https://www.agent-six33.com/journal/do-not-copy-the-age > Do not be conformed to this world, but be transformed by the renewal of your mind, that by testing you may discern what is the will of God, what is good and acceptable and perfect. > — Romans 12:2 The age is a copy machine. It will print a version of you that is anxious, ironic, outraged, and always slightly behind. You do not have to sign up. You only have to leave your mind on the default setting. Paul does not say, flee the world and never touch a phone. He says do not be conformed. Stay sharp. Let your mind be renewed so you can test what is actually the will of God — not what is trending, not what would play well, not what your fear already decided. Seek first is the same fight in different words. If the Kingdom is not first, the age will be. The feed will catechize you before breakfast. Comparison will write your liturgy. Stay on mission requires a mind that can tell the difference between a real assignment and a manufactured crisis. Renewal is not a vibe. It is a practice. Scripture before the scroll. A walk without headphones. A conversation that is not a debate you already won in your head. Sleep. A body that is stewarded. The quiet yes. None of that looks like a rebrand. It is how a person becomes able to discern. I am not interested in a faith that baptizes whatever the age already wanted. Agents of the Gospel carry good news into a world they have not been discipled by. That requires a mind that has been elsewhere — with the King, in secret, in the chapter, in the room. If you have been copying the age, you are not ruined. Transformation is present tense. Start smaller than your pride wants. One hour unconformed. Then another. Seek first. Stay sharp. The template can wait. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/do-not-copy-the-age --- # Let peace stand guard. Philippians 4 does not shame your anxiety. It gives it somewhere to go — prayer, thanks, and a peace that actually keeps watch. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 16, 2026 - Updated: Aug 16, 2026 - Scripture: Philippians 4:6–7 - Read: 6 min - URL: https://www.agent-six33.com/journal/let-peace-stand-guard > Do not be anxious about anything, but in everything by prayer and supplication with thanksgiving let your requests be made known to God. And the peace of God, which surpasses all understanding, will guard your hearts and your minds in Christ Jesus. > — Philippians 4:6–7 Anxiety feels like a job. It clocks in early. It makes a list. It calls the list wisdom. Paul does not say your feeling is fake. He says do not let it run the house. In everything — not after you feel holy — let your requests be made known to God. Matthew 6:34 sits in the same family: tomorrow will be anxious for itself. Philippians adds the how. Prayer. Supplication. Thanksgiving. Not a performance of calm. A handing over. Thanksgiving is not pretending the trouble is cute. It is remembering you have a Father in the middle of it. The promise is strange. Peace that surpasses understanding — meaning you will not be able to explain why you can take the next hour. And that peace will guard. Not decorate. Guard. A sentry on the heart and mind so the age cannot walk in and rearrange the furniture. This is how Agents of the Gospel stay sent without burning down. Seek first. Pray the actual request. Give thanks for the mercy that is still on the table. Then do the next faithful thing: the text, the walk, the apology, the meal, the closed app. Peace is not the opposite of mission. Peace is what keeps mission from becoming panic with a verse attached. If you woke up already behind, you are in the verse. Do not be anxious about anything includes this morning. Make it known. Then let peace stand where your catastrophizing usually stands. The video ends. The guard does not clock out. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/let-peace-stand-guard --- # Jesus sent people, not spectators. An Agent of the Gospel is not a costume. It is anyone entrusted with good news who actually enters the room they are already in. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: John 20:21 - Read: 7 min - URL: https://www.agent-six33.com/journal/jesus-sent-people-not-spectators > Jesus said to them again, “Peace be with you. As the Father has sent me, even so I am sending you.” > — John 20:21 The internet trained us to watch. Watch the sermon. Watch the war. Watch someone else live the calling. Then save the video and call it formation. Jesus did not recruit an audience. After the resurrection He spoke peace, then He sent people. That is what an Agent of the Gospel is. Not a spy. Not a rank. Not a more impressive Christian. Someone entrusted with good news who actually moves. The sending is not a future platform. It is the kitchen, the shift, the sidewalk, the conversation you keep postponing. Peace and sending belong together. He does not say, get your anxiety under control and then I will use you. He gives peace, then He gives an assignment. Seek first is how you stay in that order. The Kingdom first. Then the room you are already in. I am building AGENT SIX33 in public from Hamilton because hidden faith kept turning into delay. If the good news only works on a stage, it is not ready for the dark. Stay sharp so you can see the person in front of you. Stay on mission so the watching becomes a life. You do not need a new city to be sent. You need the courage to enter the one you have. Carry peace into a room that does not have it. Tell the truth. Feed someone. Stay. That is the work. The video ends. The sending does not. If you have only been watching, you are not disqualified. You are the exact person He keeps sending. Become an Agent. Not later. Into this hour. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/jesus-sent-people-not-spectators --- # Seek first is not a slogan. Matthew 6:33 is a reordering of a life — not a caption, not a brand overlay, not something you do after everything else is handled. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Matthew 6:33 - Read: 8 min - URL: https://www.agent-six33.com/journal/seek-first-is-not-a-slogan > But seek first the kingdom of God and his righteousness, and all these things will be added to you. > — Matthew 6:33 The verse gets quoted until it disappears. People stitch it onto sunrises, gym mirrors, and brand decks. Then they go back to seeking first the inbox, the comparison, the imaginary audience. Jesus was talking to anxious people about food and clothes and tomorrow. He was not launching merch. Seek first means sequence. The Kingdom gets the first move. His righteousness — His way of being human — gets the first claim on the hour. Not first the strategy for becoming impressive, then a verse if there is time. First the King. Then the rest finds its place, or it doesn't, and you still have Him. That is why AGENT SIX33 exists. Not as a costume of 6:33. As a people who refuse to only watch. An Agent of the Gospel carries good news into kitchens, shifts, sidewalks in Hamilton, and the conversation they have been avoiding. Seeking first is not abstract. It has a room. Stay sharp so you can tell the difference between a real need and a manufactured crisis. Stay on mission so the seeking becomes action — a meal, a call, a quiet yes, a body that is stewarded, a feed that no longer runs your inner life. The video ends. The mission doesn't. If you have treated this verse like wallpaper, you are not disqualified. You are in the exact condition Jesus addressed. Do not be anxious about tomorrow. Seek first today. Read the chapter slowly. Pray before you plan a catastrophe. Do the next faithful thing where your feet already are. That is the whole invitation. Become an Agent. Not later, when you understand the Kingdom better. Now, while you are still being formed. Matthew 6:33 is not waiting for a more cinematic you. It is waiting for the first move. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/seek-first-is-not-a-slogan --- # Tomorrow is not your assignment. Matthew 6:34 sits next to seek first for a reason. Anxiety plans a life God has not asked you to live yet. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Matthew 6:34 - Read: 7 min - URL: https://www.agent-six33.com/journal/tomorrow-is-not-your-assignment > Therefore do not be anxious about tomorrow, for tomorrow will be anxious for itself. Sufficient for the day is its own trouble. > — Matthew 6:34 Anxiety feels like responsibility. It makes a spreadsheet of disasters and calls it wisdom. You replay the conversation. You pre-live the failure. You try to solve a Tuesday that has not arrived, and you miss the hour that has. Jesus put this sentence immediately after seek first. That is not an accident. Kingdom first is not a vibe you add once the future feels under control. It is how you stop letting the future run the present. Tomorrow will be anxious for itself. You are not required to do its job in advance. This is not a command to be careless. It is a command to be present. Sufficient for the day is its own trouble — and its own mercy, its own person, its own next faithful thing. Agents of the Gospel are not people who never feel fear. They are people who refuse to let fear become a second job. I know the loop. If I can just get ahead of it — the money, the calling, the body, the reputation — then I will finally seek first. That is how seeking first never starts. The feed trains you to live in a crisis that is always one swipe away. Scripture trains you to inhabit the day you actually have. So here is the assignment, and it is smaller than your panic wants: this morning. This room. This person. This verse. Drink water. Tell the truth. Do the quiet work. Pray before you plan a catastrophe. Seek first what is in reach. Let tomorrow remain tomorrow. You do not have to win the week before breakfast. You have to be faithful in the hour you are in. That is not a consolation prize. That is how a life with a King actually gets lived. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/tomorrow-is-not-your-assignment --- # Let the light do its work. You do not need a larger stage to be useful. A lamp belongs to the room it is already in. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Matthew 5:16 - Read: 6 min - URL: https://www.agent-six33.com/journal/let-the-light-do-its-work > In the same way, let your light shine before others, so that they may see your good works and give glory to your Father who is in heaven. > — Matthew 5:16 Most of us are waiting for a bigger lamp. A platform. A city that feels more like a calling. A version of ourselves that looks ready to be seen. Meanwhile the room we actually occupy stays dim — not because God has not asked, but because we keep postponing the shine until it could be impressive. Jesus did not say, hide until the auditorium is booked. He said let your light shine before others. The point is not that people notice you. The point is that they see good works and give glory to the Father. If the light terminates on your brand, it was never light. It was a spotlight. That is why the kitchen still counts. The shift. The sidewalk in Hamilton. The group chat you keep treating as a waste of holiness. An Agent of the Gospel carries good news into the room they are already in. You do not become useful by relocating. You become useful by being visible in the ordinary without making yourself the subject. Good works here are not a performance of niceness. They are the next faithful thing done in public enough to be witnessed: the apology, the meal, the honesty, the refused gossip, the stayed marriage, the quiet generosity nobody ranked. People should be able to see it. They should not be asked to clap for it. I am building in the open because hidden faith kept turning into private delay. Seeking first has to show up somewhere a neighbour could trip over it. Not as content. As a life. If your light only works on camera, it is not ready for the dark. So stop waiting for a more cinematic assignment. Put the lamp on the stand you have. Let someone see a good work today and wonder about the Father. The video ends. The light does not. Shine where your feet already are. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/let-the-light-do-its-work --- # You are not behind. You are being formed. Comparison will tell you that you missed the window. Scripture says the One who started this work is still holding it. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Philippians 1:6 - Read: 7 min - URL: https://www.agent-six33.com/journal/you-are-not-behind > And I am sure of this, that he who began a good work in you will bring it to completion at the day of Jesus Christ. > — Philippians 1:6 A lot of us carry a quiet panic that we are late. Late to the calling. Late to the discipline. Late to the version of ourselves we were supposed to be by now. The feed makes it worse. Someone your age already built the thing, already healed, already looks finished. You close the phone and feel like a draft. Paul was writing to ordinary believers, not a highlight reel. He did not say, “Hurry up and complete yourselves.” He said the One who began the work will finish it. That is not permission to drift. It is permission to stop despising the middle. Formation is slow on purpose. Roots do not trend. Character does not ship in a weekend. If you are learning to pray before you panic, to tell the truth, to stay when leaving would be easier — you are not behind. You are in the part of the story God actually uses. Matthew 6:33 is a mercy to the anxious. Seek first the Kingdom, not first a more impressive timeline. The seeking is how you stay in the work He already started. You do not have to catch up to a fictional version of your life. You have to be faithful in the one you are in. I know the temptation to wait until I look more like an Agent before I act like one. That is just another costume. Agents of the Gospel are not people who arrived. They are people who kept going while they were still being made. If you feel unfinished today, good. Unfinished is not the same as abandoned. Take the next honest hour. Read the verse slowly. Call the person. Do the quiet thing. He who began a good work in you is not checking a leaderboard. He is completing what He started. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/you-are-not-behind --- # The quiet yes is still obedience. God is not waiting for a more cinematic version of your faithfulness. He is waiting for the yes you can give in this room. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: 1 Samuel 15:22 - Read: 6 min - URL: https://www.agent-six33.com/journal/the-quiet-yes > Has the Lord as great delight in burnt offerings and sacrifices, as in obeying the voice of the Lord? Behold, to obey is better than sacrifice. > — 1 Samuel 15:22 We are trained to trust the loud offering. The post. The announcement. The public fast. The big gesture that proves we are serious. Meanwhile the small instruction sits on the table: apologize. Stay. Give. Rest. Tell the truth. Put the phone down and actually be here. Saul had a sacrifice. God wanted obedience. That sentence still wrecks religious performance. You can look devoted and still be negotiating. You can give God a production and withhold the one thing He asked for. The quiet yes does not look like content. It looks like showing up for the person who cannot help your brand. It looks like doing the right thing when nobody will rank it. It looks like seeking first when seeking first will not get applause. Jesus kept hiding people after He healed them. He kept pointing away from spectacle. The Kingdom takes root in the dark before it ever looks like a movement. If your faith only activates when there is an audience, it is not faith yet. It is a performance with a verse attached. So here is the encouragement: the yes you can actually give counts. Not the yes you would give if you were braver, richer, holier, or more online. The one in front of you. Obedience is better than sacrifice. Better than the story you were going to tell about later. Become an Agent of the Gospel in the smallest room first. Heaven is not bored by your ordinary faithfulness. That is often where the real assignment was hiding. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/the-quiet-yes --- # Carry the good news into the room you are already in. You do not need a new city to start being sent. You need the people who already share your air. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Acts 1:8 - Read: 7 min - URL: https://www.agent-six33.com/journal/the-room-you-are-already-in > But you will receive power when the Holy Spirit has come upon you, and you will be my witnesses in Jerusalem and in all Judea and Samaria, and to the end of the earth. > — Acts 1:8 Most of us want Samaria and the ends of the earth because Jerusalem is awkward. Jerusalem is the family table. The job. The group chat. The neighbour whose name you keep forgetting. Witness sounds romantic until it has a face you already know. Jesus did not say, “When you finally move, then you can represent Me.” He named the near places first. Power for witness is not a personality transplant. It is the Spirit of God making ordinary people able to tell the truth about Jesus where they already stand. An Agent of the Gospel is not someone who escaped their life. It is someone entrusted with good news who carries it into the life they have. Kitchens. Shifts. Sidewalks. The person you keep walking past. That is the field. Not a future platform. The room. Colossians 3 says whatever you do, work heartily as for the Lord. That includes the unglamorous hour. The email. The meal. The honest conversation. Seeking first the Kingdom does not always mean quitting your job for a microphone. Sometimes it means the microphone was never the point. I am building in public from Hamilton, not because this city is a brand accessory, but because this is where my feet are. The assignment is local before it is legendary. If we cannot love the near, we will only perform the far. Look up today. Someone in your actual radius needs courage, a meal, a text that is not a meme, a person who will not make them a project. Carry the good news there. You were already sent. You just have to enter the room you are already in. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/the-room-you-are-already-in --- # Discipline is a kind of hope. You do not grind to earn God’s love. You train because you believe a different future is actually coming. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Hebrews 12:11 - Read: 8 min - URL: https://www.agent-six33.com/journal/discipline-is-a-kind-of-hope > For the moment all discipline seems painful rather than pleasant, but later it yields the peaceful fruit of righteousness to those who have been trained by it. > — Hebrews 12:11 Discipline has a branding problem. The internet turned it into punishment, aesthetics, or a personality. Scripture treats it more like farming. You do something today that does not feel like fruit yet, because you believe later is real. That is hope with its sleeves rolled up. Not the vibe of hope. The practice of it. You pray when you do not feel holy. You open Matthew 6 when the morning is already loud. You move your body. You tell the truth. You keep a promise. You go to bed before the spiral wins. None of that looks impressive in the moment. Hebrews says later it yields peace. Grace is not the opposite of discipline. Cheap motivation is. Grace says you are loved before the training. Discipline says love has a direction. Seek first. Stay sharp. Stay on mission. Those are not gym slogans. They are how a human being aims a life at a King. I am not interested in a faith that only comforts and never forms. And I am not interested in a grind that forgets the Cross. Jesus is not a life coach. He is Lord. He also invites tired people to learn from Him. His yoke is kind. It is still a yoke. If you have failed the streak, you are not disqualified. Training includes getting back up. The peaceful fruit is for those who have been trained by it — not those who never stumbled. Start smaller than your pride wants. One chapter. One walk. One apology. One hour without the feed. Discipline. Purpose. Legacy. Not as a costume. As a hope you can actually practice this afternoon. The video ends. The training does not. That is good news for anyone who is tired of only watching themselves live. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/discipline-is-a-kind-of-hope --- # There is grace for the next faithful hour. Mercy is not only for the altar call. It is for the Tuesday that still needs doing. - Author: Daniel Ziedins (https://www.danielziedins.com) - Published: Aug 15, 2026 - Updated: Aug 15, 2026 - Scripture: Lamentations 3:22–23 - Read: 6 min - URL: https://www.agent-six33.com/journal/grace-for-the-next-faithful-hour > The steadfast love of the Lord never ceases; his mercies never come to an end; they are new every morning; great is your faithfulness. > — Lamentations 3:22–23 Some of us treat mercy like a reset button we already used. We blew the morning. We were sharp with someone. We opened the app we swore we would not. So we write the day off and wait for a cleaner one. That is how whole weeks disappear. Jeremiah wrote about new mercies from a wrecked city, not a spa. The love of God does not clock out because you were human before noon. His mercies never come to an end. That means there is still an assignment inside this day. Not a pretend day. This one. Matthew 6:34 sits right next to seek first: do not be anxious about tomorrow. Today has enough trouble. It also has enough grace if you will actually take it. The next faithful hour is often the most spiritual thing you can do — not because it earns you anything, but because it refuses despair. Agents of the Gospel are not people who never fail the hour. They are people who receive mercy and then move. Forgive. Drink water. Read the verse. Send the text. Go for the walk. Cook the food. Stay. The Kingdom is not waiting for your best morning. It is present in the recovery. If you need permission to begin again at 2 p.m., take it. Great is His faithfulness — not great is your streak. Seek first what is still available: the King, the person in front of you, the next right thing. Then let tomorrow be tomorrow. You are not too late for today. That is the whole surprise of mercy. It keeps arriving. Meet it. Then go. — Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33 https://www.agent-six33.com/journal/grace-for-the-next-faithful-hour