Enterprise software often forgets about the importance of listening to the user.
If you've ever worked at a large company, you can understand the frustration of being forced to use software that wasn't designed with you in mind. I strive to challenge the myth that oil & gas software has to be a dreadful experience. But as a design team of one (for now), I have to balance the need for thorough user feedback with the need to iterate quickly and constantly.
I can't do it alone - which is why our user feedback isn't sourced from one team. Although every team comes with their own set of biases, they also each bring unique insight to our users that I can learn from.
For example, the customer success team represents the direct line to our users. They ensure our users are happy by addressing any issues that might arise.
Sometimes we get feature requests for features that already exist. Questions begin reeling in my head -
- Why was the user unable to navigate to this feature?
- Did we educate the user on the existence of this feature?
- Is the copy used appropriate? Is an industry term needed here?
- Was the UI not apparent enough? Is it hidden in a dropdown? Does it need to be visible on load?
- Does the feature we thought addressed this request actually address the underlying issue for the user?
From here, I can begin addressing the issue in my next design iterations.
Join Our Team
If you believe in the importance of user feedback in enterprise design, then you'd probably be a good fit for our team. We are always looking for team members to help us transform oil and gas into a safer and more efficient industry.