Incident management platform.
Helping wind farm operators manage incidents faster and and stay compliant during critical incidents.
#OrstedMalaysia
*Some visuals and details have been modified to respect client confidentiality.
Overview
-
A platform that helps wind farm operators manage incidents efficiently by assessing issues remotely, taking initial actions, and forwarding unresolved cases to on-site technicians all while ensuring compliance with wholesale energy market regulations.​
Challenges
-
Understanding the underlying logic behind updating and publishing incidents, which required deep comprehension of the system’s workflow and data dependencies
-
Finding the right balance between automation and user flexibility, deciding how much of the process should be handled automatically by the system versus how much control should be left to the user.
Role
UX Designer
Project time
approx. 2 months
Platform
Desktop
User
Wind farm operator approx. 10-15 users
Goal
Simplify the incident management process to make it easier and faster for operators to handle complex incidents.
Why this matters:
- Reduce delays: Complex workflows slow down how quickly incidents are reported and resolved.
-
Ease onboarding: Simplified steps help new operators learn the system faster and reduce training time.
Understanding the problem
What's the problem?
The current platform allows wind farm operators to publish incident information to the public energy market. However, as incidents become more complex or extend over longer periods, the increasing data and workflow complexity go beyond what the existing design and user flow can effectively support, leading to user frustration.
To better understand the root causes of this frustration, I initiated discussions with both the lead wind farm operators and the head of department. Working closely with the lead operators, I mapped the current user journey and identified key pain points to uncover where the main challenges lie. With the head of department, the focus was on understanding the broader business goals.
​In this project, I focused on redesigning the user flow for publishing incident information to the public energy market platform.
Discovery - mapping current user journey and reviewing past incident
.jpg)
Based on the user journey, we can identify the key pain points and opportunities.
Key reasons:
-
Difficulty identifying the latest updates

When users first access the workspace, it’s not clear which information is most current, leading to confusion and inefficiency. -
Tasks misaligned with real actions

Current system created tasks for the users that many of which don’t reflect the actual steps users need to take in their workflows. This mismatch create confusion and slows down their decision making. -
Unintuitive information structure

The current layout presents too much information at once and doesn’t align with users’ mental models of how information should be organized. As a result, it’s harder for them to locate what matters most and act efficiently.
Opportunities:
-
Enhance the incident details page by prioritizing critical information to reduce cognitive load.
-
Improve navigation and ensure the design supports future scalability.
-
Integrate relevant external data sources to minimize the need for switching between multiple applications.
​
In this design phase, I reviewed past medium to complex incidents to better understand user behaviors and system workflows. I also involved developers early in the process, not only to gain a deeper understanding of the system logic, but also to exchange ideas and explore potential opportunities for improvement.​
Ideation - quick prototyping and feedback gathering
In this design phase, I had the opportunity to explore Figma Make, which allowed me to quickly build interactive prototypes and test design ideas early. I collaborated closely with both operators and developers throughout this process, operators provided valuable feedback on usability and workflow alignment, while developers offered insights into technical feasibility. This collaboration helped refine the prototype and ensure that the final design balanced user needs with system capabilities.
Design
During the design phase, I followed an iterative process of prototyping, feedback gathering, and refinement. I shared early design concepts with operators and developers to collect their input, then continuously improved the designs based on their feedback. This back-and-forth collaboration helped validate ideas, uncover usability issues early, and ensure the final design aligned with both user needs and technical constraints.
In the previous design, users had to view all past events as soon as they opened the incident details, even those no longer relevant to the current situation. In the new design, the interface focuses only on the active and relevant information, allowing users to concentrate on what truly matters and act more efficiently.
