PsodaJobs app
Will Donaldson
The product:
An app, designed towards the energy sector, where technicians can take job information from a fully planned and resourced project out into the field.
Project overview
Project duration:
2 months
The problem:
Currently projects are planned and resourced in isolated spreadsheets and drives, which are then passed manually from project managers to technicians out in the field.
Project overview
The goal:
To create a central hub of data so that project managers can plan and resource the project in Psoda (PPM tool), then that same information can be used in this new PsodaJobs app for technicians and project managers out in the field.
My role:
Lead UX designer and researcher.
Project overview
Responsibilities:
User research, wireframing, prototyping, usability testing and accessibility considerations.
Understanding
the user
User research: summary
The user research was mainly planned around a single persona who the app is targeting. This is the ‘crew boss’ or ‘technician’, who will be leading a team out in the field and using the app to receive and update information about the task.
Persona: Bill
Problem statement:
Bill is a crew boss who wants receive, edit and update information on upcoming jobs so that he can successfully complete and document the job process.
User journey map 1
User journey map 2
User journey map 3
Empathy map
User flow - examples
Starting
the design
Paper wireframes
By sketching multiple wireframe concepts, I could create different visualisations of the same screen for usability testing.
Digital wireframes
I transformed all my paper wireframes into digital wireframes in Figma. I started to add basic functionality such as opening menus and dropdowns on click/tap.
Clear and easy workflow button to log the start of work.
Quick and easy button to plug into Google Maps
Digital wireframes
I created multiple versions of the main screens to show different ways of presenting and using the information.
Clear planner of the days tasks and travel time.
Offline capable app with clear options for a reload when in wi-fi range.
Low-fidelity prototype - examples
Usability study: findings
Usability testing was held on the multiple different wireframe prototypes to find what aspects of each prototype users liked or disliked.
Round 1 findings - examples
Saving a job functionality not needed as it doesn’t provide that much value
1
How do we add a job on the fly?
2
Round 2 findings - examples
Missing a search on the notes/files screen
3
Star icon for saving a job was not clear
1
Need to accommodate a large number of files and attachments
2
Don’t need the big search bar if it searches the whole calendar
3
Refining
the design
Mockups
The large search bar on one of the original wireframes was moved into a small search icon in the user menu. This change came from feedback in the usability testing that the search would be used on more specific cases and not daily, so it is not needed on the main screen.
Before usability study
After usability study
Mockups
In the first set of wireframes, there was no way for a technician to add a job on the fly. For example, if something needed fixing urgently on that day. Based on that feedback an add (plus icon) button was added so that users can add a new task.
Before usability study
After usability study
High-fidelity mockups
High-fidelity mockups
High-fidelity mockups
Accessibility considerations
Included in app settings is an option to change the text size in the app. This is so that technicians can read important information if they have any sight difficulties. This also helps with increasing button sizes for when technicians are wearing big gloves.
A high contrast setting was also added to the app settings to help any users with visual impairments.
Animations (mainly on screen transitions) are able to be turned off for users that have trouble viewing motion.
1
2
3
Going forward
Takeaways
Impact:
This project had a positive impact on Psoda as the initial intended customer loved the designs and concept so much that they agreed to sign up with Psoda. Once this customer gets their PPM structures built into the Psoda tool, this jobs app can be developed for real-world use.
What I learned:
In this project, I have learnt that communication is key. There was a slight miscommunication through the channels early on in this project around certain requirements. By quickly speaking up, these issues were clarified early enough not to impact the project majorly.
Next steps
This prototype has been handed off to the development team to begin work on once other dependencies have been met.
I will continue to work closely with the development team once they start work on this app.
Continuing to get usability feedback from the technicians and other stakeholders will continue throughout the development process.
1
2
3
Let’s connect!
Insert a few sentences summarizing the next steps you would take with this project and why. Feel free to organize next steps in a bullet point list.
Thanks for reading my case study for this project!
I would love to say hi and connect on LinkedIn:
https://www.linkedin.com/in/will-donaldson-52193b116/