Overview
MIXIT is Grundfos’s all-in-one energy efficiency solution for hydronic heating systems.
I led the main UX work on migrating MIXIT into the GO platform – shifting from single-product logic to system-level design.
This required restructuring how the system is modelled, not just how it is presented, and establishing a shared language across UX, product, and engineering.
The product received the Designplus Award at Light + Building 2026 in the Sustainability & Future Energy+ category.
My contribution
Product Design
Product Discovery
UX Leadership
UX Team Coordination
Cross-functional Alignment
Research
The team
1 x Product Manager
1 x Technical Product Owner
1 x Lead Technical Project Manager
1 x Lead UX (me)
1 x Design Platform UX
2 x UX Support
2 x Scrum Masters
1 x MIXIT Complete Team
1 x Apps Team
1 x Test Team
+ Additional teams & Individuals
Year
2023 – 2026
Outcome
Structural impact
Shifted the GO platform from single-product logic to system-level design
Reduced ambiguity in configuration and operation flows, making correct decisions more obvious for installers and operators
Complexity reduction
Structured 128 scattered assumptions into actionable, prioritised hypotheses
Mapped and clarified ~1200 IA elements, exposing system-wide dependencies and gaps
Organisational impact
Established a shared language across UX, product, and engineering – aligning teams around common terms, definitions, and models
Process
Framing the system
Mapping the existing system across flows, information architecture, and user journeys to expose structural complexity and establish a shared foundation for decision-making.
→ This exposed inconsistencies and dependencies that prevented system-level design.
Understanding users and priorities
Grounding the work in real installer and operations needs through research and structuring scattered assumptions into actionable, prioritized hypotheses.
→ This clarified what to prioritize vs ignore
Reframing the problem
Aligning MIXIT’s system logic with the GO platform architecture to identify the structural gap between single-product design and system-level support.
→ This clarified what to prepare on platform before a migration was possible
Designing and validating solutions
Iterating on flows and concepts to define how the solution should evolve – balancing technical feasibility with usability across multiple design cycles.
→ This shaped the future iterations and solutions