Back To Top

Hiring a Healthcare IA Consultant? Ask These 9 Questions First

Summary:

  • Information architecture isn’t a web design deliverable — it’s a content decision about what exists, how it’s grouped, and what it’s called.
  • Health systems that structure content around patient search behavior, service line overlap, and location strategy are better positioned for both patient navigation and AI-driven discovery.
  • Content, SEO, and web design teams can’t hand a sitemap down the line in sequence. They need to decide on the structure together, content first.

You’ve got a massive website project on the horizon, a timeline that’s tighter than you’d like, and a pile of stakeholders with opinions. Now you need to find an information architecture (IA) consultant who can organize your multi-service line health system website so that patients can actually navigate it.

Information architecture is a content job, not a web design job. What content exists, how it’s grouped, what it’s called, and which page a patient lands on when they’re scared and searching at 11 p.m. — those are content decisions.

Content and patient search data shape the IA, and the design team builds something beautiful around it. Flip that order, and you spend the project squeezing content into a template built for looks, not for how patients search or what AI engines can cite.

How we chose these questions for healthcare IA partner evaluation

We’ve participated in dozens of major hospital website rewrites at Aha Media Group, auditing thousands of pages and creating content to populate brand-new websites. We approach IA from the content side, where the structural decisions get made.

So these questions target the challenges of multi-service line environments — competing stakeholder priorities, provider directories, location-based content, and the politics of a health system merger.

Example IA or visual sitemap for hospital service line.

1. How many multi-service line health system websites have you structured?

Start with experience. A regional hospital with 5 service lines is different from a 20-hospital system with 50+ specialties, multiple physician groups, and branded centers of excellence.

Ask for specific project counts and complexity indicators — the number of pages managed, service lines organized, and locations folded into a single IA structure.

Watch out for vague answers like “we work with healthcare clients.” Push for specifics about enterprise-level health system projects, not just smaller hospital websites.

To create an IA for a complex health system, you need to understand how service lines relate to each other, where patients enter the site, and how to organize content that serves both consumers and referring physicians.

2. How do you handle service line overlap and competing priorities?

If you’ve worked at a health system, you know this one well. Cardiology wants top billing. Oncology believes their service line should be the homepage hero. Primary care argues they’re the front door to everything else. And everyone has data to back it up.

You want a consultant who names this tension out loud and has a process for working through it. Listen for stakeholder alignment sessions, decision frameworks, and prioritization built on patient data.

This is where healthcare experience shows. Consultants who’ve worked with health systems understand the political landscape. Those who haven’t may promise a clean, logical IA without acknowledging the organizational realities that will complicate it.

3. What’s your approach to patient journey mapping for healthcare?

Patient journey mapping in healthcare is different from customer journey mapping in other industries. Patients arrive at your site with varying levels of health literacy, different emotional states, and search patterns that change based on urgency.

You want a process that accounts for multiple entry points (search engines, physician referrals, internal links, social media) and different intents — researching symptoms, comparing providers, booking appointments.

Strong answers reference real data — search analytics, heatmaps, user surveys, competitor research. Weak answers rely on assumptions about how patients “should” navigate a healthcare site.

This is the question that shows whether content is driving the structure. A newly diagnosed patient needs different words and reading level than a caregiver comparing surgeons. Figuring that out is content work, and it’s what tells your design team where the flow should go — so the wireframes they build are both gorgeous and effective.

4. How do you balance stakeholder input with user data?

Stakeholders have strong opinions about how the website should be organized. Sometimes those opinions align with user data. Sometimes they don’t.

Ask what happens when stakeholder preferences and user behavior conflict. A good answer includes a real framework, plus a description of how they present data to stakeholders and run the conversation about tradeoffs.

At Aha Media, we call this framework the decision triangle. Every content decision should balance data, internal politics, and common sense. All 3 matter, and none should dominate completely.

Decision triangle showing how to make decisions in a hospital marketing team using a balance of data, politics, and common sense.

A consultant who always defers to stakeholders won’t build a site that serves patients well. A consultant who ignores stakeholder input won’t survive the approval process. Find someone who can navigate between both.

5. What’s your process for content auditing at scale?

Enterprise health system websites often have thousands of pages, many of them outdated, duplicated, or orphaned from the main navigation. Before restructuring the IA, understand what you’re working with.

Ask how they inventory and evaluate existing content — including their tools, categorization method, and process for deciding which pages to keep, rewrite, merge, or sunset.

Strong consultants will describe a process that goes beyond spreadsheets. It should involve content-scoring criteria, stakeholder review workflows, and timelines for decision-making across thousands of pages. Healthcare content at scale takes specific expertise.

See our approach to content audits for website redesigns.

6. How do you structure location-based content for multi-site systems?

Multi-site health systems run into the same fundamental IA question. How do you organize content around locations while still promoting systemwide service lines, providers, and brand messaging?

You want someone who’s lived in the tension between regional identity and system-level consistency. Ask how they handle location pages, regional service line content, and provider directory integration across sites.

Listen for awareness of the usual headaches — duplicate content across locations, services offered at some facilities but not others, and navigation that works both for patients with a preferred location and those without.

A consultant with health system experience will have opinions about hub-and-spoke models, regional microsites, and when to flatten the architecture versus when to maintain location-specific depth.

If your system grew by acquisition, this question gets bigger fast. You need someone who can help you sort through your options.

7. What’s your experience with CMS migrations in healthcare?

Information architecture work often happens alongside a CMS migration. The 2 projects are deeply connected. A consultant who understands that connection will create an IA that you can implement smoothly in your new platform.

Ask for direct experience migrating healthcare content to common enterprise CMS platforms. And get specifics on how they work with technical teams to keep the IA buildable inside the platform’s constraints.

