infusing intelligence in oil extraction

Service:

UX/UI, Research, MVP

Client

Schlumberger, United States of America

Field:

Oil&Gas

Year:

2024

Project impact

frog and SLB partnered on an intensive 10-week sprint to define ICAP: a modern product vision for turning Intelligent Completion data into clearer, faster operational decisions.

The work moved from research to MVP definition and high-fidelity prototypes, translating a highly technical domain into a product strategy, navigation model, and realistic end-to-end experience.

User Interviews

20+

20+

20+

Deliverables

2

2

2

N of screens delivered

N of screens

N of screens

80+

80+

80+

What was blocking adoption

Intelligent Completion hardware could capture real-time well data, but the software experience was still making interpretation slow and fragmented. The opportunity was to turn raw measurements into actionable decisions for operators, engineers, and business stakeholders.

Research revealed four core blockers: outdated interface patterns, fragmented workflows, low usability, and limited support for modern decision-making. We translated those findings into a clearer information architecture, flowcharts, user templates, and two validated end-to-end prototypes.

Research revealed four core blockers: outdated interface patterns, fragmented workflows, low usability, and limited support for modern decision-making. We translated those findings into a clearer information architecture, flowcharts, user templates, and two validated end-to-end prototypes.

From insight to product vision

Designing for oil extraction meant entering a domain of high-stakes decisions, dense data, safety protocols, and shifting operational roles. The challenge was not to simplify the domain, but to make its complexity usable.

We ran two research tracks in parallel: stakeholder and user interviews to understand business and field needs, and a UX audit of the legacy tool to identify friction, missing patterns, and opportunities for modernization.

Instead of relying on static personas, we built a flexible user matrix around five macro-steps: set thresholds, monitor, inspect assets, make decisions, and take action. This connected user needs to measurable workflow moments.

Three primary POVs emerged: reservoir-focused users, field operators, and production-focused users. Cross-referencing these POVs with the journey map helped us isolate the two experience flows that best proved ICAP’s value.

What changed in the product

ICAP transformed the legacy WWA workflow into a modern decision platform. The experience introduced a three-level navigation model — field, well, and equipment — so users could move from overview to action without losing context.

The product also introduced interactive data visualization, custom analysis views, built-in calculations, and proactive monitoring. Instead of exporting data or interpreting static tables, users could investigate, calculate, and respond inside one platform.

What I learned

This project pushed me to design inside a highly technical, constraint-heavy domain. The strongest lesson was learning how to translate expert workflows into something structured, usable, and still credible to the people who rely on it daily.

It also reinforced the role of design as translation: absorbing unfamiliar terminology, questioning assumptions, and turning operational complexity into decisions people can understand and act on.

Reflections & Learnings

This project pushed me to design inside a highly technical, constraint-heavy domain. The strongest lesson was learning how to translate expert workflows into something structured, usable, and still credible to the people who rely on it daily.

It also reinforced the role of design as translation: absorbing unfamiliar terminology, questioning assumptions, and turning operational complexity into decisions people can understand and act on.

More works