CASE NARRATIVE — CONFIDENTIAL
Manufacturing Research Platform
Research and information architecture for a complex enterprise platform supporting cross-functional decision-making.
ROLE
Senior UX Researcher
SCOPE
Discovery to Architecture
METHODS
Stakeholder Interviews · User Research · Information Architecture · Prototype Testing
TIMELINE
Multi-phase discovery
Applied Principle: Research before assumptions.
THE CONTEXT
When technical complexity meets information fragmentation.
An enterprise platform needed to rethink how different specialized roles collaborated and interacted with complex technical information within a single system. I joined as Senior UX Researcher to lead the discovery, research, and information architecture process — from the first stakeholder conversation to the validated architecture proposal.
THE CHALLENGE
he core challenge wasn't designing screens—it was creating an information architecture that could support different user perspectives without compromising clarity. The goal was to help people with distinct workflows and mental models navigate the same product with confidence.
Due to confidentiality agreements, the client name, final product details, and specific business outcomes cannot be disclosed. This case describes the process and reasoning behind the UX decisions, not the product itself.
MY ROLE
What I was responsible for.
Leading the full discovery and research process
Defining the strategic insight that guided all subsequent decisions
Conducting interviews with specialized technical user profiles
Designing the information architecture proposal
Identifying workflow patterns and tool dependencies
Conducting prototype testing and validation with technical users
DISCOVERY
Research objectives & methodology.
Objective ↓ / Method →
Stakeholder Interviews
Scope & goals
Technical profiles
User Interviews
Pattern Analysis
Workflows
Prototype Testing
Validation
Understand the project scope, business objectives, and end-user profiles involved
01
Research how specialized technical users worked day-to-day beyond initial assumptions
02
Identify patterns in tool adoption and external integrations across technical disciplines
03
Translate findings into a strategic architectural insight that guided all design decisions
04
Validate the proposed information architecture with specialized technical users
05
● Directly addressed by this method
○ Not a primary source for this objective
Five objectives, four methods — mapped to show which method answered which question.
KEY FINDINGS
What the research revealed.
01
Users needed a natively integrative model
Users needed a system that unified multiple specialized workflows without relying on fragmented external tools — reducing context switching and information loss.
04
Context switching was the real usability problem
The core friction wasn't visual complexity—it was helping users navigate complex workflows efficiently.
02
Tool fragmentation created invisible friction
Dependency on external integrations created workflow gaps that users had normalized over time — making the friction invisible until research surfaced it.
05
No shared middle ground existed between expertise levels
Existing information structures served either technical specialists or business stakeholders — never both simultaneously. Every design decision forced a tradeoff.
03
The same data meant different things to different roles
Information that one discipline considered primary, another treated as secondary context. Shared data had fundamentally different meanings across expertise levels.
DESIGN PROCESS
How the discovery unfolded.
The process followed a structured 6-stage discovery framework — from initial scope definition to validated architecture. Due to confidentiality, visual artifacts and specific product details cannot be shared. This diagram represents the process and reasoning behind the UX decisions, not the product itself.
01
SCOPE
Scope Understanding
Initial discovery sessions to define the project's objectives, business goals, and the primary user groups involved.
02
RESEARCH
Research with Specialized Users
Interviews with diverse user profiles to understand their goals, workflows, and day-to-day challenges.
03
SYNTHESIS
Pattern Identification
Analysis of users' workflows, information needs, and the factors that influenced how they completed complex tasks.
04
INSIGHT
Strategic Insight
The core finding was that users needed a more cohesive experience—one that supported complex workflows without disrupting continuity. This insight became the guiding principle behind every design decision.
05
ARCHITECTURE
Information Architecture
Translation of research insights into an information architecture that balanced diverse user needs within a single, coherent experience.
06
VALIDATION
Validation
Interviews and prototype testing evaluated usability, clarity, and how effectively the proposed experience supported users' workflows.
Due to confidentiality agreements, visual artifacts and specific product details cannot be shared publicly. This framework represents the process and reasoning behind the UX decisions — not the product itself. Full methodology available through direct conversation.
DESIGN PRINCIPLES
The principles that shaped decisions.
◈
Integrate before adding
A natively integrative model reduces friction more effectively than adding features. Consolidation is a design decision.
○
Design for multiple expertise levels simultaneously
The architecture had to work for engineers and business stakeholders at the same time — without simplifying for one at the expense of the other.
◇
Reduce context switching
Every transition between tools is a cognitive cost. Minimizing context switches was as important as any interface decision.
◎
Make the process visible at every stage
Users needed to know where they were in the process at all times — visibility of state reduces anxiety and improves decision confidence.
OUTCOMES
What the research produced.
Architecture Proposal
The information architecture proposal was positively validated by the technical users involved and served as the foundation for the project's subsequent phases.
Strategic Alignment
The discovery process created a shared understanding between technical and business stakeholders — reducing friction in decision-making across disciplines.
Research Framework
The 6-stage discovery framework developed for this project became a reusable methodology for subsequent enterprise research initiatives.
Specific business outcomes and implementation results are under confidentiality agreement and cannot be shared publicly. Methodology and findings are available through direct conversation.
REFLECTION
What this project taught me.
"In highly specialized technical contexts, the real challenge is rarely visual. It's building an information model that different types of expertise can interpret and trust at the same time."
This project reinforced something that guides how I work: when you design for users with deep technical expertise, the risk isn't oversimplifying — it's imposing a structure that doesn't match how they actually think. The architecture had to earn trust from multiple disciplines simultaneously. That meant understanding not just what users needed to see, but how they needed to think about the same information from fundamentally different perspectives.