Strong consultants will ask you questions about your planned CMS, your technical team’s capabilities, and any platform-specific features (like physician directory integrations) that will affect the IA.

This question also helps you assess whether the consultant can work effectively with your other vendors. Website projects involve multiple partners, and the IA consultant needs to collaborate with web design, development, and content teams.

8. How do you measure success post-launch?

An information architecture project doesn’t end at launch. The real test is whether patients can find what they need and whether the site meets your business objectives.

You want a consultant who thinks past deliverables to outcomes. Ask which metrics they’d recommend for healthcare IA success and how they’d track them over time.

Good metrics for healthcare IA include task completion rates for key user journeys (finding a doctor, scheduling appointments, locating services), search refinement rates, bounce rates on service line pages, and conversion metrics tied to your organizational goals.

Watch out for consultants who only talk about page views or generic engagement metrics. Healthcare website success is about helping patients act, not just generating traffic.

9. How do you handle physician and provider directory architecture?

The find-a-doctor functionality is often the most-used feature on a health system website. It’s also one of the most complex IA challenges, requiring integration between provider data systems, appointment scheduling, and patient-facing search functionality.

Look for specific experience with physician directory architecture and the data challenges that come with it. Ask about their approach to specialty categorization, location filtering, and connecting providers to service line content.

Strong consultants will ask about your provider data source, your scheduling integration, and your current challenges with the directory. They’ll have opinions about how specialties are named and grouped, what belongs on a provider profile, and how to handle providers who work across multiple locations or specialties.

This is a litmus test for healthcare-specific expertise. The content makes a directory work — the specialty taxonomy, the condition-to-provider mapping, and the words patients type when they’re looking for care. The interface matters too, and that’s a job for your design and development partners. But if the taxonomy underneath is wrong, no interface will rescue it.

🚩Red flags when evaluating healthcare IA consultants

Warning signs to look out for during your evaluation process:

  • No healthcare-specific examples: If their portfolio is heavy on retail, SaaS, or finance but light on hospitals and health systems, they’ll face a learning curve on your project.
  • Oversimplified solutions: Healthcare IA is complex because healthcare is complex. Consultants who promise a clean, simple structure may not understand what they’re walking into.
  • No mention of stakeholder management: The politics of a health system website project are real. Consultants who don’t acknowledge this haven’t done enough enterprise healthcare work.
  • Generic UX jargon without healthcare context: Terms like “user-centered design” and “information scent” are fine, but ask how they apply specifically to healthcare scenarios.
  • Reluctance to discuss past challenges: Every IA consultant has projects that hit obstacles. If they only tell you success stories, they’re not being honest about the work.
  • No content thinking behind the sitemap: If the answer to “how do you build the sitemap” is a wireframe, ask who’s making the content decisions underneath it. Structure comes from labels, hierarchy, and patient intent. Good design teams want that answer as much as you do, because it’s what makes their wireframes work.

Learn more about the difference between IAs and sitemaps.

What to do with the answers

Take notes as you go and look for patterns across candidates. Pay attention to how they talk about healthcare, not just whether they’ve done it — the right partner will use your terminology, name your constraints, and ask questions that show they’re thinking about your situation. Bring in the team members who’ll work with them day to day because their read on collaboration style matters as much as the credentials.

Finding the right healthcare IA partner

The right IA consultant has done this work before, understands the complexity you’re facing, and can navigate both the content and political dimensions of a major website project. Use these 9 questions early to find that partner — before you’re paying someone to learn on your dime.

If you’re preparing for a hospital website redesign or content migration, Aha Media Group has served 12 of the top 20 academic medical centers on the U.S. News Honor Roll and participated in over 100 major hospital website rewrites. We do the content work — IA, content strategy, and the copy that fills it — and we work alongside your web design and development partners on the rest. Let’s talk about your project.

FAQs about website IAs

Information architecture (IA) is the structure and organization of content on a website. For healthcare sites, this includes how service lines, provider directories, locations, and patient resources are organized and connected. A good healthcare IA helps patients find relevant information quickly and supports organizational goals, like appointment scheduling and patient acquisition.

Timeline varies based on site size and complexity.

  • For a mid-sized health system with 500-2,000 pages, expect 3-6 months for discovery, content auditing, IA development, and stakeholder approval.
  • Enterprise systems with thousands of pages and multiple regions may need 6-12 months or longer, especially if the IA project is coupled with a CMS migration.

In practice, they’re the same job. Website content strategy decides what content to write, how it’s laid out on the page, and how it’s positioned to be genuinely useful to patients and legible to search engines and AI.

Information architecture does that same thing at the site level — what exists, how it’s grouped, what it’s called. Split them across 2 vendors, and you usually end up with a sitemap that a writing team can’t use. If you do split the work, make sure the IA partner is a content shop and that both teams share one vision for the site.

Costs depend on project scope, site size, and consultant experience. Request detailed proposals that break down deliverables and phases so you can compare vendors accurately.

  • Discovery and IA development for a mid-sized health system typically land in the mid-five figures.
  • Enterprise-level projects with extensive content auditing and stakeholder facilitation may cost more.

Information architecture focuses on content organization, navigation structure, and how information is categorized and labeled. User experience (UX) encompasses IA plus visual design, interaction patterns, accessibility, and overall usability.

The distinction matters most when you’re hiring. Content teams decide what the experience is made of, and UX teams design how it feels to move through it. You want both, in that order. On enterprise healthcare sites, the structure question is almost always a content question — which specialties get their own section, what a service line page is called, where a newly diagnosed patient goes first. That’s why IA often belongs with your content partner, and your design firm builds around it.

We could talk about healthcare marketing all day. 

Join thousands of healthcare marketers, writers, and leaders who read our newsletter. We’ll keep it short, sweet, and packed with info you can use to sound smart (because you are).