An AI-powered platform to unify teams and streamline energy operations.
Client
LYTT
Role
Design Lead
Services
UI Design / Research & Insights / Prototyping
I led the end-to-end design of a real-time collaboration feature for BP’s engineering platform, focusing on improving how engineers share and interpret data.
Starting with a cross-functional MVP workshop, I aligned the team using JTBD, defined priorities via MoSCoW, and facilitated example mapping to surface risks. I mapped the user journey, collaborated on system architecture with engineers, and iterated on the UI to reduce cognitive load and support focused data interpretation.
Through targeted user research with BP engineers, I validated the new sharing functionality and uncovered a need for saved data views, later prioritised by the business.
Outcome:
The Beta release saw enthusiastic adoption, with engineers reporting faster workflows, reduced documentation effort, and improved peer collaboration, validating the design direction and setting the foundation for future enhancements.
To support BP engineers in resolving performance issues faster and more accurately, we set out to redesign the way they share and interpret fibre sensor data. The goal: enable real-time collaboration and reduce inefficiencies caused by fragmented communication and manual documentation.
BP’s engineering teams needed a smarter, more connected way to collaborate on data analysis. Key hurdles included:
Disconnected workflows across teams
Heavy reliance on external documentation
Delays in feedback loops during issue resolution and optimisation
Enable real-time collaboration: Introduce a shared project space where engineers can compare data, annotate, and interpret findings together.
Streamline feedback: Create in-app commenting and discussion features to reduce dependency on emails and offline reviews.
Increase efficiency: Reduce the need for external documentation by embedding key communication tools directly in the platform.
Establish a scalable foundation: Design with future enhancements in mind, including version control, role-based access, and more granular sharing.
I initiated a cross-functional MVP kick-off workshop to align the team on goals, summarising prior research and unpacking key Jobs to Be Done (JTBD). This ensured shared understanding of user pain points and business goals from the outset.
I facilitated a core MVP workshop, consolidating research insights, ideating features, and applying the MoSCoW framework to define priorities. This led to a clear MVP scope, supported by an example mapping exercise that surfaced technical and experience concerns early.
I created the MVP user flow, ran collaborative reviews, and translated it into actionable user stories and technical spikes for the PO and dev team. I then conducted a system design mapping session to align UX flows with backend architecture.
Throughout development, I led iterative design reviews with engineers and product leads. When we identified potential distractions in the UI, I facilitated workshops to reduce complexity and revalidate user flows. I also clarified key interaction states—such as annotation behaviours—through detailed tables in the final handoff.
I conducted 1:1 user interviews with BP engineers (Petroleum, Reservoir, and Petrophysicists), using Dovetail to extract insights. This not only validated our direction but also uncovered a new user need: saved views for fibre data interpretation—later prioritised for future development.
To support handoff and ensure implementation accuracy, the development team requested clarity on how annotation functionality should behave within the shared project experience. In response, I delivered a detailed table outlining all annotation states and their interactions. This documentation was integrated into the final production-ready design, streamlining development and reducing ambiguity during build.
We launched the new project-sharing feature in Beta via feature flag to a select group of BP engineers. Feedback was overwhelmingly positive. Engineers reported:
The success of the launch validated our design direction and proved that real-time collaboration directly enhanced performance engineering outcomes.
Additionally, through user research, I uncovered a previously unspoken but critical need: the ability to save and bookmark fibre data views for easier reference and pattern recognition. I built a business case using insights from interviews and observation, leading to prioritisation of this new functionality in the next product iteration.