HAL Best Practices Promoter, IA/UX Design Direction Challenge

Welcome to the "HAL Best Practices Promoter, IA/UX Design Direction Challenge."
This is not your average design challenge! Our customer is looking for your help to create an intuitive tool that will effectively manage Best Practice knowledge for a connected set of users. We are looking for fresh creative thinking to explore a new system.

This Design Direction challenge is part of Information Architecture and part UX Design. We are looking for you to visually present how an app could work. Consider user stories, background information, and exploration ideas. Use them to define the workflows and user experience for a new application.

The goal of this "Design Direction" challenge is NOT to create high-fidelity designs (The UI Design challenge will come next!). Focus on thinking through the problem and proposing direction and structure for the application. Your solution should excite and inspire our customers. The winning solution will become the guide for a UI Design challenge to follow. 

CHALLENGE TIMELINE

• Submission Start: Wednesday, Dec. 2, 2020, 11:00 AM ET
• Rolling Checkpoint Review: Sunday, Dec. 6, 2020, 09:00 AM ET (5 Potential Submissions in Rolling Checkpoint receive $100 each)
• Submission End: Wednesday, Dec. 9, 2020, 9:00 AM ET

CHALLENGE OBJECTIVES

• Focus on a solution. Visually describe and present the experience that the app will give our users.
• Clearly communicate your ideas. Show information architecture, workflows, interactions, and content samples.
• Create a storyboard-type presentation to convey your solution. This could include diagrams, flow charts, rough wireframes, sketches, and/or written descriptions of your concept.
• Submit your solution as a PDF document OR MarvelApp presentation that is easy to review and understand. You may use any tool to create your ideas and visuals. However, your submission must be a single PDF document or MarvelApp presentation. See Deliverables listed below.

OVERVIEW
Background:
HAL is a provider of oilfield services around the globe. They have access to a huge amount of data collected as “Best Practices” related to well drilling projects. This knowledge is critical to their employees for project safety and success. HAL is looking for a new system - Best Practices Promoter - to help key employees know and take advantage of this data in the easiest way possible.

Expected Solution:
The Best Practice Promoter should understand what the user needs. Knowledge must be:

• Easy to access
• Known at the right time
• Valuable and current

Project Goals:
How could Best Practices data be delivered, shared, and captured with the least effort and interruption?

• Explore potential use cases and workflows to take advantage of Best Practices data.
• Conceptualize how users could benefit from the dissemination of these Best Practices.
• Describe how users would need to share data and interact with one another
• Suggest an efficient method for each user to engage with such a tool.
• Utilize current technology, native device features, automatic functionality and latest trends to create a seamless user experience.

Best Practices Details:
Best Practices (BPs) will be sets of data that identify and describe a “Best Practice” related to any task that makes up a well drilling project. 

BP Types:

• Lessons Learned (captured knowledge)
• Reported Incidents
• Process Instructions
• Warnings of non-productive time

Assume there will be a collection of data that could be accessed:

• Automatically by a tool (for example an application when a  project plan is created)
• Manually by a user who is editing a BP
• Manually by a user who is capturing new BP data
• Automatically by a piece of equipment (for example a sensor that alerts to an incident or to non-productive time).
   

• Type (listed above)
• Title of BP
• Code(s) for project association
• Drilling Location
• Author
• Capture Date
• Occurrence Date
• Applicable Projects/Tasks
• Equipment Involved
• Short Description
• Approval Required (y/n)

AUDIENCE:
Users sharing Best Practice data:

• Project Manager
• Drilling Supervisor
• Service Providers (technicians in the field)

GLOSSARY

• BP = Best Practice data
• well = an excavation or structure created in the ground by digging, driving or drilling to access liquid resource
• project plan = the information that is used to guide project execution, including schedule and task details
• non-productive time = time that a task is on hold, employees not able to work
• KPI = key performance indicator

USER STORIES / EXPLORATION GUIDE
Below, we describe the users who will benefit from Best Practices knowledge and their basic job requirements. Consider each user and imagine the structure for an application that will allow them to utilize and share this knowledge in the best way possible.

1. Jay - Project Manager:
Typical work environment: indoor office

• Jay is a HAL Project Manager who plans drilling projects for many types of wells.
• When Jay is managing a project plan for constructing a well, he sees a schedule with tasks. The template he uses to create the project plan gathers BP data related to each phase and task in the project.
• Note: The creation and management of the project plan itself is NOT part of the Best Practice Promoter.
• Jay should be able to manage the BP information for each task, and customize which BPs are included in his plan. He has the ability to search the BP repository if he wants to add or replace any of the BPs included.
• Some tasks have BPs that require approval for inclusion. He is able to approve/decline any of these, based on the situation of his drilling project.
• The saved project plan will be accessed by other stakeholders. The BP information should be made available to the project’s Drilling Supervisor via Best Practice Promoter.
• Jay should be able to verify that the BPs are being seen and used by the Service Providers for his various projects. He will want to see this measurement reported as a KPI for his projects.

Challenge Exploration:

• What methods and devices make the most sense for Jay to interact with?
• What information might Jay need to double-check before saving the BPs with his project plan?
• How can Jay learn about valuable BP data that is new or changed?
• How do the appropriate pieces of information or events get communicated to the Drilling Supervisor?
• How can Jay see how consistently the Service Providers on his projects are following BPs? Which projects? Which BPs?

