CASE STUDY 06 / IOT HEALTH DASHBOARD
BettAir
Turning office air-quality data into one score anyone can read
Read the case study
CENTRAL DESIGN QUESTION
How can raw air-quality readings make sense at a glance?
BettAir was a startup building a sensor that measures the air in an office: carbon dioxide, fine particles, humidity and noise. The raw numbers mean little to most people, yet the air affects everyone’s focus and wellbeing. At 22 Design I designed the dashboard that turns those readings into one score, two everyday questions and a few clear next steps. The sensor itself was still a prototype, so the design had to work before the product was finished.
MY ROLE
Product and UI designer at 22 Design, working directly with the startup’s team and presenting the flows to them and their developers.
SCOPE
Score model, information structure, the main dashboard, supporting screens and the mobile view.
DELIVERY
About a month of weekly design iterations. The client’s developers built the product on this design.
Designing for a product that was still being built
When the project started, the sensor existed only as a prototype. Nobody could say yet exactly which values it would report, how often, or how reliable they would be. That made it unusually hard to decide what the interface should show.
We met the client often and worked in weekly iterations for about a month. Each round tested one part of the idea against what the hardware was expected to deliver, and the next round built on what we had agreed.
Instead of waiting for final data, I designed the structure first: what people need to know, in what order, and where the detail lives. The exact values could change later without breaking the screens.
From raw readings to one score
The starting point was close to a technical monitor: a list of readings with units and limits. For an office worker, 1,240 ppm of carbon dioxide answers nothing. What they want to know is simpler: is the air good right now, and does it affect how I work?
I proposed a model in three layers. Each sensor reading is compared with a comfort range, for example carbon dioxide below 1,000 ppm, and turned into a value from 0 to 100. These values feed two everyday questions: can people focus, and is the room calm? The answers become the productivity and distraction levels, and together they make the BettAir score.
OPTION NOT TAKEN
Show every reading
Complete and accurate, but it asks people to interpret units and limits they have never learned.
SELECTED APPROACH
One score, detail on demand
The score answers the main question. The readings stay one click away.
The rules were deliberately simple and easy to change. I treated the model as a clear first version that the client could fine-tune once real measurements came in.
FIG 1 · SCORE MODEL · ILLUSTRATIVE VALUES
A dashboard built around one question
The dashboard reads from top to bottom like a short answer. A strip of daily scores shows the week at a glance. Below it, the BettAir score explains today in plain words, and the two levels say what it means for work.
See how today compares with the rest of the week
Read today’s score and what it means
Act on a goal or a tip, or open the details
The right-hand column turns data into small actions. Goals give the office something concrete to aim for, such as keeping carbon dioxide below 1,000 ppm. Daily tips suggest simple fixes, and achievements reward people who keep checking in.
I also kept the tone light. “The office is as calm as a meditation retreat” is easier to remember than a decibel value, and the number is still there for those who want it.
FIG 2 · THE MAIN DASHBOARD
Supporting screens and the mobile view
Dashboards
Today’s score and the week at a glance
Stats & Report
The trends behind every reading
Device management
LIVE
Each sensor, its room and status
Notifications
CO₂
Alerts when a value leaves its range
The navigation follows the same idea as the dashboard: the answer first, the evidence second. Stats & Report holds the history behind the score. Device management is for the people who install and look after the sensors. Notifications reach everyone else only when something needs attention.
The mobile view keeps the score and the two levels at the top, so a quick check between meetings gives the same answer as the desktop dashboard.
FIG 3 · ACHIEVEMENTS ON MOBILE
Achievements turn small habits into rewards, from checking the dashboard every day to keeping the office quiet.
Handing over a structure that could grow
At the end of each week I presented the updated flows to the client and their developers. Walking through the screens together kept design and development aligned while the hardware was still changing.
The developers built the product on this design. Its structure gave them a stable frame: the score, the two levels and the supporting screens could stay in place while the formulas behind them were refined.
DESIGN NOTE
The score model was a starting point, not a finished formula. Because its rules were simple, the client could recalibrate it with their own measurements without redesigning the interface.
06 · WHAT THE WORK ACHIEVED
How can raw air-quality readings make sense at a glance?
07 · TAKEAWAY
BettAir taught me to design the structure before the data is final. When a product is still changing, a clear order of questions holds the interface together. The numbers behind it can then be refined without starting again.
RESTART CASE STUDIES
Digital Citizenship Program
Helping Hungary’s program shape a clearer unemployment service