BP

Research & design of a wells documentation tool

Role

User Research / UX Design / UI Design

Platform

Desktop Web App
BP hero

Intro

BP is one of the world's largest multinational oil and gas companies and they have been in the process of digitising their processes. Falcon is a documentation app for internal use. It is predominantly used by reservoir engineers and geologists.

The problem

Users were working on Word and Excel documents for wells and sharing them via e-mail. They were starting to lose track of what the most up to date documents were and which ones needed to be reviewed and approved. Therefore they needed a web app designed where they could work on well documentation collaboratively and tracked.

macbook showing document screen

Dashboard for wells documents

From a business perspective, they wanted to highlight Priority Wells, which are a list of the top 10 wells which are in focus for the year.
Users wanted the ability to see My Wells which they have created and are working on.

From a business perspective, they wanted to highlight Priority Wells, which are a list of the top 10 wells which are in focus for the year. Users wanted the ability to see My Wells which they have created and are working on.

Dashboard list view showing field and well names and their status
Dashboard list view showing field and well names and their status
macbook showing list view for dashboard
macbook showing list view for dashboard
hover for list view showing progress of documents and approvals
hover for list view showing progress of documents and approvals

Card view to easily scan data for your wells

Users want to see what stage a document is in and the status of the documents for that well. This enables the design to show who created the well and updated it last. The dashboard design incorporates a search for the whole product and also to refine the wells area.

macbook showing card view

Stakeholder requirements gathering

I spoke with the stakeholders to find out what they require from the product in terms of viewing and editing documents. They’re the ones who requested this product to be built because of the issues they faced. So it was ideal to find out what they wanted in terms of features, for me to validate with other users.

  • We want to see the progress of documents and to be able to see history of changes and who has worked on a particular document.

    Stakeholder
  • We have decision points D1 to D11 tracking well progress, each requiring specific documents for users to complete.

    Stakeholder
  • We want the ability to send documents and whole decision points for review and approvals.

    Stakeholder
  • We want to assign roles for those reviewers and approvers.

    Stakeholder
  • We want a task list for users to check as a benchmark for what they need to work on and for other users to see the progress of those tasks.

    Stakeholder
  • If a user can’t complete a document or task, it can be deferred to the next decision point.

    Stakeholder
  • We want to see the progress of documents and to be able to see history of changes and who has worked on a particular document.

    Stakeholder
  • We have decision points D1 to D11 tracking well progress, each requiring specific documents for users to complete.

    Stakeholder
  • We want the ability to send documents and whole decision points for review and approvals.

    Stakeholder
  • We want to assign roles for those reviewers and approvers.

    Stakeholder
  • We want a task list for users to check as a benchmark for what they need to work on and for other users to see the progress of those tasks.

    Stakeholder
  • If a user can’t complete a document or task, it can be deferred to the next decision point.

    Stakeholder
  • We want to see the progress of documents and to be able to see history of changes and who has worked on a particular document.

    Stakeholder
  • We have decision points D1 to D11 tracking well progress, each requiring specific documents for users to complete.

    Stakeholder
  • We want the ability to send documents and whole decision points for review and approvals.

    Stakeholder
  • We want to assign roles for those reviewers and approvers.

    Stakeholder
  • We want a task list for users to check as a benchmark for what they need to work on and for other users to see the progress of those tasks.

    Stakeholder
  • If a user can’t complete a document or task, it can be deferred to the next decision point.

    Stakeholder
user avatars

User interviews

I spoke with these users to understand their current workflows and any current pain points they may face. I also wanted to find out if they ever had any ideas or discussions which may have come up in the past to improve their workflow.

This is also the perfect opportunity for me to find out if a user is neurodivergent. One user confirmed they are colour blind, so this meant I could test out the accessibility on colours when I got to the user testing stage on the clickable prototypes.

I spoke with these users to understand their current workflows and any current pain points they may face. I also wanted to find out if they ever had any ideas or discussions which may have come up in the past to improve their workflow.

