Planning Sitemap Structures That Actually Work
Learn how to organize content logically so users find information without getting lost in the hierarchy.
How to run card sorting sessions with Hong Kong users to confirm your navigation structure matches how people actually think. Practical steps from planning to analysis.
Card sorting isn’t some mysterious UX technique. It’s straightforward. You write content categories, topics, or navigation items on physical cards (or digital equivalents), then ask users to organize them into groups that make sense to them. Then you watch. You listen. You discover whether your mental model of how navigation should work matches reality.
Here’s the thing — we design navigation based on our assumptions. We think “Products” should be grouped with “Services.” We assume users understand our terminology. But they don’t always. Not in Hong Kong. Not anywhere. Card sorting reveals where those assumptions break down.
The method works because it’s low-pressure. No right answer. No judgment. Just “How would you organize these?” And that’s where you find gold.
Navigation that works in Singapore might confuse people in Hong Kong. Language, culture, business context — these things matter. When you’re designing for a Hong Kong audience, you can’t just copy navigation patterns from international templates. You need validation from actual Hong Kong users.
Card sorting does that. It forces you to test your assumptions against real thinking patterns. You’ll discover which category names resonate locally. You’ll see which items users expect to find together. You’ll learn if your sitemap structure makes intuitive sense or if it’s fighting against how people actually organize information.
Sites that validate navigation through card sorting report lower bounce rates and fewer “lost” users. People find what they’re looking for. They don’t get frustrated. That’s worth the 3-4 hours it takes to run a proper session.
Start here. Planning is where most sessions succeed or fail. You can’t just grab 6 people and shuffle cards around.
List all major sections, categories, and pages you want to validate. Don’t include everything — aim for 30-50 items maximum. Too many cards overwhelms participants. Too few gives you shallow data.
Find 6-12 people from your actual Hong Kong audience. Age diversity matters. Job titles matter. One finance manager and one university student will organize differently. That’s the point. Recruit through LinkedIn, local user groups, or online panels if you can’t find them organically.
Physical cards work best. Tactile. Easier to photograph. But digital tools (Miro, UserTesting, Optimal Workshop) work too if you’re remote. Either way, test your setup first. Nothing worse than discovering the pen doesn’t work or the Zoom lag is terrible halfway through a session.
The session itself is simple if you’re prepared. Give clear instructions. Step back. Let users think out loud. Don’t correct them or guide them toward your “right” answer. That defeats the whole purpose.
Typical session timeline: 5 minutes intro, 20-25 minutes sorting, 10 minutes conversation about why they organized things that way. That’s 40 minutes well spent. Pay people for their time — even a small amount shows respect for their effort.
One critical thing: Ask follow-up questions. “Why did you put these together?” “What would you call this group?” These conversations reveal the language users naturally use. That’s often more valuable than the sorting itself. You’ll discover terminology that should be on your navigation labels.
You’ve got data. Now what? Don’t overthink this. Look for patterns.
If 9 out of 12 users grouped “Product Documentation” and “Technical Specs” together, that’s a strong signal. Your navigation should reflect that. If people consistently create a group you didn’t anticipate, that’s a gap in your sitemap. If they use different names than you do, you’ve found labeling issues to fix.
Create an affinity map. Take photos of each sorting, list which items clustered together across all sessions, note the group names users suggested. Simple spreadsheet works. You’re looking for agreement patterns — where most users align.
You don’t need statistical significance here. This isn’t a large-scale survey. You’re validating a direction. If 7-8 people consistently organize content a certain way, that’s enough to change your sitemap. Trust the pattern. Move forward.
Anything over 60 items creates decision fatigue. People rush. Quality drops. Stick to 30-50 items max. Focus on categories you’re actually uncertain about.
Your colleagues will organize differently than your actual users. Age, industry, language proficiency — these affect how people categorize. Get real users or you’ll validate nothing.
Don’t say “That usually goes with this.” Don’t hint at your preferred structure. Your job is to observe, not teach. Let them think.
If your site is in Chinese, run card sorting in Chinese. The language shapes thinking. English-language card sorting won’t tell you how Cantonese speakers organize information.
Card sorting isn’t the end point. It’s input. Use the results to reshape your sitemap, reorganize your main navigation, rename categories, or redesign your information hierarchy.
If your current sitemap contradicts what users showed you, change it. That’s what validation is for. Don’t defend the old structure because you designed it. The users just told you it doesn’t work for them.
Document the findings. Show stakeholders what users did. Explain the patterns. Make the case for changes based on real behavior, not guesses. That’s how you build better navigation.
Card sorting provides valuable insights into user mental models and organizational preferences. However, results are specific to your participant group and context. Always combine card sorting findings with other research methods — user interviews, analytics review, usability testing — for a complete picture. This guide is informational. Adapt these practices to your specific audience and goals.