菜单
A descriptive model of a person (user, stakeholder, team member, etc), this tool is most often used to help a team define and understand the needs of its customer.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
In this physical variant on brainstorming, participants use their body and inexpensive materials or objects to role-play and mimic interaction with a system, product, or experience.
This hands-on activity allows participants to communicate and document their mental model and how they think about a set of information, creating a logical structure (e.g., relationships, sequences, timing).
A fast way to capture and prioritize stakeholders.
A framework based on “influence channels” that shape and define an organization’s culture.
Visually synthesize and communicate a user’s end-to-end experience through actions, pain points, wins, and opportunities in a phased process.
Focus the power of brainstorming using a structured, visual representation of ideas—pushing you to fill out every box with new ideas.
| name | itk-personas |
| description | A descriptive model of a person (user, stakeholder, team member, etc), this tool is most often used to help a team define and understand the needs of its customer. |
| intent | Understand users’ needs, motivations, limitations, and capabilities. Represent the full range of diversity among stakeholders, customers, or other groups. Ensure the final product is something a human being will need or want. |
| type | component |
| phase | understand |
| outcome | understand |
| difficulty | intermediate |
| group_size | 6+ people |
| time_required | 45+ minutes |
| best_for | ["Early discovery when you need to align engineering, design, and sales on who the actual target user is","Translating raw user research from interviews and surveys into shareable archetypes the whole team references","Prioritizing a backlog when competing feature requests serve different user segments with conflicting needs","Onboarding new team members or stakeholders who lack context on who the product actually serves","Pressure-testing a roadmap assumption that 'users want X' before committing engineering capacity"] |
| sources | ["MITRE Innovation Toolkit (ITK)","https://itk.mitre.org/toolkit-tools/personas/"] |
A descriptive model of a person (user, stakeholder, team member, etc), this tool is most often used to help a team define and understand the needs of its customer.
Understand users’ needs, motivations, limitations, and capabilities. Represent the full range of diversity among stakeholders, customers, or other groups. Ensure the final product is something a human being will need or want.
When exploring new ideas or potential applications.
Archetype vs. Stereotype — A persona is a research-grounded composite of real behaviors and goals, not a demographic caricature. Stereotypes built on assumptions produce decisions that fail the actual user base.
Goals and Motivations — The core of a persona is what the user is trying to accomplish and why, not their job title. This maps directly to Jobs-to-be-Done and drives feature prioritization.
Specificity Principle — Useful personas are narrow (rank, specialty, experience level) rather than generic ('military member'). Specificity forces concrete design tradeoffs instead of designing for an impossible everyone.
Primary vs. Secondary Personas — One persona should be the primary design target whose needs the product must satisfy; secondary personas are accommodated but never drive core decisions. Without this hierarchy, scope balloons.
Diversity Coverage — The persona set must span the real range of users — edge cases, accessibility needs, varied expertise — so the product isn't optimized only for the loudest or most convenient cohort.
Evidence Grounding — Every persona attribute should trace back to observed data from interviews, analytics, or field research. Invented quotes and traits are acceptable only as summaries of real patterns, not fabrications.
Journey Mapping Storyboarding
| Field | Value |
|---|---|
| ITK Phase | UNDERSTAND |
| Difficulty | Intermediate |
| Group Size | 6+ people |
| Time Required | 45+ minutes |
| Source | itk.mitre.org |
