Lead UX — Halliburton
Internal enterprise platform for managing and distributing geoscience data
Cover image coming soon
01 — Problem & Context
Halliburton's geoscience teams relied on scattered internal systems to find, request, and access critical data sets. There was no unified platform — engineers spent significant time locating data instead of using it.
The goal: design a centralized marketplace where teams can discover, preview, and request access to internal data products — with clear ownership, metadata, and governance built in.
02 — Process
1.0
Stakeholder Interviews
Mapped pain points across data producers, consumers, and governance teams.
Interview synthesis2.0
Information Architecture
Defined data taxonomy, navigation model, and search patterns.
IA documentation3.0
Wireframes & Flows
Core user journeys — browse, search, preview, request access, manage datasets.
Lo-fi prototype4.0
Usability Testing
Validated flows with internal users across multiple business units.
Usability report5.0
Hi-fi Design
Final screens following corporate design system with custom components.
Hi-fi prototype6.0
Hand-off
Developer specs, component documentation, interaction guidelines.
Figma handoff03 — UX Strategy
UX strategy is a long-term plan that connects user insights, product vision, and business objectives into a coherent direction for designing and improving the user experience.
| Vision | Provide a user-friendly means of accessing curated, trusted data, reports, models, and AI Agents that are a part of Halliburton's Data Ribbon. |
| Problem | Users cannot efficiently work with data because it is difficult to find, difficult to access, and not easy to compare across multiple sources. |
| Success looks like | Data engineers use the dashboard daily as the primary entry point to find, validate, request access, and consume data assets within minutes — not days or weeks. |
Data Scientist / Engineer
Browse data products, fast and relevant search, preview data, request & obtain access quickly.
Business User
Find existing reports (PBI, Tableau, Spotfire, Databricks) that answer questions from trusted data.
Data Product Owner
Manage data product info, approve/reject accesses, define level of access.
Data POD Lead
Oversee data products across teams, monitor quality and access patterns.
04 — UX Strategy
Phase 2 evolved the marketplace from a browsing tool into an intelligent, trust-driven data discovery platform powered by AI.
| Vision | Transform the Data Marketplace from a browsing tool into an intelligent, trust-driven data discovery platform powered by AI. |
| Problem | Users can find data but cannot judge if it's reliable, relevant, or safe to use. Discovery is manual, trust signals are absent, and social knowledge is invisible. |
| Success looks like | Engineers and business users describe what they need in plain language, receive ranked trusted results in seconds, and make access decisions confidently. |
| Phase 1 → 2 | Main page becomes Explore page (browse + filters, unchanged). New Main page = AI-powered Home page with large search bar + 6 personalized recommendation boxes. Intent-first entry point. |
05 — Wireframes
Lo-fi wireframes defined the core layout before any visual design decisions were made.
06 — Mockups
Final designs built on top of the corporate design system with custom marketplace components.
07 — Outcome
The Data Marketplace was delivered to Halliburton's internal engineering teams in 2026. The platform unified data discovery across the organization and introduced a governed access request workflow for the first time.
Specific metrics and adoption data are confidential under NDA.
08 — Reflection
What I'd do differently
Involve data governance stakeholders earlier in the process. Their requirements surfaced late and required reworking the access request flow mid-project.
What I learned
Enterprise data products need trust-building at every layer — from metadata quality to access transparency. Users won't adopt a tool if they can't trust the data inside it.