Purpose
To create a quick snapshot of the target user during discovery.
This avoids assumptions and gives enough clarity to guide early UX flows — without investing time in full persona creation.
Table – Persona Lite Sheet
| Section | Field | Description | Sample Entry |
| Basic Info | Persona Name | Lightweight, relatable label | “Startup PM – Riya” |
| Segment | Broad classification | “SaaS Product Manager, Age 30–40” | |
| Goals | Primary Goal | What this user wants to achieve | “Deliver PRDs quickly & accurately” |
| Secondary Goals | Supporting aims | “Collaborate smoothly with devs, avoid rework” | |
| Pain Points / Blockers | Key Frustrations | Problems in current context | “Too much manual formatting in PRDs, confusing templates” |
| Digital Maturity | Comfort with tools/tech | “High – daily user of Jira, Confluence, Figma” | |
| Behaviors | Typical Actions | How they approach tasks | “Search for templates, consult peers, iterate drafts” |
| Tool Usage | Tools they rely on | “Jira, Confluence, Slack, Figma” | |
| Environment & Constraints | Work Context | Setting/conditions of use | “Works in fast-paced startup, multiple roles to juggle” |
| Constraints | Limitations they face | “Limited time, no design team support” | |
| Design Implications | What Design Must Enable | Direct takeaways for designers | “Clarity, fewer steps, template-driven workflows” |
Usage Notes
- Must be created within the intake stage (after stakeholder interview, before UX planning).
- Keep it 1-page max — discovery only.
- Updated/refined later if the project requires full personas.
- Store alongside Design Brief + Stakeholder Notes in MIC folder.