Interact City
Advanced web app used by municipalities to monitor and control streetlights. Various workflows for different user roles, from light level scheduling to energy monitoring, to fault investigation.
When
2018 to 2024
for Signify (formerly known as Philips Lighting)
My role
Design lead
Interaction design
User interviews
Usability testing
Learnings
Team planning & agility
Application architecture
Design systems
Web app design
Complexity management
Evolving a complex product
Over the years, Signify (previously known as Philips Lighting) has offered various city lighting solutions, each with unique software, hardware, and advantages.
With Interact City, our goal was to create a unified and modern interface that could integrate all these systems gracefully. This required us to understand each system well, recognizing common elements while preserving their unique features.
Aligning things could be challenging. For instance, changing workflows too much could confuse users accustomed to the older products. On top of that we gradually added features and support for new technologies, like sensors, solar-powered lights, or simplified commissioning.
In short, we needed to keep the design adaptable but complexity manageable.
↑ The quick comparison tool. When they troubleshoot a light, engineers like to start by checking its energy usage against another light. They can do this in just two clicks on the map; a usability improvement that came directly from chatting with a user.
↑ The inspection tool. Initially designed to display streetlight properties, this evolved as a more general helper tool that proved relevant to many workflows. It combines tree and tab views to organize function and information efficiently.
How we worked
Our main project contacts were PMs, software architects and customer-facing engineers. We were up to 3 contributing designers, plus a technical writer, while system experts (who are daily users of the product) informed our work with regular inputs and feedback.
We used the SAFe agile method. Every quarter I scheduled design work for the design team so as to stay ahead of R&D and make time for solid solutions. Over the years, I delivered most of the design evolutions – though the initial version came from an agency, and we built largely on Signify's design system.
I encouraged the team to join global meetings such as the Change Control Board (CCB), to connect with project members in diverse roles. Good for socializing, motivation, and demonstrating that designers don’t mind getting their hands dirty when needed.