Diseño Web y UX
Gransolar Connect
How do people actually work with solar data once the panels are already in place?
That question framed the work on Gransolar Connect.
The platform was designed for teams already operating in the solar energy space, people who deal with performance, incidents, and decisions on a daily basis.
The challenge was not introducing the domain.
It was supporting it.
Services:
• UX Strategy
• Experience Design
• Interface Design
Industry:
• Renewable Energy
• Solar
• Enterprise Software
The team:
• Product management
• Front-end and back-end development
• Marketing
• UX design (me)
• Business stakeholders
Year:
2020
What is Gransolar Connect
Gransolar works across the solar energy sector, supporting the development and operation of large-scale installations. Their teams rely on accurate information and clear systems to monitor performance and react when needed.
Gransolar Connect was conceived as an internal product to bring that information together in a single place.
Project overview
The project involved close collaboration with product managers, developers, and marketing. The application was never intended for public release; it was built as a private tool to support internal teams and selected users.
Because of that, expectations were high. Users were familiar with the domain and sensitive to anything that slowed them down or felt unclear. The platform needed to fit into existing workflows rather than replace them.
Scope of work
The work focused on how information was accessed, interpreted, and acted upon.
Sessions with the product and technical teams helped surface where people lost time, where decisions felt harder than they should, and where existing tools created friction. Design decisions were made alongside development, adjusting as constraints and real usage patterns became clearer.
Screens were structured around tasks rather than features. Labels and data groupings were reviewed repeatedly to reduce ambiguity. The goal was to make the platform predictable enough to be trusted, without flattening the complexity of the work itself.
Final result
The result was a private platform that supported daily operational work without drawing attention to itself.
Teams used it to review performance, understand trends, and identify issues without relying on multiple disconnected tools. Usage remained steady over time, particularly among users who had previously managed the same information through spreadsheets and manual reporting.
Internally, conversations shifted. Less time was spent locating data, more time discussing what it meant and what actions to take next. The tool became part of the workflow rather than an extra step.
What this project reinforced
Complex domains don’t need louder interfaces.
They need clearer ones.
This project highlighted how much impact small decisions have in internal tools, where users return every day and expectations are shaped by experience, not onboarding screens. Designing here meant listening carefully and adjusting continuously, often without visible gestures.
That kind of work doesn’t always show up in screenshots.
It shows up in how smoothly things run afterward.