To validate your SaaS feature organisation, conduct a card sorting study with 15-20 target users to test how they naturally group and categorize your features. This user-centered approach reveals whether your current SaaS navigation structure aligns with users' mental models and expectations. Combine this with tree testing to validate the findability of specific features within your proposed information architecture, ensuring optimal feature discoverability across your platform.

Key Takeaways

Time required: 2-3 weeks from setup to actionable insights
Difficulty: Intermediate
What you need: List of features, 15-20 target users, card sorting tool
Key tip: Test both your current structure AND alternative groupings to identify the best SaaS information architecture

What You'll Need

Complete inventory of your SaaS features and functionalities
15-20 participants who match your target user personas
ValidateThat account (free at validatethat.io)

Step 1: Audit Your Current Feature Set

Create a comprehensive list of all features, tools, and sections in your SaaS platform to establish your testing baseline. Document every clickable element, menu item, and functionality that users interact with, regardless of how minor it seems. This audit should include feature names as they currently appear in your interface, along with brief descriptions to ensure consistency during testing.

Pro tip: Screenshot each section of your SaaS navigation and create a spreadsheet listing features exactly as users see them—inconsistent naming during testing will skew your results.

Step 2: Design Your Card Sorting Study

Set up an open card sorting study where participants group related features without predetermined categories, revealing natural mental models for SaaS feature organisation. Prepare 30-50 feature cards using the exact terminology from your platform, ensuring each card represents a distinct functionality users need to locate. Randomize the card order for each participant to eliminate bias from presentation sequence.

Example: Instead of generic cards like "Settings," create specific cards like "Password Management," "Team Permissions," and "Billing Preferences" to test granular feature discoverability.

Step 3: Recruit Representative Users

Identify 15-20 participants who actively use SaaS tools similar to yours and match your primary user personas. Focus on users who perform the core tasks your platform supports, as they'll provide the most valuable insights into intuitive SaaS information architecture. Avoid internal team members or users overly familiar with your current navigation structure.

Pro tip: Recruit 20% more participants than needed—card sorting typically sees 10-15% dropout rates, and you need adequate sample size for reliable patterns.

Step 4: Conduct the Card Sorting Sessions

Run moderated sessions where participants organize feature cards into logical groups and name their categories. Allow 30-45 minutes per session, encouraging participants to think aloud as they organize features to understand their reasoning. Record which features participants group together and what category names they assign, as this directly informs optimal SaaS navigation structure.

Example: If 80% of users group "User Management," "Role Assignment," and "Access Controls" together and label it "Team Settings," this reveals a strong mental model for your information architecture.

Step 5: Analyze Grouping Patterns

Calculate the percentage of participants who grouped specific features together to identify strong associations in your data. Features grouped together by 60% or more participants indicate natural categories for your SaaS feature organisation. Use dendrograms or similarity matrices to visualize these relationships and identify the optimal number of main navigation categories.

Pro tip: Pay attention to "orphan" features that participants consistently struggle to categorize—these often need renaming or repositioning for better feature discoverability.

Step 6: Design Alternative Navigation Structures

Create 2-3 different navigation proposals based on your card sorting insights, incorporating the most common grouping patterns and category names. Structure each proposal with 5-7 main navigation items (optimal for cognitive load) and organize sub-features according to user mental models. Ensure each structure addresses the pain points revealed in your analysis.

Example: If card sorting revealed users expect "Analytics" and "Reports" as separate top-level items rather than sub-items under "Data," restructure your SaaS information architecture accordingly.

Step 7: Validate with Tree Testing

Test the findability of critical features within your proposed navigation structures using tree testing methodology. Present participants with realistic task scenarios and measure success rates, time to completion, and navigation paths through your proposed SaaS feature organisation. Compare performance across different structural options to identify the highest-performing information architecture.

Pro tip: Test 8-10 core tasks that represent 80% of user workflows—this ensures your optimized structure supports primary use cases effectively.

Pro Tips

✅ Test seasonal workflows: Include features used during onboarding, renewals, or year-end processes that might be overlooked in regular usage patterns

✅ Validate category names: Test proposed navigation labels separately to ensure they clearly communicate section contents to users

✅ Consider user roles: Segment analysis by user type (admin vs. end-user) as different roles may prefer different SaaS navigation approaches

✅ Document mental models: Record participant explanations during grouping to understand the reasoning behind effective SaaS information architecture

Common Mistakes to Avoid

❌ Testing only current users: Existing users adapt to poor navigation—include prospects to identify true usability issues with feature discoverability

❌ Using internal terminology: Feature names familiar to your team may confuse users—test with actual interface language and user-friendly alternatives

❌ Ignoring mobile context: Many SaaS users access features via mobile devices where navigation constraints affect optimal feature organisation

❌ Over-categorizing features: Creating too many navigation levels reduces feature discoverability—keep structures shallow and intuitive

Frequently Asked Questions

How long does it take to validate your SaaS feature organisation?

Validating SaaS feature organisation typically requires 2-3 weeks: 3-5 days for study setup and recruitment, 1-2 weeks for data collection with 15-20 participants, and 3-5 days for analysis and recommendations.

What tools do I need to validate your SaaS feature organisation?

You need a card sorting platform (like OptimalSort or ValidateThat), tree testing capabilities for validation, and analytics tools to track current user behavior patterns in your existing SaaS navigation structure.

What are the most common mistakes when validating SaaS information architecture?

The top mistakes include testing only power users who've adapted to poor navigation, using internal jargon instead of user-friendly terms, and failing to test mobile navigation scenarios where space constraints affect feature discoverability.

How do I know if my SaaS feature organisation is effective?

Strong SaaS information architecture shows 60%+ agreement in card sorting groupings, 80%+ success rates in tree testing for core tasks, and reduced support tickets about feature location after implementation.

validate your SaaS feature organisation