Transforming fragmented operational data into a unified planning experience that helped operations teams identify blockers, coordinate dependencies, and confidently prioritize work execution.
<aside>
馃敀 NDA-protected work. All visuals are recreated portfolio artifacts. No proprietary data, real screenshots, internal system names, or sensitive operational labels are included.
</aside>
Recreated and anonymized planning experience. Proprietary data, internal system names, real screens, and operational labels have been removed.
Enterprise operations teams rely on numerous interconnected systems to coordinate field work. Before any work can begin, multiple operational dependencies, such as materials, approvals, engineering reviews, and scheduling, must all be completed.
However, this information was scattered across several enterprise applications, making it difficult for managers to understand which work items were truly ready to move forward.
I was asked to explore how we could simplify this process by designing an experience that provided operational teams with greater visibility into work readiness, blockers, and next actions.
| Company context | Enterprise energy / power delivery IT |
| Project | Work Execution Planning Experience |
| Role | Senior UX Designer |
| Responsibilities | User Research 路 Workflow Mapping 路 Interaction Design 路 AI-Assisted Design 路 High-Fidelity Prototyping 路 Engineering Collaboration |
| Team | Operational stakeholders 路 Technical leads 路 Engineering 路 Product 路 IT leadership |
| Status | First version released to operational users for initial evaluation |
The project originated from conversations between operational leaders and IT leadership. Teams responsible for planning and coordinating work were spending significant time navigating multiple enterprise systems just to determine why work was delayed.
The original request was to design a reporting interface. After early discovery, it became clear the real challenge was not reporting; it was operational visibility and decision-making.