HAVEN IAQ DASHBOARD REDESIGN

HAVEN IAQ ecosystem is complex

---

Key features for homeonwers:

• Real-time Monitoring: 24/7/365 insights into filtration, ventilation, humidity, and temperature.
• Alerts & Recommendations: Notifications when air quality thresholds are crossed and get actionable advice.
• Data & Scores: Home's IAQ status, including specific contaminant levels and an overall score, with data often integrating from devices like EcoQube for radon.
• Automation Management: A robust automation system that bring in fresh air or controls ventilation based on air quality events.
• Basic automation thresholds editing capabilities to accomodate for sensitivities and changing seasons.
• Support from HAVEN team and HVAC pros.

Key features for HVAC professionals:

• Installation of HAVEN devices linked to various equipment using templates of varying complexity and custom layouts.
• Alerts & Recommendations: Notifications when home onwer needs to be aware that concerning patterns are developing long-term.
• Data & reports: comprehensive IAQ reports that can be shared with home owners that help troubleshoot existing issues.
• Automation Management: allows to edit existing automation thresholds and settings without the need visit the customer.

INTRO

---

MY ROLE

---

I lead the project. Here's what I did:

Definition:

• Conducted user inverviews with the home owners to identify where the experience isn't the best and what we can improve on with the least effort.
• Interviewed HVAC professionals who install HAVEN system to hear their insights and wants.
• Gathered suggestions from team members who were willing to share.
• Conducted workshopt with the team.

Synthesizing the findings

• I created multiple affinity maps (homeonwers vs pros vs team members)
• Took the best ideas that were reasonable enough to implement gain vs investment-wise.
• Used AI LLM as an assistant to help with notes and some insights/patterns synthesis.

Hi-fidelity redesign, iteration and user testing loop

• Since the design system and patterns were already established I took advantage of that and moved towards creating and iterating on hi-fi prototypes
• Conducted user testing sessions mostly internally to verify design desiciions, iterating and repeating.
• In the final testing round the pros and homeonwers were involved again.
• Final iteration was completed after that.

Handoff support

• The handoff was underway while our new developer was still learning how things work, so it helped to feed him bits an pieces of the features that were finished in small chunks, without overwhelming him, and that game me time to work on the rest.

QA

• The team was small, so all of us were responsible for QA. I made sure to keep track of everyone's feedback and ensure the designs and the live product are updated.