Purpose
Create a simple, actionable user typology by plotting users along two independent, behaviorally-relevant dimensions, producing four distinct quadrants that represent meaningfully different user types with distinct needs, contexts, or behaviors. The 2×2 framework balances simplicity (easy to communicate and remember) with analytical rigor (grounded in behavioral data), enabling teams to prioritize which user types to focus on without overwhelming complexity.
Unlike demographic segmentation (age, gender, income) or firmographic segmentation (company size, industry), 2×2 behavioral segmentation reveals why users behave differently—enabling tailored problem definitions, solution designs, and go-to-market strategies per segment.
When to Use
Use 2×2 segmentation when:
- A1.2 research reveals behavioral diversity—users experiencing the same need in different ways, contexts, or intensities
- Need to prioritize which user types to address first (boundary definition for A1.3)
- Stakeholders/team need simple, memorable segmentation for decision-making (4 quadrants easier than 10+ personas)
- Two clear behavioral dimensions emerge from A1.2 data (usage frequency, expertise level, motivation type, context, etc.)
- Building foundation for persona development (A1.2 Step 5)—segments become persona archetypes
Do NOT use when:
- User population is homogeneous—behavioral diversity insufficient to warrant segmentation
- Only one meaningful dimension identified—use simple high/low split, not 2×2
- Need more granular segmentation (6+ types)—use clustering analysis or multi-dimensional segmentation instead
- Segmentation based on demographics, not behavior—2×2 should reveal behavioral differences, not just descriptive attributes
- Data insufficient to validate segments—need 15+ users minimum with observable behavioral patterns
Sample Size and Duration
Participants: 3-5 people
- Essential: User researcher (A1.2 lead—knows data intimately), product owner
- Recommended: Domain expert (validates behavioral dimensions), A1.3 lead (will use segments for boundaries)
Duration:
- Dimension brainstorming: 30-45 min
- Pair evaluation: 30 min (test 2-3 pairs)
- User plotting: 20 min
- Quadrant definition: 30 min
- Validation & prioritization: 30 min
- Documentation: 20 min
- Total: 2.5-3 hours (can be split across 2 sessions)
Prerequisites
- A1.2 research data: 15+ interviews or observations showing behavioral diversity
- Behavioral data: Observable actions, workflows, contexts, motivations—not just demographics
- Affinity diagram or thematic analysis: Completed analysis revealing behavioral patterns and themes
- Team workshop time: 2-3 hours with 3-5 people (user researcher, product lead, domain expert)
- Visual workspace: Whiteboard or digital tool (Miro, Mural) for plotting users
Complete Procedure
Step 1: Identify Candidate Behavioral Dimensions (30-45 minutes)
Review A1.2 affinity diagram, interview themes, and observation notes to identify behavioral dimensions along which users differ meaningfully.
Candidate dimension types:
| p8.5cm Dimension Type | Examples |
|---|---|
| Usage Frequency | Daily vs. weekly vs. monthly users; heavy vs. light usage |
| Expertise/Skill Level | Novice vs. expert; first-time vs. experienced users |
| Motivation/Goal | Efficiency-driven vs. quality-driven; cost vs. convenience; intrinsic vs. extrinsic motivation |
| Context/Situation | Work vs. personal use; high-stakes vs. low-stakes contexts; time-constrained vs. flexible |
| Control/Autonomy | Decision-maker vs. end-user; high autonomy vs. constrained by policy |
| Complexity Handled | Simple/routine tasks vs. complex/non-routine tasks |
| Workflow Integration | Standalone tool use vs. integrated with other systems/processes |
| Relationship to Change | Early adopter vs. late majority; innovation-seeking vs. stability-preferring |
Dimension selection criteria:
- Behavioral, not demographic: Dimension must relate to how users act, decide, or experience the need—not just who they are itemize
- Good: “Task complexity handled” (behavioral—simple vs. complex workflows)
- Bad: “Age” (demographic—doesn't reveal behavior) itemize
- Independent dimensions: X-axis and Y-axis should be uncorrelated—knowing user's position on one dimension shouldn't predict their position on the other itemize
- Good: Expertise (X) vs. Usage Frequency (Y)—can have novice daily users and expert occasional users
- Bad: Expertise (X) vs. Feature Adoption (Y)—highly correlated (experts use more features) itemize
- Actionable: Each dimension should suggest different solutions, priorities, or experiences itemize
- Good: “Motivation: Cost-driven vs. Quality-driven”—implies different value propositions, pricing strategies
- Bad: “Likes blue vs. likes red”—trivial difference, no design/strategy implications itemize
- Evidence-supported: Must see clear examples of users at both ends of each dimension in A1.2 data itemize
- Test: Can you name 3+ users who are “high” on this dimension? 3+ who are “low”? itemize
Brainstorm process:
- Team generates 5-8 candidate dimensions from A1.2 data
- For each, ask: Behavioral? Independent from others? Actionable? Evidenced in data?
- Select top 3-4 dimensions for further evaluation
Step 2: Evaluate Dimension Pairs (30 minutes)
Test combinations of candidate dimensions to find the pair that creates the most meaningful, distinct quadrants.
Evaluation method:
For each pair (Dimension A × Dimension B):
- Sketch 2×2 grid with Dimension A on X-axis, Dimension B on Y-axis
- Label quadrants (e.g., Low A / Low B, Low A / High B, High A / Low B, High A / High B)
- Plot 10-15 users from A1.2 data on grid based on observed behavior
- Assess: itemize
- Distribution: Are users spread across all 4 quadrants? (If all users cluster in 1-2 quadrants, dimensions aren't independent or don't capture diversity.)
- Distinctiveness: Do quadrants represent meaningfully different user types with different needs/behaviors?
- Actionability: Does each quadrant suggest different problem definitions, solutions, or priorities? itemize
Example evaluation—Sales Forecast Confidence:
- Candidate pair 1: Deal Complexity (X) × Forecast Frequency (Y) itemize
- Test: Plot users—most cluster in “High Complexity × Weekly Forecast” quadrant. Poor distribution.
- Verdict: Dimensions likely correlated (complex deals require more frequent forecasting). Try different pair. itemize
- Candidate pair 2: Deal Volume (X) × Deal Complexity (Y) itemize
- Test: Plot users—spread across all 4 quadrants (some manage many simple deals, some manage few complex deals, etc.)
- Quadrants distinct: itemize
- Q1 (Low Volume, Low Complexity): Simple, relationship-based sales
- Q2 (High Volume, Low Complexity): Transactional, pipeline velocity focus
- Q3 (Low Volume, High Complexity): Strategic deal orchestration
- Q4 (High Volume, High Complexity): Enterprise at scale (rare but exists) itemize
- Verdict: Strong pair—good distribution, distinct needs per quadrant. SELECT THIS. itemize
Step 3: Plot Users on Selected 2×2 Grid (20 minutes)
Create 2×2 grid:
verbatim High Y-Axis (e.g., Deal Complexity) │ Q3 │ Q4 Low Volume, │ High Volume, High Complexity│ High Complexity ───────────────┼─────────────────── Q1 │ Q2 Low Volume, │ High Volume, Low Complexity │ Low Complexity │ Low Y-Axis
Low X-Axis ←─────────────→ High X-Axis (e.g., Deal Volume) verbatim
Plot individual users:
- For each user from A1.2 (interviews, observations), assess their position on both dimensions based on behavioral data
- Place user initials or ID on grid (e.g., P03, P07, P11)
- Use evidence from interviews/observations to justify placement
Example plotting—Sales Managers:
| p3cmp3cmp4cm User | Deal Volume | Deal Complexity | Quadrant |
|---|---|---|---|
| P01 | 50+ opps/quarter | Simple (5K-20K, 2-week cycle) | Q2 (High Vol, Low Complex) |
| P03 | 10-15 opps/quarter | Complex (100K-500K, 3-6 month cycle, multi-stakeholder) | Q3 (Low Vol, High Complex) |
| P07 | 30-40 opps/quarter | Moderate (20K-50K, 1 month) | Q2 (High Vol, Low Complex) |
| P11 | 8-12 opps/quarter | Very complex (enterprise, $1M+, 6-12 month) | Q3 (Low Vol, High Complex) |
After plotting all users, count distribution:
- Q1: 3 users (15%)
- Q2: 8 users (40%)
- Q3: 7 users (35%)
- Q4: 2 users (10%)
Good distribution—users in all quadrants, Q2 and Q3 are largest (primary segments).
Step 4: Name and Define Quadrants (30 minutes)
For each quadrant, create:
- Descriptive name: Memorable, behavioral label (not just “Quadrant 1”)
- Definition: 2-3 sentences describing typical user in this quadrant
- Key characteristics: Behaviors, needs, contexts, motivations
- Example users: 2-3 users from A1.2 who exemplify this quadrant
- Distinct needs: How does this quadrant's need differ from others?
Example—Sales Forecast Segmentation:
| p8.5cm Quadrant | Definition and Characteristics |
|---|---|
| Q1: Relationship Builders | Low Volume, Low Complexity |
| (15% of managers) | Small number (5-10) of simple, relationship-based deals (10K-30K). Long customer relationships, minimal formal process. |
| Key need: Relationship tracking, touch-point management | |
| Example: P05 (5-year avg customer tenure, informal check-ins) | |
| Q2: Volume Target Chasers | High Volume, Low Complexity |
| (40% of managers) | High deal volume (30-60 opps/quarter), transactional sales (5K-30K, 1-4 week cycles). Pipeline velocity critical. |
| Key need: Pipeline visibility, conversion rate optimization, activity tracking | |
| Example: P01, P07 (50+ active opps, daily pipeline reviews) | |
| Q3: Strategic Deal Orchestrators | Low Volume, High Complexity |
| (35% of managers) | Small number (8-15) of complex, high-value deals (100K-1M+, 3-12 month cycles). Multi-stakeholder, strategic sales. |
| Key need: Deal health assessment, stakeholder mapping, risk identification | |
| Example: P03, P11 (enterprise deals, 6-month avg cycle, C-suite engagement) | |
| Q4: Enterprise Scalers | High Volume, High Complexity |
| (10% of managers) | High volume (20-30) of complex deals—managing scale complexity. Often team-based selling (manager coordinates reps). |
| Key need: Team coordination, deal delegation, aggregate forecasting | |
| Example: P14 (manages 5 reps, 25 enterprise opps, team forecast rollup) |
Step 5: Validate Segments and Prioritize (30 minutes)
Validation:
- Distinct needs test: Can you articulate a meaningfully different need or solution for each quadrant? itemize
- If Q2 and Q3 need the same solution, segments aren't distinct enough—refine dimensions. itemize
- Evidence test: Does each quadrant have 3+ users from A1.2 data? itemize
- If Q1 has only 1 user, it may be outlier—consider collapsing into another quadrant. itemize
- Stakeholder validation: Share segments with domain experts or sample users—do they recognize these types? itemize
- Example: “Show sales VPs the four manager types—do they say 'Yes, we have all four in our org'?” itemize
Prioritization for A1.3 boundaries:
Assess which quadrant(s) to focus on:
| p3cmp3cmp3cm Quadrant | Size | Need Intensity | Strategic Fit |
|---|---|---|---|
| Q1: Relationship Builders | 15% | Moderate | Low priority—niche |
| Q2: Volume Chasers | 40% | High (pipeline anxiety) | Medium—large, but different need |
| Q3: Strategic Orchestrators | 35% | Highest (forecast anxiety) | HIGH—best fit for deal health solution |
| Q4: Enterprise Scalers | 10% | Moderate | Defer—complex, team-based |
Decision: Focus A1.3 on Q3 (Strategic Deal Orchestrators)—highest need intensity, good size (35%), clearest solution direction (deal health assessment). Defer Q2 to future iteration (different root cause—pipeline velocity vs. deal health).
Step 6: Document Segmentation (20 minutes)
Create segmentation summary for A1.2 deliverable:
- 2×2 visual: Grid showing dimensions, quadrant names, distribution (%)
- Segment profiles: 1 paragraph per quadrant (definition, characteristics, needs, examples)
- Dimension rationale: Why these two dimensions selected (behavioral, independent, actionable, evidenced)
- Prioritization recommendation: Which segment(s) for A1.3 focus, with rationale
- Evidence map: Table showing which A1.2 users fall into which quadrant
Quality Criteria
Excellent 2×2 segmentation demonstrates:
- Behavioral dimensions: Both axes based on observable user actions, workflows, contexts, or motivations—not demographics
- Independence: Users distributed across all 4 quadrants (not clustered diagonally)—dimensions uncorrelated
- Distinctiveness: Each quadrant represents meaningfully different user type with different needs, behaviors, or contexts
- Evidence-grounded: Dimension selection and user placement justified by A1.2 data (interview quotes, observations, behavioral logs)
- Actionability: Each quadrant suggests different problem definitions, solution approaches, or go-to-market strategies
- Parsimony: 4 quadrants are sufficient—captures meaningful diversity without overwhelming complexity
- Stakeholder validation: Domain experts/users recognize these types as real, familiar patterns
- Prioritization clarity: Clear rationale for which quadrant(s) to focus on (size, need intensity, strategic fit)
Dimension Selection Patterns
Common effective dimension pairs by domain:
| p4cmp4cm Domain | X-Axis | Y-Axis |
|---|---|---|
| B2B SaaS | Usage frequency (daily/weekly/monthly) | User expertise (novice/expert) |
| E-commerce | Purchase frequency (one-time/repeat) | Price sensitivity (budget/premium) |
| Healthcare | Patient complexity (simple/complex conditions) | Care autonomy (self-directed/provider-guided) |
| Education | Learner motivation (intrinsic/extrinsic) | Learning context (self-paced/structured) |
| Financial services | Financial sophistication (novice/expert) | Risk tolerance (conservative/aggressive) |
| Productivity tools | Workflow complexity (simple/advanced) | Collaboration need (individual/team) |
Challenges and Solutions
Challenge 1: Correlated Dimensions—Poor Distribution
Symptoms:
- All users cluster in 1-2 quadrants (diagonal pattern)
- Example: Expertise (X) × Feature Usage (Y)—experts always use advanced features, novices don't
Solutions:
- Independence test: Ask “Can I find users who are high on X but low on Y? And vice versa?” If no, dimensions are correlated.
- Choose different dimension: Replace one with uncorrelated alternative itemize
- Instead of Expertise × Feature Usage, try Expertise × Usage Frequency (experts can be occasional users if they're efficient) itemize
- Validate with data: If possible, calculate correlation coefficient—aim for r < 0.3
Challenge 2: One Dimension Dominates—Other Doesn't Matter
Symptoms:
- Quadrants on same side of one axis (e.g., Q1 and Q3, or Q2 and Q4) have nearly identical needs
- Y-axis doesn't add meaningful differentiation
Solutions:
- Actionability test: For each quadrant pair (Q1/Q3, Q2/Q4), ask: “Do these need different solutions?” If no, Y-axis isn't adding value.
- Replace weak dimension: Find dimension that creates distinct needs when combined with strong dimension
- Consider 1D segmentation: If truly only one dimension matters, use simple high/low split instead of forcing 2×2
Challenge 3: Too Many Edge Cases—Hard to Classify Users
Symptoms:
- Many users fall on axis lines (exactly medium on a dimension)
- Team debates “Is this user Q2 or Q3?” for 30% of users
Solutions:
- Accept ambiguity: 2×2 is simplification—some users will be borderline. Focus on clear exemplars.
- Define thresholds explicitly: itemize
- Example: “High volume = >25 opps/quarter; Low volume = <15 opps; 15-25 = medium (classify based on secondary criteria)” itemize
- Refine dimensions: If 40%+ of users are ambiguous, dimensions may not be creating clear behavioral clusters—try different pair.
Challenge 4: Demographic Temptation—Choosing Non-Behavioral Dimensions
Symptoms:
- Team selects Age (X) × Income (Y) or Company Size (X) × Industry (Y)
- Quadrants describe “who users are,” not “how they behave”
Solutions:
- Behavioral forcing function: Every dimension must answer “How does this user act/decide/experience the need?”
- Demographics as descriptors, not dimensions: After behavioral segmentation, you can note “Q3 users tend to be 40-55 years old” as secondary characteristic—but don't segment by age.
- Ask “So what?”: For proposed dimension, ask “If I know a user is X on this dimension, what does that tell me about their behavior or needs?” If answer is “Not much,” it's not a good dimension.
Relationship to Other Methods
2×2 Segmentation receives input from:
- A1.2 Interviews: Behavioral patterns, contexts, motivations observed across users
- A1.2 Observations: Workflow differences, task complexity variations
- Affinity Diagramming: Themes revealing behavioral dimensions
- Journey Mapping: Context and situational differences across users
2×2 Segmentation provides input to:
- Persona Development (A1.2 Step 5): Each quadrant can become persona archetype—add narrative, goals, pain points
- A1.3 Boundary Definition: Quadrant prioritization informs user/stakeholder boundaries (which segments in-scope?)
- A1.4 Strategic Fit: Segment size and strategic alignment influence go/no-go decisions
- A2 Ideation: Quadrants may require different solution concepts or feature sets
- B2 Market Segmentation: Behavioral segments inform go-to-market strategy, pricing tiers
Example: Meditation App Users
Dimensions selected:
- X-axis: Meditation Experience (Novice → Experienced)
- Y-axis: Motivation (Stress Reduction → Personal Growth / Spirituality)
2×2 Grid:
verbatim High Motivation: Personal Growth/Spirituality │ Q3 │ Q4 Novice, │ Experienced, Growth-Seeking │ Growth-Seeking ───────────────┼─────────────────── Q1 │ Q2 Novice, │ Experienced, Stress-Driven │ Stress-Driven │ Low Motivation: Stress Reduction
Low Experience ←─────────────→ High Experience (Novice) (Experienced) verbatim
Quadrant Definitions:
| p8.5cm Quadrant | Definition and Needs |
|---|---|
| Q1: Stressed Beginners | Novice, Stress-Driven (45%) |
| High-stress professionals seeking quick anxiety relief. No meditation experience. Want immediate results. | |
| Need: Simple, guided sessions (5-10 min); progress tracking (stress reduction); habit formation scaffolding | |
| Example: P03 (startup founder, anxiety, tried meditation once), P09 (new parent, sleep-deprived) | |
| Q2: Stress-Relief Veterans | Experienced, Stress-Driven (20%) |
| Meditate regularly (6+ months) for anxiety management. Functional motivation. | |
| Need: Variety (different techniques), personalization (adapt to stress levels), efficiency (shorter sessions when busy) | |
| Example: P14 (meditates 2 years, uses for work stress), P18 (anxiety disorder, meditation as therapy complement) | |
| Q3: Curious Seekers | Novice, Growth-Seeking (25%) |
| Interested in mindfulness for self-improvement, spirituality, or life philosophy. New to practice. | |
| Need: Education (what is meditation?), exploration (different styles—mindfulness, loving-kindness, transcendental), community/belonging | |
| Example: P07 (read about Buddhism, curious), P11 (yoga practitioner, wants to deepen practice) | |
| Q4: Dedicated Practitioners | Experienced, Growth-Seeking (10%) |
| Long-term meditators (years) seeking depth, mastery, spiritual development. | |
| Need: Advanced content (silent retreats, teacher guidance), tracking subtle progress, community of peers | |
| Example: P15 (10-year practice, Buddhist background), P20 (meditation teacher training) |
Prioritization Decision:
Focus A1.3 on Q1 (Stressed Beginners)—largest segment (45%), highest abandonment rate (root cause analysis target), clearest market opportunity. Q3 (Curious Seekers) secondary—defer to future iteration.
Tools and Templates
Physical workshop:
- Large whiteboard or poster (3×3 feet minimum) for 2×2 grid
- Sticky notes (user IDs/names) to plot on grid
- Index cards for quadrant definitions
Digital tools:
- Miro/Mural: 2×2 grid template with drag-drop user cards
- Google Sheets: Data table with X/Y coordinates, conditional formatting to visualize quadrants
- Airtable: User database with dimension scores, filtered views per quadrant
Analysis tools (if quantitative data available):
- Scatter plot (Excel, Python, R): Plot users on X/Y axes to visualize distribution
- Correlation analysis: Validate dimension independence (r < 0.3 target)
Share how you use 2×2 Segmentation
This is where practitioners will be able to share field notes, variations, and additional templates for this method — what worked, what to watch for, and adaptations for different contexts.
Until the community space opens, we welcome contributions by email and will fold the best into the method page.