Dashboard Design Process: From User Decisions to Tested UI
A beautiful dashboard is expensive when nobody can act on it. See ANODA’s process for decisions, data, filters and states users can trust.
ANODA connects energy customers and operators through clear project status, documents and device readings, so people can take the next step without another call for answers.
Energy products a household acts on, and an operator can run at scale.
Pairing and control for any connected device.
Energy & Smart Home Product Design
What energy data means to a home and to an operator.
Not included
Four gaps between energy data and the people who read it, and the design work for each.
A month of use shown with clear units, periods and comparisons.
Groups, statuses and failing devices recognisable at a glance, not found by search.
Location, schedule, status and history, with a whole building's settings set once.
A card on a phone and a table on a monitor, built from the same parts and rules.
You receive
Another chart will not answer a homeowner waiting for installation or an operator investigating a silent device. ANODA designs the project, document, reading and recovery states around the job. In heimWatt, that meant a customer portal for heat-pump and solar installations: project status, quotes and documents together, with a responsive frontend connected to the company’s HubSpot data.
It fits when customers need to understand an installation or their home’s energy, while operators need the context behind it. Begin with the journey that creates the most repeated questions or stalled work.
Thermostats, meters or sensors report, and people read the result.
A household wants one number; an operator wants every device.
Hundreds or thousands of devices, locations or buildings to watch.
Your team already knows what counts as an anomaly and who may change a setting.
A different starting point
Show us the installation status customers chase, the documents they cannot find or the readings operators cannot act on. We will map the first journey to fix and the screens, states and implementation scope it needs.
Energy projects run under one service at a time, and that proposal sets the scope and when you review each piece.
Tell us about the installations, homes, devices and operators, and the task people cannot finish without calling your team.
Message received.
Within 15 minutes, we’ll email you initial feedback and follow-up questions.
Ask for energy or smart-home work shown from both sides, not only a handsome thermostat. A partner worth hiring can show how consumption becomes something a household acts on, what an operator sees when a device fails, how a location with many devices stays readable, and how every state was written down for engineers. Also ask where their part ended, since design covers neither hardware nor metering.
Who uses what, household and operator flows with every device and data state, consumption and analytics views, a clickable prototype, UI on one design system, and specs your engineers build from. The number of roles, device types and platforms moves cost and time, as do redesigning while homes depend on the product and how much real data you can share. Your first service's proposal fixes both.
Householders and the people they share a home with, installers, operators and support teams, and the admins who set up buildings and locations. The workflows are reading consumption, comparing a month, setting temperatures and routines and switching to away mode, and on the operator side, grouping devices, watching status, handling a failing sensor and reading performance across many homes. Smart home app design starts from the room and the person in it; the operator platform starts from the fleet and the device that just went quiet.
In energy app design, the household app fits Mobile App Design; an operator platform in the browser fits Web App Design. Dashboard Design answers what a single screen of fleet data should say. Two products that must look like one fit Design Systems. An energy product still on the drawing board goes through UI/UX & Product Design; if the work is mostly pairing and controlling devices, IoT & Connected Apps is the better start.
They stay with your team and advisers; we design how those rules appear. That covers how a reading and an estimate are labelled, what a household sees about the data collected in its home, who may change a building's settings, and what stays visible when data is late. Nothing in our work certifies a tariff, a meter reading or your privacy notice. Hardware, firmware and device protocols are outside our work, and we do not promise savings — a clearer chart is not a lower bill.
Test homes or simulated devices on staging, a login for householder, installer and operator, and a product owner with the final say. The data rules as they stand — what counts as an anomaly, how comparisons are made — plus support tickets and failure logs. Talk to engineering early: the device cloud and how often readings arrive decide what the screens can promise.
heimWatt: a customer portal where homeowners follow their heat-pump or solar installation — its status, quotes and documents, in German and English — designed from scratch, with its frontend built by us on top of the company’s HubSpot. We designed neither the devices nor their firmware.
Yes. Homes and operators lean on energy products every day, so redesigns usually happen on a live system. We use your files and system if you have them, work with your designers and engineers, protect the habits households and operators already have, and all files are yours at the end.