Mobile App | Research, Strategy, UX/UI

Homeowner App
for Managing Thermostats Remotely

Scope: 6-week long design sprint focused on designing
the new proposed features for the new MVP Launch

My Role: UX Researcher & UX Designer

Client: HVAC Company

The Challenge

A previous design team had already designed initial MVP core features. My role was to design and validate the additional prioritized features needed for the MVP release.

Business Goals & Intented Outcomes

+ Design identified features for homeowners managing their thermostat to best support their home comfort

+ Validate hypothesized features and values being added to the new homeowner app experience

+ Gather feedback and insights into current processes for how homeowners manage their system for future feature planning

Methods Used

Usability Testing, Prototyping, UX/UI Design

Key Research Questions for Design Sprint

+ How is the current experience for homeowners when managing their thermostats remotely?
+ Are these new hypothesized MVP feature additions meeting the needs of our homeowners?
+ Are the new features understandable and easy to use?

Solution Overview

The new features added to the design sprint focused on giving Homeowners more data and options to manage their thermostat remotely, with the ability to schedule maintenance appointments and contact help directly in the app.
New Registration Process

To make it even easier for Homeowners to connect their thermostat for remote management, we streamlines the registration process in the app onboarding.

In-App Alerts

Homeowners receive alerts when there's an issue with their thermostat. The alerts make it easy to take action if desired.

Schedule or Contact a Dealer About an Alert

The ability to schedule an appointment or directly contact a dealer within the app in order to get help with an alert.

View Thermostat Operating Information

Homeowners can now learn new detail about their thermostat's energy consumption and operating status. This helps them make decisions about their thermostat's usage and maintenance.

Process Overview

Where I joined the project

Development team takes over

Market Research &
Product Definition


Design Phase 1




Development Handoff and Implementation

Market Research, Requirement Gathering and Feature Prioritization

The team took an agile approach to designing the app functionality using design sprints

Designing remaining features needed for MVP release

1:1 Semi-structured user-testing sessions to validate features

Refined prototyped features based on findings from test sessions

Initial MVP
Feature Sprints

Final MVP
Feature Sprint


Previous Product + Design Team

Refine Final
MVP Designs


Design & Prototype Features

I focused on designing and testing 4 main feature areas based on previous feature prioritization work completed before I joined.

1. Seamless Configuration
2. Service Scheduling with Alerts
3. Energy Usage + Spending
4. Monitoring Air Health

Screens I designed in collaboration with the UX Designer Manager on the project.


User Research Methods for Testing

9 moderated qualitative, 30-minute 1:1 user testing sessions


+ Better understanding of homeowners’ experience managing their thermostat remotely

+ Understand whether the newly designed features are clear and easy to understand for homeowners

+ Validate whether hypothesized features are useful and bring value to homeowners

Interview Structure

1. Background & Current Experience of the App

2. Provide open-ended tasks related to each of the 4 main feature areas

Stakeholder Involvement

+ Prototype review before testing

+ Interview protocol review: Testing goals and focus areas

Participant Profiles

+ Pre-determined list of users created by the client

+ 9 Homeowners who currently use the legacy app

High-level Findings

Seamless configuration was overall intuitive and easy to use.

Participants were hesitant about entering personal information because it felt unneeded for the purposes of managing their thermostat.

Service scheduling with alerts delighted participants.

Most participants mentioned they would rather self-troubleshoot first, and were nervous the scheduling may not be accurate.

Monitoring Air Health was easy to understand but some participants didn’t see the value.

Some participants felt this information wasn’t useful for the app because it didn’t provide any actionable items or information to help manage their thermostat if air quality was poor.

Energy Usage + Spending was confusing to understand for most participants.

The data visualization and design of this feature wasn’t clear to many participants. Some participants stated comfort outweighs cost and therefore wouldn’t find value in this feature to prompt them to change their thermostat settings.

Legacy App: technological
issues is a major painpoint for Homeowners

App connection issues with the participants’ thermostat system are frequent, and cause the app to stop functioning. Some participants have sought other thermostat solutions as a result.

Legacy App: notification mistrust due to an overload of inaccurate and unhelpful alerts

