About the project
MyEpiroc is a versatile platform created for Epiroc, a leader in the mining industry, available on desktop, iOS, and Android.
For Epiroc employees, it streamlines customer management, user accounts, technical modules, product promotions, and FAQs.
For customers, it provides real-time oversight of their equipment, enabling services, inspections, fault reporting, machine tracking, and efficient management of drilling and blasting operations.
MyEpiroc's landing page on desktop.
The app is available on Google Play Store and AppStore.
My role
I spent two and a half years as a tester and designer on the MyEpiroc project.
Initially, I worked as a co-designer alongside three others, but I quickly transitioned into the role of design lead within my team.
As a tester, I collaborated with two peers of similar experience, each responsible for quality mindset and testing outcomes within our respective teams. We also worked cross-team to exchange ideas, align efforts, and address shared challenges.
In the next section, I will outline the workflow and outcomes of my design and testing work for a module of the system called Help Center.
Image from Unsplash by Hal Gatewood
About the project
MyEpiroc is a versatile platform created for Epiroc, a leader in the mining industry, available on desktop, iOS, and Android.
For Epiroc employees, it streamlines customer management, user accounts, technical modules, product promotions, and FAQs.
For customers, it provides real-time oversight of their equipment, enabling services, inspections, fault reporting, machine tracking, and efficient management of drilling and blasting operations.
The app is available on Google Play Store and AppStore.
MyEpiroc's landing page on desktop.
Help Center
The Help Center was a newly introduced feature designed for both Epiroc employees and customers.
It served as a centralized hub where users could access support for MyEpiroc, its tools, integration systems, equipment manuals, and more—available in all supported languages.
Details about the design and development process, along with screenshots*, are provided below.
* Screenshots: No actual screenshots from our Miro board or development is included due to legal reasons. I have included similar screenshots found online instead. A few design screenshots exists.
Design & testing workflow
We began our research by interviewing reference customers and Epiroc back-office staff to gather insights into their needs and challenges. This approach helped us empathize with them and better understand their requirements & needs.
The data collected was both quantitative and qualitative. Using Miro, we organized and analyzed it, clustering metrics, defining user roles and personas, identifying pain points, and mapping user journeys and functions.
Using Miro, we collaborated to brainstorm potential solutions and address the challenges identified during our research.
Following our brainstorming sessions, I created a prototype, first on paper and then in Figma, to present and test with our reference customers and users. We refined it through several iterations until we achieved a solution that we felt worked.
The design featured two main components: a backend for Epiroc users to manage content—such as products, questions, media, links, styles, inline translations, and other resources—and a frontend portal where customers could easily access the help they needed.
We broke the design into User Story Maps and value-sliced it in Miro to prioritize tasks that delivered the most value with the least effort. Throughout this phase, we identified risks for each slice and maintained a quality-first mindset, helping the team to perform good testing before and during development.
The development team adopted Extreme Programming, working in short iterations with frequent testing, customer demos, and feedback. This approach allowed us to quickly validate whether we were on the right track and make necessary adjustments to the design, development, and testing.
The combination of a quality-first mindset and Extreme Programming minimized context switching, kept the team aligned, and significantly reduced the number of bugs, as most issues were identified early in the process.
Image from seannhicks.com
Throughout the process, we maintained close communication with users, continuously gathering their feedback and incorporating it into our design prototypes and development iterations.
We made frequent, small releases, ensuring users felt their feedback was valued and they remained involved throughout the process. During one particularly productive week, we completed 5 releases in 5 days, each delivering distinct value to different users, with no bugs* reported. We referred to this as our “perfect week.”
*Bugs were rarely reported during development or from production, though the absence of bugs doesn’t necessarily mean they don’t exist. It simply indicates that they are either few or difficult to identify. The number of bugs found also depends on the thoroughness of testing and the effort invested in it.
My role
I spent two and a half years as a tester and designer on the MyEpiroc project.
Initially, I worked as a co-designer alongside three others, but I quickly transitioned into the role of design lead within my team.
As a tester, I collaborated with two peers of similar experience, each responsible for quality mindset and testing outcomes within our respective teams. We also worked cross-team to exchange ideas, align efforts, and address shared challenges.
In the next section, I will outline the workflow and outcomes of my design and testing work for a module of the system called Help Center.
Image from Unsplash by Hal Gatewood
Help Center
The Help Center was a newly introduced feature designed for both Epiroc employees and customers.
It served as a centralized hub where users could access support for MyEpiroc, its tools, integration systems, equipment manuals, and more—available in all supported languages.
Details about the design and development process, along with screenshots*, are provided below.
* Screenshots: No actual screenshots from our Miro board or development is included due to legal reasons. I have included similar screenshots found online instead. A few design screenshots exists.
Design & Development workflow
We began our research by interviewing reference customers and Epiroc back-office staff to gather insights into their needs and challenges. This approach helped us empathize with them and better understand their requirements & needs.
The data collected was both quantitative and qualitative. Using Miro, we organized and analyzed it, clustering metrics, defining user roles and personas, identifying pain points, and mapping user journeys and functions.
Using Miro, we collaborated to brainstorm potential solutions and address the challenges identified during our research.
Following our brainstorming sessions, I created a prototype, first on paper and then in Figma, to present and test with our reference customers and users. We refined it through several iterations until we achieved a solution that we felt worked.
The design featured two main components: a backend for Epiroc users to manage content—such as products, questions, media, links, styles, inline translations, and other resources—and a frontend portal where customers could easily access the help they needed.
We broke the design into User Story Maps and value-sliced it in Miro to prioritize tasks that delivered the most value with the least effort. Throughout this phase, we identified risks for each slice and maintained a quality-first mindset, helping the team to perform good testing before and during development.
The development team adopted Extreme Programming, working in short iterations with frequent testing, customer demos, and feedback. This approach allowed us to quickly validate whether we were on the right track and make necessary adjustments to the design, development, and testing.
The combination of a quality-first mindset and Extreme Programming minimized context switching, kept the team aligned, and significantly reduced the number of bugs, as most issues were identified early in the process.
Image from seannhicks.com
Throughout the process, we maintained close communication with users, continuously gathering their feedback and incorporating it into our design prototypes and development iterations.
We made frequent, small releases, ensuring users felt their feedback was valued and they remained involved throughout the process. During one particularly productive week, we completed 5 releases in 5 days, each delivering distinct value to different users, with no bugs* reported. We referred to this as our “perfect week.”
*Bugs were rarely reported during development or from production, though the absence of bugs doesn’t necessarily mean they don’t exist. It simply indicates that they are either few or difficult to identify. The number of bugs found also depends on the thoroughness of testing and the effort invested in it.