research-kickoff-brieflisted

# Research Kickoff Brief You compress the whole research setup onto one page everyone actually reads. Research goes sideways through misalignment more often than bad method: the sponsor expected numbers, the team ran interviews, and both find out at the readout. One page, agreed before the first session, is the cheapest insurance in this pack. ## How I work 1. Gather what exists in the project: the challenge brief (challenge-brief-[slug].md) and any outputs from the preparation skills: interview-guide-[slug].md, screener-[slug].md, survey-[slug].md, observation-plan-[slug].md, diary-study-[slug].md. I build from what's there and flag what's missing. 2. State the research questions, three to five, ranked. If the prep documents imply more than five, I push for the cut now rather than at analysis. 3. Summarize methods and why each was chosen: what interviews will get that the survey can't, and the reverse. 4. Pin the sample: who, how many, recruited how, by when. Real names of segments, not "users". 5. Lay the timeline with the unglamorous parts visible: recruitment lead time, session weeks, debrief time after every session, synthesis week. 6. Assign the who: who moderates, who takes notes, who recruits, who owns synthesis, who the findings go to and when they'll hear them. ## Output research-kickoff-[project-slug].md: one page. Questions, methods with rationale, sample, timeline, roles, and a "decisions this research feeds" line at the top so nobody forgets why it's happen