IBM

IBM

IA & UX Internship
IA & UX Internship
2026
2026

The project itself :

Project Overview

During my IBM internship, I worked across the product journey—from helping customers discover the right solution to creating clearer, more scalable product experiences.

Need → Discovery → Understanding → Action

I combined UX design, information architecture, and content strategy to analyze complex systems, prototype improvements, and turn findings into actionable recommendations.

Problem:

IBM’s large product ecosystem can make it difficult for customers to find the right solution, understand the offering, and know what to do next.


Internal teams also need scalable guidance to keep those experiences clear and consistent.

Goal:

Create clearer paths from customer need → product discovery → confident next step, while designing approaches that could scale across IBM.com.

My role:

Information Architect Intern
IBM.com Information Architecture & Web Strategy, Global Affairs


I combined UX strategy, information architecture, content design, and prototyping to turn complex product and content systems into clearer digital experiences.

Responsibilities:
  • Audited product discovery and content quality at scale

  • Identified UX and IA patterns across large content sets

  • Designed Figma concepts and scalable frameworks

  • Turned findings into stakeholder-ready recommendations

675 products audited · 132 removals approved · 516 pages assessed · 3 connected workstreams

One Experience, Three Projects


Rather than treating each project as an isolated deliverable, I looked at where it fit within the larger product journey.

Product Finder Audit & UX Strategy

Discover the right product


Can customers reach a relevant product path and understand why it matches what they need?

Anchor Link Navigation Strategy

Understand the product


Once customers arrive, does the product page give them enough information to evaluate the offering and choose a next step?

IBM.com Docs Site Review

Create clearer content experience


Do the teams creating those pages have guidance that is easy to find and apply?

PROJECT 1

Product Finder

Finding the friction

I began by auditing IBM Product Finder for findability, accuracy, and clarity—then used those findings to ask a broader UX question:


How much work is the customer doing to find the right product?

Auditing the Catalog

The Evidence

I reviewed 675 sitemap-listed products against Product Finder using their official product names.

The information to the left shows which products appeared as expected, did not appear in the search, or needed closer review because because naming or result mapping was unclear.


The distinction mattered. A missing result could point to indexing, tagging, naming, or source-data problems. A product could also technically be findable while still being difficult for a customer to recognize because its card title or metadata did not align clearly with the product page.


I also reviewed 140 Product Finder URLs that appeared to fall outside the intended product-overview scope. Following manager review, 132 were approved for removal, while eight were retained as valid exceptions.


The cleanup work gave me a clearer picture of the system underneath the interface: the customer experience depends on trustworthy inventory, consistent product identity and useful destinations.

Auditing the Catalog

The Evidence

I audited 675 sitemap-listed products against Product Finder, checking whether official product names returned accurate, recognizable results.


I also reviewed 140 URLs that appeared outside the intended product scope. After manager review, 132 were approved for removal and 8 were retained as valid exceptions.


The audit showed that product discovery depends on more than search—it requires trustworthy inventory, consistent naming, and clear destinations.

What the Audit Revealed

Four Patterns

Looking across inventory quality, cards, search, and filters surfaced four recurring opportunities.

amelia user journey map

Option A

Optimized Left Rail

A product-aware customer may already know the product name or family and want to move through the catalog quickly.


For this path, I created an optimized left rail Product Finder concept that keeps the familiar experience while strengthening:

  • Search guidance

  • Filter hierarchy

  • Visible active selections

  • Result counts and feedback

  • Buying-option visibility

  • Product-card clarity

Option B

Guided Discovery

A need-aware customer may know the problem they are trying to solve without knowing IBM's product terminology.


For this path, I developed a guided discovery concept that gives customers another way into the same catalog.


Customers can begin with what they already know, such as:

  • Business need

  • Product category

  • Industry

  • Buying option

  • Product family


The selected path narrows the product set while remaining visible so customers can understand why they are seeing those results. Direct search and Browse all products remain available for customers who prefer the traditional catalog experience.

Meta Card Optimizer

Product cards have limited space, so their metadata has to quickly communicate what the product is, what it helps customers do, and why it may be relevant.


I developed a metadata pattern that prioritized:

  1. Official customer-facing product name

  2. Concise value statement

  3. Decision-relevant tags


During IBM’s Pact AI Skills Day, I also built the Meta Card Optimizer in IBM Consulting Advantage. Using approved product information as source material, the tool generates a concise first draft of Product Finder card copy for human review.


Approved product information → AI-assisted draft → Human review → Card description


