Worldview Analysis

Summary: People act in accordance with their identity. If a behavior conflicts with their self-image (“I am not that kind of person”), they will resist it regardless of the “benefit.” We must map their worldview to select behaviors that confirm their identity.

The Core Insight

Identity > Utility. A user will reject a “useful” tool if it makes them feel low-status, incompetent, or misaligned with their tribe. Conversely, they will adopt a “difficult” behavior if it signals “I am a pro.”

The Analysis Framework

1. Identity Labels

How does the user describe themselves?

• “I am a hacker.” (Prefers CLI, rejects GUIs).
• “I am a caring parent.” (Will do high-effort things for safety).
• “I am busy/important.” (Rejects “onboarding” as a waste of time).

2. Status Signals

What behaviors signal “status” in their world?

• Enterprise: “Automating workflows” signals seniority. “Data entry” signals juniority.
• Consumer: “Discovering music first” signals taste. “Top 40” signals normie.

Strategy: Frame your target behavior as a High-Status Signal.

3. The “Enemy” Narrative

Who or what is the user fighting?

• “I am fighting bureaucracy.”
• “I am fighting bad code.”
• “I am fighting mediocrity.”

Strategy: Position the behavior as a weapon against their enemy.

Behavior Selection Filter

Test your candidate behaviors against the Worldview:

• Behavior: “Ask manager for permission.”
• Worldview: “I am autonomous.”
• Result: Conflict. User will hide usage.
• Fix: Change behavior to “Inform manager of decision” (aligns with autonomy).

Output

A Psychographic Alignement Map. A set of identity constraints that your selected behavior must honor.