Participants have experienced receiving an overwhelming number thermostat alerts and notifications that aren’t accurate or provide them any value. This deters them from using the application.

Next Steps After Testing Sessions

How I worked with the team

After doing a read out of findings, I worked with the product team to prioritize changes.

Changes to the 4 features were made based on the findings, and 6 new features were designed and added to the app, based on business decisions.

Key constraints we used to help prioritize changes:

+ Our Statement of Work (SOW)

+ Project & Contract Timeline

+ Quick Wins (High-impact, low-effort)


Final Design Iteration

Before & After Highlights Based on Findings

Changes to the 4 features were made made based on the findings, and 6 new features were designed to the app based on business decisions. Over 100 new screens were designed and handed over to the new development team.

Seamless Configuration



Simplified seamless integration flow in onboarding. Updated language of notifications that new users can opt-in to sharing their systems data if they want.

Seamless Configuration



Simplified seamless integration flow in onboarding. Updated language of notifications that new users can opt-in to sharing their systems data if they want.

Seamless Configuration



Simplified seamless integration flow in onboarding. Updated language of notifications that new users can opt-in to sharing their systems data if they want.

Seamless Configuration



Simplified seamless integration flow in onboarding. Updated language of notifications that new users can opt-in to sharing their systems data if they want.

Unique Challenges During the Design Sprint

Challenge 1: Designing the Prototype

Lack of Requirements: The client had a list of high-level features, but there was little information about the details.

Workaround & Key Takeaway

I leveraged best practices found in other apps to help information key interactions and feature design. I planned to evaluate overall effectiveness, clarity and ease of use in the usability study.

Challenge 2: Designing the Prototype

Previous MVP features had not been tested. After investigating the file, I noticed many UX gaps in the design.

Workaround & Key Takeaway

Unfortunately, changing the original features was out of scope for my work. I made sure to raise concerns to the Product Owner. This emphasized the importance of thoroughly designing original features before piling on new ones.

Challenge 3: Scoping Challenge

User testing and my analysis of the design revealed many feature gaps that the Product Owner wanted added to the design, but that we didn’t have time or budget to design.

Workaround & Key Takeaway

I created a backlog list of all the design changes potentially needed and used this to communicate with the Product Owner and team about what changes we were prioritizing. This allowed us to clearly communicate and prioritize the most critical changes given the constraints we had.

Business Impact

Quick Iterative designs were completed for this phase of work that give homeowners value

+ Gathered feedback on whether the new features were meeting homeowners’ needs

+ Provided recommendations, and completed iterative design changes to improve the overall value provided to homeowners in the short timeframe

Insights to help drive next phases of work to improve overall customer satisfaction & retention

+ Identified pain points in the current experience to ensure the business can mitigate this in the new app

+ Provided insights about what current homeowners find valuable, which the product team can use to drive decisions for future state priorities and feature roadmaps

Next steps recommendations to help guide the team in the next design sprint & future work

+ Conduct a usability study on the previous design work that wasn’t studied in this sprint

+ Investigate which critical and routine alerts homeowners receive and how we can make sure they only see understandable, actionable alerts

+ Conduct a usability study on additional updated and newly added features


What would I have done differently?

+ Usability study on initial MVP features already designed before adding additional features. Some of the initial features, including Homeowners setting temperature schedules for their homes, were not tested by the previous teams. Usability issues with these features are critical to catch before implementing the second found features.

+ Follow-up co-design workshop with Homeowners. and allow for more time to make design changes. There was limited time to ideate and iterated on potential solutions.

+ Stakeholder priority workshop before starting this phase of work. During the project the stakeholders had a laundry list of features they wanted to add, but didn't have a clear priority. The workshop could have level-set on the what and why is most important for this next phase.

What did I learn?

+ Qualitative user testing can provide valuable feedback to the business to help shape next steps of a product's roadmap. However, it's still important the organization takes this into consideration and has a broader strategy for prioritizing features.

+ The importance of level-setting on scope before, during and after testing session with stakeholders. Especially with stakeholders who are new to UX, it can be overwhelming if the design team is given full responsibility to make scoping decisions.

+ Users’ previous experience with a product can greatly impact future perceptions and attitudes towards the business.