Role: Senior UX & Product Designer
Industry: B2B SaaS · Energy Management · Enterprise
Scope: Product flows · Design system · Hardware management · Security flows · Product positioning · Testing
Collaboration: Product owners · Developers · Sales · Support · Business stakeholders
Focus: Turning a growing enterprise platform into a clearer, more scalable and easier-to-deliver product experience
Due to GDPR and contractual constraints, I cannot share production screens or detailed internal product visuals. This case study focuses on product logic, anonymised flows, design decisions, and outcomes. More detailed walkthroughs can be shared during interviews or under NDA.
Enmon is a B2B SaaS platform for energy management, financial control, and regulatory compliance. It helps organisations such as utilities, hospitals, and public institutions monitor energy consumption, manage costs, and meet legal and ESG requirements.
The platform operated in a complex environment where data privacy, auditability, and reliability were essential. At the same time, the product was growing quickly and needed to become easier to understand, easier to maintain, and more consistent across teams.
I worked as a Senior UX & Product Designer with end-to-end responsibility for the user experience across the platform.
My work covered core product flows, design system development, security-related journeys, hardware management, and product messaging. I worked closely with product owners, developers, sales, and support teams to turn business goals, technical constraints, and user needs into practical product decisions.
Different parts of the platform had been built at different times, by different teams, and with different rules.
The product worked, but it was becoming harder to navigate, maintain, and scale. Users struggled with complex hardware logic, manual data entry, and workflows that often required support or developer involvement.
At the same time, the company needed to strengthen security, meet growing enterprise expectations, and better explain the business value of the platform to decision-makers.
The website and early product touchpoints focused heavily on technical monitoring. They did not clearly explain why the platform mattered for financial control, compliance, or business decision-making.
I reworked the information structure and messaging around the outcomes enterprise customers care about most: cost control, risk reduction, compliance, and accountability.
This made the product easier to explain to non-technical stakeholders and helped sales conversations focus on business value rather than technical features.
The interface had grown across multiple libraries and legacy components. This created visual inconsistency and made collaboration between design and development slower than it needed to be.
I took ownership of the design system as shared product infrastructure. I introduced design tokens, clarified component rules, and created a more consistent structure for reusable patterns.
This improved consistency across the platform and made it easier for designers and developers to prototype, review, and deliver changes with fewer mismatches.
Hardware management was one of the most complex areas of the product. The existing setup was based on legacy concepts that were difficult for users to understand and often required developer support for basic configuration changes.
I redesigned the information architecture around a clearer model of manufacturer, model, and module. The new structure reflected real hardware logic while supporting both simpler and more advanced workflows.
The result was a more understandable experience for users and a stronger foundation for bulk actions and future product expansion.
Manual data entry produced errors and made it difficult to understand who changed what and when. This reduced trust in reporting and created additional correction work.
I redesigned the workflow with inline validation, clearer error states, and visible ownership of changes. I also introduced basic data-quality insights to help teams understand patterns over time.
This improved accountability, reduced avoidable mistakes, and gave users more confidence in the accuracy of the reports.
As security requirements increased, the platform needed to introduce two-factor authentication without creating unnecessary friction or support issues.
I designed the authentication experience around clarity and predictability, including edge cases such as expired codes, resending, validation, and error recovery.
The platform met higher security expectations while keeping the login experience understandable and stable for users.
More consistent product experience across features and teams
Faster design-to-development collaboration through a shared design system
Clearer hardware management with less dependency on developer support
Better validation and accountability in manual data entry workflows
Stronger security without sacrificing usability
Clearer product messaging for enterprise stakeholders and sales conversations
This work strengthened my ability to shape complex B2B products where UX, product decisions, technical constraints, and business priorities are closely connected.
It also taught me how much impact good product structure can have. Clear systems, clear ownership, and clear flows make a platform easier to use, easier to sell, and easier to scale.