This is also the perfect opportunity for me to find out if a user is neurodivergent. One user confirmed they are colour blind, so this meant I could test out the accessibility on colours when I got to the user testing stage on the clickable prototypes.

Participants

Senior Wells Engineer
Advisor for Subsurface Well Delivery
Senior Drilling Engineers
Senior Completions Engineers

  • What are the pain points in the current process?

    Question
  • Do you ever add attachments and if so what type?

    Question
  • What can we do to make your working process easier?

    Question
  • What is your working process outside of Falcon?

    Question
  • Is there anything we can do to improve your task based process?

    Question
  • How do you currently carry out the review and approvals process?

    Question
  • What are the pain points in the current process?

    Question
  • Do you ever add attachments and if so what type?

    Question
  • What can we do to make your working process easier?

    Question
  • What is your working process outside of Falcon?

    Question
  • Is there anything we can do to improve your task based process?

    Question
  • How do you currently carry out the review and approvals process?

    Question
  • What are the pain points in the current process?

    Question
  • Do you ever add attachments and if so what type?

    Question
  • What can we do to make your working process easier?

    Question
  • What is your working process outside of Falcon?

    Question
  • Is there anything we can do to improve your task based process?

    Question
  • How do you currently carry out the review and approvals process?

    Question

Decision points

The decision point screen tested well, and I refined it based on stakeholder feedback and user interviews. Documents are now displayed as cards with progress indicators, showing the last modifier and allowing users to defer them.

A sticky header tracks completed documents and tasks, while users can assign reviewer and approver roles and submit the decision point for approval. A history log records modifications for transparency, and search auto-refines document and task lists for efficiency.

screen showing decision point cards
screen showing decision point cards
screen showing decision point cards

Tasks

User interviews revealed that users wanted the ability to comment on tasks, add an assignee so that they get notified of a task they need to work on and defer or mark tasks as N/A. These features look to improve workflow efficiency, accountability and collaboration.

task modal on macbook screen
task modal on macbook screen

User flow

This is an example of one of the wells user flows for a logged in user, who already has their default region selected. I worked on the user flows to work out the most intuitive and easiest route for a user to complete documents, work collaboratively and send for reviews/approvals.

user flow showing happy journey
user flow showing happy journey

Document edit mode

The design tested well for easy text input. Based on user feedback, I added drag-and-drop attachments, a guidance button for complex sections, checkboxes to mark as N/A or complete, and a history view for tracking changes from themselves or other users.

screen showing document in edit mode
screen showing document in edit mode
screen showing document in edit mode

Commenting

Initially, I placed the comments feature next to input fields in edit mode, but user tests revealed a need for commenting on specific areas. As the users are used to using Mural, I redesigned it to allow free comments anywhere on the screen with easy tagging.

commenting version one
commenting version two

Notifications

Initially I had designed an actions panel for the dashboard. However it was becoming confusing what the difference between actions and tasks were, so the best way to inform a user was to introduce notifications.

Because we are sending documents for review, approvals and also by adding the commenting function, the notifications needed to be designed to show the users what they may have been tagged in or requested to do.

macbook showing document screen with notification panel

0+

0+

Total internal users

Up compared to 2,000 in 2022

0+

0+

Total internal users

Up compared to 2,000 in 2022

0+

0+

Average monthly active users

Falcon became a mandated tool by BP

0+

0+

Average monthly active users

Falcon became a mandated tool by BP

0K

0K

Total number of sessions

On average in a year

0K

0K

Total number of sessions

On average in a year

0+

0+

Total internal users

Up compared to 2,000 in 2022

0+

0+

Total internal users

Up compared to 2,000 in 2022

0+

0+

Average monthly active users

Falcon became a mandated tool by BP

0+

0+

Average monthly active users

Falcon became a mandated tool by BP

0K

0K

Total number of sessions

On average in a year

0K

0K

Total number of sessions

On average in a year

Next project

QVC

© 2025 - Design Forensics

© 2025 - Design Forensics

© 2025 - Design Forensics