Information Architecture IA

⬢ 티어 2기술

보통

연봉 영향

2개월

학습 기간

보통

난이도

직무

한눈에 보기

Information architecture (IA) is designing how information is organized: navigation structures, categorization, labeling, search. Examples: website sitemap, app tab layout, knowledge base taxonomy. Mastery takes 3-4 weeks of user research, card sorting, taxonomy design. You earn 10-20% premium by reducing user confusion (30% fewer support tickets, higher conversion). It's rare because most teams skip IA (jump straight to design) and suffer misclassification, lost users, poor SEO.

Information Architecture IA이란

Information Architecture (IA) is the structural design of information environments. It answers: "How is this information organized? How do users find what they need? What categories exist, and how are they labeled?" Examples: a website's navigation menu (categories, hierarchy), an app's bottom tab bar (primary sections), a knowledge base's taxonomy (how articles are grouped). IA is the skeleton on which UI is hung.

🔧 도구 & 생태계

Card sorting toolsMiroOptimal WorkshopTree testingAnalytics dataUser researchTaxonomy designWireframing

📋 시작하기 전에

Interaction Design Advanced

💰 지역별 연봉

지역	주니어	미들	시니어
USA	$65k	$108k	$160k
UK	$40k	$66k	$98k
EU	$46k	$75k	$112k
CANADA	$62k	$103k	$155k

🎓 자격증

IA Institute Certification Information Architecture (Lou Rosenfeld)Optimal Workshop IA Resources

🎯 Information Architecture IA을(를) 활용하는 직무

Conversational Designer

Design Ops Manager

Industrial Designer

Intent Based Protocol Engineer

Market Researcher

Product Manager

Product Operations Manager

Service Designer

⚖ 비교하기

Interaction Design Advanced

❓ 자주 묻는 질문

What's the difference between IA and UX?

IA is structure (where things live, how they're organized). UX is experience (how it feels to use). IA = architecture of a building (layout, rooms, hallways). UX = paint color, furniture, lighting. Good IA is invisible: users find what they need easily. Bad IA is felt: users get lost. IA is prerequisite for good UX.

How do I decide if content should be under 'Support' or 'Resources'?

Card sorting: show 20-30 content items (cards) to users, ask them to group into categories and name categories. Analyze: where do users put the item? If 80% say 'Support', use that. Don't decide alone; let users decide.

What's a taxonomy and how do I build one?

Taxonomy is a hierarchical classification (like biological taxonomy: Kingdom → Phylum → Class). For a knowledge base: Topics → Subtopics → Articles. Build it: analyze existing content, group by theme, name groups, create hierarchy. Validate with tree testing (users navigate mock hierarchy).

How do I handle items that belong in multiple categories?

Use tags or faceted navigation. Example: article 'AWS Billing' could be in Pricing OR AWS OR Cloud. Don't force one-category-only; let users filter by multiple tags. Faceted search: filter by technology + use case + difficulty level.

What's tree testing and when should I do it?

Tree testing is validating navigation structure before building it. Show users a text-only hierarchy (no design). Ask: 'Find [X task].' Users navigate the tree; you measure success rate (found it?), efficiency (how many clicks?). Iterate tree based on feedback before building UI.

How does IA affect SEO?

IA determines URL structure, internal linking, content clustering. Flat, clear IA = better crawlability. Related content linked together = stronger semantic signals. Hierarchical categories = keyword-rich breadcrumbs. Good IA is good for SEO.