Research and testing.

What should I learn before I build more?

A large mission does not tell you which uncertainty to investigate this week. This collection connects the decisions between an early idea and a small, responsible test. It is for founders, community teams, and people building useful resources who need to learn before expanding a promise. Each guide offers a concrete output, a worked example, and limits on what the method can establish.

If a proposed feature is doing the work of a problem statement, begin with the first guide. If the person and task are already clear, move to the belief that could change your next commitment. Interviews help you understand recent experiences; synthesis turns the accounts into source-linked findings. A brief then gives an agreed piece of work a boundary and an owner. A pilot plan specifies how a particular promise will be tested rather than treating delivery as evidence of success.

Before arranging sessions, use the recruitment guide to connect the question to relevant experience and participation arrangements. If a version already exists, the usability guide helps you observe a realistic task without supplying the answer. Keep that observed task separate from an interview account: both can inform the next decision, but the source and method should remain visible. The research-session working pack brings the blank recruitment, observation, and synthesis prompts into one editable file.

You do not have to follow this collection in one direction. A follow-up can reveal that the original problem was incomplete, and a maintenance dependency can change a brief before any prototype is needed. Return to the earlier decision when the evidence calls for it. The blank documents in the field kit are optional working aids, not a certification process. Keep participant details private, and obtain appropriate review before higher-risk work. The examples are illustrative, not reported SIX33 results or universal sample-size rules.