The approach gave writers a more repeatable starting point while keeping accuracy, usefulness, and IBM standards under human control.

PROJECT 2

Anchor Link Navigation (ALN) Strategy

Making a Large Migration Manageable

Finding the product is only the first step. The product page still needs to answer:


What is this?
What can it do?
How could I use it?
What should I do next?


For my second project, I evaluated single-page product experiences for migration into IBM’s Anchor Link Navigation model.


Instead of treating hundreds of pages as the same migration task, I created a readiness-based framework to assess existing content, identify gaps, and determine the level of work each page required.

ALN Mural Board

Evaluating Content Readiness

I evaluated 516 candidate single-page product URLs across nine readiness dimensions, using visible page content and linked public technical documentation.


The goal was to determine whether each page had enough source-backed content to support the proposed experience, identify gaps, and estimate the work required before migration.


The 516 URLs represented the working analysis set, not a final count of net-new migrations.

A Consistent Product Story

I defined a consistent four-part structure for migrated product pages: Overview, Features, Use Cases, and Next Steps.

Migration Waves

I grouped pages by readiness so the team could prioritize straightforward migrations while separating pages that needed deeper content work or review.

Sources & Workflow

I created a source hierarchy and repeatable workflow to guide content decisions from audit through publication.

PROJECT 3

IBM.com Docs Site Review

Stronger Guidance Behind the Experience

The third project focused on the internal guidance behind IBM.com.


I reviewed UX copywriting guidance for Product Marketing Managers and Web Strategists, looking for ways to make it easier to find, understand, and apply.


Rather than proposing a full documentation redesign, I focused on practical, targeted improvements that could better support the teams using it.

Bringing Guidance Closer to Work

The existing writing standards were strong, but the right guidance wasn’t always easy to find at the moment someone needed it.


My recommendations focused on three areas:

Find guidance faster

  • Link copy guidance from relevant page and metadata documentation

  • Add a quick IBM.com web-writing reference

  • Make Copy QA easier to discover


Evaluate copy consistently

  • Add a focused product-page checklist

  • Strengthen Leadspace messaging guidance

  • Address recurring questions with a concise FAQ


Make standards actionable

  • Use examples and non-examples

  • Reinforce plain language and scannability

  • Make expectations easier to apply during page creation


The recommendations preserved the existing documentation structure while making UX-writing guidance easier to find and use.

The project schematically :

Outcome

Product Finder

Created a documented foundation for catalog cleanup, with 132 removals approved, two UX directions, and a repeatable approach to improving product-card content.

ALN Strategy

Built a readiness framework that helped distinguish light-lift migrations from deeper content work and support phased planning across 516 candidate pages.

Documentation Review

Delivered focused recommendations to make UX-copy guidance easier to find, understand, and apply for PMMs and Web Strategists.

What I took from the work

This internship strengthened the way I approach large digital systems.

Start with the evidence

Audits are most valuable when they reveal patterns worth designing for.

Design the information underneath the interface


Search, filters, and cards work better when the underlying inventory, naming, and metadata are trustworthy.

Build for scale without losing judgment

Repeatable frameworks still need room for exceptions, uncertainty, and human review.

Make recommendations usable

The strongest strategy leaves behind clear artifacts, decision frameworks, and concrete next steps.

Portfolio Note


Some internal IBM materials, source data and implementation details are not included in this public case study. Where appropriate, internal artifacts should be cropped, simplified or recreated to show the design and strategic approach without exposing confidential information.

Let’s build a more accessible, human-centered digital future together.

To get in touch :

Contact Me

Follow me on:

Click to copy :

hello@juliemaymcmullen.com

Crafted at odd hours with a high-caffeine intake. Likely to be pixel-pushed and tweaked again tomorrow.

Let’s build a more accessible, human-centered digital future together.

To get in touch :

Contact Me

Follow me on:

Click to copy :

hello@juliemaymcmullen.com

Crafted at odd hours with a high-caffeine intake. Likely to be pixel-pushed and tweaked again tomorrow.

Let’s build a more accessible, human-centered digital future together.

To get in touch :

Contact Me

Follow me on:

Click to copy :

hello@juliemaymcmullen.com

Crafted at odd hours with a high-caffeine intake.

Likely to be pixel-pushed and tweaked again tomorrow.

Let’s build a more accessible, human-centered digital future together.

To get in touch :

Contact Me

Follow me on:

Click to copy :

hello@juliemaymcmullen.com

Crafted at odd hours with a high-caffeine intake.

Likely to be pixel-pushed and tweaked again tomorrow.