ThermoPal

Google Nest redesign for shared workplaces

A cross-platform system that helps employees express comfort, coordinates shared-room decisions, and makes energy tradeoffs visible.

  • Shared-Space Coordination
  • Interaction Design
  • Visual Design & System

Overview

What is ThermoPal?

We redesigned the Nest mobile and device experience for shared offices, connecting personal temperature preferences with group coordination and energy-aware feedback.

The system captures personal preferences, supports shared temperature coordination, and makes energy tradeoffs visible through a Friendly & Cheerful design language.

Team & Role

UX Designer4-person team

My work focused on shaping core flows and feature decisions, refining the interaction and visual direction, and developing the final Style Guide.

Product strategy · Interaction · Design systemMobile app + Nest device

Timeline

10-week project · Design & delivery shown: Weeks 4–10
  1. Scope & alignmentW4–5
  2. Interaction & prototypingW5–6
  3. Review & visual refinementW6–8
  4. Design systemW8–9
  5. Final deliverablesW9–10

The starting point

The problem reaches beyond a temperature dial.

Employees want personal comfort. People sharing a room affect one another. An organization has energy goals. The interface has to communicate these relationships as well as the temperature itself.

01 / Connecting the system

Personal preferences become a shared action.

Users express their temperature preferences and connect them with meeting-room information. In the original design, the system averages the preferences of people booking a room and automatically adjusts its temperature.

Individual preferenceSeasonal personal temperature preference settings
Shared room stateShared room home screen with preferred temperature and group avatars
Personal inputs feed a shared room setting. The original design applies the group average automatically.Open an image for full-size detail ↗
The unresolved trade-off

An average is easy to calculate. That does not mean it is comfortable for everyone—or clear who has the right to override it.

02 / A cross-device system

Each device has a different job.

The mobile app carries preferences and room context. The thermostat communicates what the room is doing right now. Its far-view, close-view, adjustment, and heating states change the emphasis with the user’s task.

Original thermostat design: Up close

Bring the temperature into focus.

The close view puts the temperature at the center, with smaller supporting feedback.

Interactive guide to the original static interface states.

A larger temperature readout helps up close. A simpler visual signal works at a distance. During adjustment, feedback needs to connect the input, target, and system response.

03 / Design evolution

Give the temperature more visual priority.

The surviving homepage versions show a move from a large character and dense circular control toward a larger temperature readout, lighter control arc, smaller character, and a separate group-information card.

Earlier directionEarlier Nest home design with a prominent character and dense circular control
Later directionLater Nest home design with a larger temperature and separate group information
The visual hierarchy became more focused on the control task. Earlier and later versions from the original process record.Open an image for full-size detail ↗

The UI kit connects controls, feedback, and navigation across the mobile and device experiences. The patterns keep related states coherent across two device contexts.

Outcome + retrospective

Shared control needs explicit rules.

Looking back, I would clarify four distinct values: current temperature, target temperature, personal preference, and group average. Then I would define overrides, missing preferences, and disagreement before expanding the experience.

Why I would reconsider the incentive system

The original design used points, competition, and a pet whose condition could worsen outside an Eco range. This loss-based feedback is difficult to justify when an individual does not fully control a shared setting.

A next iteration should identify what each person can actually control, then test feedback that acknowledges different comfort needs. This is a retrospective assessment, not a change the original team implemented.

Continue exploringNotyAI makes a plan. You make it yours.← Back to all work