Define Problem/ Goal Statement
Problem:
Documentation tasks take a long take to record and if an error occurs during documentation the additional process of correction may also prolong entry and accuracy of logs.

​​​​​​​

Goal:
To mitigate errors, add a quick and simple action to add data entry for GMP use.


Proposal/ HMW
How Might We:
How can gmp techs record performed tasks without compromising area cleanliness?
What can improve access for document reviewal?
Is there a way I can implement a visual reminder of tasks that need to be completed? 
Proposal:
I propose a documentation app that would automatically send data to a folder after verified compilation of task within the area where the task was completed.
Who might use this app?
Persona: James J.
Age: 28
Occupation: GMP Tech Lead
Location: Thousand Oaks, California
Behaviors
Creates nightly schedule in beginning of shift
Checks completion of tasks and records on nightly checklist at end of shift
Goals
Uses documents, tasktrackers and checklists to verify completion of tasks 
Ensures accuracy of data
Persona:Barbara B.
Age: 30
Occupation: GMP Cleaning Tech
Location: Thousand Oaks, California
Behaviors
Records completed tasks on forms in designated areas  
Sanitizes GMP clean rooms for production and frequency
Goals
Document error free and accurate data 
Quickly record tasks after completion before starting next task
Lets check out some of the competition
Competitive Analysis 
Success
The ability to share files
Googledocs
 Signatures are applied fast
Adobe Acrobat
Freehand, portable and able to correct
Paper checklist
Fail
Limited access in manufacturing areas
Not secure


Every computer has to have adobe installed
One location at a time and takes up space
User Flow
After a user flow and Journey I can start on some ideas using the Crazy 8s method.
Now I can move on and come up with a wireframe. 
After tree testing and some ideas on paper we can start building a clickable prototype for user testing. This early in the ideation process things can be changed around if something isnt working.
Task: App Navigation Usability
Hello my name is Alvaro. Today we are going to navigate through a prototype meant to document completed tasks. As You navigate through the app I will ask you to click on icons that may or may not be easy to recognize as links to the corresponding pages within the app. We are testing the Mobile App so it's encouraged for you to think out loud. This can be anything you find appealing, unpleasant, enjoyable, ect. 
Findings:
·Participant Struggled to find location scroll down   menu
·Profile,edit,and view icons are recognized to   navigate through app. 
·Participant had difficulty knowing which button   was meant for sharing documents.
A/B Testing 
A
B
Asked participant which navigation they preferred. 

Findings:
·Participant preferred simplified navigation than   additional quick buttons that would take up screen   space. B was there prefered option.
Based on participate feedback I will further simplify navigation.
Version 1
Version 1
Version 2
Version 2
Version 3
Version 3
Further Development of wireframe.
Usability Test
Task: Can you fill out scanned page, sign and submit your completed task?
Findings:
·While testing it became clear that the task asked   to perform was vague.
·Not all screens were updated which changed the   direction the participant finished the task. 
·Participant expressed that she felt a need for a       tutorial 
29MAY2024 Current Test findings
Participant thoughts out loud 
  1.Why are there no links like a table of content for the document
  2.Flipping through pages would take to long if I had to find one 
  3.I dont know how to find it
  4.Liked the look of the toggles 
  5.Don't know what the filter icon ment 
  6.Checkmark Success overlay helped to know when scan was done 
Next steps 
Finish adding a share page
Add graphics to login menu , add profile avatars 
Fix drop down menus to a functioning list 
Organize Design system 
Preform additional testing for Share page and share process 
Add prototype to portfolio along with testing and findings
Determine what features to keep in hamburger menu
Continue working on view documents page, improve searching for different documents with selected dates 
Flesh out Comment section and pop up window
What Ive learned while creating this Prototype
Simplicity is preferred in a mobile application rather than features.
Testing is important, write down everything a participant does, it can lead to insights.
Talk out loud Method helped participants use product but can also let moderators target problematic areas.
A short video of my progress so far

Still not a believer? Here is more to explore

Back to Top