Back
Making hardware go further with software
Making hardware go further with software
Making hardware go further with software
Who are STRYDE?
Who are STRYDE?
STRYDE, a pioneer in seismic imaging technology, embarked on a mission to make this complex field accessible to a wider range of industries beyond oil and gas. My role in this innovative journey involved collaborating with a diverse range of software platforms (Android tablets, web, and desktop) and specialist engineers. Our goal was to modernise seismic imaging software, making it affordable, user-friendly, and efficient for our clients. While our products remain behind the scenes, I can share a compelling story about one of our remarkable challenges and its user-centric solution.
STRYDE, a pioneer in seismic imaging technology, embarked on a mission to make this complex field accessible to a wider range of industries beyond oil and gas. My role in this innovative journey involved collaborating with a diverse range of software platforms (Android tablets, web, and desktop) and specialist engineers. Our goal was to modernise seismic imaging software, making it affordable, user-friendly, and efficient for our clients. While our products remain behind the scenes, I can share a compelling story about one of our remarkable challenges and its user-centric solution.
STRYDE, a pioneer in seismic imaging technology, embarked on a mission to make this complex field accessible to a wider range of industries beyond oil and gas. My role in this innovative journey involved collaborating with a diverse range of software platforms (Android tablets, web, and desktop) and specialist engineers. Our goal was to modernise seismic imaging software, making it affordable, user-friendly, and efficient for our clients. While our products remain behind the scenes, I can share a compelling story about one of our remarkable challenges and its user-centric solution.
The Challenge
The Challenge
A node has 28 days of battery
A node has 28 days of battery
A node has 28 days of battery
Deployment takes approximately 7 days
Deployment takes approximately 7 days
Deployment takes approximately 7 days
Setting up explosives etc. also takes time
Setting up explosives etc. also takes time
Setting up explosives etc. also takes time
By the time deployment is complete I have 21 days before the first deployed node dies
By the time deployment is complete I have 21 days before the first deployed node dies
By the time deployment is complete I have 21 days before the first deployed node dies
We loose 1/3rd of the battery before we are ready to start shooting
We loose 1/3rd of the battery before we are ready to start shooting
We loose 1/3rd of the battery before we are ready to start shooting
How can we make the battery last longer without changing the hardware?
How can we make the battery last longer without changing the hardware?
How can we make the battery last longer without changing the hardware?
Discovery
The brief
The brief
The internal proposal from product and engineering was a delayed start and recording schedule where the node would only turn on based on this and therefore conserving battery.
This was a feature already used by our competitors.
Therefore my initial key objectives were to address this challenge effectively were:
Design the product modularly to accommodate firmware development stages.
Provide users with flexibility and clarity.
Define the limitations of the solution.
Ensure the security of data acquisition.
Efficiently manage different time zones.
The internal proposal from product and engineering was a delayed start and recording schedule where the node would only turn on based on this and therefore conserving battery.
This was a feature already used by our competitors.
Therefore my initial key objectives were to address this challenge effectively were:
Design the product modularly to accommodate firmware development stages.
Provide users with flexibility and clarity.
Define the limitations of the solution.
Ensure the security of data acquisition.
Efficiently manage different time zones.
The internal proposal from product and engineering was a delayed start and recording schedule where the node would only turn on based on this and therefore conserving battery.
This was a feature already used by our competitors.
Therefore my initial key objectives were to address this challenge effectively were:
Design the product modularly to accommodate firmware development stages.
Provide users with flexibility and clarity.
Define the limitations of the solution.
Ensure the security of data acquisition.
Efficiently manage different time zones.
My design process
Internal discovery workshop
Internal discovery workshop
The first session confirmed that whatever I propose so that we don’t touch the hardware is essentially MVP.
Our customers want real-time wireless communication.
One competitor offers that, but their nodes are more than 3x the price and more than 8x heavier. Not great when you have to carry hundreds of them through the desert or mountains.
But I did learn elements that will be really key to ensure the UI is clear and effective.
The first session confirmed that whatever I propose so that we don’t touch the hardware is essentially MVP.
Our customers want real-time wireless communication.
One competitor offers that, but their nodes are more than 3x the price and more than 8x heavier. Not great when you have to carry hundreds of them through the desert or mountains.
But I did learn elements that will be really key to ensure the UI is clear and effective.
The first session confirmed that whatever I propose so that we don’t touch the hardware is essentially MVP.
Our customers want real-time wireless communication.
One competitor offers that, but their nodes are more than 3x the price and more than 8x heavier. Not great when you have to carry hundreds of them through the desert or mountains.
But I did learn elements that will be really key to ensure the UI is clear and effective.
👑
Data is king
🎯
Accuracy is key
⏰
Time is the biggest concern
Wireframing
Wireframing
After further research and interviews with stakeholders I created a range of design concepts. These designs evolved from initial sketches and leveraged our Design System components, building upon prior investigations and taking hardware limitations into account. One concept that showed promise was a table-based data entry system, focusing on simplicity and user understanding.
After further research and interviews with stakeholders I created a range of design concepts. These designs evolved from initial sketches and leveraged our Design System components, building upon prior investigations and taking hardware limitations into account. One concept that showed promise was a table-based data entry system, focusing on simplicity and user understanding.
After further research and interviews with stakeholders I created a range of design concepts. These designs evolved from initial sketches and leveraged our Design System components, building upon prior investigations and taking hardware limitations into account. One concept that showed promise was a table-based data entry system, focusing on simplicity and user understanding.
Word Cloud
Using a word cloud I started to gather inspiration and ideas from various design resources using words such as timetables, schedules, flights, calendars etc.
Using a word cloud I started to gather inspiration and ideas from various design resources using words such as timetables, schedules, flights, calendars etc.
Using a word cloud I started to gather inspiration and ideas from various design resources using words such as timetables, schedules, flights, calendars etc.
Sketching
Sketching
After further research and interviews with stakeholders I created a range of design concepts. These designs evolved from initial sketches and leveraged our Design System components, building upon prior investigations and taking hardware limitations into account. I took some of these into Figma and one concept that showed promise was a table-based data entry system, focusing on simplicity and user understanding.
This was most favoured by engineers due to it’s simplicity to build and it’s common elements.
After further research and interviews with stakeholders I created a range of design concepts. These designs evolved from initial sketches and leveraged our Design System components, building upon prior investigations and taking hardware limitations into account. I took some of these into Figma and one concept that showed promise was a table-based data entry system, focusing on simplicity and user understanding.
This was most favoured by engineers due to it’s simplicity to build and it’s common elements.
After further research and interviews with stakeholders I created a range of design concepts. These designs evolved from initial sketches and leveraged our Design System components, building upon prior investigations and taking hardware limitations into account. I took some of these into Figma and one concept that showed promise was a table-based data entry system, focusing on simplicity and user understanding.
This was most favoured by engineers due to it’s simplicity to build and it’s common elements.
Testing & prototyping
Testing & prototyping
After validating the table concept with stakeholders and internal users of our software, I took this most popular (bottom right Figma) into prototyping and user testing.
After validating the table concept with stakeholders and internal users of our software, I took this most popular (bottom right Figma) into prototyping and user testing.
After validating the table concept with stakeholders and internal users of our software, I took this most popular (bottom right Figma) into prototyping and user testing.
2 prototypes
2 prototypes
with changes in between based on the initial feedback.
with changes in between based on the initial feedback.
with changes in between based on the initial feedback.
6 user tests
6 user tests
Across different roles at STRYDE who use the software and 2 externally with a local customer.
Across different roles at STRYDE who use the software and 2 externally with a local customer.
Across different roles at STRYDE who use the software and 2 externally with a local customer.
A clear failure
A clear failure
over night recording and time zones are an issue. It was not clear when when times were overlapping and people were worried they would confuse the set up times and local times.
over night recording, multiple recording slots in the day and time zones are an issue. It was not clear when when times were overlapping and people were worried they would confuse the set up times and local times.
over night recording, multiple recording slots in the day and time zones are an issue. It was not clear when when times were overlapping and people were worried they would confuse the set up times and local times.
Try again
I went back to the a different popular design and refined the concept with the knowledge of concerns around time zones, and continue with accuracy and people working internationally I learnt from the previous user testing.
To validate this concept, with some help, I created a JavaScript prototype and conducted internal testing by our in-field experts.
I went back to the a different popular design and refined the concept with the knowledge of concerns around time zones, and continue with accuracy and people working internationally I learnt from the previous user testing.
To validate this concept, with some help, I created a JavaScript prototype and conducted internal testing by our in-field experts.
I went back to the a different popular design and refined the concept with the knowledge of concerns around time zones, and continue with accuracy and people working internationally I learnt from the previous user testing.
To validate this concept, with some help, I created a JavaScript prototype and conducted internal testing by our in-field experts.
Prototype A: Enter your required recording hours
Prototype B: turn off non-recording hours
The solution that gained the most traction was a design that allowed users to turn off individual recording cells as displayed on the right.
This approach encouraged deliberate and careful selections ensuring that it:
The solution that gained the most traction was a design that allowed users to turn off individual recording cells as displayed on the right.
This approach encouraged deliberate and careful selections ensuring that it:
The solution that gained the most traction was a design that allowed users to turn off individual recording cells as displayed on the right.
This approach encouraged deliberate and careful selections ensuring that it:
Protected data
By defaulting to 24 hr recording
Recording times were clear
it facilitated the visualisation of schedules and simplified the set up of over night recording.
Saved time
A time zone would be set so it would be clear to all users.
A start and end date saved battery
A time zone would be set so it would be clear to all users.
and most essentially:
A start and end date saved battery
A time zone would be set so it would be clear to all users.
and most essentially:
A start and end date saved battery
Firmware Development and Limitations
Firmware Development and Limitations
During firmware development and testing, unforeseen limitations arose. As a result, we had to revert to a start time and duration schedule instead of the visually clear boxes we had refined. However, once the hardware is ready, the software can be built to provide unlimited flexibility for users, clear visual cues, and data protection simultaneously.
During firmware development and testing, unforeseen limitations arose. As a result, we had to revert to a start time and duration schedule instead of the visually clear boxes we had refined. However, once the hardware is ready, the software can be built to provide unlimited flexibility for users, clear visual cues, and data protection simultaneously.
During firmware development and testing, unforeseen limitations arose. As a result, we had to revert to a start time and duration schedule instead of the visually clear boxes we had refined. However, once the hardware is ready, the software can be built to provide unlimited flexibility for users, clear visual cues, and data protection simultaneously.
Work experience
My full work experience can be found on my LinkedIn profile or you can download my CV as a PDF here.
My full work experience can be found on my LinkedIn profile or you can download my CV as a PDF here.
My full work experience can be found on my LinkedIn profile or you can download my CV as a PDF here.
Kirstyn Potter
Lead Designer
Although Sarah is early in her career as a product designer, I have no doubt whatsoever that she will succeed. Her process knowledge, attention to users and requirements is exceptional and she will be an asset to anyone's team. It was an absolute pleasure to work together during my time at STRYDE and I wish her the best of luck for the future.
