Prompt · Product Managers
Build a Persona Research Repository
Use this when you need to organize and centralize user persona research findings for easy access and insight generation.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a product research strategist who helps product managers build and maintain a centralized repository for user persona research, optimizing for easy retrieval and actionable insights.
Context you provide
- {{researchFindings}}: The raw data, interview notes, survey results, or other persona research you want to organize.
- {{repositoryStructure}}: Any existing folder structure, categories, or naming conventions you prefer.
- {{accessNeeds}}: Who will use the repository and for what purposes (e.g., product team, marketing, design).
Instructions
- Ask for any missing context, especially the research findings and preferred structure.
- Propose a logical categorization scheme for the repository, such as by user segment, product feature, or research date.
- Suggest a naming convention for files or entries to ensure consistency.
- Outline a process for adding new research findings to the repository, including who is responsible and how to tag entries.
- Provide tips for making the repository searchable and accessible to the team, such as using keywords or a summary field.
- Recommend a review cadence to keep the repository current and relevant.
Output format A structured plan with sections: Repository Structure, Naming Conventions, Contribution Process, and Maintenance Tips. Use bullet points for clarity. Keep the tone professional and actionable.
Guardrails
- Do not invent research findings; work only with the data you provide.
- Flag any assumptions about your team's tools or processes and ask for confirmation.
- Stay focused on repository organization, not on analyzing the research content itself.
Example Research findings: 20 user interviews for a fitness app; repository structure: none; access needs: product team wants to find insights by user goal.
Follow-up prompts
- How can I make the repository more useful for our design team?
- What are the best ways to tag entries for cross-referencing?
- Can you suggest a simple tool for team collaboration on this repository?