This project is private. I will share my process and not talk about the software details. Designs are blurred to keep Halliburton's ideas safe.
My role: UX Designer
Tasks include: Researching users, Planning user tasks and flows, Creating wireframes and prototypes, Testing usability, and Designing user interfaces
Tools used: Figma, Axure and Visio
The back story: Purpose of CDR or Chemical Disclosure Report
A standalone application that is compliant with the Emergency Planning and Community Right to Know enacted in 1986. This act was to raise public awareness and knowledge of the right-to-know provisions of hazardous and toxic chemicals at facilities.
In 2011 Halliburton came up with the CDR and the report generation capability currently resides in another system, the vision of CDR is to be standalone with minimal to no dependency which will also allow additions, updates, and deletion of material. The bigger goal is to remove the business risk of proprietary information available through a few keystrokes and clicks to competitors.
The problem
Users were using a dirty database with bad data to create reports:
New Materials weren’t being added to the database quickly had to wait for a manual add which may take months and when added information could be fat-thumbed with wrong information
The user not able to see who was the last person to make edits and the date when a job was edited/updated
Needed the ability to search and select job data
Users wanted an updated CDR application:
Ability to search for job edits and use a clean database to generate a report
Ability to search for materials and create new ones for the job
Ability to add more than one sales order number to a job (add/delete)
Ability to identify 3rd party Materials from Halliburton Materials
Discovery
I was working on creating a PE (Performance Enhancement) stand alone web-based software designed to have little dependencies on other main software, generate reports compliant to EPCRA and a more stream-lined work flow.
The software features the following: dashboards, customization per region, data importing, and in context launching of software.
I am the UX Design Lead on a multidisciplinary team that includes the Product Owner (Cementing Product Manager), Product Champion, Software Architect, Business Analyst, I.T Lead, and Development Leads from other software groups.
Software Development and Implementation is performed by onsite and offshore developers and QA teams.
The persona
The process
The user is made up of regional groups practicing different approaches to Job/data management. User Personas and Journey Maps were created separately for each region to understand the differences that define each global teams work flow.
Weekly meetings with core team members (Product Owner, Product Champion, Software Architect, Business Analyst and UX) served as the core process to gathering requirements for the Business Requirement Document and User Stories. These sessions were used to solution software needs and requirements whether they are business, technical or usability related.
First Iteration designs
Final Designs
Agile Design/Development
During the development phase, we attend daily scrums and weekly grooming sessions to gather updates from the team and discuss any issues that require attention or flag any blockers.
Prior to sprints, we perform grooming sessions to go over user stories. During these sessions I am able to refine wireframes prior to start of next sprint.
We provide functional documentation for both the development and QA teams. UX Functional documentation shows screen shots for wireframes/components for UI developers with input specs. Input specs provide detailed information on the page for onshore and off shore development and QA teams can understand the functionality of what needs to be built.
We maintained an Agile development process with UI development team. During sprints, I kept open communication with team to answer questions and make changes to designs if necessary.