Product Designer for an enterprise energy platform
At Enmon, I worked as a Senior UX and Product Designer responsible for the end to end user experience of a complex enterprise SaaS platform. I owned UX across the product ecosystem, including core workflows, design systems, security flows, and product positioning. I worked closely with product owners, developers, sales, and support teams, and acted as a bridge between business goals, technical constraints, and user needs. My role required long term ownership, system thinking, and decision making under strict regulatory and GDPR constraints.
Enmon is an enterprise SaaS platform focused on energy management, financial control, and regulatory compliance. The product is used by large organizations such as utilities, hospitals, and public institutions to monitor energy consumption, manage costs, and meet legal and ESG requirements. The platform operates in a highly regulated environment, where data privacy, auditability, and system reliability are critical.
The product was growing fast, but the experience was not ready for scale.
Different parts of the platform were built at different times, by different teams, and with different rules. This created an interface that worked, but was hard to understand, hard to maintain, and easy to break.
Users struggled with complex hardware logic, unreliable manual data entry, and workflows that required support or developer help. At the same time, the company needed to introduce stronger security and meet stricter enterprise and regulatory expectations.
Externally, the public website did not reflect the real value of the product. It explained what the system monitors, but not why it matters for financial control, compliance, and business decisions.
Problem: New users and decision makers did not understand what the product actually helps them achieve. The website and early product touchpoints described technical monitoring, but not the financial and legal consequences users cared about. This created confusion during demos and slowed down sales conversations.
Solution: I reworked the information structure and messaging to clearly explain how the platform supports financial control, cost optimisation, and regulatory compliance. I aligned the narrative with how enterprise customers think about risk, savings, and accountability, not technical features.
Outcome: The product became easier to explain to non-technical stakeholders, demos became more focused, and the website started to support sales instead of creating additional questions.
Problem: The product UI was inconsistent because it was built on multiple libraries and legacy components. Designers and developers worked with different assumptions, which caused frequent mismatches and slowed down delivery. Over time, this made the product harder to maintain and scale.
Solution: I took ownership of the design system and treated it as shared product infrastructure. I introduced design tokens, cleaned up component logic, and defined clear rules for how components should be designed, reused, and implemented.
Outcome: Visual consistency improved across the platform, design to development collaboration became smoother, and teams were able to prototype and ship changes faster with fewer errors.
Problem: Hardware management was one of the most complex parts of the platform. The existing structure was based on legacy concepts that were difficult to understand and forced users to rely on developers for simple configuration changes.
Solution: I redesigned the hardware information architecture and introduced a clear model based on manufacturer, model, and module. This structure reflected real world hardware logic and supported both simple and advanced user workflows.
Outcome: Hardware management became more understandable for users, support and developer dependency was reduced, and the system was prepared for bulk actions and future extensions.
Problem: Manual data entry workflows produced frequent mistakes and unreliable outputs. Users had little feedback while entering data, and there was no clear visibility into who changed what and when. This reduced trust in reports and required manual corrections.
Solution: I redesigned the workflow to guide users through data entry with inline validation, clear error messages, and visible ownership of changes. I also added basic insights to help teams understand data quality over time.
Outcome: Error rates decreased, accountability improved, and users gained higher confidence in the accuracy of reports generated by the system.
Problem: Security requirements increased over time, especially the need for two factor authentication. There was a real risk that stricter security would result in login issues, user frustration, and higher support volume.
Solution: I designed authentication flows with strong focus on clarity and predictability. I carefully handled edge cases such as expired codes, resending, and error states, and added trust communication to explain what was happening at each step.
Outcome: The platform met higher security standards while keeping the login experience stable and understandable, without a significant increase in support issues.
The platform became more consistent, scalable, and easier to operate. Product delivery improved due to a unified design system and clearer collaboration with development. Hardware management became understandable for power users and less dependent on developers. Security standards were raised without sacrificing usability. Data quality improved, reducing manual corrections and increasing trust in reports. The product became easier to explain, sell, and maintain across teams.
Due to GDPR and contractual constraints, production user interfaces cannot be publicly displayed. This case study focuses on system logic, anonymized flows, component specifications, and outcomes that demonstrate senior level UX ownership and decision making. Detailed walkthroughs can be shared during interviews or under NDA.