2. Dana - Drilling Supervisor:
Typical work environment: well location, in an onsite office or outside at the construction site

• Dana is the Drilling Supervisor assigned to a HAL well drilling project.
• To begin the workday, it helps Dana to have a view of the project plan and get a sense of the upcoming tasks for her project’s Service Providers.
• In more detail, Dana needs to see the tasks that her Service Providers will start or continue that day. For each upcoming task, the related Best Practices must be known by the individuals that will be involved. Dana must share the appropriate BPs with all of her Service Providers so they are prepared before beginning the work.
• Dana also knows that there could be BPs that are outdated or not useful for her specific project. Dana has the option to delete, add or modify the BPs associated with any given task. To do this, she must somehow access and search the repository of BPs. She may connect a different BP to a task. Or, she may capture a description for a new BP to add to the repository.
• At any point, Dana is able to select a BP for a task and rate its value.
• Dana should be able to verify that the BPs are being seen and used by the Service Providers.

Challenge Exploration:

• What methods and devices make the most sense for Dana to interact with?
• What information might Dana need to check before sending to a Service Provider?
• When should Dana be watching for a risk situation? At a specific time, are there additional steps she can take to mitigate risk to her project (safety, lack of productivity)?
• Are there valuable ways that Dana’s input to BPs can be seen by other stakeholders who plan future projects?
• How can Dana easily add to the value of BP data - ranking or voting?
• How can Dana see how often BPs are being followed by Service Providers? Who? Which BPs? For her project or in general for the industry?

3. Alex - Service Provider:
Typical work environment: well location, outside at the construction site

• Alex is a drill operator working in the field on a HAL project.
• When Alex arrives at his position for the day, he is notified that he will begin a new drilling operation that morning. He sees that he is scheduled to be working on this task for only half of his day, and then he will begin a second procedure at the same site.
• Alex is alerted that there are a few Best Practices important for him to know before he begins drilling. He is able to access this information immediately and then confirm that he is aware and understands how they impact his task.
• Alex is able to confirm when he begins the operation.
• When completing his task, Alex realizes that an important piece of safety advice is missing from the instructions he received. He is easily able to enter a few lines of text describing this tip, and adds it to the related Best Practices for this operation.
• Alex also is able to rate one of the other BPs he received as not valuable as it contained incorrect information. He rates another BP as very valuable as it saved him time in completing the task.
• Once Alex confirms that he has completed the operation, he is made aware of his next scheduled task. He again sees Best Practices that are important for him to know before beginning. He smoothly goes through the same steps to complete this task.

Challenge Exploration:

• What methods and devices make the most sense for Alex to interact with?
• When does Alex need to know this information? That hour? That day? The day before? The week prior?
• How could Alex be alerted to a dangerous situation as he moves into a risk area of the field?
• How would Alex confirm that he has followed the BP with his task?
• How can Alex easily add to the value of BP data - ranking or voting?
• How can Alex be encouraged to capture valuable ideas without having his day interrupted?
• What information could be automatically captured based on his location, schedule, user profile, other project plan information?

REQUIREMENTS

• The three user stories should shape the workflow and experience you are proposing as a solution. Each user and their needs should be addressed in your presentation.
• Recommend devices and views that would make the experience seamless for the user.
• Suggest the content that users would see and interact with at different points in their workflow.
• Focus on the problem: architecture, workflows, and "prototyping" your visual concept.
• Create diagrams, flow charts, rough wireframes, sketches, and/or written descriptions to make your solution understandable.

EXPLORATION SCORE
In terms of expectations, we would like to measure the concept against the following in the one to ten scales (ask the client to rate each of the parameters):

Creativity: 10
1: barely new ideas
10: a utopic product but with features that can be fully implemented

Aesthetics: 2
1: low-fidelity design, wireframe, or plain sketch
10: top-notch finished looking visual design

Exploration: 10
1: strictly follow an existing reference or production guideline
10: open to alternative workflows/features not listed here that would help the overall application

Branding: 1
1: don’t care at all about the branding just functionality
10: without a properly branded product there is no success

BRANDING GUIDELINES
- Not applicable to this challenge. UI Design with branding will be part of another challenge.

TARGET DEVICE
- Your solution should recommend device(s) for the users’ experience.

DELIVERABLES
Present your design for review in a single PDF file or MarvelApp presentation.
IMPORTANT to include in PDF or MarvelApp:

• Overview: Provide a brief overview of how your idea addresses our users’ needs.
• User Journey / Flow: workflows from the time app is open, what content each user sees, key actions needed, the options available to the user.
• Visualized User Experience: sketches, diagrams, wireframes, etc.
• Recommended Devices: representation of the devices being used
• Ideation Details: written notes to describe details of your idea.

Make sure to provide all source files (as usual: files created with Adobe PS, AI, XD, Sketch, Figma, etc.; Axure wireframes; scans of sketches) and submission files.

SUBMISSION AND SOURCE FILES
Submission File
Submit all files based on Challenge submission requirements stated above

Source File
All source files of all graphics created in either Adobe XD or Sketch or Figma and saved as an editable layer

Declaration File 
Declaration files document contains the following information:

• Stock Photos Name and Source Links from an allowed sources
• Stock Art/Icons Name and Source Links from an allowed sources
• Fonts Name and Source Links source from an allowed source
• MarvelApp share link for review

FINAL FIXES

• As part of the final fixes phase, you may be asked to modify content or user click paths